WO2015080461A1 - Method and device for searching for available device in m2m environment - Google Patents

Abstract

The present invention relates to a method and a device for searching for an available device in an M2M environment. According to one embodiment of the present invention, an M2M node constituting an M2M system including a request node for transmitting a search request message and a target node for providing a search result, comprises: a discovery unit for receiving the search request message from the request node and receiving, from the target node, the search result including an application resource; a communication management/delivery handling unit for transmitting the received message to the target node when the received message indicates a search of available applications; and a control unit for controlling the discovery unit and the communication management/delivery handling unit so as to perform the search by using the state information of the application resource.

Description

Method and device for discovering available devices in M2M environment

The present invention relates to a machine to machine communication (M2M) technology, and more particularly, to a method for searching for a device using a network technology and an apparatus therefor.

M2M, "Machine to machine communication" or MTC, "Machine type communication" or smart device communication, "Smart Device communication" or "Machine oriented communication" or the Internet of Things, "Internet of Things" is a human communication process Refers to all communication methods in which communication is performed without intervening. Recently, there has been a discussion about M2M in oneM2M, but technical elements that satisfy the architecture and requirements of oneM2M have not been presented.

When a request is made to a target node, an intermediate node, or a base node to search for a specific device to be used in the current M2M environment, it is previously unknown whether devices searched for the target node, the intermediate node, or the base node are available. I could not. For this reason, there is a situation in which a device cannot be used even when a device is searched because it cannot be used when searching for a specific device. The present invention seeks to provide a device that can be used quickly in situations such as emergency as well as general situation in communication between things by knowing whether or not to use the device to be searched at the time to search and use the device through the present invention.

An M2M node constituting an M2M system including a request node transmitting a search request message and a target node providing a search result according to an embodiment of the present invention receives a search request message from the request node and receives an application resource from the target node. A discovery unit for receiving a search result including a communication management, when the received message instructs the search of the available application, the management node for delivering the received message to the target node (Communication Management / Delivery Handling) And a control unit which controls the discovery unit and the communication management transfer handling unit to perform a search using state information of an application resource.

An M2M node that receives a search request message and provides a search result according to another embodiment of the present invention is a communication management handling (Communication Management / Delivery Handling) unit for receiving a search request message, the application of the received message is available. Data management and repository for confirming installation or use of the application when instructing to search, and the application to the node that sent the search request message when the application is installed and the application is available. And a control unit controlling the communication management and delivery handling unit to transmit resource state information.

An M2M system including a search node, a target node, and a request node for transmitting and receiving and searching for a request message according to another embodiment of the present invention generates and sends a search request message of an application resource including a search request message to the search node. If the requesting node, and the received message instructs the search of the available application, perform a search using the status information of the application resource, transfer the received message to the target node, and the application resource from the target node A search node for receiving a search result including a, and a target node for performing a search using the state information of the application resource.

According to another embodiment of the present invention, a method for searching for a device available in an M2M environment may include: receiving, by a search node, a search request message of an application resource; A search node includes forwarding the search request message to a target node, and the search node receives a search result including an application resource from the target node, wherein the search node or target node is in a state of an application resource. Searching is performed using the information.

According to the device search request, it is possible to propose a method of selecting only the available equipment at the time of the search request, so that a device having an application service that can be used in real time between M2M communications can be selected and serviced.

1 is a view showing the configuration of a system constituting the present invention.

2 is a diagram illustrating a system constituting the present invention from a high level functional point of view.

3 is a view showing a functional structure constituting the present invention.

4 is a diagram for configuring a common service entity according to an embodiment of the present invention.

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

6 is a diagram illustrating an architecture of a common service entity to which an embodiment of the present invention is applied.

7 is a configuration diagram of an application resource according to an embodiment of the present invention.

FIG. 8 is a diagram for explaining a lower resource type constituting an application resource according to an embodiment of the present invention. FIG.

FIG. 9 is a diagram illustrating an attribute configuring an application resource according to an embodiment of the present invention. FIG.

10 is a diagram illustrating a process of performing an available device search request according to an embodiment of the present invention.

11, 12, and 13 illustrate a detailed process of performing an available device search request according to an embodiment of the present invention.

14 to 19 are diagrams showing the configuration of a message according to an embodiment of the present invention.

20 is a diagram illustrating an example of an application resource to be answered according to an embodiment of the present invention.

FIG. 21 is a diagram illustrating a configuration of a search node performing a search and a target node to be searched according to an embodiment of the present invention.

22 is a diagram illustrating a process of searching for a device usable in an M2M environment based on a search node according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are only for distinguishing the components from other components, and the nature, order or order of the components are not limited by the terms. If a component is described as being "connected", "coupled" or "connected" to another component, that component may be directly connected or connected to that other component, but between components It will be understood that may be "connected", "coupled" or "connected".

Embodiments of the present invention will be described based on communication of things. IoT can be variously referred to as Machine to Machine communication (M2M), Machine Type Communication (MTC), Internet of Things (IoT), Smart Device Communication (SDC), or Machine Oriented Communication. Can be. Recently, oneM2M has presented many technical matters related to IoT. The thing communication refers to various communication in which a communication is made without a person intervening in a communication process. IoT is the energy sector, the enterprise sector, the healthcare sector, the public services sector, the residential sector, the retail sector, the retail sector, the transportation sector, and others. It is divided into fields. The present invention includes the above fields, and can be applied to other fields.

In the present invention, identification refers to a process of recognizing an entity in a specific domain from other entities. Authentication means determining the identity of an entity or establishing the source of information. Authorization means granting rights, which include assignment based on access rights. Confidentiality is a property that makes information unavailable or undisclosed for an unauthorized object or process. Credentials are data objects that are used in security procedures and are used to uniquely identify objects. Encryption refers to a process of generating plaintext as ciphertext using a cryptographic algorithm and a key. Integrity means ensuring the accuracy and completeness of the processing of information and methods. A key is a parameter used in combination with an encryption algorithm, and an entity having information about the key can reproduce the key or perform the encryption process in reverse. An entity having no information about the key can reproduce the key. Or reverse can not be performed. Mutual authentication refers to entity authentication that guarantees mutual identification. Privacy is the right of individuals to control or influence related information may be collected and stored by the subject to be disclosed. Repudiation means to deny an event or action requested from an entity. Secure is not vulnerable to any attack, and it means either enduring a vulnerable attack or repairing damage resulting from an attack, despite security. Security is created by creating and maintaining a way to protect a system. The state of the system. Sensitive data refers to the classification of stakeholder data that causes problems if unintentionally tampered with or modified without the consent of the affected stakeholder. A subscription is a classification of agreement, which means an agreement between a provider and a subscriber for the use (or consumption) of a service for a period of time. Subscription usually means commercial consent. Trust is the relationship between two components, where component x is a component only if component x has confidence that component y will behave in a predefined manner that does not violate a given security identity. Trust y and have a relationship of three activities and security policies. Verification means confirmation by providing objective evidence that specific requirements are met.

An M2M application refers to an application that operates service logic and uses M2M common services using a specific open interface in oneM2M. An M2M application infrastructure node is a device (a collection of physical servers of an M2M application service provider). The M2M application base node manages data and executes a coordination function of an M2M application service. The application based node hosts one or more M2M applications. .

The M2M application service is implemented through the service logic of the M2M application, and is operated by an M2M application service provider or a user. An M2M application service provider refers to an entity that provides an M2M application service to a user. M2M Area Network (M2M Area Network) is a form of the underlying network, and provides a data transport service (data transport service) between the M2M gateway, M2M devices, Sensing / Actuation Equipment (Sensing / Actuation Equipment). M2M Local Area Networks (LANs) may use heterogeneous communication technologies and may or may not support IP access.

The field domain consists of an M2M gateway, an M2M device, sensing / actuating equipment, and an M2M local network. An infrastructure domain is composed of application infrastructure and service infrastructure. Sensing / actuation equipment provides the ability to sense or affect the physical environment by interaction with one or more M2M application services. It interacts with M2M systems but does not host M2M applications. An M2M solution is a system implemented or deployed to satisfy the following criteria, and means to meet end-to-end M2M communication requirements of a specific user. The M2M system refers to a system that implements or deploys an M2M solution. Underlying network refers to a function, network, busses or other technologies for data transmission / connection services.

1 is a view showing the configuration of a system constituting the present invention. 1 includes an application 110, a common service 120, and an underlying network service 130. These constitute an Application Layer, a Common Services Layer, and a Network Services Layer, respectively. The application layer contains business logic and operational logic related to oneM2M applications. The common service layer consists of a oneM2M service function that runs a oneM2M application. Management, discovery, and policy enforcement apply to this.

The common service entity is an example of implementing a common service function. The common service entity provides a subset of common service functions to be used and shared by M2M applications. The common service entity leverages the functionality of the underlying network and interacts with other common service entities to implement the service.

2 is a diagram illustrating a system constituting the present invention from a high level functional point of view. As shown in FIG. 2, each component constituting the field domain and the infrastructure domain is as follows. Application Entity (AE) 210, 215 provides application logic for an end-to-end M2M solution. For example, it may be a collective tracking application such as a vehicle, a remote blood sugar monitoring application, or a remote power metering and controlling application. The common services entity (CSE) 220 and 225 is a set of service functions, and these service functions are functions commonly used in an M2M environment. These service functions are exposed to other functions through Reference Points Mca and Mcc, and use the base network services using Reference Point Mcn, M2M Subscription Management, and Location Service. Can be. The subfunctions provided by the CSE can be logically understood as Common Service Functions (CSFs). Some of the CSFs in the CSE of the oneM2M node may be mandatory and some may be optional. Similarly, sub-functions within the CSF may be mandatory or optional.

Underlying Network Services Functions (NSFs) 230 and 235 provide services to common service entities. Examples of services include device management, location services and device triggering.

Reference Points are supported by Common Service Entities (CSEs). Mca Reference Points are reference points that direct the flow of communication between an Application Entity and a Common Service Entity. The Mcc reference point is a reference point that directs the flow of communication between two common service entities. The Mcn reference point is a reference point that directs the flow of communication 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. 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 can exist in the same physical entity or in separate physical entities.

The Mcc reference point makes such use available to common service entities that wish to use the services of other common service entities that provide the necessary functionality. Services provided through the Mcc reference point depend on the functionality provided by the common service entity. Mcc reference points may be supported between different M2M nodes.

The Mcn reference point enables such use for common service entities that wish to use service entities in the underlying network that provide the necessary functionality, which provides services other than transport and connectivity. An instance of the Mcn reference point is implemented dependent on the services provided by the underlying network. Information exchange between two physical M2M nodes may use transport and connectivity services of an underlying network providing basic services.

The Mcc 'reference point indicates the flow of communication between CSEs.

3 is a view showing a functional structure constituting the present invention. In the functional architecture of FIG. 3, AE represents an application entity and CSE represents a common service entity. IN, MN, ADN, and ASN, which are combined in front of AE and CSE, are respectively an infrastructure node (Infrastructure Node, IN, or infrastructure node), an intermediate node (Middle Node, MN, or middle node), and an application dedicated node (Application Dedicated node). , ADN) and an Application Service Node (ASN). The CSEs of different nodes are not identical and depend on the services supported by the CSEs in the node.

An application dedicated node (ADN) is a node that contains at least one application entity (AE) and does not include a common service entity (CSE). The application dedicated nodes 311 and 312 communicate with the intermediate nodes 321 and 322 or the base node 330 using the Mca reference point.

An application service node (ASN) is a node that includes one common service entity (CSE) and at least one application entity (AE). The application service node communicates through the Mcc reference point as follows: It communicates with one intermediate node 321 or with one base node 330. The communication scheme may communicate with exactly one intermediate node or base node.

An intermediate node (MN) is a node that contains one common service entity (CSE) and zero or more application entities (AEs). The intermediate node communicates with IN or MN using at least Mcc, communicates using IN / MN / ASN and Mcc, or communicates using ADN and Mca.

The base node 330 is a node that includes one common service entity (CSE) and zero or more application entities (AEs). The intermediate node communicates with two or more nodes through each Mcc reference point as follows. Communicate with one or more intermediate nodes, and / or with one or more application service nodes. The base node may also communicate with one or more application dedicated nodes 313, 314 using the Mca reference point.

4 is a diagram for configuring a common service entity according to an embodiment of the present invention. 4 includes a processing function of identification information.

The functions provided by the common service entity can be summarized as shown in FIG. 4 by addressing & identification, application and service layer management, data management & storage, location, Security, Communication Management / Delivery Handling, Registration, Service Session Management, Device Management, Subscription / Notification, Connection Management (Connectivity Management), Discovery, Service Charging / Accounting, Network Service Exposure / Service Execution and Triggering, Group Management.

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

Each function is as follows.

Addressing and Identification (AID) provides the information needed to identify and manipulate physical and logical resources in an M2M environment. Logical resources are objects associated with software such as applications, CSEs, and data. Physical resources are hardware related entities associated with the underlying network and M2M devices. AID CSF supports the provisioning of different types of M2M identifiers and combining identifiers with M2M applications, CSEs, M2M devices.

Application and Service Layer Management (ASM) is responsible for managing the AEs and CSEs of ADN, ASN, MN, and IN, including configuration, troubleshooting, upgrades, and upgrades of AEs. .

Communication Management and Delivery Handling (CMDH) is responsible for communication between different CSEs, AEs, and NSEs. The CMDH is responsible for storing the communication request at what time using which communication connection (CSE-CSE communication), when it is needed and when it is authorized, and when delivery of the communication is subsequently delayed. CMDH is performed according to the provisioned policies and delivery handling parameters specific to each request for communication. In communication using the underlying network data transmission service, the underlying network may support the same forwarding handling function. In this case, the CMDH can use the underlying network and can act as a front end that accesses the same forwarding handling capabilities for the underlying network.

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

The Device Management (DMG) CSF is responsible for managing device functions of devices in the MN and device nodes (ADN, ASN) and M2M area networks. The AE can manage the device capabilities of the nodes using the services provided by the DMG CSF, and the AE does not need to manage specific technical knowledge. Enable device management to provide one or more of the following features: It includes installation and setting up of application software, configuration setting and provisioning, firmware updates, logging and monitoring and analysis, topology management of the area network, and devices within Airy Network Management.

DIS (Discovery) CSFs are information that corresponds to the permissions granted within a given scope and topic (including those granted by M2M service subscriptions) and requests from the originator within a given scope, such as supported attributes. Is responsible for retrieving resources. The originator can be an application or another CSE. The scope of the search can be one CSE or multiple CSEs. The discovery result is returned to the originator.

Group Management (GMG) handles groups associated with the request. Requests are sent for the management of groups and their membership, and are also responsible for the bulk operations supported by the group. When you add or remove members from a group, you need to make sure that the members conform to the group's purpose. Bulk operations include reading, writing, subscribing, informing, and device management. Requests or subscriptions are made through a group, and the group is responsible for combining these requests and notifications. Members of the group have the same role for access to resources. In this case, access control is by group. If the underlying network provides broadcasting and multicasting capabilities, the GMG CSF should take advantage of these features.

LOC (Location) CSF enables M2M AEs to acquire geographic location information of M2M nodes (eg, ASNs, MNs) for location-based services. Such location information may be requested from M2M AEs that exist within the same or different M2M nodes.

The Network Service Exposure, Service Execution and Triggering (NSSE) CSF communicates with the underlying network to access network service functions through the Mcn reference point in an available or supportable manner for service requests from M2M systems on behalf of M2M applications. Manage. The NSSE CSF hides other CSFs and AEs from the specific technologies and mechanisms supported in the underlying network. Network service functions provided from the underlying network include, but are not limited to, device triggering, small data transfer, location notification, policy rule settings, location query, IMS service, device management, and the like. These functions do not include general transport services.

REG (Registration) is responsible for handling an application or other CSE to register with the CSE, to allow the registration of an entity that wants to use the services provided by the CSE. The REG CSF handles the registration of the device's properties / properties as well as the device's registration with the CSE.

SEC provides security-sensitive data handling, security operations, security bindings, authorization and access controls, and identity protection. Sensitive data handling provided by the SEC CSF provides protection for local credentials that require security during storage and manipulation.

Service Charging and Accounting (SCA) provides the charging function of the service layer. It supports different charging models including online charging and offline charging. The SCA CSF secures billable events, stores information, and generates billing records and billing information. The SCA CSF can interact with the charging 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 the charging information for charging.

Service Session Management (SSM) CSF manages M2M service sessions, which 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. The management of M2M service sessions includes session state management, session authentication and establishment, management of underlying network connections and services associated with the session, coordination of session extensions in the CSE's multi-hop cse, exchange of information between session ends, and session termination. Include. The SSM CSF uses the CMDH CSF in the local CSE to send and receive messages to / from the next hop CSE or application within a given M2M service session. The SSM CSF uses the SEC CSF for session management related to the security credentials and authentication of session participants. The SSM CSF generates session-specific billing events and also communicates with the SCA CSF in the local CSE .

Subscription and Notification (SUB) provides notifications to keep subscriptions and tracks changes in resources (eg, deletion of resources). Subscriptions to resources are initiated by the AE or CSE, and access rights are granted by the hosting CSE. During an active subscription, the hosting CSE sends a notification to the address the resource subscriber wants to receive when a change in the subscribed resource occurs.

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

Meanwhile, an identifier required for implementing the present invention is as follows. M2M identifiers include M2M Service Provider Identifier (M2M-SP-ID), Application Instance Identifier (App-Inst-ID), Application Identifier (App-ID), CSE Identifier (CSE-ID), M2M-Node-ID (M2M Node Identifier / Device Identifier), M2M-Sub-ID (M2M Service Subscription Identifier), and M2M-Request-ID (Request Identifier).

The following M2M framework, M2M system, and M2M architecture are words that can be used interchangeably.

The M2M service provider must be uniquely identified by the M2M-SP-ID. The M2M-SP-ID is a static value assigned to the service provider. The App-Inst-ID is an identifier that uniquely identifies an M2M Application Instance that exists in an M2M M2M node, or an identifier that identifies an M2M application instance that interacts with an M2M node. The App-Inst-ID is used to identify the application to interact with or originate from the application within the M2M system. The M2M service provider must ensure that the App-Inst-ID is globally unique and the App-Inst-ID contains an application identifier (App-ID).

The CSE-ID identifies the CSE and is a globally unique identifier used when a CSE is instantiated at an M2M node in an M2M system. The CSE-ID is used to identify the CSE at every interaction to or from the CSE within the M2M system.

The M2M-Node-ID uniquely identifies the M2M node that hosts the CSE and / or the application as a whole. In the M2M system, the M2M service provider sets the CSE-ID and the M2M-Node-ID to the same value. The M2M-Node-ID allows an M2M service provider to bind a CSE-ID with a specific M2M node.

The M2M-Sub-ID allows an M2M service provider to bind an application, M2M node, and CSEs to a specific M2M service subscription. Thus, the M2M-Sub-ID belongs to the M2M service provider, allows to identify subscriptions to the M2M service provider, enables communication with the M2M service provider, and is distinct from the M2M Underlying Network Subscription Identifier. It can be changed according to the change of the M2M service provider. There may be multiple M2M-Sub-IDs for M2M based networks.

The M2M-Request-ID (M2M Request Identifier) is an identifier for end-to-end tracking of requests initiated by the application through the Mca reference point or from the CSE through the Mcc and Mcn reference points. It is also included in the response to the request. In order for the application to track the request and its response through the Mca reference point, the application must include an application request identifier that is unique per request when initiating a request through the Mca reference point with the CSE.

The M2M External Identifier (M2M-Ext-ID) is an identifier used by the M2M SP and is used when a service targeting a CSE identified by the CSE-ID is requested from the base network. The M2M-Ext-ID causes the base network to identify the M2M device associated with the CSE-ID in response to the service request. As a result, the base network maps the M2M-Ext-ID with the base network identifier assigned to the target M2M device. The M2M SP must also maintain the association between the CSE-ID, the M2M-Ext-ID, and the identity of the underlying network.

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

510 is the originator, 520 is the receiver, and the exchange of information between the two entities is via the Mca reference point between the application and the CSE, or through the Mcc reference point between the CSEs. In addition, information is exchanged through Send and Response. Send request is made from the originator 510 to the receiver 520 and includes the following information.

"op" is the operation to be executed, including C (Create), R (Retrieve), U (Update), D (Delete). "to" is an address of a target resource, and "fr" means an address of a resource representing an originator. "hd" is a header including meta information about a transmission request and "cn" means content to be transmitted.

6 is a diagram illustrating an architecture of a common service entity to which an embodiment of the present invention is applied. The common service entity includes a set of common service functions and a set of enabler functions. The enabler function consists of a service extension enabler and other enablers. The service extension enabler supports the CSE providing M2M services through Mca and Mcc reference points. Make it possible. The service extension enabler provides the following functions. i) Check module authentication, ii) Check node resources, iii) Check interoperability between existing modules, and iv) Check for conflicts. Check policies and rights to determine how to handle conflicts eg Do not register new module or deregister to check how policies and permissions are determined to determine how to handle them. existing module, etc.), and also v) Register new module, vi) Add new service (s) due to new module to list of services.) vii) Modify API support to reflect new service capabilities, viii) Change module-to-module communication to incorporate new modules (Modify inter-module communications to incorporate new module)

oneM2M is a requirement that must be met to implement the system. Overall System Requirements, Management Requirements, Data Model & Semantics Requirements, Security Requirements Requirements, Charging Requirements, and Operational Requirements.

In the present specification, a description will be given with respect to M2M, in particular oneM2M. However, this description is not limited to M2M, but is applicable to all systems and structures that provide inter-device communication, that is, thing communication, and communication that occurs in these systems.

When communicating between objects in oneM2M environment, Local CSE and application must be registered with each other. At this time, an application instance is created and this information is stored in the form of application resources. The component of the application resource contains the state information about the application, and can check whether the actual local CSE is available when communicating with the application instance by referring to the application resource information. Therefore, the present invention has presented a method for finding a device that can be used based on application resource information. When the search range is included as the method, the present invention is divided into cases including only a search target.

7 is a diagram illustrating a configuration form of an application resource according to an embodiment of the present invention.

Application resources include property values such as expirationTime, accessRightID, creationTime, lastModificationTime, creator, lifeCycleStatus, searchStrings, ReachabilityStatus, AppId, App-Inst-Id as property values, and subordinate resources such as Group and Subscription Resource.

The application resource stores information about the application, and the creation time is created as a result of successful registration with the local CSE by the application instance. The application resource may apply a CRUD (Create, Retrieve, Update, Delete) operation. That is, they may be generated by an application creation request, retrieved, and attributes may be updated or deleted. The expirationTime attribute is specified in the application resource so that the application can be deleted when the time expires. In addition, lifeCycleStatus exists in the application element, which holds the process as the status value until the application is created and stopped. In one embodiment, as a value that lifeCycleStatus may have, it may include all the states from installation to removal of an application such as Deployed, Install, Start, Stop, and Uninstall. Or it can have states such as Idle, Start, Stop from execution to stop of the application. In addition, the "ReachabilityStatus" element indicates whether the message sent from the Local CSE can be received. If the value has a value such as "OK" or "True" that means that the value is reachable, the application instance receives the message. Indicates that it can be received at present. The application elements lifeCycleStatus and ReachabilityStatus are the elements that know the status of the current application, which can be used to select available application instances. Therefore, if you focus on the availability of the application during the search, you can see the values of lifeCycleStatus and ReachabilityStatus above. In addition, expirationTime can be checked during the search process. If it has already expired, it can be excluded from the search results. In addition, expirationTime can be excluded from the search result even if the expiration is imminent. For example, if it is set to expire within 10 minutes, it can be configured not to include the search request of an application that takes 1 hour to run.

An application resource has a group resource and a subscription resource as subordinate resources. An application can belong to a specific group and can be subscribed to.

8 shows sub-resource components of an application resource according to an embodiment of the present invention.

A group resource represents a group to which an application belongs. In some cases, there is no group, and if it belongs to a group, a group name can be specified. Application resources can also be created by subscription requests.

9 shows a detailed description of attribute values of an application resource according to an embodiment of the present invention.

expirationTime represents the expiration time of the application. If the expiration time is set, the application can be stopped or deleted when the expiration time is reached. The expiration time may be used as a search condition in the availability of the application in the search process. As mentioned earlier, if the application is to be used for more than 1 hour, the application whose expirationTime is set to within 1 hour can be excluded from the search results. accessRightID means the right to access the application. When a CRUD request for the application is received, the accessRightID is first checked for access right. creationTime is the creation time of the application resource, and lastModifiedTime is logged when a modification is made to the application resource. The creator is the creator of the application, and lifeCycleStatus holds a value for the current lifetime status of the application. searchStrings can contain keywords, etc. for application resources, and can have values so that application resources can be searched. ReachabilityStatus is a value indicating whether the application instance can receive a message from the local CSE. App-Id represents an identifier value for an application, and App-Inst-Id refers to an application instance that is actually running in an execution environment. When this value is 1, an application resource is in an application instance state. Alternatively, the App-Inst-Id may include information identifying a separate application instance.

10 is a diagram illustrating a process of performing an available device search request according to an embodiment of the present invention.

1010 shows a process of requesting a search for an available device that includes a search range, and 1050 shows a process of requesting a search of an available device that does not include a search range.

The search process of 1010 is as follows. The ASN 1 1012 transmits a search request message to the base node) 1 1014 to search for a device available based on a search range at a specific location (S1021). The search request message includes location information of the ASN 1 1012, search range information, and application state information of an available device. The location information and the search range information of the search request message of the ASN 1 1012 are entered as options, and the application status information refers to an attribute value that can know the application status among the application resource information.

When the search request message includes a condition such as a search range and is forwarded to the base node 1 1014, the base node 1 1014 checks the search request message to determine the nearest MN based on the ASN 1 1012 that made the search request. 1 (1016) is found and MN 1 (1016) delivers a search request message (S1022). The MN 1 1016 performs a broadcast after checking the search request message (S1023). The ASN 2 1018 receiving the broadcast message transfers an application resource including its application current state and location information to the requesting MN 1 1016 (S1026). The MN 1 1016 transmits the response result to the base node 1 1014 (S1027), and the base node 1 1014 selects a response result that meets the search request condition from the response result and sends the response result to the ASN 1 1012. It passes (S1028).

When the search process of 1010 is summarized, when a node requesting a search transmits a search request message, the base node or an intermediate node that receives the search node uses the location information of the node requesting the search and is a node to be searched. Broadcast a search request message to them.

A search process of 1050 when the search condition does not include the search range condition in the search request message is as follows. The base node 1 1054 receiving the search request message from the ASN1 1052 as S1061 forwards the search request message to the search target to know the application status of the search target (S1062 and S1063). The search node ASN 2 1058 receiving the search request checks the search request message and transmits the response result to the base node 1 1054 by including the current application state information in the application resource information (S1066 and S1067). The base node 1 1054 checks the response result and transmits the response result that satisfies the search request condition to the ASN 1 1052 (S1068). When the base node 1 1054 forwards the search request to the ASN 2 1058, if the ASN 2 1058 is far away, the base node 1 1054 may forward the search request through the intermediate node MN 1 1056 (S1062). In addition, the ASN 2 1058, which is the target node, may directly receive the request message to confirm the ASN 1 search request including the search request message, and deliver the corresponding application resource information to the ASN 1 1052 as a response result.

In 1050 of FIG. 10, the base node IN 1 1054 and the intermediate node MN 1 1056 may be selectively configured, and are indicated by dotted lines.

11, 12, and 13 are diagrams illustrating a detailed process of performing an available device search request according to an embodiment of the present invention.

The ASN 1 1102 generates a search request message in which information about an object to be searched (for example, an application ID, a group URI, or an application search phrase, etc.), and a search range are configured in an optional form. ASN 1 1102 transmits the search request message to IN 1 1104, which is a base node (S1110). IN 1 1104, the discovery unit checks the search request message (S1111) and determines whether a search range condition is an option in the search request message (S1112). If the search range request condition is included, a search request is made to the data management storage unit (DMR) to find the MN closest to the ASN 1 (1102) that is the originator requesting the search (S1113). The data management storage unit responds to the access information of the nearest MN 1 1106 (S1114), and the discovery unit transmits a search request message to the MN 1 1106 including a broadcast request message to the MN 1 1106 (S1114). S1115, S1120).

The MN 1 1106 detects the search request message received from the IN 1 1104 (S1121), and requests to perform a broadcast including a search condition (S1122). MN 1 1106 performs a broadcast including a search request message (S1123 and S1130).

The process proceeds in FIG.

The ASN 2 1108 receiving the search request message in a broadcast form checks the search request message (S1241) and makes an application resource request including application status information to the application service manager (S1242). The application service manager configures information about application resources that meet the conditions of the search request message and returns a response result to the MN 1 1106 (S1243 and S1245). At this time, when there is no application instance or when all of the application instances are not possible, the application instance is created, the application resource information is configured, and the response result is returned to the MN 1 1106.

The MN 1 1106 transmits the response result to the IN 1 1104 (S1245), and the IN 1 1104 selects only items that meet the search request conditions from the response result and returns the search result to the ASN 1 1102 ( S1246).

If ASN 1 1102 is a message configuration without a search range condition in the search request message (NO in S1112 of FIG. 11), the discovery unit of the IN 1 1104 receiving the search request message is S1111 and S1112. After the process is performed in the same manner, if there is no search range condition, the discovery unit transmits a search request message to the ASN 2 1108 corresponding to the search target information in the search request message (S1247). The ASN 2 1108 checks the message in the search request, and the CSE stores the current application information corresponding to the condition of the search request message in the form of an application resource and returns a response result (S1254). At this time, when there is no application instance or when all of the application instances are not possible, the application instance is generated, the application resource information is configured, and the response result is returned to the MN 1 1106 (S1260). The IN 1 1104 receiving the response result selects only the items that meet the search request condition and returns the response result to the ASN 1 1102 (S1270).

The process proceeds in FIG.

When ASN 1 1102 sends a search request that does not include a range search to MN 1 1106, MN 1 1106 checks the search request message and forwards the search request to ASN 2 1108 as the search target ( S1324). Upon receiving the search request message, the ASN 2 1108 checks the message in the search request, and the CSE stores the current application instance information corresponding to the condition of the search request message in the form of an application resource and returns a response result (S1335 and S1339). At this time, when there is no application instance or when all of the application instances are not possible, the application instance is created, the application resource information is configured, and the response result is returned to the MN 1 1106. The MN 1 1106 receiving the response result selects only the items that meet the search request condition and returns the response result to the ASN 1 1102 (S1345 and S1346).

When ASN 1 1102 forwards a search request that does not include a range search to ASN 2 1108, which is the search target, ASN 2 1108 that receives the search request message checks the message in the search request and the CSE determines The current application information meeting the condition is stored in the form of an application resource, and the response result is returned (S1356). At this time, when there is no application instance or when all of the application instances are not possible, the application instance is created, the application resource information is configured, and the response result is returned to the MN 1 1106. The MN 1 1106 receiving the response result selects only the items that meet the search request condition and returns the response result to the ASN 1 1102 (S1391).

The contents of FIGS. 11 to 13 are summarized as follows.

The elements constituting the M2M system include search nodes IN1 and MN1, target nodes IN1, MN1 and ASN2 and request nodes ASN1 which transmit and receive request messages. IN1 and MN1 become search nodes and target nodes, which receive a search request message from ASN1, and thus IN1 becomes a target node, and IN1 becomes a search node since the search request message is transmitted to MN1. Similarly, since MN1 receives a search request message from IN1, MN1 becomes a target node, and MN1 becomes a search node because it forwards the search request message to ASN2.

11 to 13 are summarized as follows when the request node is IN1, the search node is MN1, and the target node is ASN2.

The request node 1104 generates and sends a search request message of the application resource including the search request message to the search node 1106. If the search node 1106 indicates a search for an available application, the search node 1106 performs a search by using the state information of the application resource, transfers the received message to the target node 1108, Receive a search result including an application resource from the target node 1108. Meanwhile, the target node 1108 performs a search by using the state information of the application resource.

The search node may be a base node or an intermediate node, and the target node may be an intermediate node or an application service node. For application resources, the application ID (AppId), application instance ID (App-Inst-Id), service expiration time (expirationTime), access right (accessRightID), creation time (creationTime), resource last modified time (lastModifiedTime), Creator, lifetime status information (lifecyclestatus) of the application, search keywords (searchStrings), whether the message can be received from the CSE, application status information (reachabilityStatus), group information (group), subscription It may include any one or more of the information (subscription).

The available device is a state in which all nodes, CSEs, and applications that make up the device are available, a node or CSE can receive and process a request message, or a request is made by an application instance from the CSE. It can be any one or more of states that can receive and process the message.

In addition, the state information of the application resource may include any one of lifeCycleStatus or reachabilityStatus state as the state of the application instance.

As described in S1112, the search request message includes a search range, and the search node may deliver the message to a target node within the search range.

14 to 19 are diagrams showing the configuration of a message according to an embodiment of the present invention.

1400 and 1500 of FIGS. 14 and 15 are configurations of messages that can be used when a search request is made (S1110 in FIG. 11). In the case of a search request message including a search range, op means a command and “RETRIEVE” is indicated. "fr" is the sender information of the message, and 1400 and 1500 include CSE-ID information of the ASN 1 1102 that is the sender. "to" is the recipient information of the message and contains the CSE-ID of IN 1. And "cn" is the content of the message, that is, the content, the search request message including the search range (1400), the search range (Search Range), Search Keyword (Originator LOC), Application status information (Application Resource lifecycleStatus, Application Resource Reachability) is included. If the search request message does not include the search range (1500), the search requestor location and the search range are not included.

In the search request message including the search range, 1600 of FIG. 16 is a search request message in which IN 1 1104 indicates a broadcast search request to MN 1 1106 (S1120 in FIG. 11). IN 1 1104 transmits to MN 1 1106 including a search method to MN 1 1106 in a search request message received from ASN 1 1102. The broadcast search request message includes the originator's location information (Originator_LOC: (10, 30)).

1700 of FIG. 17 indicates a message type included when MN 1 1106 performs a broadcast (S1130 in FIG. 11). Search keywords include application ID, group URI, and searchStrings information.

1800 of FIG. 18 indicates that the search request message is sent to the target whose IN 1 1104 is specified in the search keyword when the search request message is not included when the ASN 1 1102 sends the search request message to the IN 1 1104. It is a message form configured when delivering (S1250 in Fig. 12). "mi" is the meta information of the search request message, "rt" specifies the response result form, and "da" allows delivery in the form of delivery when delivering the message to the search request target. "rt" can be received in the form of application resources, and "da" is set to ON, which allows delivery in the form of delivery when IN 1 passes to ASN2.

1901 and 1902 of FIG. 19 show response result messages to the ASN2 1108 in response to the search request message (S1245 and S1260 in FIG. 12, respectively). An application resource is received as a response result in the "cn" item, and the response result for the search request message received in broadcast form as a search request including a range is 1901. Otherwise, it is configured in the form of 1902.

The message transmission and response in FIG. 13 will be described with reference to FIGS. 14 to 19. In FIG. 13, S1307 is 1500, S1328 is 1800, S1339 is 1902, S1350 is 1500, and S1361 is the same as that of 1902.

20 is a diagram illustrating an example of an application resource to be answered according to an embodiment of the present invention.

Among the elements of the application resource 2000, the application instance from the CSE with the value of lifeCycleStatus except Deployed, Install, Stop, Uninstall, etc., and the reachabilityStatus as "OK" except for the status that is not the stage to perform the application's original functions. Indicates that the application can receive the message, and when the App-Inst-Id is present to say that it is an application instance, the application instance is said to be available. If reachabilityStatus has a value indicating that it is not received or not "OK", or if the value of lifeCycleStatus is not a situation in which an actual application can operate, the application instance is in an unavailable state.

In the present invention discussed so far, the present invention has been described for defining a resource type including a definition of a usable device and application state information and searching for the resource type. In this regard, the apparatus and process will be described in detail.

First, the available device refers to a state in which nodes, CSEs, and applications that are elements of the device are available. When the device receiving the search request message is in the process of processing the search request message, the node and the CSE are available because the process of receiving the search request message and executing the command. However, if the node, CSE, is available, and the application is not available, then the device can be said to be unavailable. Therefore, in the present specification, since the node and the CSE process a message by receiving a search request, the node and the CSE provide a method of finding an available device by finding an available state of the application on the premise of the available state.

Information about the application running in the device is stored in the application resource, and the application resource creation time is created as a result of successful registration with Local CSE. In addition, application resources may be CRUD (Create, Retrieve, Update, Delete). The elements that make up an application resource include a "lifeCycleStatus" with current lifetime information and a "ReachabilityStatus" element indicating the status of receiving a message from the CSE. The "lifeCycleStatus" and "ReachabilityStatus" elements are used to inform the status of the application. Since multiple applications can exist within a single device, the components also have "App-Id" and "App-Inst-Id" values to distinguish application resources. If the application exists in the execution environment, it has a value of "App-Inst-Id", which is called an application instance.

An embodiment for finding a usable device is broadly divided into two types: a search for an available device including a search range and a search for an available device by specifying a search target. In the case of searching for an available device by specifying a search target, detailed examples are divided into a case where a search request is made to a base node, an intermediate node, and a search target node.

An embodiment of searching for an available device including a search range is as follows. The first base node constituting the M2M system consisting of the base node checks the search request message with the request application service node as the original dispatcher (originator, Originator) to determine whether to search the scope, and impersonate the request application service node In order to find the nearest intermediate node, we request the Data Management & Repository Department and the Discovery Division, which requests the intermediate node to search by Braodcast, and the Data Management District which has a list of intermediate nodes served by the first base node. And delivering a result of performing the search request to a first application service node.

The first intermediate node receiving the search request message from the first base node checks the search request message and broadcasts a discovery request, and a broadcast management / delivery handling for performing a broadcast. The second application service node that checks the broadcast message includes a discovery unit for requesting an application state by checking a broadcast message, a CSE for checking a current application state and providing information in the form of an application resource. And transmitting the result to the first base node via the first intermediate node, and transmitting only information that satisfies the search request condition to the first application service node in the result received from the first intermediate node.

As an embodiment of an available device discovery request by specifying a discovery target, the first foundation node constituting the M2M system configured as the foundation node checks the discovery request message with the requesting application service node as the original dispatcher to make an available status check request. Forwarding to a second application service node that is to be searched, requesting an available state to a CSE by a second application service node that receives an available status request message, communicating the result to the first base node, And transmitting, by the second application service node, only information that meets the search request condition to the first application service node.

As another example of an available device discovery request by specifying a discovery target, a first intermediate node constituting an M2M system configured as an intermediate node checks the availability status by checking a discovery request message with the requesting application service node as the original dispatcher. Forwarding the request to the second application service node being searched for, the second application service node receiving an available status request message, requesting an available status from the CSE, and delivering the result to the first intermediate node; And transmitting, by the first intermediate node receiving the same, only information satisfying the search request condition to the first application service node.

In another embodiment of a device search request that is available by specifying a search target, a second application service node, which is a search target of a first application service node as a first dispatcher, confirms a search request message, and the second application service node sends a CSE to the CSE. Requesting an available state, delivering the result to the first application service node, and selecting only information that meets the search condition by the first application service node receiving the same.

FIG. 21 is a diagram illustrating a configuration of a search node performing a search and a target node to be searched according to an embodiment of the present invention.

The node 2110 (search node) performing a search means an intermediate node or a base node, and the node 2120 to be searched is a node having an application to be searched, such as ASN2, or a node 2110 performing the search. ) Means an intermediate node or a base node that receives a search request message.

An M2M system comprising a requesting node for sending a search request message (including a base node that receives and forwards a search request message from an originator or originator) and a target node providing a search result (a search target node, 2120). Looking at the configuration of the M2M node 2110 constituting the following.

There is a discovery unit 2112 that receives a search request message from the requesting node and receives a search result including an application resource from a target node (search target node), wherein the received message indicates a search for an available application. In one case, the communication management and delivery handling unit 2116 for delivering the received message to the target node, and the discovery unit 2112 to perform a search using state information of an application resource. And a control unit 2118 for controlling the communication management transfer handling unit 2116, and the M2M node 2110 searches for a device available in an M2M environment.

In more detail, when the search request message is a message for requesting a location-based range search, the discovery unit 2112 may include information on an intermediate node closest to a node that is the originator of the search request message. Management and Repository).

In addition, the M2M node 2110 may be a base node or an intermediate node. The target node 2120 may be an intermediate node or an application service node. In addition, the target node 2120 may be a base node when the base node has a structure capable of delivering a search request message to another base node or when a base node performs a search by receiving a search request from an application service node.

The status information of the application resource may include one of lifeCycleStatus or reachabilityStatus status as the status of the application instance, and may be controlled to be included or not included in the search result according to the status of the application instance. The search request message includes a search range, and the M2M node 2110 may deliver the message to the target node 2120 within the search range.

Next, the search target node 2120 will be described. The search target node 2120 may be any one of a base node, an intermediate node, and an application service node, and is an M2M node 2120 that receives a search request message and provides a search result. Looking at the configuration, if the communication management and delivery handling (Communication Management / Delivery Handling) unit 2124 receiving the search request message, the command to search for the available application, confirms the installation or use of the application The Data Management and Repository 2122 and the communication management forwarding handling to transmit the status information of the application resource to the node that sent the search request message when the application is installed and the application is available. And a control unit 2126 for controlling a communication management / delivery handling unit 2124, and the M2M node 2120 provides an application resource that can be used in an M2M environment. The controller 2126 checks service expiration time information of the application and transmits state information of the application resource for which the application service has not expired. Here, although the service expiration time has not been reached in the process of checking the service expiration time information, the service may be considered expired even if the service expires soon.

In more detail, the application resource may include an application ID (AppId), an application instance ID (App-Inst-Id), and a service expiration time (expirationTime). From accessRightID, creationTime, creationTime, resource lastModifiedTime, creator, lifetime status of the application, lifecyclestatus, search keywords, searchStrings, CSEs It includes one or more of whether the message can be received, application status information (reachabilityStatus), group information (group), subscription information (subscription).

In addition, the usable device is a state in which all nodes, CSEs, and applications constituting the device are available, a state in which the node or the CSE can receive and process a request message, or an application instance from the CSE. Can be any one or more of states that can receive and process the request message. The state information of the application resource may include any one of lifeCycleStatus or reachabilityStatus state as the state of the application instance.

22 illustrates a process of searching for a device available in an M2M environment based on a search node according to an embodiment of the present invention. The search node may be IN1 or MN1 of FIGS. 11 to 13.

When the search node receives a search request message of an application resource (S2210), the search node checks whether the search request message indicates a search for an available application, and when the search request message indicates a search for an available application, The search node transmits the search request message to a target node (S2220). Thereafter, the search node or the target node performs a search using state information of an application resource (S2230). In more detail, the search node may be a base node or an intermediate node, the target node may be an intermediate node or an application service node, and the application resource may include an application ID (AppId), an application instance ID (App-Inst-Id), and a service. Expiration time, access right (accessRightID), creation time (creationTime), resource last modified time (lastModifiedTime), creator, lifetime status information of the application (lifecyclestatus), search keyword ( searchStrings), whether a message can be received from the CSE, application status information (reachabilityStatus), group information (group), and subscription information (subscription) may be any one or more.

In addition, the usable device is a state in which all nodes, CSEs, and applications that make up the device are available, a state in which the node or the CSE can receive and process a request message, or an application instance from the CSE. Can be any one or more of states that can receive and process the request message.

The state information of the application resource may include any one of lifeCycleStatus or reachabilityStatus state as the state of the application instance.

Meanwhile, the search request message may include a search range, and when the search range includes the search range, the search node delivers the message to a target node within the search range.

One embodiment of the present invention as described above relates to a method for searching for devices available in an M2M system. The present invention relates to a method for receiving and processing an ASN1 and a search request including a search target, application status information, a request range, and the like. It consists of IN 1, MN 1 and ASN 2 which receives the application status request and provides the result, and presents a method to find when an event to search for available devices occurs.

In IN 1 that receives a search request message with ASN 1 as the first sender, the search request node is selected and MN 1 closest to ASN 1 is selected and forwarded. Alternatively, the MN1 receiving the search request message with ASN 1 as the first sender transmits a search request to the search target node or delivers a search request message to ASN 2 whose ASN 1 is the first originator. When the search target node receives the search request message, the search node returns information including information including the current application status. In the case of a range-based search request, IN 1 making a search request forwards the search request to MN 1 closest to ASN 1, MN 1 performs a broadcast, and ASN 2 receiving it receives the status of the application. Return the results including what information you include.

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

Claims (24)

1. In the M2M node constituting the M2M system comprising a request node for sending a search request message and a target node for providing a search result,

   A discovery unit for receiving a search request message from a request node and receiving a search result including an application resource from a target node;

   A communication management delivery handling unit for delivering the received message to the target node when the received message indicates a search for an available application; And

   And a control unit for controlling the discovery unit and the communication management transfer handling unit to perform a search using state information of an application resource.
2. The method of claim 1,

   The discovery unit, when the search request message is a message for requesting a location-based range search, searches for information of an intermediate node closest to the node that is the originator of the search request message from the data management and repository. M2M node characterized.
3. The method of claim 1,

   The M2M node is a base node or an intermediate node, and the target node is an intermediate node or an application service node.
4. The method of claim 1,

   The application resource includes an application ID (AppId), an application instance ID (App-Inst-Id), a service expiration time (expirationTime), an access right (accessRightID), a creation time (creationTime), a resource last modified time (lastModifiedTime), and a creator ( creator), the current lifecycle status (lifecyclestatus), search keywords (searchStrings), whether the message can be received from the CSE, application status information (reachabilityStatus), group information (group), subscription information ( M2M node comprising any one or more of the (subscription).
5. The method of claim 1,

   The available device is a state in which all nodes, CSEs, and applications that make up the device are available, a node or CSE can receive and process a request message, or a request is made by an application instance from the CSE. M2M node, characterized in that any one or more of the states that can receive and process the message.
6. The method of claim 1,

   M2M node, characterized in that the state information of the application resource includes any one of lifeCycleStatus or reachabilityStatus status as the state of the application instance.
7. The method of claim 1,

   The search request message includes a search range,

   And the M2M node forwards the message to a target node within the search range.
8. An M2M node that receives a search request message and provides a search result,

   Communication management delivery handling unit for receiving a search request message (Communication Management / Delivery Handling) unit;

   A data management and storage unit for confirming installation or use of the application when the received message indicates a search for an available application; And

   And a control unit for controlling the communication management delivery unit to transmit the status information of the application resource to the node that has transmitted the search request message when the application is installed and the application is available. M2M nodes that provide application resources available in the environment.
9. The method of claim 8,

   The application resource includes an application ID (AppId), an application instance ID (App-Inst-Id), a service expiration time (expirationTime), an access right (accessRightID), a creation time (creationTime), a resource last modified time (lastModifiedTime), and a creator ( creator), the current lifecycle status (lifecyclestatus), search keywords (searchStrings), whether the message can be received from the CSE, application status information (reachabilityStatus), group information (group), subscription information ( M2M node comprising any one or more of the (subscription).
10. The method of claim 8,

    The available device is a state in which all nodes, CSEs, and applications that make up the device are available, a node or CSE can receive and process a request message, or a request is made by an application instance from the CSE. M2M node, characterized in that any one or more of the states that can receive and process the message.
11. The method of claim 8,

    M2M node, characterized in that the state information of the application resource includes any one of lifeCycleStatus or reachabilityStatus status as the state of the application instance.
12. The method of claim 8,

    The controller checks service expiration time information of the application and transmits state information of the application resource whose application service has not expired.
13. In an M2M system including a search node, a target node, a request node for transmitting and receiving a request message and search,

    A request node for generating a search request message of an application resource and transmitting the same to the search node;

    When the received message indicates a search for an available application, a search is performed by using state information of an application resource, the search message is transmitted to the target node, and the search includes an application resource from the target node. A search node for receiving results; And

    An M2M system for discovering devices available in an M2M environment, including a target node performing a search using state information of an application resource.
14. The method of claim 13,

    The search node is a base node or an intermediate node,

    M2M system, characterized in that the target node is an intermediate node or an application service node.
15. The method of claim 13,

    The application resource includes an application ID (AppId), an application instance ID (App-Inst-Id), a service expiration time (expirationTime), an access right (accessRightID), a creation time (creationTime), a resource last modified time (lastModifiedTime), and a creator ( creator), the current lifecycle status (lifecyclestatus), search keywords (searchStrings), whether the message can be received from the CSE, application status information (reachabilityStatus), group information (group), subscription information ( M2M system, characterized in that it comprises any one or more of).
16. The method of claim 13,

    The available device is a state in which all nodes, CSEs, and applications that make up the device are available, a node or CSE can receive and process a request message, or a request is made by an application instance from the CSE. M2M system, characterized in that any one or more of a state capable of receiving and processing a message.
17. The method of claim 13,

    M2M system, characterized in that the status information of the application resource includes any one of lifeCycleStatus or reachabilityStatus status as the status of the application instance.
18. The method of claim 13,

    The search request message includes a search range,

    The search node delivers the message to a target node within the search range.
19. The search node receiving a search request message of the application resource;

    If the search request message indicates a search for an available application, the search node forwarding the search request message to a target node; And

    The search node receiving a search result containing an application resource from the target node,

    The search node or the target node performs a search using the state information of the application resource, the method for searching for a device available in the M2M environment.
20. The method of claim 19,

    Wherein the search node is a base node or an intermediate node, and the target node is an intermediate node or an application service node.
21. The method of claim 19,

    The application resource includes an application ID (AppId), an application instance ID (App-Inst-Id), a service expiration time (expirationTime), an access right (accessRightID), a creation time (creationTime), a resource last modified time (lastModifiedTime), and a creator ( creator), the current lifecycle status (lifecyclestatus), search keywords (searchStrings), whether the message can be received from the CSE, application status information (reachabilityStatus), group information (group), subscription information ( subscription).
22. The method of claim 19,

    The available device is a state in which all nodes, CSEs, and applications that make up the device are available, a node or CSE can receive and process a request message, or a request is made by an application instance from the CSE. And at least one of a state capable of receiving and processing a message.
23. The method of claim 19

    And the status information of the application resource includes any one of lifeCycleStatus or reachabilityStatus status as the status of the application instance.
24. The method of claim 19

    The search request message includes a search range,

    And said search node forwards said message to a target node within said search range.

Images