KR20150067037A - The methods and apparatuses of optimization for criteria of subscription in M2M Systems - Google Patents

Abstract

The present invention relates to a method and an apparatus for optimizing reference information of subscription by analyzing similar criteria of subscription in an M2M system. More specifically, according to the method, a node including a common service entity (CSE) controls resource for subscription. The method includes: a request message reception step of receiving, from an issuer, a request message for requesting generation of a first subscription with respect to the resource for subscription; a determination step of generating the first subscription based on the request message and determining whether a second subscription with respect to the resource for subscription exists; a subscription information change step of changing a reporting condition of the resource for subscription by comparing criteria information of the first subscription and the second subscription if the second subscription is determined to exist; and a transmission step which transmits reporting information changed by an application object controlling the resource for subscription.

Description

METHOD AND APPARATUS FOR OPTIMIZING BASIC INFORMATION OF SUBSCRIPTIONS IN M2M SYSTEMS

The present invention relates to M2M (Machine to Machine Communication) technology, and relates to a method and apparatus for analyzing and optimizing similar resource subscription criteria 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.

In the M2M system, the criteria for indicating the alert criteria for changes in the resource being subscription vary according to the subscriber. The M2M system communicates the changed conditions to the M2M device responsible for generating (updating / updating) the resource data in order to satisfy various subscription conditions. As a result, network traffic increases and M2M devices with limited computing resources can not process multiple conditions at the same time. In an M2M environment with network availability constraints or computing resource constraints of M2M devices, technology is needed to minimize network traffic and efficiently utilize the computing resources of M2M devices.

According to an aspect of the present invention, there is provided a method of controlling a subscription target resource by a node including a hosting CSE (Common Services Entity), the method comprising: generating a first subscription for a subscription target resource from an issuer; A request message receiving step of receiving a request message for requesting a subscription target resource and a determination step of generating a first subscription based on the request message and determining whether a second subscription to the subscription target resource exists or not, A subscription information changing step of changing a reporting condition of the subscription target resource by comparing criteria information of each of the first subscription and the second subscription, and a transmitting step of transmitting reporting information changed to the application object controlling the subscription target resource . ≪ / RTI >

The present invention also provides a method for an application object to manage a subscription target resource, the method comprising: receiving a reporting condition of a subscription target resource from a node including a hosting CSE (Common Services Entity) The method comprising: changing a reporting condition to a received reporting condition when an event occurs that satisfies a changed reporting condition; transmitting data of a subscription target resource to a node including a serving CSE (Common Services Entity) The method comprising the steps of:

In addition, the present invention provides a node including a hosting CSE (Common Services Entity) for controlling a subscription target resource, receives a request message for requesting generation of a first subscription for a subscription target resource from an issuer A first subscription is created based on the Communication Management and Delivery Handling unit and the request message, and a determination is made as to whether or not there is a second subscription to the subscription target resource. If it is determined that the second subscription exists A subscription and notification unit for comparing the criteria information of each of the first subscription and the second subscription to change the reporting condition of the subscription target resource and the application information for controlling the subscription target resource, (Data Management & Repository) unit.

According to another aspect of the present invention, there is provided an application object for managing a subscription target resource, comprising: a CSE interface unit for receiving a reporting condition of a subscription target resource from a node including a hosting CSE (Common Services Entity) And a resource control unit for changing a reporting condition to a received reporting condition when the event is related to a subscription target resource, wherein when an event satisfying the changed reporting condition occurs, the CSE interface unit transmits data of the subscription target resource to the hosting CSE To a node including the node.

Subscription optimizations can optimize and configure the reporting cycle of M2M devices to reduce network traffic between M2M devices and M2M gateways, or between M2M gateways and M2M service platforms, and to efficiently use the computing resources of limited M2M devices.

1 is a diagram showing a configuration of a system constituting the present invention.
Figs. 2A and 2B are diagrams showing a system constituting the present invention from a high-level functional viewpoint. Fig.
3A and 3B are views showing the functional structure constituting the present invention.
4 is a diagram illustrating a common service entity according to an exemplary embodiment of the present invention.
5 is a diagram illustrating a communication flow at a reference point according to an exemplary embodiment of the present invention.
6 is a diagram illustrating an architecture of a common service object to which an embodiment of the present invention is applied.
7 is a diagram illustrating a configuration of an M2M service according to an embodiment of the present invention.
FIG. 8 is a signal diagram briefly illustrating a signal flow of an issue source, a node, and an application object according to an embodiment of the present invention.
9 is a diagram illustrating a message flow between one or more issue words according to an embodiment of the present invention, a hosting CSE that is requested to be subscribed from an issue, and an application entity that controls a resource to be subscribed.
10 is a view for explaining an operation of a node including a host CSE according to an embodiment of the present invention.
11 is a diagram illustrating a subscription optimization function according to an embodiment of the present invention.
12 is a diagram for explaining operations of an application entity according to an embodiment of the present invention.
13 is a diagram illustrating an example in which reference information is included in a subscription resource according to an embodiment of the present invention.
14 is a diagram exemplarily showing the structure of criteria resources.
15 is a diagram illustrating a configuration of a node including a hosting CSE according to an embodiment of the present invention.
16 is a diagram illustrating a configuration of an application entity according to an embodiment of the present invention.
17 is a diagram showing an expected effect when the subscription optimization function according to an embodiment of the present invention is applied to the CSE.

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 even though 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.

In the present invention, identification refers to a process of recognizing an entity in a specific domain differently from other entities. (Process of recognizing an entity in a particular domain as distinct from other entities). Authentication is the process of determining the identity of an entity or establishing the source of the information. Authorization is the granting of rights, which involves assigning based on access rights (The granting of rights, which includes granting of access based on access rights). Confidentiality refers to a property that makes information unavailable or unavailable to unauthorized entities or processes. (This property is not available or disclosed to unauthorized individuals, entities, or processes.) . Credentials are data objects that are used in security procedures and are used to uniquely identify entities. (Data objects are used to uniquely identify entities and which are used in security procedures. . Encryption refers to the process of generating a plaintext as a ciphertext using a cryptographic algorithm and a key. (The process of changing a plaintext into a ciphertext using a cryptographic algorithm and key). Integrity means ensuring the accuracy and completeness of the processing of information and methods (Safeguarding the accuracy and completeness of information and processing methods). A key is a parameter used in combination with an encryption algorithm. An entity having information on the key can reproduce the key or perform the encryption process inversely, and an entity having no information about the key can perform the reproduction Or a reverse operation can not be performed (A parameter used in conjunction with a cryptographic algorithm that determines the operation in such a way that an entity with knowledge of the key can reproduce or reverse the operation, while an entity without knowledge of the key can not ). Mutual authentication refers to entity authentication that ensures mutual identity. (Entity authentication, which guarantees each other's identity). Privacy is the ability of individuals to control or influence information to be collected and stored by those who are to be exposed (see below). and to whom that information may be disclosed. Repudiation means denying an event or action requested from an entity. (Denial by an entity of a claimed event or action.) Secure means not to be vulnerable to all attacks, to resist vulnerable attacks or to recover damage from attacks in spite of vulnerabilities (not vulnerable to most attacks) Security is the state of the system that occurs by creating and maintaining a scheme to protect the system (for example, A system condition that results in the establishment and maintenance of measures to protect the system. Sensitive data refers to the classification of stakeholder data that causes problems if they are inadvertently known or tampered with without the consent of the affected stakeholder. If it is not possible, then it will not be possible for the owner of the affected stakeholder. A subscription is a classification of an aggrement, which means the agreement between a provider and a subscriber on the use (or consumption) of a service over a period of time. A subscription usually refers to a commercial agreement. (A classification of an agreement, where the agreement is between a provider and a subscriber for a period of time. Trust refers to the relationship between two components, only if component x has confidence that a component y will behave in a predefined manner that does not violate the given security congestion, (a relationship between two elements, a set of activities and a security policy), and a trust relationship between the activity and the security policy. A well defined way (with respect to the activities) that does not violate the given security policy. Verification means confirmation through the provision of objective evidence that a particular requirement is satisfied. (Confirmation, through the provision of objective evidence, that specified requirements have been fulfilled).

An M2M application is an application that runs service logic and uses an M2M common service with a specific open interface in oneM2M (applications that run the service logic and use M2M Common Services accessible via a set of oneM2M specified open interfaces. Specification of M2M Applications is not subject to the current oneM2M specifications). The M2M application infrastructure node is a device (a collection of physical servers of the M2M application service provider). The M2M application-based node manages data and implements an adjustment function of the M2M application service. An application-based node hosts one or more M2M applications. (eg a set of physical servers of the M2M Application Service Provider) that manages data and executes coordination functions of M2M Application Services.

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 is realized through the service logic of an M2M application and is operated by the User or an M2M Application Service Provider). An M2M application service provider is an entity that provides M2M application services to users (M2M Application Services to the User). The M2M Area Network is a form of an underlying network and provides data transport services between M2M gateways, M2M devices, and Sensing / Actuation Equipment. M2M LAN (Local Area Network) can utilize heterogeneous communication technologies and may or may not support IP access (M2M Gateway (s), M2M Device (s), and Sensing & Actuation Equipment. M2M Local Area Networks can use heterogeneous network technologies that may or may not support IP access.

The field domain consists of M2M gateway, M2M device, sensing / actuation device, and M2M local network. Infrastructure Domain is composed of Infrastructure and Service Infrastructure (consists of M2M Devices, M2M Gateways, Sensing and Acting (S & A) Equipment and M2M Area Networks). A sensing / actuation device provides functionality that senses or influences the physical environment by interacting with one or more M2M application services. It interacts with the M2M system but does not host the M2M application (M2M Application Services, which interacts with the M2M System, however does not host the M2M application) not host an M2M Application.). An M2M solution is a system that is implemented or deployed to meet the following criteria: it meets the end-to-end M2M communication requirements of a specific user. The M2M system refers to a system that implements or deploys an M2M solution (satisfying all the following criteria: 1. It satisfies the end-to-end M2M communication requirements of particular users; Some part of the M2M Solution is realized by including services compliant to oneM2M specifications). Underlying network means functions, networks, busses or other technologies for data transmission / connection services (Functions, networks, busses and other technologies assisting in data transport connectivity services).

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 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.

2A is a diagram showing a system constituting the present invention from a functional viewpoint of a high 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. Likewise, the subfunctions in the CSF can be either mandatory or optional (Common Services Entity (CSE): A Common Services Entity is the set of "service functions" that are common to the M2M environments and are specified by oneM2M. Subcontracts, etc., are provided in the following subsections: Data Management, Device Management, M2M Subscription Management, Location Services etc. Such "subfunctions" (CSFs), some of the CSFs can be mandatory and others can be optional. Also, inside a CSF, some subfunctions can be mandatory or CSF, some of the subfunctions like "Application Software Installation", "Firmware Updates", "Logging", "Monitoring", etc. can 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. (Underlying Network Services Entity (NSE): An Underlying Network Services Entity provides services to the CSEs. 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 on the same physical entity or on different physical entities (The Mca reference point designates communication flows between An Application Entity (AE) and a Common Services Entity (CSE). The Mca reference point shall allow an AE to use the services provided by the CSE, and for the CSE to communicate with the AE.

The services provided via the MCA reference points are dependent on the functionality supported by the CSE.

NOTE: The AE and the CSE it invokes may or may not be co-located within the same physical entity. 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. The Mcc reference point can be supported between different M2M nodes (The Mcc reference point designates communication flows between two Common Service Entities (CSEs). The Mcc reference points are dependent on the functionality supported by the CSEs. 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. The exchange of information between two physical M2M nodes can use the transport and connectivity services of the underlying network to provide basic services (The Mcn reference point designates communication flows between a Common Service Entity (CSE) and the Underlying Network Services Entity (NSE). The Mcn reference point shall allow a CSE to use the services provided by the underlying NSE.

The services provided by the McN are dependent on the services provided by the Underlying NSE.

FIG. 2B is a diagram illustrating a functional configuration according to another embodiment of the present invention. Field domain and an infrastructure domain, and the relationship of the AE-CSE-NSE is maintained as shown in FIG. 2A. The entities of the base domain are connected to the entities of the field domain and also to the base domain of the external service provider.

3A is a diagram 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. (Application Dedicated Node, ADN), 313 and 314 denote Application Service Nodes (ASN), and 321 and 322 denote Middle (MN), and 330 denotes an infrastructure node (IN). The CSEs of the different nodes are not identical to each other, and depend on the services supported by the CSE in the node.

The application specific nodes 311 and 312 are nodes including at least one application entity (AE) and not including 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 Mca reference points. (An Application Dedicated Node is a Node that contains at least one Application Entity and does not contain a Common Services Entity An Application Dedicated Node communicates with a Middle Node or an Infrastructure Node over an Mca reference point.

The application service nodes 313 and 314 are nodes including one common service entity (CSE) and including at least one application entity (AE). The application service node communicates through the Mcc reference point as follows. Communicates with one intermediate node 321, or communicates with one base node 330. The communication scheme can communicate with exactly one intermediate node or base node. (An Application Service Node contains a Node that contains one Common Services Entity and contains at least one Application Entity. An Application Service Node may communicate over a Mcc reference point with either: exactly one Middle Node, or exactly one Infrastructure Node.

The intermediate nodes 321 and 322 are nodes that contain one common service entity (CSE) and contain zero or more application entities (AEs). The intermediate node communicates with two or more nodes through each Mcc reference point as follows, which does not operate exclusively. Communicate with one or more application service nodes, communicate with one or more intermediate nodes, or communicate with one infrastructure node. In addition, the intermediate node can communicate with zero or more application dedicated nodes 313, 314 using the Mca reference point (A Middle Node is a Node that contains one Common Services Entity and contains zero or more Application Entities. In addition, a middle node communicates with zero or more Application Dedicated Nodes (DOCs), one or more Middle Nodes, one or more Application Nodes over all Mca reference points ..).

The base node 330 is a node that includes one common service entity (CSE) and includes at least one application entity (AE). 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 communicate with one or more application service nodes. The base node may also communicate with one or more application dedicated nodes 313, 314 using an Mca reference point (An Infrastructure Node is a Node that contains one Common Services Entity and may contain Application Entities. Mcc reference points with: one or more Middle Node (s); and / or one or more Application Service Node (s). In addition, an Infrastructure Node communicates with one or more Application Dedicated Nodes.

FIG. 3B shows a structure including the nodes illustrated in FIG. 3A. FIG. 3B shows the configuration of service nodes configured in the oneM2M architecture. In Figure 3B, NoDN indicates nodes that are not M2M device nodes. In Figure 3b, M2M nodes (ADN, ASN, MN, IN) are connected to Mca, Mcc, and Mcn interfaces. In FIG. 3B, CSE Capable Nodes (CSE Capable Nodes) refer to an entity having at least one CSE as a logical entity and having zero or more AEs.

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

The functions provided by the common service object can be summarized as shown in FIG. 4, and can be classified into Addressing & Identification, Application and Service Layer Management, Data Management & Repository, Location, Security, Communication Management / Delivery Handling, Registration, Service Session Management, Device Management, Subscription / Notification, Connection Management Service Charging / Accounting, Network Service Exposure / Service Execution and Triggering, Group Management, and so on.

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.

Addressing and Identification (AID) provides the information needed to identify and manipulate physical and logical resources in an M2M environment. Logical resources are software, such as applications, CSEs, and data. Physical resources are hardware-related entities associated with the underlying network and M2M devices. The AID CSF supports the provision of different types of M2M identifiers and the combination of identifiers with M2M applications, CSE, M2M devices (Identification and Identification (AID) CSF provides information on identifying and manipulating physical and logical resources in M2M environment . The logical resources are entities related to software such as CSEs and Data. The physical resources are hardware related entities such as the entities in the Underlying Network and M2M Devices etc. The AID CSF provides for the provision of different types of M2M Identifiers and the association of such Identifiers with M2M Applications, CSEs, M2M Devices etc.).

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 The Application and Service Layer Management (ASM) CSF is responsible for providing management of AEs and CSEs on the Application Dedicated Nodes, Application Service Nodes, Middle Nodes and Infrastructure Nodes. CSE as well as the AEs.

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, CMDH can use the underlying network and act as a front-end that accesses the same forwarding-handling function to the underlying network (CSDs CSFs, CSEs, AEs and NSEs. The CMDH CSF is responsible for deciding what time to communicate and which CSE-to-CSE communication is used. In this paper, we propose a new CMDH CSF based on the proposed CMDH-based CSDF, which is based on the CMDH protocol. The CMDH CSF is available on the Underlying Network, and it may act as a fro nt end to access the underlying network equivalent delivery handling functionality.

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 a large amount of data constitutes what is known as a Big Data Storage function. (One of the goals of one M2M CSEs is to enable M2M Applications to exchange data with each other. Data Management and Repository The "data" can be either raw data transparently retrieved from the M2M Device, or orbiting the data. This is a collection of large amounts of data constitutes what is known as the Big Data Repository functionality.

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 this network management. (DMG) CSF enables the management of device capabilities on Middle Nodes (M2M Devices) and Device Nodes (M2M Devices) as well as devices that reside within M2M Area network. Device Management (DMG) CSF enables the Firmware Updates, Logging, Monitoring, Diagnostics, Topology Management of Area Networks, Devices within an 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 (Discovery (DIS) CSF is responsible for searching for information / resources according to a request from an originator within a given scope and subject to permissions. The CSE is a collection of CSE files that can be downloaded from the CSE web site.

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, then the GMG CSF should use this functionality (Group Management (GMG) CSF is responsible for handling Group Group related requests. Membership as well as bulk operations are supported by the Group. Bulk operations include read, write, subscribe, and notify. , device management, etc. The Group is a member of the Group, the Group is responsible for aggregating its responses and notifications. This case, access control is facilitated by grouping, and the GMG CSF is able to utilize such capability.

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. (LOC) CSF allows M2M AEs to obtain geographical location information of M2M Nodes (eg, ASN, MN) for location-based services. 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 general transport services (eg, Network Service Exposure, Service Execution and Triggering (NSE) CSF manages communications with the Underlying Networks for accessing network services functions. The NSE CSF shields other CSFs and AFs are supported by the Underlying Networks. The network services functions are provided by the underlying network, including but not limited to, device triggering, small data transmission, location notification, policy rules settings, location queries, IMS services, device management.

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 the registration of the device's properties / attributes as well as the registration of the device to the CSE (Registration (REG) CSF is responsible for handling an application or CSE to register with a CSE in order to allow registered entities to use The REG CSF handles registration of a Device as well as the registration of the Device's properties / attributes with the CSE.

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. A unique identifier of an entity may be used for authorization, and an identity protection function may provide an anonymity that serves as a temporary identifier so that it is not linked to an entity or an actual identity associated with the user (SEC (SEC) : Sensitive Data Handling functionality; Security Association Establishment functionality; Authorization and Access Control functionality; Identity Protection Functionality; Sensitive Data Handling functionality in the SEC; CSF protects the local credentials on which security relies during storage and manipulation. It performs other sensitive functions as well as security algorithms such as the following: - Creation and administration of dedicated security environments Upported by Sensitive Data Handling functionality; Provisioning and administration of subscriptions related to M2M services and M2M application services. Security Association Establishment functionality is responsible for establishing security association between corresponding M2M nodes, in order to provide services such as confidentiality, integrity, authentication, authorization, etc. Authorization and Access Control functionality is responsible for authorizing services and data access to authenticated entities. The unique identifiers of an entity are used for authentication, the Identity Protection functionality provides pseudonyms which serve as temporary identifiers.

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 the charging information for charging (Service Charging and Accounting (SCA) CSF provides charging functions for the Service Layer. The SCA CSF is responsible for capturing chargeable events, recording of information, generating charging records and charging information. The SCA CSF can interact with the charging system in the Underlying Network also. It is the responsibility of the SCA to support the charging of the SCA in the service layer.

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 a session-specific billing event and also communicates with the SCA CSF in the local CSE (an M2M service session is an end-to-end Service Layer connection managed by the SSM CSF. The SSM CSF manages M2M M2M Application, a CSE, or CSEs. The management of a M2M service session includes capabilities such as management of session state, session authentication and establishment, management of underlying network connections and services related to the SSM CSF uses the CMDH CSF within its local CSE for sending / receiving messages to / from the next-hop CSE or to / from An application for a given M2M service session. The SSM CSF also uses the SEC CSF for the management of session related security credentials and authentication of session pa The SSM CSF generates session specific charging events that are communicated to the SCA CSF within its 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 subscribe to if a change in the subscribed resource occurs (CSF is not responsible for providing subscriptions) A subscription to a resource is initiated by an M2M or a CSE, and is granted by the Hosting CSE subject to access rights. (es) where the resource subscriber wants to receive it.

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

Meanwhile, an identifier required for implementing the present invention will be described as follows. The M2M identifier includes an M2M Service Provider Identifier (M2M-SP-ID), an App-Inst-ID (Application Instance Identifier), an App-ID (Application Identifier), a CSE-ID (CSE Identifier), an M2M- A Node Identifier / Device Identifier, an M2M Service Subscription Identifier (M2M-Sub-ID), and an M2M-Request-ID (Request Identifier).

The following M2M framework, M2M system, and M2M architecture are interchangeable words.

The M2M service provider shall be uniquely identified by the M2M-SP-ID. The M2M-SP-ID is a static value assigned to the service provider (an M2M Service Provider will be uniquely identified by the M2M Service Provider Identifier (M2M-SP-ID). Service Provider.). The App-Inst-ID is an identifier that uniquely identifies an application instance (M2M Application Instance) present in the M2M M2M node, or an identifier that identifies an M2M application instance that interacts with the M2M node. The App-Inst-ID is used to identify an application from an application within the M2M framework or to interact with it towards an application (an Application Instance Identifier (App-Inst-ID) uniquely identifies an M2M Application instance resident on an An M2M node or an M2M application instance that interacts with an M2M node. An App-Inst-ID will identify an application for the M2M framework. The M2M service provider must ensure that the App-Inst-ID is globally unique and the App-Inst-ID contains the application identifier (App-ID) App-Inst-ID is globally unique. The App-Inst-ID will include the Application ID). App-ID corresponds to an application and does not guarantee that it is globally unique (this is equivalent to the application name and is not guaranteed to be globally unique on its own).

The CSE-ID identifies the CSE and is globally unique and is used when the CSE is instantiated on the M2M node within the M2M architecture. The CSE-ID is used to identify the CSE in all interactions from or to the CSE within the M2M framework (CSE-ID, when the CSE-ID is instantiated within an M2M node in the M2M architecture. The CSE-ID shall identify the CSE for the purpose of all interactions from / to the CSE within the M2M framework.

The M2M-Node-ID uniquely identifies the M2M node hosting the CSE and / or application. 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 the M2M service provider to bind the CSE-ID to a specific M2M node (an M2M node, hosting a CSE and / or Application (s) Node-ID. The M2M system shall allow the M2M Service Provider to set the CSE-ID and the M2M-Node-ID to the same value. specific M2M node.

The M2M-Sub-ID allows the M2M service provider to bind the application, M2M node, and CSEs to a specific M2M service subscription. Therefore, the M2M-Sub-ID belongs to the M2M service provider, identifies the subscription to the M2M service provider, enables communication with the M2M service provider, and is distinguished from the M2M Underlying Network Subscription Identifier It may be changed according to the change of M2M service provider. There are a number of M2M-Sub-IDs available for M2M-based networks (The M2M-Sub-ID enables the M2M Service Provider to bind application (s), M2M nodes, CSEs to a particular M2M service subscription. The M2M Service Provider is an M2M service provider that enables the M2M service provider to communicate with the M2M service provider. The M2M service provider is capable of communicating with the M2M service provider. There can be multiple M2M Service Subscription Identifiers per M2M Underlying Network subscription.).

The M2M-Request-ID (M2M Request Identifier) is an identifier that tracks the request initiated from the CSE in a one-to-one fashion. It is also included in the response to the request. The M2M-Request-ID is assigned by the CSE that initiated the request. A request initiated by the CSE may be the result of an application request, or it may be the result of a request automatically initiated by the CSE to satisfy the service. Here, the CSE that has received the request from the peer CSE must include the received M2M-Session-ID in all requests (including the case of the received request) that are generated by adding it, and may be combined with the received request if applicable . If applicable, the same M2M-Session-ID can be included in the interaction with the underlying network. The M2M-Request-ID must be globally unique (this is an identifier that tracks a Request initiated by a CSE end to end. The request is initiated by the CSE and may result in an Application Request, or a Request initiated autonomously by the CSE to fulfill a service. Request-ID in its interactions with the underlying network, where applicable. The CSE shall include the same. . An M2M-Request-ID allocated to a CSE shall be globally unique.

M2M-Ext-ID (M2M External Identifier) is an identifier used by M2M and is used when a service targeting the CSE identified by CSE-ID is requested from the underlying network. The M2M-Ext-ID allows the underlying network to identify the M2M device associated with the CSE-ID upon service request. As a result, the underlying network maps the M2M-Ext-ID to the base network identifier assigned to the target M2M device. In addition, the M2M SP must maintain a combination of CSE-ID, M2M-Ext-ID, and identification information of the underlying network. Pre-provisioning is supported, and plug-and-play coupling between CSE-ID and M2M-Ext-ID is also supported dynamically. (M2M Service Provider (M2M SP)), which identifies and identifies the M2M device associated with the underlying M2M service provider. In addition, the M2M SP shall maintain the association between the CSE-ID for the service request. To that effect, the Underlying Network maps the M2M-Ext-ID to the Underlying Network Identifier -ID, the M2M-Ext-ID and the identity of the underlying network. Both pre-provisioned and dynamic plug and play associations between the CSE-ID and the M2M-Ext-ID should be supported.

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

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

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

6 is a diagram illustrating an architecture of a common service object to which an embodiment of the present invention is applied. A common service entity includes a set of common service functions and a set of enabler functions. The Enabler functionality consists of a Service Extension Enabler and other Enablers. The Service Enabler allows the CSE to provide M2M services through Mca and Mcc reference points. . The Service Extension Enabler provides the following features: check policy authorizations, check for nodeless leases, check for interoperability between existing modules, and check policies and permissions to determine how to deal with conflicts, V) register a new module, vi) add a new service because the new module is added to the service list, vii) modify the API to reflect the new service capability, And viii) change the inter-module communication to combine the new modules. (The CSE comprises a set of Common Service Functions (CSFs) and a set of Enabler Functions (EFs). The Services Extension Enabler enables the CSE to offer M2M Services over the Mca and Mcc reference points. The Services Extension Enabler provides the following functions: 1. Check module authentication 2. Check node resources 3. Check interoperability with e 5. Register new module. 6. Add new module (s) to module to list of services. 7. Modify inter-module communications to incorporate new module capabilities.

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.

Subscription optimization, as described herein below, may mean that a node changes the reporting condition of a subscription target resource for one or more subscriptions, and the node may change the subscription information to minimize transmission resources or power usage It means all the operations. Thus, the subscription optimization below may refer to operations performed by the Subscription and Notification portion of the present invention.

7 is a diagram illustrating a configuration of an M2M service according to an embodiment of the present invention.

7, the M2M service configuration includes an underlying node 700, an intermediate node 710, an application service node 730, or an application dedicated node 720.

The application entity or the common service entity of the base node 700 becomes an issue requesting a subscription to a resource existing in the CSE of the intermediate node 710. [

The configuration of the intermediate node 710 will be described below. The application entity provides the application logic for an end-to-end M2M solution. The communication management delivery handling unit receives a message requesting creation of a first subscription to the resource from the issue resource, and transmits a message including the result of the first subscription to the issuer. Then, the subscription-notification unit generates a first subscription and performs a subscription optimization based on the first subscription and the second subscription by confirming the second subscription previously generated for the resource. The data management storage also indicates conditions of subscriptions optimized for application entities that modify resources based on optimized subscriptions.

The application node of the application dedicated node 720 or the application service node 730 receives the condition of the optimized subscription from the intermediate node 710 and generates data of the resource to be subscribed if the condition is satisfied, Lt; / RTI >

FIG. 8 is a signal diagram briefly illustrating a signal flow of an issue source, a node, and an application object according to an embodiment of the present invention.

The issue word 801 of the present invention may include an application entity of a base node or a common service entity. Node 802 may refer to an intermediate node and may include a hosting CSE and receive a subscription request message from an issuer. The application object 803 is an entity that manages a resource to be subscribed. It may be located at the same node as the hosting CSE, or may be located at a separate node. In this case, the separate node where the application object 803 is located may be an application dedicated node or an application service node. If the application object 803 is included in the same node as the hosting CSE, the hosting CSE and the application entity can exchange information using the internal interface. Hereinafter, the hosting CSE and the application entity described in this specification include both cases where they are configured in the same node or in a separate node as described above.

Referring to FIG. 8, a node 802 including a hosting CSE receives a request message for receiving a request message for requesting generation of a first subscription for the subscription target resource from the issuer 801 (S810).

The node 802 including the hosting CSE generates a first subscription based on the request message and determines whether there is a second subscription to the subscription target resource (S820). For example, the first subscription and the second subscription are generated by the subscription request information about the same subscription target resource, and the subscription conditions and the like may be set differently or the same.

If it is determined that the second subscription exists, the node 802 including the hosting CSE compares the criteria information of each of the first subscription and the second subscription to change the reporting condition of the subscription target resource (S830). The reference information includes a reporting condition for a subscription target resource, and includes information about an event condition for reporting a subscription target resource when a preset event occurs. In addition, it may contain information related to various criteria included in the subscription.

The node 802 including the hosting CSE transmits the changed reporting information to the application entity controlling the subscription target resource (S840). As described above, the hosting CSE and the application entity may reside in the same or different nodes.

In step S850, the application object 803 receives the reporting information of the subscription target resource from the hosting CSE, and changes the reporting condition to the received reporting condition if the reporting condition of the subscription target resource is related to a previously stored subscription target resource. If the received reporting condition is not related to an existing subscription target resource, a new subscription target resource is created and the received reporting condition is applied to the resource.

Thereafter, the application entity 803 determines whether an event satisfying the changed reporting condition occurs (S860). For example, it can be determined that an event has occurred only when the resource to be subscribed exceeds the reference number of the reporting condition. Or when the resource to be subscribed becomes smaller than the criterion of the reporting condition. The event may be set in a reporting condition or stored in an application object via a separate signal.

If it is determined that the event condition is satisfied, the application entity 803 may transmit the generated data according to the changed reporting information to the node 802 including the hosting CSE (S870). When the application object 803 and the hosting CSE are configured in the same node, the data can be transferred using the internal interface.

The node 802 including the hosting CSE may determine the occurrence of an event of the first subscription or the second subscription (S880), and may transmit the received data to the first subscription or the second subscription corresponding to the corresponding issue (S890). For example, according to the satisfaction of the reporting condition, the received data may be used to transmit the received data to the first subscription or the second subscription based on the reference information stored in the first subscription or the second subscription. That is, when the data transmission period of the first subscription is 2 and the transmission period of the second subscription is 4, the received data is transmitted to the first subscription in the transmission period 2. In addition, when the transmission period 4 of the second subscription is reached, the reception data can be respectively transmitted to the first subscription and the second subscription.

In FIG. 9, the signal flow of the present invention explained based on FIG. 8 will be described again in more detail.

9 is a diagram illustrating a message flow between one or more issue words according to an embodiment of the present invention, a hosting CSE that is requested to be subscribed from an issue, and an application entity that controls a resource to be subscribed.

Referring to FIG. 9, at least one issue word 901 transmits a message requesting creation of a subscription to a hosting CSE 902 in which a resource desired to be subscribed exists (S910). The hosting CSE 902 creates a subscription (S915) and retrieves whether there is an existing subscription (S920). If there is no existing subscription (NO in S920), a new reporting condition is transmitted to the application entity (S925). The application object (AE) 903 sets a new reporting condition for generating the resource data (S930).

If there is an existing subscription (YES in S920), a function of optimizing a criterion value of attributes of existing and new subscription resources is performed (S935). The optimization function is described in detail below. Then, the changed value of the existing reporting condition is transmitted to the application object 903 (S940, S945). The application object 903 updates the existing reporting condition for generating the resource data (S950). The hosting CSE 902 sends a response to the message requesting creation of the subscription to the issuer (S948). The step S948 is performed after the step S945, and the order of the step S950 and the step S950 is irrelevant.

On the other hand, if the reporting condition is satisfied, the application object 903 generates resource data and transmits it to the hosting CSE 902 (S955, S960). At this time, the hosting CSE 902 can confirm that a subscriber event has occurred and transmits a notification message of the resource change to the corresponding subscriber (S965, S970). Here, the subscriber refers to an issue 901 corresponding to the subscription. The issue word 901 transmits a response message to the notification message to the hosting CSE 902 (S975).

10 is a view for explaining an operation of a node including a host CSE according to an embodiment of the present invention.

A method of controlling a subscription target resource by a node including a hosting CSE (Common Services Entity) according to the present invention includes receiving a request message for requesting generation of a first subscription for a subscription target resource from an issuer The method comprising: a first step of generating a first subscription based on a message reception step and a request message and determining whether a second subscription to the subscription target resource is present; and determining whether a second subscription exists, A subscription information changing step of changing a reporting condition of the subscription target resource, and a transmitting step of transmitting the changed reporting information to the application object controlling the subscription target resource.

Referring to FIG. 10, the node includes a request message receiving step of receiving a request message requesting a first subscription creation for a subscription target resource (S1000).

In addition, the node includes a determination step of generating a first subscription based on the request message and determining whether there is a second subscription to the subscription target resource (S1002). In one example, a node generates a first subscription in response to a request message. Thereafter, it is determined whether there is a second subscription requesting the same subscription target resource as the subscription target resource to be the first subscription target. The second subscription may be a subscription created prior to the creation of the first subscription, or a subscription created with the first subscription.

Thereafter, the node performs the aforementioned subscription optimization. Specifically, the node includes a subscription information changing step of comparing the criteria information of each of the first subscription and the second subscription to change the reporting condition of the subscription target resource, when it is determined that the second subscription exists (S1004 ).

For example, in the case where the interval attribute information is included in each of the first subscription and the second subscription, the maximum common value of the first subscription interval attribute information and the second subscription interval attribute information is calculated, Can be changed. Specifically, when the interval attribute information value of the first subscription is 5 and the interval attribute information value of the second subscription is 20, the subscription information changing step may change the reporting condition by calculating 5, which is the greatest common divisor of 5 and 20 . That is, the subscription target resources that are the targets of the first subscription and the second subscription can be set to report the corresponding changed resource information at intervals of 5. In this case, the host CSE can transmit the subscription target resource information received in five cycles in five cycles as an issue corresponding to the first subscription according to the interval information of each subscription, and 20 cycles as the issuer corresponding to the second subscription . Thus, even if a separate subscription is created, the application object can provide data according to the greatest common denominator of the first subscription and the second subscription, without having to provide additional resources to be subscribed. Accordingly, data transmission / reception can be reduced and power consumption of each node or entity can be reduced.

As another example, the subscription information changing step may change the reporting condition of the subscription target resource by changing the comparison value (compareValue) based on the reference information of each of the first subscription and the second subscription. Specifically, the comparison value may be calculated as a minimum value or a maximum value of a comparison value of the first subscription and a comparison value of the second subscription, according to a relational operator of the reference information. For example, when the comparison value of the first subscription is greater than the relation operator of the second subscription (>), the comparison value of the first subscription is compared with the comparison value of the second subscription, You can change the setting. That is, the comparison value that can satisfy both the first subscription and the second subscription can be set as a comparison value of the changed reporting condition. In contrast, when the comparison value of the first subscription and the relational operator of the second subscription are both set to less than (<), the comparison value of the first subscription is compared with the comparison value of the second subscription, Can be set. It may also include the above-mentioned abnormality, and the following may also include the following.

In another example, the reference information may be included as a child resource indicating a notification criterion for the subscription target resource.

As another example, the subscription information change step may change the reporting condition of the subscription target resource when the first subscription or the second subscription is deleted. Specifically, when the subscription of one of the first subscription and the second subscription is deleted, it is necessary to re-change the reporting condition changed by the above-described method, so that the reporting condition of the subscription target resource can be re-changed according to the above- .

If there is no second subscription with the same subscription target resource as the first subscription, the node sends a message containing the base information for the first subscription to the application entity, and the application entity sends a message for reporting the first subscription A new condition can be set to provide a subscription target resource.

Meanwhile, the node may include a transmitting step of transmitting the changed reporting information to the application entity that controls the subscription target resource (S1006). When the application object is configured on the same node as the hosting CSE, the above-described reporting information can be transmitted through the internal interface.

On the other hand, the node receives the generated data according to the changed reporting information from the application entity, and transmits the data to the first subscription or the second subscription corresponding to the occurrence of the event of the first subscription or the second subscription . That is, the node receives the data according to the changed reporting condition, and if the generation of the data transfer event is satisfied based on the reference information or the subscription information of each subscription, the node can transmit the data in one or more of the issues according to the event satisfaction condition.

Hereinafter, a specific operation for performing the subscription optimization function including the subscription information changing step will be described with reference to FIG.

11 is a diagram illustrating a subscription optimization function according to an embodiment of the present invention.

The communication management delivery handling unit receives a message requesting creation of a subscription for the resource from the issue resource (S 1100). The subscription-notification unit confirms the authority for creating the subscription of the requestor, and generates a subscription for the resource (S1105, S1110).

Then, it is determined whether there is an existing subscription in the target resource of the request subscription (S1115). If there is an existing subscription, the value of the criterion among the attributes of the existing and new subscription resources is compared (S1120). It is determined whether there is an interval item of criteria (S1125). The interval item may include information on transmission of data or transmission interval of resources. If there is an interval item of criteria, the greatest common divisor of interval values of existing and new subscriptions is calculated (S1130). The greatest common denominator value can be an optimized value of the period that the M2M device changes the data of the resource to which the issue is subscribed.

On the other hand, it is determined whether the conditionCounter of the criteria is 1 (S1135). If the conditionCounter value of the criterion is 1 and the relational operator value is greater than (> YES) (YES in S1140), the minimum value among the comparison values (compareValue) of the existing and new subscriptions is calculated (S1145). The minimum value is the optimized value of the event type condition that the M2M device changes data of the resource to which the issue is subscribed.

If the conditionCounter value of the criteria is 1 and the relational operator value is smaller (<) (YES in S1150), the maximum value of the comparison values (compareValue) of the existing and new subscriptions (S1155). The minimum value is the optimized value of the event type condition that the M2M device changes data of the resource to which the issue is subscribed.

Although steps S1135 to S1155 are performed after step S1130, only steps S1135 to S1155 may be performed, and steps S1135 to S1155 may be performed separately from step S1130. have.

12 is a diagram for explaining operations of an application entity according to an embodiment of the present invention.

The present invention will be described with reference to an application object. The application object includes a step of receiving a reporting condition of a subscription target resource from a node including a hosting CSE (Common Services Entity) The method comprising the steps of: changing a reporting condition to a received reporting condition when the event is related to a resource, and transmitting an event of a subscription target resource to a node including a serving CSE (Common Services Entity) when an event satisfying the changed reporting condition occurs . &Lt; / RTI &gt;

Referring to FIG. 12, the application object includes receiving a reporting condition of a subscription target resource from a node including a hosting CSE (S1200). For example, the reporting condition of the received subscription target resource may include interval attribute information calculated as the greatest common value of the first subscription interval attribute information and the second subscription interval attribute information. As another example, the reporting condition of the received subscription target resource may include a changed comparison value (compareValue) based on the reference information of each of the first subscription and the second subscription. May be calculated as the minimum value or the maximum value of the comparison value of the first subscription and the comparison value of the second subscription according to the relational operator (relational operator). Meanwhile, the above-described reference information may be included as a child resource indicating a notification criterion for the subscription target resource.

The application object may be configured in a separate node from the node containing the hosting CSE. Or may be included in the same node as the node including the hosting CSE. When an application object is included in the same node, the application entity and the hosting CSE entity can exchange reporting condition information and the like via the internal data transfer interface and exchange data.

13 is a diagram illustrating an example in which reference information is included in a subscription resource according to an embodiment of the present invention.

13, in order to reflect the embodiment of the present invention in oneM2M standard, a "criteria" 1300 indicating a notification criterion for a resource in a <Subscription> resource described in oneM2M TS 0001 is referred to as an attribute attribute can be changed to a child resource display.

14 is a diagram exemplarily showing the structure of criteria resources.

Referring to FIG. 14, a structure of a criteria resource indicated by a lower resource may be defined as shown in FIG. 14, and a criterion resource attribute may be defined as shown in [Table 1].

<criteria> Resource attribute (attribute) Attribute Name Multiplicity RW /
RO /
WO Description interval 0..1 RW The interval for reporting conditionCounter One RW The number of conditions for a subscriber relationalOperator 0..n RW operator that tests or defines some kind of relation between two entities
less than or equal to (=), less than or equal to (=), less than or equal to (=), less than or equal to (=), compareValue 0..n RW The value of comparing with resource logicalOperator 0..n-1 RW The symbol is used to connect two or more sentences of a natural language (eg, AND, OR, NOT)

15 is a diagram illustrating a configuration of a node including a hosting CSE according to an embodiment of the present invention.

The node 1500 including the hosting CSE according to the present invention may perform a Communication Management and Delivery Handling (CSM) for receiving a request message for requesting a subscription creation request for a subscription target resource from an issuer, ) Unit 1510 and the request message to determine whether there is a second subscription to the subscription target resource, and if it is determined that a second subscription exists, the first subscription and the second subscription, respectively, A subscription and notification unit 1520 for comparing the criteria information of the subscription target resource with the subscription and notification unit 1520 for changing the reporting condition of the subscription target resource and data management for transferring the changed reporting information to the application object for controlling the subscription target resource (Data Management & Repository) unit 1530.

15, a communication management and delivery handling unit 1510 receives a message requesting creation of a first subscription to an subscription target resource from an issuer, You can send a message that contains the results for the subscription.

Subscription and Notification unit 1520 generates subscription and subscription optimization based on the first subscription and the second subscription by creating a first subscription and identifying a second subscription previously created for the resource, Can be performed. Specifically, when the interval attribute information is included in each of the first subscription and the second subscription, the subscription-notification unit 1520 calculates a maximum common value of the first subscription interval attribute information and the second subscription interval attribute information So that the reporting condition can be changed. Alternatively, the subscription-notification unit 1520 may change the comparison condition (compareValue) based on the reference information of the first subscription and the second subscription to change the reporting condition of the subscription target resource. Here, the comparison value may be calculated as a minimum value or a maximum value among a comparison value of the first subscription and a comparison value of the second subscription, according to a relational operator of the reference information. The reference information may be included as a child resource indicating a notification criterion for the resource to be subscribed. For example, the criteria information includes information on the number of event type conditions (conditionCounter) as attribute information, time interval information (interval), relation operator information (relationOperator), comparison value information (compareValue) Operator information (logicalOpeartor). Or the subscription-notification unit 1520 can re-change the reporting condition of the subscription target resource when the first subscription or the second subscription is deleted. When the first subscription or the second subscription is updated, the subscription-notification unit 1520 may re-optimize the subscription for the resource.

The Data Management & Repository unit 1530 can indicate the condition of the subscription optimized for the application entity that changes the resource based on the optimized subscription.

Meanwhile, the data management & repository unit 1530 receives data generated according to the changed reporting information from the application entity, and the communication management and delivery handling unit 1510 1 &lt; / RTI &gt; subscription or an occurrence of an event of the second subscription, the data may be transmitted as an issue corresponding to the first subscription or the second subscription.

As described above, the operation of each configuration of the node performing the subscription optimization is summarized once again.

The communication management and delivery handling unit 1510 receives the subscription creation request for the resource from the issuer and provides it to the subscription and notification unit 1520. The subscription-notification unit 1520 performs authorization checking for creation of the subscription of the issuer, and generates a subscription for the resource. In addition, the subscription-notification unit 1520 compares 'criteria' indicating the notification criteria for the resources of the existing subscription and the new subscription. Then, the subscription-notification unit 1520 calculates the greatest common divisor of the time interval information in order to optimize the time interval information of the 'criteria'. Also, the subscription-notification unit 1520 may calculate the minimum value or the maximum value according to the relational operator information on the value of the resource and the comparison value in order to optimize the event type condition of 'criteria'.

16 is a diagram illustrating a configuration of an application entity according to an embodiment of the present invention.

The application object 1600 according to the present invention includes a CSE interface 1610 for receiving a reporting condition of a subscription target resource from a node including a hosting CSE (Common Services Entity), and a subscription target resource The resource control unit 1620 changes the reporting condition to the received reporting condition.

In addition, when an event satisfying the changed reporting condition occurs, the CSE interface unit 1610 can transmit the data of the subscription target resource to the node including the CSE (Common Services Entity).

As described above, the hosting CSE and the application entity of the present invention may be configured in one node. That is, the present invention includes a hosting CSE of an M2M system composed of one or more issuers and a common CSE (Common Services Entity) that is requested to be subscribed from an issuer and an application entity that controls resources to be subscribed Node.

17 is a diagram showing an expected effect when the subscription optimization function according to an embodiment of the present invention is applied to the CSE.

17, when N application entities make a subscription request with different time intervals, in a CSE without a subscription optimization function (AS-IS portion in FIG. 17), every N application subscription requests, The user must transmit the reporting period message every time. When the M2M device receives the reporting period message, a Job (a kind of process) for processing it is generated and operated. In the CSE, the reporting period message is transmitted to the M2M device by the number of the subscription requests of the application entities, and in the M2M device, a lot of jobs are generated to process the same. In general, M2M devices have limited computing resources, so the number of jobs that can be generated is limited. In addition, as the number of jobs increases, the number of messages reporting the processed result increases, so network traffic between the M2M device and the CSE also increases, and the battery consumption to process the increasing reporting messages also increases.

When the subscription optimization function of the present invention is applied to the CSE (TO-BE portion in FIG. 17), when N application entities make a subscription request with different time intervals, the CSE sends a subscription optimization function to the M2M device You can optimize the reporting period messages you send. That is, the reporting period message according to the subscription request of the application object 1 is transmitted to the M2M device. Upon receiving the reporting period message, the M2M device generates and operates a job (a kind of process) for processing the message. When Application Object 2 makes a subscription request, the CSE does not generate and deliver a separate reporting period message through the subscription optimization function. Instead, it sends an interval value with the same message ID as the reporting period message sent earlier by Application Object 1 to the optimized time As shown in FIG. This will not create a new job because the M2M device will process this message in Job # 1. Also, the time interval is set to the optimized time, and the number of reporting to the CSE is also reduced.

Accordingly, the subscription optimization function of the present invention reduces the number of jobs generated by the M2M device, thereby reducing computing resources and battery usage, reducing the number of reporting times that the M2M device sends to the CSE, thereby reducing the network traffic between the two nodes You can expect.

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.

110: Application
120: Common Services
130: Infrastructure Network Services
700: Base Node
710: intermediate node
720: application-only node
730: application service node

Claims (20)

CLAIMS 1. A method for controlling a subscription target resource by a node comprising a hosted Common Services Entity (CSE)
Receiving a request message for requesting generation of a first subscription for a subscription target resource from an issuer;
A determination step of generating the first subscription based on the request message and determining whether there is a second subscription to the subscription target resource;
A subscription information changing step of comparing the criteria information of each of the first subscription and the second subscription to change the reporting condition of the subscription target resource if it is determined that the second subscription exists; And
And transmitting the changed reporting information to an application entity that controls the subscription target resource.
The method according to claim 1,
The subscription information changing step includes:
Wherein when the first subscription and the second subscription include interval attribute information, a maximum common value of the first subscription interval attribute information and the second subscription interval attribute information is calculated to change the reporting condition &Lt; / RTI &gt;
The method according to claim 1,
The subscription information changing step includes:
And changing the comparison value (compareValue) based on the reference information of each of the first subscription and the second subscription to change the reporting condition of the subscription target resource.
The method of claim 3,
The comparison value is a value
Wherein the minimum value or the maximum value is calculated as a comparison value of the first subscription and a comparison value of the second subscription according to a relational operator of the reference information.
The method according to claim 1,
The reference information includes:
And a child resource indicating a notification criterion for the subscription target resource.
The method according to claim 1,
The subscription information changing step includes:
And if the first subscription or the second subscription is deleted, re-changing the reporting condition of the subscription target resource.
The method according to claim 1,
Receiving data generated according to the changed reporting information from the application entity; And
Further comprising transmitting the data to the first subscription or the second subscription corresponding to the occurrence of the event in the first subscription or the second subscription.
As to how an application object manages a subscription target resource,
Receiving a reporting condition of a subscription target resource from a node including a hosting CSE (Common Services Entity);
Changing a reporting condition to the received reporting condition when the reporting condition of the subscription target resource is related to a previously stored subscription target resource; And
And transmitting data of the subscription target resource to a node including the CSE (Common Services Entity) when an event satisfying the changed reporting condition occurs.
9. The method of claim 8,
Wherein the reporting condition of the received subscription target resource includes:
And interval attribute information calculated as the greatest common value of the first subscription interval attribute information and the second subscription interval attribute information.
9. The method of claim 8,
Wherein the reporting condition of the received subscription target resource includes:
And a modified comparison value (compareValue) based on the reference information of each of the first subscription and the second subscription.
11. The method of claim 10,
The comparison value is a value
Wherein the minimum value or the maximum value is calculated as a comparison value of the first subscription and a comparison value of the second subscription according to a relational operator of the reference information.
11. The method of claim 10,
The reference information includes:
And a child resource indicating a notification criterion for the subscription target resource.
A node comprising a hosting Common Services Entity (CSE) controlling a subscription target resource,
A Communication Management and Delivery Handling unit for receiving a request message requesting a first subscription to the subscription target resource from an issuer;
Determining whether there is a second subscription to the subscription target resource based on the request message; if the second subscription exists, determining whether the first subscription and the second subscription exist A Subscription and Notification unit for comparing the criteria of the subscription target resource with the criteria of the subscription target resource to change the reporting condition of the subscription target resource; And
And a data management & repository unit for transmitting the changed reporting information to an application entity that controls the subscription target resource.
14. The method of claim 13,
The Subscription and Notification section may include:
Wherein when the first subscription and the second subscription include interval attribute information, a maximum common value of the first subscription interval attribute information and the second subscription interval attribute information is calculated to change the reporting condition &Lt; / RTI &gt;
14. The method of claim 13,
The Subscription and Notification section may include:
And changes the comparison value (compareValue) based on the reference information of each of the first subscription and the second subscription to change the reporting condition of the subscription target resource.
16. The method of claim 15,
The comparison value is a value
Wherein the minimum value or the maximum value is calculated as a comparison value of the first subscription and a comparison value of the second subscription according to a relational operator of the reference information.
14. The method of claim 13,
The reference information includes:
Wherein the node is included as a child resource indicating a notification criterion for the subscription target resource.
14. The method of claim 13,
The Subscription and Notification section may include:
And re-changing the reporting condition of the subscription target resource when the first subscription or the second subscription is deleted.
14. The method of claim 13,
The Data Management & Repository may receive data generated according to the changed reporting information from the application entity,
Wherein the communication management and delivery handling unit transmits the data to the first subscription or the second subscription based on an event occurrence of the first subscription or the second subscription. Node.
An application object for managing a resource to be subscribed, comprising:
A CSE interface unit for receiving a reporting condition of a subscription target resource from a node including a hosting CSE (Common Services Entity); And
And a resource control unit for changing the reporting condition to the received reporting condition when the reporting condition of the subscription target resource is related to a previously stored subscription target resource,
Wherein the CSE interface unit transmits data of the subscription target resource to a node including the CSE (Common Services Entity) when an event satisfying the changed reporting condition occurs.

Images