KR20160073927A - The methods for controlling replacement of devices in M2M system and Apparatuses thereof - Google Patents

Abstract

The present invention relates to a machine to machine communication (M2M) technology and relates to a method and an apparatus for controlling replacement of devices in an M2M system. More specifically, the present invention relates to a technology for automatically controlling setting information according to replacement of devices by using profile information in an M2M system. In particular, the method for controlling replacement of devices, which is performed by a common service object, comprises: a receiving step of receiving registration request information from a first apparatus; an identity determining step of determining the presence or absence of profile information of a second apparatus identical or similar to profile information of the first apparatus based on the registration request information and pre-stored profile information of each apparatus; a registration method determination step of, when it is determined that the profile information of the second apparatus is present, determining a registration method of the first apparatus based on whether the apparatus registered in the common service object is terminated or information on a termination type; and a setting control step of, when the registration method of the first apparatus is determined to be a replacement registration, performing control to apply setting information of the second apparatus to the first apparatus.

Description

[0001] The present invention relates to a method and apparatus for controlling the replacement of a device in an M2M system,

The present invention relates to a M2M (Machine to Machine Communication) technology, and a method and apparatus for controlling the replacement of a device in an M2M system. More particularly, the present invention relates to a technology for automatically controlling setting information according to replacement of a device using profile information in an M2M system.

"Machine to Machine Communication" or MTC, "Machine Type Communication" or "Smart Device Communication" or "Machine oriented communication" or "Internet of Things" In which communication is performed without intervening in the network. Recently, oneM2M has been discussing M2M, but there are no technical elements to meet the architecture and requirements of oneM2M.

On the other hand, a plurality of devices registered and managed in the M2M system may need to be replaced / changed due to failure, aging, upgrade, and movement of each device. However, when the device is replaced or changed, there is a need to perform the setting procedure again for the newly registered device.

In addition, there is a problem in that the same setting as that of an existing device registered and used in the M2M system must be re-entered or reset to the replaced device.

SUMMARY OF THE INVENTION The present invention has been made in view of the above background and it is an object of the present invention to propose a specific method and apparatus for controlling the replacement of a device using profile information of the device in an M2M system.

In addition, the present invention proposes a specific method and apparatus that can automatically apply a setting of an existing device to a replaced device without an unnecessary reset operation when the device is replaced in the M2M system.

According to another aspect of the present invention, there is provided a method of controlling device replacement in a common service entity, the method comprising: receiving registration request information from a first device; When it is judged that there is profile information of the second device which is the same as or similar to the first device and whether the profile information of the second device exists, And a setting control step of controlling the setting information of the second device to be applied to the first device when the registration method of the first device is determined to be replacement registration . ≪ / RTI >

In addition, the present invention provides a common service entity for controlling device replacement, comprising: a receiving unit for receiving registration request information from a first device; and a second device, which is identical or similar to the first device, based on registration request information and pre- If it is determined that there is the profile information of the second device and the identity determiner for determining whether the device profile information exists, the registration of the first device is performed based on the information about the end and the end type of the device registered in the common service entity And a setting control unit for controlling the setting information of the second apparatus to be applied to the first apparatus when the registration method determining unit for determining the method and the registration method of the first apparatus are determined to be the replacement registration.

The present invention described above provides an effect of automatically controlling the replacement of the device using the profile information of the device in the M2M system.

In addition, when the device is replaced in the M2M system of the present invention, an existing device can be directly replaced without additional work, and an unnecessary reset operation is prevented from being performed when the existing device is reused.

1 is a diagram showing a configuration of a system constituting the present invention.
Fig. 2 is a diagram showing a system constituting the present invention from a functional viewpoint of a higher level.
FIG. 3 is a diagram illustrating a common service entity according to an exemplary embodiment of the present invention. Referring to FIG.
4 is a diagram illustrating a communication flow at a reference point according to an exemplary embodiment of the present invention.
5 is a diagram for explaining an M2M system environment to which the present invention can be applied.
6 is a flowchart illustrating a method of controlling a device replacement by a common service entity according to an exemplary embodiment of the present invention.
FIG. 7 is a diagram illustrating exemplary profile information of a device according to an embodiment of the present invention.
8 is a diagram for explaining a registration method determination operation using the determination of identity according to an embodiment of the present invention.
9 is a diagram for explaining a registration method determination operation using the existence of a terminated apparatus according to an embodiment of the present invention.
10 is a diagram for explaining an example of an environment to which the present invention can be applied.
11 is a view for explaining another example of an environment to which the present invention can be applied.
12 is a diagram for explaining another example of an environment to which the present invention can be applied.
13 is a diagram for explaining another example of an environment to which the present invention can be applied.
14 is a diagram for explaining another example of an environment to which the present invention can be applied.
15 is a diagram illustrating a configuration of a common service entity 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 numerals whenever 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 . OneM2M has recently introduced many technical issues related to object communication. Object communication refers to various communication in which communication is performed without a person intervening in the communication process. In the field of telecommunication, there are various fields such as energy field, enterprise field, healthcare field, public service field, residential field, retail field, transportation field, and others Field, and so on. The present invention includes the above-mentioned fields, and is applicable to other fields.

1 is a diagram showing a configuration of a system constituting the present invention. 1 illustrates an application 110, a common service 120 and an underlying network service 130. The layer 130 includes an application layer, an application layer, the Underlying Network Services Layer. Each of them constitutes an application layer, a common service layer, and a network service layer. The application layer contains the business logic and operational logic associated with oneM2M applications. The common service layer consists of a oneM2M service function that operates oneM2M application. For this, management, discovery, and policy enforcement are applied.

A common service entity (CSE) is an instantiate of a common service function. The common service entity provides a subset of common service functions to be used and shared by the M2M application. The common service entity uses the functions of the underlying network and interacts with other common service objects to implement the service.

Fig. 2 is a diagram showing a system constituting the present invention from a functional viewpoint of a higher level. The Application Entity (AE) 210 provides application logic for an end-to-end M2M solution. For example, a fleet tracking application such as a vehicle, a remote blood sugar monitoring application, or a remote power metering and controlling application (Application Entity (AE): Application Entity provides application logic for the end-to-end M2M solutions. Examples of the Application Entities can be fleet tracking application, remote blood sugar monitoring application, or remote power metering and controlling application. A common service entity (CSE) 220 is a set of service functions, and these service functions are functions commonly used in the M2M environment. This service function is exposed as a different function through reference points Mca, Mcc, and uses the base network service using the reference point Mcn. An example is data management, device management, M2M subscription management, location service, and the like. The subfunctions provided by the CSE can be logically understood as a CSF (Common Service Function). Some of the CSFs within the CSE of oneM2M node are mandatory and some may be optional. Similarly, the subfunctions in the CSF may also be mandatory or optional.

An underlying network services function (NSF) 230 provides services to the common service entity. Examples of services include device management, location services and device triggering.

Reference Points are supported in the common service entity (CSE), and the Mca reference point is a reference point that indicates the communication flow between the application entity and the common service entity. The Mcc reference point is a reference point that indicates the communication flow between two common service entities. The Mcn reference point is a reference point indicating the communication flow between the common service entity and one network service entity.

More specifically, the Mca reference point allows one application entity (AE) to use the services supported by the common service entity. The services provided through the Mca reference point are dependent on the functionality provided by the common service entity, and the application entity and the common service entity may reside in the same physical entity or in different physical entities. The Mcc reference point enables such use by a common service entity that wishes to use the services of other common service entities that provide the necessary functionality. The services provided through the Mcc reference point are dependent on the functionality provided by the common service entity. Mcc reference points can be supported between different M2M nodes. The Mcn reference point enables such use by a common service entity that wishes to use the service object of the underlying network providing the necessary functionality, which provides services other than transport and connection. The instance of the Mcn reference point is implemented dependent on the service provided in the underlying network. Information exchange between two physical M2M nodes can use the transport and connectivity services of the underlying network to provide basic services.

In this specification, a common service entity can be described as a CSE, and a network service entity can be described as an NSE.

FIG. 3 is a diagram illustrating a common service entity according to an exemplary embodiment of the present invention. Referring to FIG. FIG. 3 includes a function of processing identification information.

The functions provided by the common service object can be summarized as shown in FIG. 3. The application and service layer management, the data management and repository, the location, the security, / Communication Management / Delivery Handling, Registration, Service Session Management, Device Management, Subscription / Notification, Connectivity Management, Discovery Discovery, Service Charging / Accounting, Network Service Exposure / Service Execution and Triggering, and Group Management.

Of course, in addition to the above functions, it may include semantics, data analysis, application enablement, and network service function management.

Each of the functions will be described as follows.

Application and Service Layer Management (ASM) is responsible for managing AEs and CSEs for ADN, ASN, MN, and IN, including configuration, troubleshoot, upgrading, and upgrading of AE .

Communication Management and Delivery Handling (CMDH) is responsible for communication between other CSEs, AEs, and NSEs. CMDH is responsible for storing the communication requests at which time to communicate using which communication connection (CSE-CSE communication), when it is needed and when it is allowed, and when the transmission of the communication is postponed. CMDH is performed according to the provisioning policy and delivery handling parameters specific to each request for communication. Based network data transmission service, the underlying network can support the same forwarding handling function. In this case, the CMDH can use the underlying network and can act as a front end accessing the same forwarding handling function to the underlying network.

Data Management and Repository (DMR) allows M2M applications to exchange data with other objects. The DMR CSF provides the ability to provide and coordinate data storage. It also includes the ability to collect and combine large amounts of data, convert data to a specific format, or store data for analysis and semantic processing. "Data " means raw data that is extracted transparently from an M2M device, or may refer to data processed or combined and processed by an M2M entity. Collecting large amounts of data constitutes what is known as Big Data Storage.

DMG (Device Management) The CSF is responsible for managing device functions of devices in MNs, device nodes, and M2M area networks. It enables device management to provide one or more of the following functions: Installation and configuration of application software, configuration settings and provisioning, firmware updates, logging and monitoring and analysis, topology management of area networks, and devices within area network management.

The DIS (Discovery) CSF is responsible for retrieving the information and resources granted in the given scope and subject (including those allowed in the M2M service subscription) and the request from the Originator within a given scope Loses. The originator can be an application or another CSE. The scope of the search may be one CSE or multiple CSEs. The discovery result is returned to the originator.

Group Management (GMG) handles the group associated with the request. Requests are sent for the management of group and group membership, and are also responsible for the bulk operations supported by the group. When adding or deleting members to a group, you need to make sure that the members conform to the purpose of the group. Bulk operations include read, write, subscribe, notify, and device management. The request or subscription is made through the group, and the group is responsible for combining these requests and notifications. Members of a group have the same role in access rights to resources. In this case, access control is done by the group. If the underlying network provides broadcasting and multicasting capabilities, the GMG CSF should use these functions.

LOC (Location) The CSF enables the M2M AE to acquire the geographical location information of M2M nodes (eg ASN, MN) for location based services. This location information may be requested from an M2M AE that is in the same or a different M2M node.

NSE (Network Service Exposure) The CSF manages communication with the underlying network to access network service functions through the Mcn reference point on an available or supportable way for service requests from the M2M system on behalf of the M2M application. The NSE CSF conceals other CSFs and AFs from specific technologies and mechanisms supported in the underlying network. The network service functions provided from the underlying network include, but are not limited to, device triggering, small data transfer, location notification, policy rule setting, location query, IMS service, device management and the like. These functions do not include common transport services

REG (Registration) is responsible for handling applications or other CSEs to register with the CSE, which allows the registration of entities that want to use the services provided by the CSE. The REG CSF handles not only device registration for the CSE, but also device property / attribute registration.

SEC (Security) provides careful (sensitive) data handling, security operations, secure association configuration, authorization and access control, and identity protection. The SEC CSF provides sensitive data handling capabilities to protect local credentials that require security during storage and manipulation. Sensitive data handling also uses security algorithms. This feature supports separate security environments with different cryptographic techniques. The security operations function provides the following functions, first providing the creation and operation of a secure environment dedicated to being supported by the sensitive data handling function. It also supports post provisioning of root credentials protected in a secure environment and supports the provisioning and operation of subscriptions related to M2M services and M2M application services. The security association setting function establishes a security association between M2M nodes to enable confidentiality, integrity, authentication, and authorization. Authorization and access control functions control the access of services and data to authorized entities according to the provisioned security policies and assigned roles. The unique identifier of the entity is used for authorization, and the identity protection function can provide anonymity that serves as a temporary identifier so that it is not linked to the actual identity information associated with the entity or user.

Service Charging and Accounting (SCA) provides billing for the service layer. Supports different billing models, including online and offline billing. The SCA CSF acquires billable events, stores information, and generates billing records and billing information. The SCA CSF can interact with the billing system of the underlying network. However, the SCA CSF is responsible for generating and recording billing information at the final service level. The SCA CSF of the base node or service layer charging server is responsible for handling billing information for billing.

SSM (Service Session Management) The CSF manages M2M service sessions that are end-to-end service layer connections. The SSM CSF manages M2M service sessions between M2M applications, or between M2M applications and CSEs, or between CSEs. Management of the M2M service session includes management of the session state, establishment and authentication of the session, management of the underlying network connection and service related to the session, coordination of the session expansion of the CSE multi-hop cse, . Within a given M2M service session, the SSM CSF uses the CMDH CSF in the local CSE to send / receive messages to / from the next hop CSE or application. The SSM CSF uses the SEC CSF for session credentials for session participants and for session management related to authentication. The SSM CSF generates session-specific billing events and also communicates with the SCA CSF in the local CSE.

Subscription and Notification (SUB) provides notification to maintain subscriptions and tracks changes in resources (for example, deletion of resources). The subscription of the resource is initiated by the M2M AE or CSE and the access rights are granted by the hosting CSE. During an active subscription, the hosting CSE sends a notification to the address that the resource subscriber wants to receive in the event of a change in the subscribed resource.

3 and the description thereof are embodiments for implementing a common service entity, and the present invention is not limited thereto.

4 is a diagram illustrating a communication flow at a reference point according to an exemplary embodiment of the present invention.

410 is an originator and 420 is a receiver. Information exchange between the two entities is made through the Mca reference point between the application and the CSE, or between the CSE and the Mcc reference point. In addition, information is exchanged between Send and Respond. A send request is made from the originator 410 to the receiver 420 and includes the following information.

"Operation" is an operation to be executed. It includes C (Create), R (Retrieve), U (Update), D (Delete) and N (Notify). "to" is the address of the target resource, and "from" means the address of the resource representing the originator. "hd" is a header including meta information about a transmission request, and "content"

oneM2M is a requirement that must be fulfilled to implement the system. It includes overall system requirements, management requirements, data model & semantics requirements, security requirements Requirements, Charging Requirements, and Operational Requirements.

In this specification, M2M, especially oneM2M, 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.

The present invention relates to a method and apparatus for controlling device replacement in an M2M system. Specifically, the present invention relates to a method and apparatus for controlling a replacement of a device by a common service entity (CSE) of a middle node or an infrastructure node. Hereinafter, a method by which the CSE of the present invention controls device replacement will be described with reference to the drawings.

5 is a diagram for explaining an M2M system environment to which the present invention can be applied.

Referring to FIG. 5, the present invention can be applied to a system constituted by an M2M or IoT device. For example, a number of sensors and devices may be configured on a farm to configure an M2M system. That is, the farm management system 500 may be configured as an infrastructure node, and the infrastructure node may control one or more middle nodes 510, 512. Each middle node 510, 512 may be configured as a small-scale management system, such as a facility management system 510 and a housing management system 512. 5, the present invention will be described with reference to the facility management system 510. FIG.

The facility management system 510 may manage one or more sensors and one or more devices. In one example, the facility management system 510 may use the information of the light intensity sensor 556 to control the illumination 554. As another example, the facility management system 510 may use the information obtained from the temperature sensor 560 and the humidity sensor 558 to control the operation of the cooling / heating unit 550 and the sprinkler 552 in the facility. Through this, the operation of the lighting 554, the cooling and heating unit 550 and the sprinkler 552 of the farm can be automatically controlled.

However, devices connected to the facility management system 510 may be replaced in response to failure, aging, and seasonal changes. For example, if a temperature sensor 560 fails, it is necessary to replace it with a new temperature sensor 570. In this case, it is necessary to manually input various setting information such as the temperature measurement period of the conventional temperature sensor 560 and the measurement result report period to the replaced temperature sensor 570 to adjust the settings. Therefore, there is a problem that it is necessary for the operator to make an effort to set the setting of the replaced device manually by changing or changing the device constituting the M2M system.

That is, when the device is changed in the M2M system, a process of setting it is necessary. In other words, to perform the same operation on the new device in the same way as the operation performed in the existing device, it is necessary to adjust the setting. In this process, a registration and a resource update operation are required. In addition, it is necessary to update setting information or subscription information (subscription, etc.) when a resource is updated due to equipment being replaced. However, since there is no procedure and information to automate device replacement, there is a problem that the information set in the existing device can not be used unless the setting is manually adjusted when the device is replaced. For example, in the case of seasonal household appliances, the registration information and the usage information (settings, etc.) are not maintained because of a long period of inactivity, so that even when the season is over and the same seasonal household appliance is used again, We need to set up new information. This inconveniences the user, and it also causes the unnecessary work to be repeated in terms of resource management.

To this end, in the present invention, when a device is replaced with an old device, an upgraded device, a malfunctioning device, or a mobile device in the M2M system, the existing device can be directly replaced without any additional work, and unnecessary resetting is not performed when reusing the existing device.

To this end, the present invention stores a profile of a device to be registered when registering a device as a resource in a registrar CSE, and updates a resource stored in the registrar CSE when a profile of the device is changed. Meanwhile, the profile stored at the time of registering the replacement device may be transmitted to be set to operate as the existing device, and the saved profile may be transmitted at the time of re-registration of the same device.

6 is a flowchart illustrating a method of controlling a device replacement by a common service entity according to an exemplary embodiment of the present invention.

 According to an aspect of the present invention, there is provided a method for controlling device replacement, the method comprising: receiving registration request information from a first device; Determining whether there is profile information of a second device that is the same as or similar to the device and determining whether there is profile information of the second device; And a setting control step of controlling the setting information of the second device to be applied to the first device when the registration method determination step of determining the registration method of the first device on the basis of the registration method of the first device and the registration method of the first device are determined as the replacement registration .

Referring to FIG. 6, the common service entity may include a receiving step of receiving registration request information from the first device (S600). The common service entity may receive the registration request information from the first device to be replaced or newly connected. The registration request information may include information necessary for registering the first device with the M2M system. In one example, the registration request information may include information on the first device, and the information on the first device may include information on the device type of the first device or application identification information. Alternatively, the information on the first device may further include manufacturer information, model information, version information, and the like of the first device.

In addition, the common service entity may include an identity determination step of determining whether there is profile information of a second device that is the same as or similar to the first device based on the registration request information and the pre-stored profile information of each device (S602). In the identity determination step, the registration request information of the first device and the profile information of each device can be compared with each other. For example, the device-specific profile information may include at least one of device type information, application identification information, and replacement reference time information. That is, the device-specific profile information may include information about each device managed by the common service entity, and the profile information may be stored and managed when each device is registered. Accordingly, the common service entity compares the same kind of attribute information among the registration request information of the newly connected first device and the profile information of each device previously stored, and obtains the same attribute information as the attribute information included in the registration request information of the first device It is possible to judge whether or not the profile information of the second device including the information exists.

For example, the common service entity may determine whether there is profile information including device type information that is the same as the device type information included in the registration request information. As another example, the common service entity may determine whether profile information including application identification information identical to the application identification information included in the registration request information exists. As another example, the common service entity may determine whether there is profile information in which both the device type information and the application identification information are the same.

Thereafter, when it is determined that the profile information of the second device exists, the common service entity determines a registration method for determining the registration method of the first device on the basis of the information on the termination type or termination type of the device registered in the common service entity (S604). If it is determined that the profile information of the second device having the same attribute information as the attribute information included in the registration request information of the first device exists, the common service entity determines whether the device registered in the common service entity Information can be confirmed. The common service entity can determine the registration method of the first device by using the information on the termination type or termination type of the registered device. The termination information includes information as to whether the connection or use of the device has been terminated, and the termination type may include information as to whether the device has been terminated through a normal procedure. That is, when the profile information of the second device including the same attribute information as the first device exists, the common service entity further uses at least one of the end information and the end information of the device registered in the common service entity, 1 device can be determined. The registration method may include a new registration and a replacement registration, and the registration method may be added or changed according to the setting. For example, the new registration means that the device is recognized as a new device and registered, and the replacement registration means a method of registering the device in place of the existing device. When registering for replacement, it is necessary to control the setting information of the existing device to be applied to the device to be replaced.

For this, the common service entity may include a setting control step of controlling the setting information of the second device to be applied to the first device if the registration method of the first device is determined as the replacement registration (S606). For example, when the registration method of the first device is determined as the replacement registration, the common service entity may transmit the setting information of the second device including the same attribute information to the first device. The first device may equally apply the setting information of the second device to the first device. If the first device partially includes the function of the second device, the setting information of the second device may be applied to the corresponding function part. For example, when the first device is a cooling device and the second device is a cooling device, the first device may apply the configuration information of the received second device to the cooling function portion of the first device. In this case, the initial setting can be maintained in the case of the heating function. Conversely, when the first device is a cooler and the second device is a cooling / heating device, the first device may apply only the setting for the cooler in the setting information of the second device to the first device.

Through the operations described above, when the apparatus is replaced or reconnected, unnecessary setting processes can be prevented from occurring by applying the same settings of the apparatus that has been used previously.

Hereinafter, the operation of each step will be described in more detail with reference to the drawings.

FIG. 7 is a diagram illustrating exemplary profile information of a device according to an embodiment of the present invention.

The common service entity of the present invention can confirm the same by comparing the attribute information included in the registration request information of the first device with the property information of the profile information per device stored in advance. A common service entity in the present invention may be configured in a middle node or an infrastructure node.

Referring to FIG. 7, the device-specific profile information may include at least one of device type information 710, application identification information 720, and replacement reference time information 730. The device-specific profile information may be included in the deviceInfo 700 resource and at least one of the device type information 710, the application identification information 720 and the replacement reference time information 730 may be sub- Information. In addition, the deviceInfo 700 resource may include various attribute information shown in FIG. 7 as a sub-attribute.

For example, the deviceInfo 700 is a resource that stores information on a device among the resources. On the other hand, in the case of home appliances used according to the season, the registration information can be stored and reused in a resource bin.

The deviceinfo 700 resource may include attribute information such as replacement reference time information (logoffTime) 730 and application identification information (App-ID) 720. This is the information necessary to distinguish between a new registration or a replacement registration of a device. In one example, the replacement reference time information (logoffTime, 730) includes information related to time in the deviceInfo 700 with the name "logoffTime", and the common service entity has the same or similar type of new When a device is connected, the device can be judged as a replacement registration. The name "logoffTime" is described only by way of example, and the replacement reference time information is not limited to the name, and may be variously named as "replacementTime ".

On the other hand, the device type information 710 includes information on the type of the device and may reflect information on the device characteristics. In addition, the application identification information 720 includes information for identifying the application. For example, a device having a cooling function may have the same application identification information 720. The application identification information 720 is information for distinguishing a device from a functional aspect, and is not limited to a specific device. For example, a device having cooling functions and a device having both cooling and heating functions may have the same or similar application identification information 720.

8 is a diagram for explaining a registration method determination operation using the determination of identity according to an embodiment of the present invention.

The common service entity according to an embodiment of the present invention judges whether the device type information or the application identification information included in the registration request information and the profile information for each device are the same or not to determine whether the profile information of the second device exists, It can be judged.

Referring to FIG. 8, the common service entity determines whether the device type or application identification information of the registration request information of the first device is the same as the corresponding attribute information of the device-specific profile information (S800). That is, the common service entity may use the device type information or application identification information to confirm whether the newly connected device is an addition for replacement or a new device. For example, when the device type information is the same, the first device and the second device can be determined as the same type of device. If the application devices of the first device and the second device are the same, it can be determined that the devices are of a similar type. That is, when the device type information is all the same as the index designated by the air conditioner, it is determined that the first device and the second device are coolers of the same type. In the case of the application identification information, the index may be assigned according to the function, so that even though the first device and the second device both contain the same application identification information, the first device is the air conditioner and the second device is judged as the air conditioner . Accordingly, the common service entity can determine whether the first device and the second device are identical using at least one of the device type information and the application identification information. Depending on the setting, it may be determined using only one piece of information.

For example, when the profile information of the second device having the same device type or application identification information does not exist, the common service entity can determine the registration method of the first device as a new registration.

As another example, if the profile information of the second device having the same value does not exist in step S800 because the number of devices that can be registered is limited, the number of devices registered in the current common service entity can be registered The number of devices can be compared (S810). If the number of registered devices is smaller than the number of registerable devices, the first device can perform a new registration procedure (S820). If the number of registration devices is equal to or greater than the number of registerable devices, the first device can not be registered in the common service entity. In this case, the common service entity can error-process and terminate the registration request of the first device. Alternatively, the common service entity may determine the presence of an unnecessary device among the registered devices, unregister the unnecessary device, and register the first device newly.

If it is determined that the profile information of the second device having the same device type or application identification information exists, the common service entity can determine the registration method of the first device by checking the presence or absence of the terminated device (S830). The specific operation of determining the registration method of the first apparatus by checking the presence or absence of the terminated apparatus will be described later in Fig.

9 is a diagram for explaining a registration method determination operation using the existence of a terminated apparatus according to an embodiment of the present invention.

If the common service entity determines that the profile information of the second device exists, the common service entity can determine the registration method of the first device based on the information on the termination type and termination type of the device registered in the common service entity.

Referring to FIG. 9, the common service entity determines whether a device terminated among the devices registered in the common service entity exists (S910). For example, the common service entity can determine whether the terminated device is present by judging whether the termination information has been received or stopped from the registered device.

If the terminated device does not exist, the common service entity can determine the registration method of the first device as a new registration (S920). That is, if the termination of the normal termination or the abnormal termination is not required and the terminated device does not exist in the common service entity, the common service entity can newly register the requested first device. This can be applied in environments such as additional installation of a cooler. If necessary, the common service entity may determine whether to perform the new registration procedure of the first device using the step S810 in Fig. 8 when the first device is determined to be a new registration.

If there is a device terminated among the devices registered in the common service entity, the common service entity can determine the registration method of the first device by determining whether the termination type of the terminated device is a normal end or an abnormal end (S930 ). For example, the discrimination between the normal termination and the abnormal termination can be performed on the basis of whether the specific device has transmitted the information on termination to the common service entity. That is, in the case of the normal termination, the terminated device can transmit information indicating disconnection or termination to the common service entity. The common service entity may determine that the information indicating the connection release or termination is received and that the device is normally terminated when the device is not operating. On the other hand, when the specific device does not transmit the information indicating the disconnection or termination, but does not transmit the information related to the operation for a predetermined period or for a predetermined period of time, it can be determined that the device is abnormally terminated.

Meanwhile, if the terminated device is normally terminated, the common service entity can determine the registration method of the first device using the termination time information and the replacement reference time information (S940). For example, the common service entity can determine the registration method of the first device by comparing the replacement reference time information described in FIG. 7 with the elapsed time from the end point to the registration request point. For example, when the registration request information of the first device is received within a time defined by the replacement reference time information (logoffTime) based on the termination time or within a predetermined time interval based on the replacement reference time information (logoffTime) The registration method of the first device can be judged as the replacement registration. As another example, when the registration request information of the first device exceeds the replacement reference time information based on the end point, the common service entity may determine the registration method of the first device as a new registration.

Here, the replacement reference time information may be set in advance and may be set to a value corresponding to the device type or application identification information of each device. For example, in the case of a device used only for a certain season, such as an air conditioner, the value of the replacement reference time information may be set according to the season cycle.

Meanwhile, if it is determined that the terminated device is abnormally terminated, the common service entity can determine whether the information on the termination time of the abnormally terminated device can be confirmed (S950). For example, it is possible to check information on the end time by determining whether the last access time of the abnormally ended device can be confirmed. That is, the last connection time can be set as the end time.

In step S940, the common service entity may determine the registration method of the first device based on the replacement reference time information and the end time information when the end time (e.g., last access time) information is available. For example, when the registration request information of the first device is received within a time defined by the replacement reference time information (logoffTime) based on the termination time or within a predetermined time interval based on the replacement reference time information (logoffTime) The registration method of the first device can be judged as the replacement registration. As another example, when the registration request information of the first device exceeds the replacement reference time information based on the end point, the common service entity may determine the registration method of the first device as a new registration.

If it is not possible to confirm the ending time of the device that has ended abnormally and can not confirm the ending time, the common service entity can determine the registration method of the first device as the replacement registration (S960). In this case, it can be determined that the abnormally terminated device is terminated due to a failure or the like, so that the first device can be judged as the replacement registration of the abnormally terminated device.

On the other hand, the terminated device described above may be the second device. For example, the second device having the same device type or application identification information as the first device may be the terminated device, and the procedure in Fig. 9 may also be performed in this case as well. In addition, when the registration method is determined to be a new registration, a procedure for determining whether to proceed with the new registration procedure using the number information of the registerable devices of the common service entity and the number information of the registration devices may be added as needed.

When the registration method of the first device is determined, the common service entity can perform the registration procedure of the first device according to the registration method. For example, if the registration method of the first device is determined as the replacement registration, the setting information of the first device can be updated using the profile information of the second device. Specifically, the common service entity can forward the configuration information of the second device to the first device so that the configuration information of the second device is equally applied to the first device, and the first device updates the setting of the first device using the configuration information of the second device can do. As described above, the setting information may be partially or entirely set to be the same, and may be partially changed and applied so that the same output is displayed depending on the characteristics of the first device and the second device. If the first device is determined to be newly registered, the basic value of the first device is stored in the middle node or the infrastructure node.

On the other hand, if the registration method of the first device is determined to be the replacement registration, the common service entity can assign the application entity identification information used in the second device to be replaced to the first device in the same manner and reuse it. Through this, it is possible to seamlessly use the AE-ID registered in the common service entity without changing the AE-ID information in use, and the entire system can be operated irrespective of the replacement, so that the device replacement can be performed independently of the system operation.

Further, when it is determined to be the replacement registration, since the existing device (for example, the second device) registered in the common service entity is replaced with a new device (for example, the first device) The resources of other devices or nodes store information about existing devices. In the case of ID-related information such as the serial number of the device, since the new device has different values, updating of the device-specific information together with replacement registration is required in order for the system to operate smoothly. For example, in the deviceInfo of FIG. 7, an attribute such as objectIDs may correspond to information to be changed.

The present invention described above provides an effect of automatically controlling the replacement of the device using the profile information of the device in the M2M system. In addition, when the device is replaced in the M2M system of the present invention, an existing device can be directly replaced without additional work, and an unnecessary reset operation is prevented from being performed when the existing device is reused.

Hereinafter, a device replacement operation in various M2M systems when the present invention is applied will be described with reference to the drawings.

10 is a diagram for explaining an example of an environment to which the present invention can be applied.

Referring to FIG. 10, caching information may be added as an example of storing settings when using seasonal appliances. In this case, the set temperature and operating time information set in the air conditioner 1000 can be cached in the setting information. Then, the heater 1010 is coupled in winter, and the air conditioner 1000 is released from registration. When the air conditioner 1 1000 is re-assembled in the summer, the set temperature and operating time information, which is the previous setting information of the air conditioner 1000 according to the replacement registration decision of the common service object, ) And can be applied equally.

11 is a view for explaining another example of an environment to which the present invention can be applied.

Referring to FIG. 11, setting information such as brightness, saturation, and color temperature of the monitor 1 1110 can be applied to a device in which replacement information is registered. For example, when the monitor 1 1110 is replaced with the notebook 1120, the setting information (e.g., brightness, saturation, color temperature information, etc.) of the monitor 1 1110 is transmitted to the notebook computer 1120 And can be set in the notebook 1120. In this case, if the registration of the notebook 1120 having the same application identification information is requested when the monitor 1 1110 ends normally, the common service entity checks the replacement reference time information and transmits the notebook 1120 to the monitor 1110 The setting information of the monitor 1 1110 may be applied to the notebook 1120. [

In the case where replacement registration is performed from the notebook 1120 to the monitor 2 1130, the setting information of the notebook 1120 can be applied to the monitor 2 1130 as well. Alternatively, when the monitor 1 1110, the notebook 1120, and the monitor 2 1130 all apply the setting information directly to a similar device, differences in brightness, saturation, and color temperature experienced by an actual user may occur. In this case, the configuration information may be partially modified and updated so that the user can feel the same by using the characteristics of the devices 1110, 1120, and 1130 and the setting information. For example, in the case of the monitor 1 1110, a brightness value different from the level 2 brightness setting of the notebook 1120 may be set when the brightness setting is set to the level 2. In this case, the notebook 1120 can receive the setting information of the monitor 1 1110 together with the characteristic information of the monitor 1 1110, and set the notebook brightness level matching the brightness value of the monitor 1 1110. Through this, the user can maintain the same usage environment even when the device is changed.

12 is a diagram for explaining another example of an environment to which the present invention can be applied.

Referring to FIG. 12, information on navigation 1210 that is mounted on the vehicle 1200 may be used in the smartphone 1220. For example, when the navigation device 1210 is installed in the vehicle 1200, the common service entity stores the profile information of the navigation device 1210, and when the smartphone 1220 is registered, It is possible to apply the setting information of the navigation 1210 to the smartphone 1220. [ That is, the common service entity of the vehicle 1200 can replace and register the smartphone 1220 by checking the replacement reference time information when the navigation 1210 is normally terminated, and when the navigation 1210 ends abnormally, The smartphone 1220 can be replaced and registered according to whether the viewpoint can be confirmed. In this case, the destination information set in the navigation 1210 or the destination information that has been being displayed can be cached and set to the navigation application of the smartphone 1220 so that the user does not repeat the same operation.

13 is a diagram for explaining another example of an environment to which the present invention can be applied.

Referring to FIG. 13, the present invention can be applied even when a physical component of a specific device is changed. For example, when the existing motor 1310 of the drone 1300 is changed to the new motor 1320, the existing motor 1310 and the new motor 1320 may be different from those of the manufacturer. That is, the user can replace the motor to improve the performance. In this case, when the present invention is applied, the device type information or the application identification information may be the same for the existing motor 1310 and the new motor 1320 in the same motor type. Accordingly, the common service entity of the present invention can determine the replacement of the new motor 1320 by confirming the information on the termination and termination of the existing motor 1310. 13, the number of motors that can be connected to the drone 1300 is limited to 4. Therefore, when the existing motor 1310 is not terminated, the new motor 1320 exceeds the number of registerable devices of the common service entity And thus can not be newly registered. When the new motor 1320 is registered for replacement, setting information such as the number of revolutions of the existing motor 1310 can be equally applied to the new motor 1320. In this way, the drone 1300 can be operated normally even when a new motor 1320 is replaced to improve performance or reduce power consumption.

14 is a diagram for explaining another example of an environment to which the present invention can be applied.

Referring to FIG. 14, when the user registers other devices around the smartphone 1490, the information of the registered devices can be utilized in the same place. For example, when the user is located in the first place 1400, the printer 1401, the notebook 1402, the headphone 1403, the refrigerator 1404, and the TV 1405 are registered and used in the smartphone 1490 Can be. Thereafter, when the user moves to the second location 1450 and registers various devices of the second location 1450 around the smartphone 1490, the first location 1400 The setting of each device set in the second place 1450 can be set to the same in each device in the second place 1450. [

Specifically, the common service entity of the smartphone 1490 registers profile information of the printer 1401, the notebook 1402, the headphone 1403, the refrigerator 1404 and the TV 1405 of the first place 1400 The wireless router 1451, the headphone 1453, the refrigerator 1454, and the TV 1455 in the second place 1450. In this case, In this case, the notebook 1452, the headphone 1453, the refrigerator 1454, and the TV 1455 registered with the same or similar device are determined to be the replacement registration, and the wireless router 1451 can decide to register new. Therefore, the notebook 1452, the headphone 1453, the refrigerator 1454, and the TV 1455 are updated through setting information of the notebook 1402, the headphone 1403, the refrigerator 1404, and the TV 1405, respectively And the wireless router 1450 is newly registered.

Through this, the user can construct an environment similar to his / her environment, and reproduce / propagate the environment of home, working environment, crop environment and laboratory environment.

In addition, the present invention can be applied to molding or restoring the shape of an existing tooth or implant, and can be applied to a mechanical device or a robot that operates properly by filling a missing part with another. On the other hand, it is possible to change the smart phone without using the authentication chip like USIM, and to share the app / data.

A common service entity capable of performing all of the operations of the present invention described above will be described with reference to FIG.

15 is a diagram illustrating a configuration of a common service entity according to an embodiment of the present invention.

15, the common service entity 1500 may include a receiving unit 1510 that receives registration request information from a first device, and a communication unit 1510 that is the same or similar to the first device, based on registration request information and pre- Based on the information about the termination and termination type of the device registered in the common service entity, if the profile information of the second device is judged to exist, A setting control unit 1540 for controlling the setting information of the second device to be applied to the first device when the registration method of the first device is determined to be replacement registration, .

The receiving unit 1510 may receive registration request information from the first device. For example, the receiving unit 1510 may receive the registration request information from the first device to be replaced or newly connected. The registration request information may include information necessary for registering the first device with the M2M system. In one example, the registration request information may include information on the first device, and the information on the first device may include information on the device type of the first device or application identification information. Alternatively, the information on the first device may further include manufacturer information, model information, version information, and the like of the first device.

The identity determination unit 1520 may determine whether or not profile information of a second device that is the same as or similar to the first device is present based on the registration request information and the previously stored profile information of each device. For this, the identity determination unit 1520 may compare the registration request information of the first device with the profile information of each device stored in advance. For example, the device-specific profile information may include at least one of device type information, application identification information, and replacement reference time information. That is, the device-specific profile information may include information about each device managed by the common service entity, and the profile information may be stored and managed when each device is registered. Therefore, the identity determination unit 1520 compares the same kind of attribute information among the registration request information of the first device connected to the first device and the profile information of each device previously stored, and identifies the same attribute information included in the registration request information of the first device It is possible to judge whether or not the profile information of the second device including the attribute information exists.

For example, the identity determination unit 1520 may determine whether profile information including device type information identical to the device type information included in the registration request information exists. As another example, the identity determination unit 1520 may determine whether profile information including application identification information identical to the application identification information included in the registration request information exists. As another example, the identity determination unit 1520 may determine whether there is profile information having the same device type information and application identification information.

If it is determined that the profile information of the second device exists, the registration method determination unit 1530 may determine the registration method of the first device based on the information about the ending or ending type of the device registered in the common service entity . When it is determined that the profile information of the second device having the same attribute information as the attribute information included in the registration request information of the first device exists, the registration method determination unit 1530 determines that the registered device connected to the common service object And information about the termination type. The registration method determination unit 1530 can determine the registration method of the first device by using the information on the termination type or termination type of the registered device connected to the common service entity. The termination information includes information as to whether the connection or use of the device has been terminated, and the termination type may include information as to whether the device has been terminated through a normal procedure. That is, when the profile information of the second device including the same attribute information as that of the first device exists, the registration method determination unit 1530 determines at least one of the termination status and the ending mode of the device registered in the common service entity The registration method of the first device can be determined. The registration method may include a new registration and a replacement registration, and the registration method may be added or changed according to the setting.

The setting control unit 1540 can control the setting information of the second device to be applied to the first device when the registration method of the first device is determined to be the replacement registration. For example, when the registration method of the first device is determined as the replacement registration, the setting control unit 1540 can transmit the setting information of the second device including the same attribute information to the first device. The first device may equally apply the setting information of the second device to the first device. If the first device partially includes the function of the second device, the setting information of the second device may be applied to the corresponding function part.

Each configuration of the common service entity 1500 may be combined into one configuration, or may be implemented in a plurality of configurations separately. That is, there is no limitation on the form in which the above-described configuration is implemented.

As described above, according to the present invention, it is inevitable to replace the device due to aging or the like in the M2M network. Therefore, a new device can be automatically set by using the profile of the existing device in order to reduce the work in replacing the device. In addition, it is possible to configure an environment that replaces the role of the existing device only by the procedure of replacing the existing device with the node that registered the device, and even when reconnecting the existing device, the existing setting can be automatically set and used conveniently .

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 (15)

A method for a common service entity to control device switching,
A receiving step of receiving registration request information from a first apparatus;
Determining whether there is profile information of a second device that is the same as or similar to the first device based on the registration request information and profile information of each device previously stored;
A registration method determining step of determining a registration method of the first device based on information on whether the device registered in the common service entity exists or not, if profile information of the second device exists; And
And a setting control step of controlling the setting information of the second device to be applied to the first device when the registration method of the first device is determined as the replacement registration. The method according to claim 1,
The device-specific profile information includes:
Device type information, application identification information, and replacement reference time information. The method according to claim 1,
Wherein,
Determining whether the profile information of the second device is present by determining whether the device type information or the application identification information included in the registration request information and the profile information of each device are the same. The method according to claim 1,
Wherein the registration method determination step comprises:
Wherein if the profile information of the second device is determined not to exist, the registration method of the first device is determined as a new registration. 5. The method of claim 4,
Wherein the setting control step comprises:
Wherein if the registration method of the first device is determined as a new registration, whether or not the first device is registered is determined based on the registerable device number information. The method according to claim 1,
Wherein the registration method determination step comprises:
Wherein the registration method of the first device is determined as a new registration when there is no device terminated among the devices registered in the common service entity. The method according to claim 1,
Wherein the registration method determination step comprises:
Wherein the method determines the registration method of the first device by determining whether the termination type of the terminated device is a normal termination or an abnormal termination, when a terminated device exists in the devices registered in the common service entity. 8. The method of claim 7,
Wherein the registration method of the first device is determined using the termination time information and the replacement reference time information when the terminated device is normally terminated. 8. The method of claim 7,
And when the terminated device is abnormally terminated, the registration method of the first device is determined to be a replacement registration. 8. The method of claim 7,
Wherein the registration method of the first device is determined according to whether or not the last access time information of the terminated device can be confirmed when the terminated device is abnormally terminated. 11. The method of claim 10,
If the last connection time information is not verifiable, the registration method of the first device is determined to be replacement registration,
And when the last connection time information is identifiable, the registration method of the first device is determined based on the replacement reference time information. 8. The method of claim 7,
Wherein the terminated device is the second device. The method according to claim 1,
Wherein the setting control step comprises:
Wherein the control unit controls so that the application entity identification information of the second device is equally applied to the first device. The method according to claim 1,
Wherein the setting control step comprises:
And transmits the setting information of the second device to the first device,
Wherein the first device updates setting information of the first device using setting information of the second device. A common service entity for controlling device switching,
A receiving unit for receiving registration request information from the first apparatus;
An identity determiner for determining whether or not profile information of a second device identical or similar to the first device is present based on the registration request information and profile information for each device previously stored;
A registration method determination unit for determining a registration method of the first device based on information on whether the device registered in the common service entity is complete or ending, if profile information of the second device exists; And
And a setting control unit configured to control the setting information of the second device to be applied to the first device when the registration method is determined as the replacement registration.

Images