WO2017175954A1 - Method for processing subscriptions for multiple resources in wireless communication system and apparatus therefor - Google Patents

Abstract

A method for processing a resource generation request associated with a multi-level subscription in a wireless communication system according to an embodiment of the present invention is performed by a reception device and may comprise the steps of: receiving a resource generation request from a source device; generating a resource according to the resource generation request; and when the generated resource is a multi-level subscription resource, adding a subscription link to a child resource of the corresponding subscription resource satisfying a level indicating the coverage of the multi-level subscription resource.

Description

Method and apparatus for processing subscription for multiple resources in wireless communication system

The present invention relates to a method and apparatus for processing a subscription for multiple resources in a wireless communication system.

The subscription / notification function is a data exchange technique between an event and a push-based application, and is widely used in an internet of things service. However, in the conventional RESTful system, a mechanism for setting a subscription to specific information (resource) desired is expressed as a method of setting one subscription to one resource. The present invention proposes a method of processing a subscription for multiple resources as the generation of one subscription resource, and these methods can effectively solve the problems that may occur at this time.

The present invention proposes a method for processing a subscription for multiple resources.

Technical problems to be achieved by the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned above are apparent to those skilled in the art from the following detailed description. Can be understood.

A method for processing a resource creation request associated with a multi-level subscription in a wireless communication system in accordance with an embodiment of the present invention, the method being performed by a receiving device and receiving a resource creation request from a source device. step; Generating a resource according to the resource creation request; And if the generated resource is a multi-level subscription resource, adding a subscription link to a child resource of a target resource of the subscription resource that satisfies a level indicating a coverage range of the multi-level subscription resource. .

Additionally or alternatively, when setting a notification according to the multi-level subscription resource for all child resources of the target resource of the subscription resource, the level of the subscription resource may be set to an integer rather than a positive integer.

Additionally or alternatively, whether the generated resource is a multi-level subscription resource may be determined by a value of an attribute indicating a level indicating a coverage of the generated resource.

Additionally or alternatively, the subscription link may include an identifier of the generated multi-level subscription resource.

Additionally or alternatively, the subscription link may include a level indicating the coverage of the generated multi-level subscription resource and / or the level of the corresponding child resource.

Additionally or alternatively, the method may further include determining that if the generated resource is not a subscription resource, the parent resource of the generated resource has a multi-level subscription resource as a subscription link or child resource in a range that includes the generated resource The method may further include determining whether or not.

Additionally or alternatively, the method corresponds to the generated resource if the parent resource of the generated resource has a multi-level subscription resource as a subscription link or a child resource in a range that includes the generated resource. The method may further include adding a multi-level subscription resource or information of the multi-level subscription resource as a subscription link.

Additionally or alternatively, the method further comprises determining whether the generated resource is a subscribable resource type and whether the creator of the multi-level subscription resource has permission to create a subscription to the generated resource. It may include.

In addition or alternatively, the method may further comprise, if the generated resource is of a subscribable resource type, and if the creator of the multi-level subscription resource has permission to create a subscription to the generated resource; The method may further include adding an activity indicator to the subscription link.

According to another embodiment of the present invention, a receiving apparatus configured to process a resource generation request associated with a multi-level subscription in a wireless communication system, comprising: a transmitter; receiving set; And a processor configured to control the transmitter and the receiver, the processor receiving a resource generation request from a source device, generating a resource in accordance with the resource generation request, and wherein the generated resource is multi- If it is a level subscription resource, it may be configured to add a subscription link to a child resource of a target resource of the subscription resource that satisfies the level indicating the coverage of the multi-level subscription resource.

Additionally or alternatively, when setting a notification according to the multi-level subscription resource for all child resources of the target resource of the subscription resource, the level of the subscription resource may be set to an integer rather than a positive integer.

Additionally or alternatively, whether the generated resource is a multi-level subscription resource may be determined by a value of an attribute indicating a level indicating a coverage of the generated resource.

Additionally or alternatively, the subscription link may include an identifier of the generated multi-level subscription resource.

Additionally or alternatively, the subscription link may include a level indicating the coverage of the generated multi-level subscription resource and / or the level of the corresponding child resource.

Additionally or alternatively, if the generated resource is not a subscription resource, the processor may determine whether the parent resource of the generated resource has a multi-level subscription resource as a subscription link or child resource in a range that includes the generated resource. It can be configured to determine whether.

Additionally or alternatively, if the parent resource of the generated resource has a multi-level subscription resource as a subscription link or child resource in the range that includes the generated resource, the processor corresponds to the generated link to the subscription link. Multi-level subscription resources or information of the multi-level subscription resources can be configured as a subscription link.

Additionally or alternatively, the processor may be configured to determine whether the generated resource is a subscribable resource type and whether the creator of the multi-level subscription resource has the right to create a subscription for the generated resource. have.

Additionally or alternatively, if the generated resource is a subscribable resource type, and if the creator of the multi-level subscription resource has the authority to create a subscription to the generated resource, the processor is configured to It can be configured to add an activity indicator to a subscription link.

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

According to an embodiment of the present invention, by generating a multi-level subscription resource through the creation of a single subscription resource, a notification service for multiple resources is possible. In addition, it is possible to identify the information on the resource in which the event occurred among the various target resources in the notification message by a single multi-level subscription configuration.

In addition, when creating a new resource, complexity may be reduced since only the information of the immediate parent resource needs to be referred to to search for a multi-level subscription for the generated resource.

The effects according to the present invention are not limited to the above-mentioned effects, and other effects not mentioned above may be clearly understood by those skilled in the art from the detailed description of the present invention. There will be.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are included as part of the detailed description in order to provide a thorough understanding of the present invention, provide an embodiment of the present invention and together with the description, illustrate the technical idea of the present invention.

1 illustrates a functional structure in an M2M communication system.

2 illustrates a configuration supported by the M2M communication system based on the M2M function structure.

3 illustrates a common service function provided in an M2M communication system.

4 illustrates a resource structure present in an M2M application service node and an M2M infrastructure node.

5 illustrates resource structures present in M2M application service nodes (eg, M2M devices) and M2M infrastructure nodes.

6 illustrates a procedure of exchanging request and response messages used in an M2M communication system.

7 shows the structure of a <accessControlPolicy> resource.

8 shows a registration procedure in an M2M communication system.

9 illustrates operations associated with a subscription service.

10 illustrates operations associated with a subscription service.

11 illustrates a monitoring range according to a subscription resource or service.

12 illustrates a notification in accordance with a multi-level subscription setting according to an embodiment of the present invention.

13 illustrates a multi-level subscription setting or a new resource generation procedure using the same according to an embodiment of the present invention.

14 illustrates an example of a multi-level subscription setting according to an embodiment of the present invention.

15 illustrates an example of a multi-level subscription setting according to an embodiment of the present invention.

16 illustrates a procedure of notification message transmission according to a multi-level subscription setup according to an embodiment of the present invention.

17 shows a block diagram of an apparatus configured to perform embodiment (s) of the present invention.

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

In some instances, well-known structures and devices may be omitted or shown in block diagram form centering on the core functions of the structures and devices in order to avoid obscuring the concepts of the present invention. In addition, the same components will be described with the same reference numerals throughout the present specification.

In the present invention, a device for device-to-device communication, that is, an M2M device may be fixed or mobile, and various devices that communicate with a server for device-to-device communication, that is, an M2M server, transmit and receive user data and / or various control information. Belongs. The M2M device may include a terminal equipment, a mobile station (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, a personal digital assistant (PDA), a wireless modem. may be referred to as a wireless modem, a handheld device, or the like. Further, in the present invention, M2M server generally refers to a fixed station that communicates with M2M devices and / or other M2M servers, and communicates with M2M devices and / or other M2M servers to control various data and controls. Exchange information.

Hereinafter, the technology related to the present invention will be described.

M2M application

An application that executes service logic and uses a common service entity (CSE) that is accessible through an open interface. M2M applications can be installed or mounted on M2M devices, M2M gateways, or M2M servers.

M2M Common Services

The set of features that M2M CSE makes available through standardized interfaces

oneM2M defines a common M2M service framework (or service platform, common service entity (CSE), etc.) for various M2M applications (or application entities (AEs)). M2M applications are software that implements service logic such as e-Health, City Automation, Connected Consumer, Automotive, etc.The oneM2M service framework includes the functions that are common to implement these various M2M applications. have. Thus, using the oneM2M service framework, these M2M applications can be easily implemented without having to configure each framework required for various M2M applications. It can integrate the M2M market, which is currently divided into multiple M2M verticals such as Smart Building, Smart Grid, e-Health, Transportation, Security, etc. around a common oneM2M service framework, which will greatly facilitate the M2M market. It is expected to be.

1 illustrates a functional structure in an M2M communication system. Describe each entity.

Application entity (AE, 101): The application entity provides the application logic for the end-to-end M2M solution. Examples of AEs include cargo tracking, remote blood sugar monitoring, remote power measurement and control applications. (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.) It may be referred to as an M2M application.

Common Service Entity (CSE, 102): The CSE consists of the service functions defined in oneM2M that are common to the M2M environment. These service functions can be used by registered AEs and other CSEs exposed through reference points Mca and Mcc. The reference point Mcn is used to access the services of the underlying network. (A Common Services Entity comprises the set of "service functions" that are common to the M2M environments and specified by one M2M. Such service functions are exposed to other entities through Reference Points Mca and Mcc.Reference point Mcn is used for accessing Underlying Network Service Entities.)

Examples of service functions provided by the CSE include data management, device management, M2M subscription management, and location services. These functions can be logically divided into Common Services Functions (CSF). Some CSFs in a CSE must be present and some may optionally be present. In addition, some of the functions in the CSF must exist and some of the functions can optionally be present. (Eg, within the “device management” CSF, some of the application software installation, firmware updates, logging, and monitoring are mandatory and some are optional.)

Underlying Network Service Entity (NSE) 103: The NSE provides services to the CSE, such as device management, location services, device triggering, and the like. N Underlying Network Services Entity provides services to the CSEs.Examples of such services include device management, location services and device triggering.No particular organization of the NSEs is assumed.Note: Underlying Networks provide data transport services between entities in the one M2M system.Such data transport services are not included in the NSE.)

In addition, it will be described for each reference point shown in FIG.

Mca reference point

The Mca reference point is the reference point between the AE and the CSE. The Mca reference point allows the AE to communicate with the CSE so that the AE can use the services provided by the CSE. (This is the reference point between an Application Entity and a CSE.The Mca reference point shall allow an Application Entity to use the services provided by the CSE, and for the CSE to communicate with the Application Entity.)

Services provided through the Mca reference point depend on the functions provided by the CSE. AEs and CSEs can be on the same physical device or on different physical devices. (The services offered via the Mca reference point are thus dependent on the functionality supported by the CSE.The Application Entity and the CSE it invokes may or may not be co-located within the same physical entity.)

Mcc reference point

The Mcc reference point is the reference point between two CSEs. The Mcc reference point allows the CSE to use the services of other CSEs. The services provided through the Mcc reference point depend on the functions provided by the CSE. (This is the reference point between two CSEs.The Mcc reference point shall allow a CSE to use the services of another CSE in order to fulfill needed functionality.Depending on, the Mcc reference point between two CSEs shall be supported over different M2M physical entities. The services offered via the Mcc reference point are dependent on the functionality supported by the CSEs)

Mcn reference point

Mcn reference point is the reference point between the CSE and the NSE. The Mcn reference point allows the CSE to use the services provided by the NSE. (This is the reference point between a CSE and the Underlying Network Services Entity.The Mcn reference point shall allow a CSE to use the services (other than transport and connectivity services) provided by the Underlying Network Services Entity in order to fulfill the needed functionality Services provided by the NSE mean more than simple services such as transport and connectivity services, and services such as device triggering, small data transmission, and positioning. Is an example.

Mcc ’reference point

The Mcc 'reference point is used for communication between CSEs belonging to different M2M service providers. The Mcc 'reference point may be similar in that it links the Mcc reference point and the CSE, but if the existing Mcc reference point was confined to communication within a single M2M service provider, the Mcc' reference point would extend the Mcc to different M2M service providers. Can be seen as a concept.

2 illustrates a configuration supported by the M2M communication system based on the M2M function structure. The M2M communication system is not limited to the illustrated configuration and can support more diverse configurations. First of all, the concept of a node, which is important for understanding the illustrated configuration, will be described.

Application Dedicated Node (ADN): An Application Dedicated Node is a Node that contains at least one Application Entity and does not contain a Common Services Entity. The Mca reference point can be connected to one middle node or one infrastructure node. ADN may exist in an M2M device.

Application Service Node (ASN): An Application Service Node is a Node that contains one Common Services Entity and contains at least one Application Entity. The Mcc reference point can be connected to one middle node or one infrastructure node. The ASN can exist in the M2M device.

Middle Node (MN): A Middle Node is a Node that contains one Common Services Entity and may contain Application Entities. A Middle Node communicates over a Mcc references point with at least two other Nodes among either (not exclusively):

One or more application service nodes (ASNs);

One or more middle nodes (MNs);

One infrastructure node (IN).

In addition, the MN may be connected through the ADN and the Mca reference point. MN may be present in the M2M gateway.

Infrastructure Node (IN): An Infrastructure Node is a Node that contains one Common Services Entity and may contain Application Entities. IN may be present in the M2M server.

The infrastructure node may communicate with the following nodes through the MN or ASN and the Mcc reference point. (An Infrastructure Node communicates over a Y reference point with either:

One or more middle node (s);

And / or one or more application service node (s)

Infrastructure nodes can communicate via ADN and Mca reference points. (An Infrastructure Node may communicate with one or more Application Dedicated Nodes over one or more respective Mca reference points.)

3 illustrates a common service function provided in an M2M communication system.

M2M service functions (ie, common service functions) provided by the M2M communication system include 'Communication Management and Delivery Handling', 'Data Management and Repository', 'Device Management', 'Discovery' and 'Group as shown in FIG. Management "," Addressing and Identification "," Location "," Network Service Exposure, Service Execution and Triggering "," Registration "," Security "," Service Charging and Accounting "," Session Management "," Subscription and Notification " have.

Below is a brief introduction of each function.

Communication Management and Delivery Handling (CMDH): Provides communication with other CSEs, AEs, and NSEs and plays a role in how messages are delivered.

Data Management and Repository (DMR): M2M application to exchange and share data.

Device Management (DMG): Plays a role for managing M2M devices / gateways. Detailed features include application installation and settings, configuration settings, firmware updates, logging, monitoring, diagnostics, and topology management.

Discovery (DIS): It is used to find resources and information based on conditions.

Group Management (GMG): A group can be created by grouping resources, M2M devices, or gateways. It manages requests related to groups.

Addressing and Identification (AID): Identifies and addresses physical or logical resources.

Location (LOC): M2M applications are responsible for obtaining the location information of the M2M device or gateway.

Network Service Exposure, Service Execution and Triggering (NSE): Enables communication of the underlying network and enables the use of the functions provided by the underlying network.

Registration (REG): An M2M application or other CSE is responsible for handling registration with a particular CSE. Registration is performed to use the M2M service function of a specific CSE.

Security (SEC): Handles sensitive data such as security keys, establishes security associations, authenticates, authorizes, and protects identity.

Service Charging and Accounting (SCA): Provides charge-adding functionality to the CSE.

Session Management (SM): Manages M2M sessions for end-to-end communication.

Subscription and Notification (SUB): When a subscription is made to a specific resource, it plays a role in notifying that the resource is changed.

These M2M common service functions are provided through the CSE, and the AE (or M2M applications) can use the common service functions through the Mca reference point or another CSE through the Mcc reference point. In addition, the M2M common service function may operate in conjunction with an Underlying Network (or Underlying Network Service Entity (NSE), for example, 3GPP, 3GPP2, WiFi, Bluetooth).

Not all devices / gateways / infrastructures have all the higher functionality. It may have some of the required functions and optional functions.

In an M2M communication system, a resource is used for organizing and representing information in an M2M communication system and means anything that can be identified by a URI. The resources may be classified into general resources, virtual resources, and announced resources. The definition of each resource is as follows.

Virtual Resources: Virtual resources are used to trigger specific processing and / or retrieve results, but are not permanently present in the CSE.

Announced Resource: An announced resource is a resource in a remote CSE that is connected to the original (or notified) source resource. Announced resources retain some of the characteristics of the original resource. Resource announcements facilitate resource discovery or discovery. The announced resource in the remote CSE is used to create child resources in the remote CSE that do not exist as children of the original resource or are not known children of the original resource.

Generic Resource: If not specified as either "virtual" or "announced", the resource is a generic resource.

4 illustrates a resource structure present in an M2M application service node and an M2M infrastructure node.

The M2M communication system defines various resources (or resources) that can be manipulated to perform M2M services, such as registering applications and reading sensor values. The resource is configured in a tree structure, and logically connected to the CSE or stored in the CSE and stored in an M2M device, an M2M gateway, a network domain, and the like. In this aspect, the CSE may be referred to as an entity that manages resources. The resource has <cseBase> as a tree root, and a representative resource is as follows.

<cseBase> resource: The root resource of the tree-organized M2M resource, including all other resources.

<remoteCSE> Resource: A resource existing under <cseBase> that contains information of other CSEs registered (connected) to the CSE.

<AE> Resource: Resource that exists under <cseBase> or <remoteCSE> resource. If it exists under <cseBase>, information of applications registered (connected) to the relevant CSE is stored.If present under <remoteCSE> The information of applications registered in another CSE (with a CSE name) is stored.

<accessControlPolicy> resource: A resource that stores information related to access rights for a specific resource. Authorization is performed using the access authority information included in this resource.

<container> Resource: Resource that stores data by CSE or AE.

<group> resource: A resource that provides the ability to group multiple resources together and process them together.

<subscription> resource: A resource that performs a function of notifying that the status of a resource, etc. is changed through notification.

5 illustrates resource structures present in M2M application service nodes (eg, M2M devices) and M2M infrastructure nodes.

For example, a method in which an AE (application2) registered in an M2M infrastructure node reads a sensor value of an M2M device will be described. The sensor usually refers to a physical device, and the AE (application1) existing on the M2M device reads the value from the sensor and stores the value read in the form of container resource in the registered CSE (CSE1). For this purpose, the AE existing on the M2M device must be registered in the CSE existing in the M2M device first. When registration is completed, M2M application related information registered in the form of cseBaseCSE1 / application1 resource is stored as shown in FIG. 5.

If the sensor value is stored in the container resource under the cseBaseCSE1 / application1 resource by the AE existing on the M2M device, the AE registered in the infrastructure node may access the value. In order to be accessible, the AE registered in the infrastructure node must also be registered in the CSE (CSE2) of the infrastructure node, which is similar to the method in which the application1 registers in the CSE1 for the application2 in the cseBaseCSE2 / application2 resource. By storing the information. In addition, application1 communicates with CSE1 and CSE2 in the middle instead of directly with application2. To do this, CSE1 must be registered in CSE2. When CSE1 is registered in CSE2, CSE1 related information (eg, Link) is stored in the <remoteCSE> resource type under the cseBaseCSE2 resource. That is, <remoteCSE> provides the CSE type, access address (IP address, etc.), CSE ID, and reachability information for the registered CSE.

Meanwhile, resource discovery refers to a process of discovering a resource in a remote CSE. Resource search is done through a RETRIEVE request. To retrieve a resource, a request for retrieval includes:

<startURI>: Indicates a URI, which can be used to limit the range of resources for which resource searches will be performed. If <startURI> points to <cseBase>, which is the root of the resource, resource search is performed for all resources of the receiver who received this retrieve request. The receiver performs resource discovery only for the resource indicated by <startURI> and its subordinate resources.

filterCriteria: This information describes information related to the resource to be searched. The receiver searches only those resources that satisfy the filterCriteria among the resources within the resource search range defined by <startURI>, and sends them to the requestor of this request.

As illustrated in FIG. 4 or 5, in the M2M system, a resource may be represented as a tree structure, and the type of a root resource is represented as <CSEBase>. Therefore, the <CSEBase> resource type must be present if there is a common service entity (CSE).

6 shows a general communication flow on Mca and Mcc reference points. The operation of the M2M system is performed based on the data exchange. For example, in order for the first device to transmit or perform a command for stopping a specific operation of the second device, the first device must transmit the command to the second device in data form. In an M2M system, data can be exchanged in request and response messages on the connection between the application (or CSE) and the CSE.

The request message includes the following information.

Operation: Type of operation to be executed (either Create / Retrieve / Update / Delete / Notify)

To: The ID of the entity to receive the request (ie the ID of the receiver)

From: ID of the sender that made the request

Request Identifier: The ID of the request message (ID used to identify the request message).

Group Request Identifier parameter (identifier to prevent duplicate group fan-out request messages)

Content: The content of the resource being passed

The response message includes the following information. First, if the request message has been successfully processed, the response message

To: ID of the sender that made the request

From: ID of the receiver that received the request

Request Identifier: The ID of the request message (ID used to identify the request message).

Result status code: the result of processing the request (for example, Okay, Okay and Done, Okay and in progress)

Content: The content of the resource being delivered (only results can be delivered)

And if the processing of the request message fails, the response message

To: ID of the sender that made the request

From: ID of the receiver that received the request

Request Identifier: The ID of the request message (ID used to identify the request message).

Result status code: The result of processing the request and the reason / code for failure (eg Not Okay).

It may include.

Meanwhile, various resource types exist as shown in the following table.

Resource Type	Short Description	Child Resource Types	Parent Resource Types
AE	Stores information about the AE. Registrar Created as a result of successful registration of CSEs and AEs) Stores information about the AE. It is created as a result of successful registration of an AE with the registrar CSE).	subscription, container, group, accessControlPolicy, mgmtObj, commCapabilities, pollingChannel	remoteCSE, CSEBase
cmdhNwAccessRule	Defines a rule for the usage of underlying networks.	schedulesubscription	cmdhNetworkAccessRules
CSEBase	It is a structural root for all resources on the CSE. The structural root for all the resources that are residing on a CSE.It shall store information about the CSE itself.	remoteCSE, node, application, container, group, accessControlPolicy, subscription, mgmtObj, mgmtCmd, locationPolicy, statsConfig	None
group	Stores information about resources of the same type that need to be processed into groups. Operations information about resources of the same type that need to be addressed as a Group.Operations addressed to a Group resource shall be executed in a bulk mode for all members belonging to the Group).	fanOutPointsubscription	Application, remoteCSE, CSEBase
locationPolicy	Includes information for obtaining and managing geographic locations. Includes information to obtain and manage geographical location.It is only referred from container, the contentInstances of the container provides location information.	subscription	CSEBase
remoteCSE	Represents a remote CSE for which there has been a registration procedure with the registrar CSE identified by the CSEBase resource.	application, container, group, accessControlPolicy, subscription, mgmtObj, pollingChannel, node	CSEBase
subscription	Represents subscription information related to a resource. Subscription resource represents the subscription information related to a resource. Such a resource shall be a child resource for the subscribe-to resource.	schedule	accessControlPolicy, application, cmdhBuffer, cmdhDefaults, cmdhEcDefParamValues, cmdhDefEcValue, cmdhLimits, cmdhNetworkAccessRules, cmdhNwAccessRule, cmdhPolicy, container, CSEBase, delivery, eventConfig, execInstance, group, contentInstance, locationPolicy, mgmtCmd, mgmtObj, m2CService request, schedule, statsCollect, statsConfig
container	Sharing data instances between entities. Shares data instances among entities.Used as a mediator that takes care of buffering the data to exchange "data" between AEs and / or CSEs).	container, contentInstance, subscription	application, container, remoteCSE, CSEBase
contentInstance	Represents a data instance in the container resource.	subscription	container

Each resource type may be located under a parent resource type of the corresponding resource type and may have a child resource type. Each resource type also has attributes, in which the actual values are stored.

Next, Table 2 below defines the attributes of the <container> resource type. The attribute where the actual values are stored must be set ('1') or optionally set ('0..1') through Multiplicity. In addition, the attributes are set as RO (Read Only), RW (Read and Write), and WO (Write Only) according to characteristics at the time of creation. Meanwhile, as shown in Table 1, the <container> resource may have <container>, <contentInstance>, and <subscription> as child resources.

Attributes of <container>	Multiplicity	RW / RO / WO	Description
resourceType	One	RO	Resource type. It is written once (which cannot be changed after a certain time) and identifies the type of resource. (Resource Type.This Write Once (at creation time then cannot be changed) resourceType attribute identifies the type of resources.Each resource shall have a resourceType attribute.)
resourceID	One	RO	This attribute is an identifier for the resource used for the "non-hierarchical URI method" or "ID-based method" case. This attribute is provided by the hosting CSE if the hosting CSE accepts the resource creation procedure. The hosting CSE assigns a unique resource ID (This attribute is an identifier for resource that is used for 'non-hierarchical URI method' or 'IDs based method' cases.This attribute shall be provided by the Hosting CSE when it accepts a resource creation procedure.The Hosting CSE shall assign a resourceID which is unique in the CSE).
parentID	One	RO	The system assigns a value to this attribute according to the parameters given in the CREATE request. The parent-child relationship is established by the parent's identifier of this child resource. This identifier uses a non-hierarchical URI representation. For example, the resource “…” The value of parent ID of AE resource with identifier “myAE1” created under //example.com/oneM2M/myCSE ”is“… ”. // parentID ”(the system shall assign the value to this attribute according to the parameters given in the CREATE Request.It establishes the parent-child relationship by identification of the parent of this child resource. Such identifier shall use the non -hierarchical URI representation.For example, an AE resource with the identifier "myAE1" which has been created under the resource "… // example.com / oneM2M / myCSE", the value of the parentID attribute will contain "… // parentID ".)
expirationTime	One	RW	Time / date the resource will be cleared by the hosting CSE. This attribute may be provided by the originator, in which case it is considered a hint to the host CSE about the lifetime of the resource. The hosting CSE may however determine the actual expiration time. If the hosting CSE decides to change the expiration time attribute value, it is known to the sender. The lifetime of the resource can be extended by providing a new value for this attribute in an UPDATE operation. Or by deleting the attribute value, for example by not providing the attribute when the hosting CSE makes a full update to determine a new value, the life of the resource can be extended. This attribute is required. If the caller does not provide a value in the CREATE operation, the system assigns an appropriate value according to local policy and / or M2M service subscription agreement (Time / date after which the resource will be deleted by the hosting CSE. This attribute can be provided by the Originator, and in such a case it will be regarded as a hint to the hosting CSE on the lifetime of the resource.The hosting CSE can however decide on the real expirationTime.If the hosting CSE decides to change the expirationTime attribute value, this is communicated back to the Originator.The lifetime of the resource can be extended by providing a new value for this attribute in an UPDATE operation.Or by deleting the attribute value, eg by not providing the attribute when doing a full UPDATE, in which case the hosting CSE can decide on a new value.This attribute shall be mandatory.If the Originator does not provide a value in the CREATE operation the system shall assign an appropriat e value depending on its local policies and / or M2M service subscription agreements).
accessControlPolicyIDs	0..1 (L)	RW	This attribute contains a list of identifiers (either IDs or URIs depending on whether a local resource exists) of the <accessControlPolicy> resource. The permissions defined in the referenced <accessControlPolicy> resource determine who is allowed to access the resource containing this attribute for a specific purpose (eg, Retrieve, Update, Delete, etc.). a list of identifiers (either an ID or a URI depending if it is a local resource or not) of an <accessControlPolicy> resource.The privileges defined in the <accessControlPolicy> resource that are referenced determine who is allowed to access the resource containing this attribute for a specific purpose (eg Retrieve, Update, Delete, etc.)).
labels	0..1	WR	Tokens used as keys to find resources. This attribute is an optional attribute and, if not present, means that the resource cannot be found through a discovery procedure that uses this attribute as a key parameter of the discovery (Tokens used as keys for discovering resources.This attribute is optional and if not present it means that the resource cannot be found by means of discovery procedure which uses labels as key parameter of the discovery).
creationTime	One	RO	Creation time / date of the resource. This attribute is a mandatory attribute for all resources and the value is assigned by the system when the resource is created locally. (Time / date of creation of the resource.This attribute is mandatory for all resources and the value is assigned by the system at the time when the resource is locally created. Such an attribute cannot be changed.)
creator	0..1	RO	The AE-ID or CSE-ID of the entity which created the resource.
lastModifiedTime	One	RO	Last modified time / date of the resource. This attribute is a required attribute and its value is automatically assigned by the system whenever the target resource changes through an update operation. be mandatory and its value is assigned automatically by the system each time that the addressed target resource is modified by means of the UPDATE operation.)
stateTag	One	RO	A counter that counts the number of changes made to a resource. When a resource is created, this counter is set to zero and incremented with every resource change. When a new instance is added to a parent resource, the stateTag attribute of the parent resource must first be incremented and copied to this stateTag attribute. it will be incremented on every modification of the resource.The stateTag attribute of the parent resource should be incremented first and copied into this stateTag attribute when a new instance is added to the parent resource).
announceTo	0..1	RW	This attribute may be included in the create or update request if the create or update request includes a list of URIs / CSE-IDs to which the generated / updated resource is announced. This attribute is present only for the original resource if the original resource is successfully announced to other CSEs. This attribute maintains a list of URIs to successfully announced resources. Updates to this attribute will trigger a new resource announcement or release of an announcement (which attribute may be included in a CREATE or UPDATE Request in which case it contains a list of URIs / CSE-IDs which the resource being created / updated shall be announced to.This attribute shall only be present on the original resource if it has been successfully announced to other CSEs.This attribute maintains the list of URIs to the successfully announced resources.Updates on this attribute will trigger new resource announcement or de-announcement).
announcedAttribute	0..1	RW	This attribute is present only for the original resource if some optional announced type attributes are announced to other CSEs. This attribute maintains a list of optional attributes (OA type attributes) advertised in the original resource. An update to this attribute will trigger an announce if the new attribute is added or if an existing attribute is removed. (This attributes shall only be present on the original resource if some Optional Announced ( OA) type attributes have been announced to other CSEs.This attribute maintains the list of the announced Optional Attributes (OA type attributes) in the original resource.Updates to this attribute will trigger new attribute announcement if a new attribute is added or de-announcement if the existing attribute is removed.)
maxNrOfInstances	0..1	RW	<contentInstance> Maximum number of instances of <contentInstance> child resources.
maxByteSize	0..1	RW	Maximum number of bytes that are allocated for a <container> resource for all instances in the <container> resource.
maxInstanceAge	0..1	RW	Maximum age of an instance of <containerInstance> resources in a <container>. Maximum age of the instances of <contentInstance> resources within the <container> .The value is expressed in seconds.
currentNrOfInstances	One	RO	<container> Number of content instances currently in the resource. (Current number of instances in a <container> resource.It is limited by the maxNrOfInstances).
currentByteSize	One	RO	<container> The current size, in bytes, of data stored in the resource. (Current size in bytes of data stored in a <container> resource.It is limited by the maxNrOfBytes).
latest	0..1	RO	Reference to latest <contentInstance> resource, when present if present.
locationID	0..1	RW		URI of a resource with attributes / policies that define how location information is obtained and managed. URI of the resource where the attributes / policies that define how location information are obtained and managed.This attribute is defined only when the <container> resource is used for containing location information).
ontologyRef	0..1	RW		A URI of the ontology used to represent the information that is managed and understood by the AE.The ontology is the domain to be addressed. Refers to a specification that defines the terms used in the document and defines the relationships between them.

The following table defines the properties of the <AE> resource.

Attributes of <AE>	Multiplicity	RW / RO / WO	Description
resourceType	One	RO	See Table 2
parentID	One	RO	See Table 2
expirationTime	One	RW	See Table 2
accessControlPolicyIDs	0..1 (L)	RW	See Table 2
labels	0..1	RO	See Table 2
creationTime	One	RW	See Table 2
lastModifiedTime	One	RO	See Table 2
announceTo	0..1	RW	See Table 2
announcedAttribute	0..1	RW	See Table 2
appName	0..1	RW	The name of the application, as declared by the application developer (e.g. "HeatingMonitoring")
App-ID	One	WO	The identifier of the application
AE-ID	One	RO	The identifier of the Application Entity
Pointofaccess	0..1 (L)	RW	List of addresses (eg, IP address, FQDN, URI) for communicating with the registered application entity via the Mca reference point via delivery services provided by the underlying network. This property is only accessed by the AE and hosting CSE. If this information is not provided, the AE shall use <pollingchannel>. Then, the hosting CSE can forward the request to the AE without using PoA (The list of addresses for communicating with the registered Application Entity over Mca reference point via the transport services provided by Underlying Network (eg IP address, FQDN) This attribute shall be accessible only by the AE and the Hosting CSE.If this information is not provided, the AE should use <pollingChannel> resource.Then the Hosting CSE can forward a request to the AE without using the PoA. )
ontologyRef	0..1	RW	See Table 2
nodeLink	0..1	RO	A URI of a <node> resource that stores the node specific information.
consecutiveRequestSupport	0..1	RW		Property that indicates the physical state of the device. Set the value to FALSE even if the device can malfunction due to a specification or external continuous request (fire).

Resource access control policy

An access control policy is defined as a "white list" or privileges, and each privilege defines "allowed" entities for specific access modes. Sets of privileges are handled such that the privileges for a privilege group are sums of individual privileges, ie the action is allowed if allowed by some / any of the privileges in the set. The selfPrivilege attribute lists the entities that have the right to read / update / delete for the resource <accessControlPolicy> itself.

In addition, all privileges defined in the access control policy also relate to location, time window and IP address.

By setting the accessControlPolicyID attribute on a resource, the permissions for accessing that resource are defined by the permissions defined in the <accessControlPolicy> resource.

7 shows the structure of a <accessControlPolicy> resource. The following table shows the attributes of the <accessControlPolicy> resource.

Attribute Name of <accessControlPolicy>	Multiplicity	RW / RO / WO	Description
resourceType (rT)	One	RO	See Table 2
parentID (pID)	One	RO	See Table 2
expirationTime (eT)	One	RW	See Table 2
labels (lBs)	0..1	RW	See Table 2
creationTime (cT)	One	RO	See Table 2
lastModifiedTime (lMT)	One	RO	See Table 2
link	One	WO	This attribute is only present on known resources. This attribute provides a link (URI) to the original resource. (This attribute shall be present only on the announced resource.This attribute shall provide the link (URI) to the original resource.This is only for <accessControlPolicyAnnc>.)
announceTo	One	RW	See Table 2
announcedAttribute	One	RW	This attribute is present on the original resource when some OA type attributes are announced to other CSEs. This attribute maintains a list of OA type attributes that are known from the original resource. An update to this attribute will trigger a new attribute announcement if a new attribute is added, de-announced or an existing attribute is removed. (This attributes shall only be present on the original resource if some Optional Announced (OA) type attributes have been announced to other CSEs.This attribute maintains the list of the announced Optional Attributes (OA type attributes) in the original resource.Updates to this attribute will trigger new attribute announcement if a new attribute is added or de-announcement if the existing attribute is removed.)
privileges (ps)	One	RW	List of permissions defined by this <accessControlPolicy> resource. The list of privileges defined by this <accessControlPolicy> resource.The privileges are applied to resources referencing this <accessControlPolicy> resource using the accessControlPolicyID attribute.)
selfPrivileges (sP)	One	RW	Defines the list of privileges for the <accessControlPolicy> resource itself.

Privileges may be generalized to actions (which may be to grant access, but more specifically, to grant access to a subset, ie, to filter a portion of data). Privileges may be generalized to conditions, which may include the identifier of the requestor (sender, requestor), all but the specified identifier, but may also include time-based conditions.

An access authorization mechanism based on an access control policy works by matching the sender's and sender's privileges stored in the <accessControlPolicy> resource. If a positive match is found, the requested action (eg, RETRIEVE) is checked using the set of allowed actions associated with the matching rights holder; If this check fails, the request is rejected. This set is referred to as a permission flag.

Self-privileges and privileges are a list of sender privileges associated with the permission flags that apply to the <accessControlPolicy> resource itself and all other resource types addressing the <accessControlPolicy> resource and the accessControlPolicyID common attribute, respectively.

All privileges defined in the access control policy are also associated with the location, time window and IP address before granting access.

Self-rights and each right in the rights may also consist of one role. This role is identified by the role name and the URL addressing the M2M service subscription resource in which the role is defined. If the sender represents itself with a particular role, the access control policy operates by matching the requesting sender with lists belonging to the specific role specified in the M2M service subscription resource.

Each right in the rights and self rights lists consists of the following elements.

Name	Description
originatorPrivileges	See Table 5
contexts	See Table 6
operationFlags	See Table 7

The originatorPrivileges includes information as shown in the following table.

Name	Description
Domain	FQDN domain
originator identifier	CSE ID or AE ID which represent a originator identity
Token	Access token usually provided as query parameter
All	All originators
Role	A role name associated with the URL the a Service Subscription resource where such role is defined

The contexts in Table 5 include the information in the following table.

Name	Description
Context	Defines the context in which every privileges of the present access control policy resource applies, eg time windows, location, IP address.)

OperationFlags of Table 5 include the information as shown in the following table.

Name	Description
RETRIEVE	Privilege to retrieve the content of an addressed resource
CREATE	Privilege to create a child resource
UPDATE	Privilege to update the content of an addressed resource
DELETE	Privilege to delete an addressed resource
DISCOVER	Privilege to discover the resource
NOTIFY	Privilege to receive a notification

In the M2M communication system, access control policy resources are stored separately from resources to which the access control policy is applied. The resource to which the access control policy is applied has only the AccessRightID (the URI of the access control policy resource) of the access control policy resource. Therefore, an M2M entity must reference an AccessRightID to check the access control policy of a particular resource.

Entity Registration

M2M entities are ready to use the system / service by performing a registration process with entities around them, whether in the field domain or the infrastructure domain. Such registration is performed at the request of the Registree, and as a result, the information of the Registrant is generally stored in the Registrar.

After the registration process is finished, the oneM2M entity may use the M2M service using the common functions provided by the CSE as shown in FIG. 3.

The oneM2M entity has an AE and a CSE. Accordingly, the registration process can be divided into an AE registration and a CSE registration. In this case, both the AE and the CSE mean a registration target and the registrar is a CSE. In the case of CSE registration, the information on the registrant CSE is also stored in the target CSE.

8 shows an AE registration process and a CSE registration process. FIG. 8A illustrates an AE registration process, in which AE1 to register requests <AE> generation to CSE1, who is in charge of registration (S81-1), whereby CSE1 uses <AE> by using the information of AE1. A resource may be generated (S82-2). Then, the CSE1 may transmit a response including the result of the registration process to the AE1 (S83-2).

8 (b) shows the CSE registration process. FIG. 8 (b) shows that if the subject to be registered is CSE1 and the registrar is CSE2 and CSE2 transmits the result of the registration request of CSE1 (S83-2), CSE1 uses the information of CSE2 to <remoteCSE> resource. It is the same as (a) of FIG. 8 except for generating (S84-2).

Subscription resource type

The <subscription> resource contains subscription information about its subscribed-to resource. A <subscription> resource is a child resource of the resource to which it is subscribed. Thus, a <subscription> resource is represented as a child resource of a subscribed resource. For example, a <container> resource has a <subscription> resource as a child resource. The <subscription> resource is deleted when the subscribed parent resource is deleted.

<subscription> resource represents a subscription to a subscribed resource. The sender may create a resource of a <subscription> resource type when the sender has a RETRIEVE privilege on the subscribed resource. The originator who created the <subscription> resource becomes a resource subscriber.

Each <subscription> resource may include a notification policy that specifies what notifications are sent, when and how. These notification policies may operate in conjunction with CMDH policies.

If the <subscription> resource is deleted, a notification request should be sent to the subscriberURI provided by the sender.

The <subscription> resource has a child resource, its name is notificationSchedule and is of type <schedule>. Under the <subscription> resource context, the notificationSchedule resource specifies when a notification can be sent to the notificationURI (s) by the hosting CSE.

Attributes specific to <subscription> resources are: The attributes in the table below list only some of the attributes of the <subscription> resource.

Attributes of <subscription>	Multiplicity	RW / RO / WO	Description
accessControlPolicyIDs	0..1 (L)	RW	If no accessControlPolicyIDs is given at the time of creation, the accesControlPolicies of the parent resource is linked to this attribute.
eventNotificationCriteria	0..1 (L)	RW	This attribute policy indicates the event criteria for which a notification is to be generated.
expirationCounter	0..1	RW	This attribute indicates that the subscriber wants to set the duration of this subscription to the limit of the maximum number of notifications. When the number of notifications sent reaches the maximum of this counter, the <subscription> resource is deleted regardless of other policies. (This notification policy indicates that the subscriber wants to set the life of this subscription to a limit of a maximum number of notifications.When the number of notifications sent reaches the count of this counter, the <subscription> resource shall be deleted, regardless of any other policy.)
notificationURI	1 (L)	RW	List of URI (s) for which the resource subscriber will receive notifications. The URI (s) in this list may not represent a resource subscriber entity. For group-related subscriptions, notificationURI is a URI generated by the group hosting CSE to receive notifications. In this case, the resource subscriber notification URI must be included in the notificationForwardingURI. (List of URI (s) where the resource subscriber will receive notifications.This list of URI (s) may not represent the resource subscriber entity.For a group-related subscription, the notificationURI shall be the URI that is generated by the group Hosting CSE to receive notifications.In this case, the resource subscriber notification URI shall be included in the notificationForwardingURI.)
gourpName	0..1	RW	The URI of a <group> resource in case the subscription is made through a group.
notificationForwardingURI	0..1	RW	This attribute is a propagation attribute that exists only for group-related subscriptions. Resource subscriber notification URI. Used by group hosting CSE to deliver aggregated notifications. (The attribute is a forwarding attribute that shall be present only for group related subscriptions.It represents the resource subscriber notification URI.It shall be used by group Hosting CSE for forwarding aggregated notifications.)
batchNotify	0..1	RW	This attribute indicates that the subscriber wants to receive batches of notifications at one time instead of each. This attribute represents the subscriber's notification policy and may have two values: the number and duration of notifications to be deployed for delivery. If either value is set, notification events are temporarily stored until a specified number of notifications have been deployed, or until a duration that started after the first notification has been created has expired. Follow what batched notifications are sent. If batchNotify is used concurrently with latestNotify, only the latest notification is sent and ec is set to "latest" (This notification policy indicates that the subscriber wants to receive batches of notifications rather than receiving them one at a time.This attribute expresses the subscriber's notification policy and may include two values: the number of notifications to be batched for delivery and a duration.When either value is set, notification events are temporarily stored until either the specified number of notifications have been batched, or, until a duration which starts after the first notification was generated has expired.Following the the batched notifications are sent.If batchNotify is used simultaneously with latestNotify, only the latest notification shall be sent and have the ec set to “latest”.)
rateLimit	0..1	RW	This attribute indicates that the subscriber wants to limit the rate at which he will receive notifications. This attribute represents the subscriber's notification policy and contains two values: the maximum number of events that can be sent during a particular duration, and the rateLimit window duration. If the number of notifications generated in the ratelimit window duration exceeds the maximum number, notification events are temporarily stored until the end of the window duration, and the transmission of the notification event is restarted in the next window duration. The sending of notification events continues as long as the maximum number of notification events for the window duration is not exceeded. (This notification policy indicates that the subscriber wants to limit the rate at which it receives notifications.This attribute expresses the subscriber's notification policy and includes two values: a maximum number of events that may be sent within some duration, and the rateLimit window duration.When the number of generated notifications within the ratelimit window duration exceeds the maximum number, notification events are temporarily stored, until the end of the window duration, when the sending of notification events restarts in the next window duration.The sending of notification events continues as long as the maximum number of notification events is not exceeded during the window duration.The ratelimit policy may be used simultaneously with other notification policies.)
preSubscriptionNotify	0..1	WO	This attribute indicates that the subscriber wants notifications sent for events generated prior to the creation of this subscription. This attribute has a value of the number of previously notified events requested. If up-to-date caching of held events includes supported and subscribed events in the hosting CSE, previous notification events will be sent up to the requested number. The preSubscriptionNotify policy can be used simultaneously with other notification policies. (This notification policy indicates that the subscriber wants to be sent notifications for events that were generated prior to the creation of this subscription.This attribute has a value of the number of prior notification events requested.If up-to-date caching of retained events is supported on the Hosting CSE and contains the subscribed events then prior notification events will be sent up to the number requested.The preSubscriptionNotify policy may be used simultaneously with any other notification policy.)
pendingNotification	0..1	RW	This attribute indicates how to handle missed notifications (according to reachability and notification schedules) generated due to the connection period. Possible values for pendingNotification include: "sendLatest" and "sendAllPending". This policy relies on the caching of held notifications on a hosted CSE. If this attribute is set, only the last notification should be sent and the last notification has ec set to "latest". If this attribute is absent, the hosting CSE does not send missed notifications. This policy applies to all notifications regardless of the delivery policy selected (batch, latestNotification, etc.). This notification policy, if set, indicates how missed notifications due to a period of connectivity (according to the reachability and notification schedules) .The possible values for pendingNotification are: “sendLatest” · “sendAllPending” This policy depends upon caching of retained notifications on the hosted CSE.When this attribute is set, only the last notification shall be sent and it shall have the ec set to “latest”. If this attribute is not present, the Hosting CSE sends no missed notifications.This policy applies to all notifications regardless of the selected delivery policy (batching, latestNotification, etc ..) Note that unreachability due to reasons other than scheduling is not covered by this policy.)
notificationStoragePriority	0..1	RW	This attribute indicates that the subscriber wants to set a priority for this subscription over other subscriptions belonging to the same subscriber. This attribute is set to a number within the priority range. If the storage of notifications exceeds the allocated size, this policy is used as an input with a storage congestion policy to determine which stored and generated notifications to drop and retain. (Indicates that the subscriber wants to set a priority for this subscription relative to other subscriptions belonging to this same subscriber.This attribute sets a number within the priority range.When storage of notifications exceeds the allocated size, this policy is used as an input with the storage congestion policy to determine which stored and generated notifications to drop and which ones to retain.)
latestNotify	0..1	RW	This notification policy indicates whether the subscriber wants only the last notification. If multiple notifications of this subscription are buffered, and the value of this attribute is set to true, only the last notification will be sent and have an ec value set to "latest". (This notification policy indicates if the subscriber wants only the latest notification.If multiple notifications of this subscription are buffered, and if the value of this attribute is set to true, then only the last notification shall be sent and it shall have the ec value set to “latest”.)
notificationContentType	One	RW	Indicates the type of notification content to be included in the notifications. Allows a notification content type that shall be contained in notifications.The allowed values are: .modified attributes only whole resource the reference to this subscription resource.)
notificationEventCat	0..1	RW	This notification policy indicates the subscriber's requested ec to be used for notification messages generated by this subscription.
creator	0..1	WO	AE-ID or CSE-ID which created the <subscription> resource.
subscriberURI	0..1	WO	URI that is sent a notification when this <subscription> is deleted.

The eventNotificationCriteria condition is as follows.

Condition tag	Multiplicity	Matching condition
createBefore	0..1	(The creationTime attribute of the resource is chronologically before the specified value.)
createdAfter	0..1	(The creationTime attribute of the resource is chronologically after the specified value.)
modifiedSince	0..1	(The lastModifiedTime attribute of the resource is chronologically after the specified value.)
unmodifiedSince	0..1	(The lastModifiedTime attribute of the resource is chronologically before the specified value.)
stateTagSmaller	0..1	(The stateTag attribute of the resource is smaller than the specified value.)
stateTagBigger	0..1	(The stateTag attribute of the resource is bigger than the specified value.)
expireBefore	0..1	The expirationTime attribute of the resource is chronologically before the specified value.
expireAfter	0..1	The expirationTime attribute of the resource is chronologically after the specified value.
sizeAbove	0..1	(The contentSize attribute of the <contentInstance> resource is equal to or greater than the specified value.)
sizeBelow	0..1	(The contentSize attribute of the <contentInstance> resource is smaller than the specified value.)
eventType	0..n	Describes the type of event. Possible event types are:-Updates to the properties of subscribed resources-Deletion of subscribed resources-Creation of immediate children of subscribed resources-Deletion of immediate children of subscribed resources. Other conditions in eventNotificationCriteria conditions Are applied to the selected event type. For example, if the event type is "creation of immediate child of subscribed resource", other eventNotificationCriteria conditions apply to the immediate child resources of the subscribed resource. If this condition is not specified, the default value is "update for attributes of subscribed resource". (The type of event.Possible event type values are:-Update to attributes of the subscribed-to resource- Deletion of the subscribed-to resource,-Creation of a direct child of the subscribed-to resource,-Deletion of a direct child of the subscribed-to resourceThe other conditions in eventNotificationCriteria conditions apply to the selected eventType.For example, if eventType is “Creation of a direct child of the subscribed-to resource” then other eventNotificationCriteria conditions is applied to the direct child resources of the subscribed -to resource.If this condition is not specified, the default value is “Update to attributes of the subscribed-to resource”)
resourceStatus	0..n	If the subscribed resource is changed by actions or expiration, the resource status is equal to the specified value. Possible values are: child created, updated, child deleted, deleted. If child created or child deleted is set, other eventNotificationCriteria conditions should be applied to child resources created or deleted. The notification includes contents for a child resource created or a deleted child resource based on the value of the notificationContentType attribute. If the subscribed-to resource is changed by the operations or expiration, the resource status is the same as the specified value.Possible values are: child created, updated, child If child created or child deleted is configured, other eventNotificationCriteria conditions shall be applied to the created or deleted child resource.Notification contains the contents for a created child resource or deleted child resource based on value of notificationContentType attribute.If this condition is not specified, the default value is updated.)
operationMonitor	0..n	Monitors whether actions accessing subscribed resources correspond to specific values. Allows you to monitor what actions are attempted for a subscribed resource, regardless of whether they were performed. This feature is useful for finding malicious AEs. Possible string arguments are create, retrieve, update, and delete. (The operations accessing the subscribed-to resource matches with the specified value.It allows monitoring which operation is attempted to the subscribed-to resource regardless of whether the operation is performed.This feature is useful when to find malicious AEs.Possible string arguments are : create, retrieve, update, delete.)
attribute	0..n	This attribute is the attribute name of the resource types. For example, the creator of the container resource type may be used as "creator = Sam". If multiple attributes are set, the result is based on the AND of all the attributes. (This is an attribute name of resource types.E.g. Creator of container resource type can be used as “creator = Sam” .When multiple attributes are set then the result is based upon the AND of all attributes.)

The M2M common service layer provides subscription / notification functionality to the application. This allows data to be exchanged between the CSE and the AE through different CSE repositories. Subscription / notification basically operates as shown in FIG.

Entity 2 wants to receive information about a specific event of entity 1 (eg, a change of a specific resource value of entity 1). To this end, entity 2 may create or set a subscription for the specific event in entity 1 (S910), and receive a response thereto (S920). When the specific event occurs and a notification according to the subscription is triggered, entity 1 may notify entity 2 (S930).

10 illustrates the case where three entities are involved in subscription / notification. Entity 2 does not necessarily have to receive notifications for subscriptions it establishes. For example, in an M2M environment, one entity creates a subscription for many different entities. Therefore, in the following environment, the entity that created the subscription may be different from the entity that actually receives the notification. That is, unlike FIG. 9, although entity 2 creates or sets a subscription (S1010), a notification according to the subscription may be delivered to entity 3 (S1030).

9 and 10, a subscription set or created is created or set in entity 1 in the form of a subscription resource (<subscirption>) described above.

11 illustrates a scope for the resource subscription described above.

A basic resource subscription means an update of a subscription target resource, event monitoring (scope 1 of FIG. 11), and notification. The prior art can extend this to provide the following functions.

1) Monitoring of request message reception targeting the target resource of subscription (scope 2 of FIG. 11) (Example: creation / acquisition / update / delete request message reception record)

2) Create or delete event monitoring targeting child resources of a subscription target resource (scope 3 of FIG. 11)

That is, when a subscription is set to a "parent" resource as shown in FIG. 12, an acquisition or update event for a child resource such as "child 1" may not be monitored. Also, you cannot monitor the child resources of "child 2" resource. To monitor this, a separate subscription should be set up for each child resource. This means that in the case of FIG. 12, a subscription should be set for all resources except for "subscription". However, when the number of resources is large, it is inconvenient to set up a subscription for each resource.

The present invention describes a method by which a resource subscriber can achieve the same effect as setting up individual subscriptions to multiple resources with only a "single" subscription setting. This method includes the following detailed methods.

1) Subscription setting information to indicate the monitoring scope of the child (child) resource

For example, a single subscription setting for multiple resources may include information on how many levels of subordinate resources are included from the "parent" resource.

2) Indicator in notification message to identify notification event that occurred in which sub-resource

For example, the notification message for a single subscription to multiple resources may include information of a "child 1" resource when an event occurs in the "child 1" resource.

3) Process of performing notification after checking subscription authority for sub resources created after creating subscription

For example, if the "great grandchild 1" resource did not exist at the time of "subscription" creation, and the resource owner (resource hosting CSE) subsequently created a grandchild resource such as "great grandchild 1", the information of the generated event and resource You can check the subscriber's permissions before sending them in the notification message.

In the following description, a subscription to multiple resources may be expressed as a multi-level subscription, a multi-resource subscription, or the like, and the subscription resource for the subscription is also a multi-level subscription resource or a multi-resource subscription resource, or the like. Although not expressly mentioned, a subscription to multiple resources mentioned in this specification may be expressed in a similar term and may be understood by those skilled in the art as "subscription" in the same sense.

Event monitoring scope indicator

In a RESTful system, resources can be configured in a tree structure, and the level of a multi-level subscription proposed in the present invention can be defined as a relationship between parent-child resources. 12 shows an example of notification for multiple resources in accordance with a multilevel subscription.

For example, in FIG. 12, when a subscription to a "parent" resource is created ("subscription" resource), the level value of a multilevel subscription may be set to 2 to monitor up to the "grandchild_1" resource. Resources that do not exist at the time the subscription is established can be set in advance through the level setting. For example, in order to monitor generation of the "greatgrandchild_1" resource, the level value of the "subscription" resource may be set to 3.

As a method of indicating a multi-resource subscription, it may be represented as "level = 3" as described above, or may be represented in the form of "multiLevel = TRUE" & "levelNumber = 3".

If you want to designate all sub-resources that can be created without limiting the level to a specific value, it may include information indicating this. For example, "level = -1 or 0" (that is, a non-positive integer).

Subscription setting including level information having a value of 1 or more from a hosting CSE owning a resource may be recognized as a multi-level subscription setting and may be separately processed for the existing single resource subscription.

The hosted CSE may exclude from the monitored resource if the subscription creator does not have the right to subscribe (eg, to acquire target and subordinate resources).

Event Raising Child Resource Indicator

When the notification message is transmitted in the conventional subscription / notification mechanism, it may indicate through which subscription reference indicator (subscription reference) that the corresponding notification event occurred. This is information indicating an address of a subscription resource. When monitoring multiple resources with a single subscription as in the present invention, indication information for distinguishing different resources is required. Accordingly, the hosting CSE may further include information of resources related to the notification event in the notification message when performing the multi-level subscription processing.

For example, in the case of FIG. 12, when a generation event of resource “greategrandchild_1” occurs, the notification message of step 3) may include relative path information on a subscription target resource, such as “/ child_2 / grandchild_1 / greategrandchild_1”.

Multilevel subscription processing

13 shows a process for processing a multi-level subscription of a hosted CSE. This is largely composed of the process of creating a multi-subscription resource and the process of processing to create a new child or child resources after the creation of a multi-subscription.

First, the procedure for creating multiple subscription resources will be described.

The hosting CSE may receive a resource creation request, and accordingly, the hosting CSE may generate a resource (S1301). In addition, the hosting CSE may check whether the generated resource is a subscription type (S1302). If the generated resource is a subscription type, it may be checked whether the generated subscription resource is a multi-level subscription (S1303a).

If the generated subscription resource is a multi-level subscription, the hosting CSE is the generated (multi-level) subscription resource for resources included in or corresponding to the level of the multi-level subscription among lower or child resources of the subscription target resource. A link (ie, a subscription link or ID (identifier) information of the generated multi-level subscription resource) may be added (S1304a).

If the generated subscription resource is not a multi-level subscription, this procedure ends.

14 illustrates an example of generation of resources for multiple resource subscriptions. It is assumed that all resources except for "subscription" have been created and a new "subscription" resource is created. When the "subscription" resource is created, multilevel subscriptions are applied to level 1 "child_1" and "child_2" resources and level 2 "grandchild_1" resources, resulting in "subLink = sub_01" for each resource. As such, the unstructured resource ID ("sub_01") of the generated multi-level subscription resource may have a link attribute (subLink).

When adding a link attribute (subLink), it may additionally include information on which level among the multiple levels the corresponding resource corresponds. This may be stored by associating the level ("tot_level") specified in the subscription resource indicated by "subLink" with the level ("curr_level") of the current resource ("child_2"), such as the "child_2" resource of FIG. 14. This may be expressed as indicated for the "grandchild_1" resource in another example.

Next, the procedure for creating a general resource will be described.

The hosting CSE may perform a resource generation procedure according to a conventional resource type. If the generated resource subscription type is not in S1302, the hosting CSE includes a subscription link in which a parent resource of the generated resource includes the generated resource as a subscription range, or the parent resource is multi-level. It is possible to check whether the subscription is a child resource (S1303b). S1303b is a procedure for determining whether the generated resource is the target of the multi-level subscription.

If the generated resource is the target of the multi-level subscription, the hosting CSE may add the information of the multi-level subscription resource to the generated resource as a sublink (S1304b). At this time, two or more subscription resource information may be added.

If the generated resource is not the subject of the multi-level subscription, the procedure ends.

The hosting CSE may check whether the generated resource is a subscribeable resource type and whether a subscription requestor has a right to create a subscription (S1305).

If the generated resource is a resource type that can be set up for subscription and the subscription generation requester has a right to create a subscription, the hosting CSE may indicate indication information indicating that a valid subscription is set in the subscription link information of the generated resource. For example, active_subscription) may be added (S1306). This is simply information indicating whether a specific resource having corresponding subscription link information is currently set up, unlike sublink information indicating multi-level subscription information. That is, when the indicator is included, the hosting CSE may perform notification event monitoring indicated by subscription link information. In other forms, the subscription resource is available as separate attribute information, such as an active subscription link (activeSubLink), only for new resources that are valid subscriptions, apart from how to use the subscription link and information that indicates a valid subscription (that is, a valid subscription indicator). Can point to

If the generated resource is not a resource type that can be set up for subscription or if the request for creating a subscription does not have a right for creating a subscription, the procedure is terminated.

15 shows an example of generating a general resource.

This indicates a situation in which "new_1" and "new_2" resources are newly created in the situation where "subscription" which is the multi-level subscription resource of FIG. 14 is created and set. In this example, it is assumed that the creator of the multi-level subscription resource indicated by sub_01 has subscription rights to the newly created resources "new_1" and "new_2". When the hosting CSE creates a resource of "new_1", it can see that its parent resource "child_2" has a subscription link (subLink) and that its multilevel subscription contains the resource "new_1" in scope, so "new_1" You can add the same subscription link as the "child_2" resource to the "resource. In this case, as shown in FIG. 14, a level value 2 (tot_level) of a subscription resource indicated by 'sub_01' and a level value 2 corresponding to a “new_1” resource may be additionally included. In the case of resource "new_2", since the parent resource "parent" resource is confirmed to have a multi-level subscription resource "subscription" as a child resource, the hosting CSE may add a subscription link value. Here too, the whole and own level information can be added.

When the Hosting CSE creates a new resource, it must ensure that it falls within the scope of the previously created multi-level subscription resource. If you do not add a multilevel subscription resource sublink, the hosting CSE traverses all parent resources from the parent resource to the root resource of the newly created resource in the resource tree and assigns the multi-level subscription resource to that resource. Make sure that it is a child resource, and if the multi-level subscription resource is as a child resource, whether the newly created resource is included in the subscription range of the multi-level subscription resource (for example, referring to a set subscription level value) You must judge. Since there may be a plurality of such multilevel subscription resources, the hosting CSE must go through the process of searching and verifying all the parent resources from the parent to the root resource of the new resource in all cases. In FIG. 15, the "new_1" resource creation is a target of searching and checking up to "child_2" and "parent" resources, and it is necessary to continuously check the parent of "parent" and the parent resource of the parent. Overloading may occur in all resource creation.

As described above, the method of checking whether a subscription link is set in a parent resource or whether the parent resource has a multi-level subscription resource does not require a verification procedure for parent resources other than the parent. This is because multi-level subscription resource related information (eg, subLink) is stored in its parent resource.

16 illustrates a process of sending a notification message by a multi-level subscription of a hosting CSE.

The hosting CSE may create a notification message when a notification event occurs in a resource (S1601). At this time, assume an event that satisfies the conditions set in the subscription.

The hosting CSE may check whether the notification event is due to a multi-level subscription (S1602). To this end, the hosting CSE may check whether the corresponding resource includes attribute information such as the sublink described above.

If the notification event is a multi-level subscription, the information on the resource in which the notification event occurs is included in a notification message (S1603), and the notification message may be transmitted to a notification target (S1604).

17 is a block diagram illustrating components of a transmitter 10 and a receiver 20 that perform embodiments of the present invention. The transmitter 10 and the receiver 20 are associated with transmitters / receivers 13 and 23 capable of transmitting or receiving radio signals carrying information and / or data, signals, messages, etc. Memory 12, 22 for storing a variety of information, the transmitter / receiver 13, 23 and the memory 12, 22 and the like is operatively connected to control the components to control the components described above And a processor 11, 21, respectively, configured to control the memory 12, 22 and / or the transmitter / receiver 13, 23 to perform at least one of the embodiments of the present invention.

The memories 12 and 22 may store a program for processing and controlling the processors 11 and 21, and may temporarily store input / output information. The memories 12 and 22 may be utilized as buffers. The processors 11 and 21 typically control the overall operation of the various modules in the transmitter or receiver. In particular, the processors 11 and 21 may perform various control functions for carrying out the present invention. The processors 11 and 21 may also be called controllers, microcontrollers, microprocessors, microcomputers, or the like. The processors 11 and 21 may be implemented by hardware or firmware, software, or a combination thereof. When implementing the present invention using hardware, application specific integrated circuits (ASICs) or digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), FPGAs ( field programmable gate arrays) may be provided in the processors 11 and 21. Meanwhile, when implementing the present invention using firmware or software, the firmware or software may be configured to include a module, a procedure, or a function for performing the functions or operations of the present invention, and configured to perform the present invention. The firmware or software may be provided in the processors 11 and 21 or stored in the memory 12 and 22 to be driven by the processors 11 and 21.

The processor 11 of the transmission apparatus 10 is predetermined from the processor 11 or a scheduler connected to the processor 11 and has a predetermined encoding and modulation on a signal and / or data to be transmitted to the outside. After performing the transmission to the transmitter / receiver (13). For example, the processor 11 converts the data sequence to be transmitted into K layers through demultiplexing, channel encoding, scrambling, and modulation. The coded data string is also called a codeword and is equivalent to a transport block, which is a data block provided by the MAC layer. One transport block (TB) is encoded into one codeword, and each codeword is transmitted to a receiving device in the form of one or more layers. The transmitter / receiver 13 may include an oscillator for frequency upconversion. The transmitter / receiver 13 may include Nt transmit antennas, where Nt is a positive integer greater than or equal to one.

The signal processing of the receiver 20 is the reverse of the signal processing of the transmitter 10. Under the control of the processor 21, the transmitter / receiver 23 of the receiver 20 receives a radio signal transmitted by the transmitter 10. The transmitter / receiver 23 may include Nr receive antennas, and the transmitter / receiver 23 frequency down-converts each of the signals received through the receive antennas to restore the baseband signal. do. Transmitter / receiver 23 may include an oscillator for frequency downconversion. The processor 21 may decode and demodulate a radio signal received through a reception antenna to restore data originally transmitted by the transmission apparatus 10.

The transmitter / receiver 13, 23 is equipped with one or more antennas. The antenna transmits a signal processed by the transmitter / receiver 13, 23 to the outside or receives a radio signal from the outside under the control of the processors 11 and 21, thereby transmitting / receiving the transmitter / receiver. It performs the function of forwarding to (13, 23). Antennas are also called antenna ports. Each antenna may correspond to one physical antenna or may be configured by a combination of more than one physical antenna elements. The signal transmitted from each antenna can no longer be decomposed by the receiver 20. A reference signal (RS) transmitted in correspondence with the corresponding antenna defines the antenna as viewed from the perspective of the receiver 20, and whether the channel is a single radio channel from one physical antenna or includes the antenna. Regardless of whether it is a composite channel from a plurality of physical antenna elements, the receiver 20 enables channel estimation for the antenna. That is, the antenna is defined such that a channel carrying a symbol on the antenna can be derived from the channel through which another symbol on the same antenna is delivered. In the case of a transmitter / receiver that supports a multi-input multi-output (MIMO) function for transmitting and receiving data using a plurality of antennas, two or more antennas may be connected.

In the embodiments of the present invention, the terminal or the UE operates as the transmitter 10 in the uplink and the receiver 20 in the downlink. In the embodiments of the present invention, the base station or eNB operates as the receiving device 20 in the uplink, and operates as the transmitting device 10 in the downlink.

The transmitter and / or the receiver may perform at least one or a combination of two or more of the embodiments of the present invention described above.

The present invention can be used in a terminal, base station, server or other equipment of a wireless mobile communication system.

Claims (18)

1. A method for processing a resource creation request associated with a multi-level subscription in a wireless communication system, the method being performed by a receiving device,

   Receiving a resource generation request from a source device;

   Generating a resource according to the resource creation request; And

   If the generated resource is a multi-level subscription resource, adding a subscription link to a child resource of a target resource of the subscription resource satisfying a level indicating a coverage of the multi-level subscription resource; How to.
2. The method of claim 1, wherein when setting a notification according to the multi-level subscription resource for all child resources of a target resource of the subscription resource, the level of the subscription resource is set to an integer rather than a positive integer. How to.
3. The method of claim 1, wherein whether the generated resource is a multi-level subscription resource is determined by a value of an attribute indicating a level indicating a coverage of the generated resource.
4. The method of claim 1, wherein the subscription link includes an identifier of the generated multi-level subscription resource.
5. The method of claim 1, wherein the subscription link comprises a level indicating a coverage of the generated multi-level subscription resource and / or a level of the corresponding child resource.
6. The method of claim 1, wherein if the generated resource is not a subscription resource, determining whether a parent resource of the generated resource has a multi-level subscription resource as a subscription link or a child resource in a range including the generated resource. Further comprising a step of doing.
7. The multi-level subscription resource of claim 1, wherein the generated resource has a multi-level subscription resource as a subscription link or a child resource of a range including the generated resource. Adding a level subscription resource or information of the multi-level subscription resource as a subscription link.
8. 8. The method of claim 7, further comprising determining whether the generated resource is a subscribable resource type and whether the creator of the multi-level subscription resource has permission to create a subscription for the generated resource. Characterized by the method.
9. 9. The method of claim 8, wherein if the generated resource is a subscribeable resource type, and if the creator of the multi-level subscription resource has permission to create a subscription for the generated resource, Further comprising adding an activity indicator.
10. A receiving device configured to process a resource generation request associated with a multi-level subscription in a wireless communication system,

    transmitter;

    receiving set; And

    A processor configured to control the transmitter and the receiver,

    The processor is:

    Receive a resource generation request from a source device, generate a resource according to the resource generation request, and if the generated resource is a multi-level subscription resource, the level indicating the coverage of the multi-level subscription resource And adding a subscription link to a child resource of a target resource of the subscribed resource that satisfies.
11. 12. The method of claim 10, wherein when setting a notification according to the multi-level subscription resource for all child resources of a target resource of the subscription resource, the level of the subscription resource is set to an integer rather than a positive integer. Receiving device.
12. The receiving device according to claim 10, wherein whether the generated resource is a multi-level subscription resource is determined by a value of an attribute indicating a level indicating an application range of the generated resource.
13. 11. The receiving device of claim 10, wherein the subscription link comprises an identifier of the generated multi-level subscription resource.
14. The receiving device according to claim 10, wherein the subscription link comprises a level indicating a coverage of the generated multi-level subscription resource and / or a level of the corresponding child resource.
15. 11. The method of claim 10, wherein if the generated resource is not a subscription resource, the processor determines whether a parent resource of the generated resource has a multi-level subscription resource as a subscription link or child resource in a range including the generated resource. A receiving device, characterized in that configured to determine whether.
16. 12. The processor of claim 10, wherein if the parent resource of the generated resource has a multi-level subscription resource as a subscription link or a child resource in a range that includes the generated resource, the processor corresponds to the generated link in the generated resource. And add the multi-level subscription resource or information of the multi-level subscription resource as a subscription link.
17. 17. The method of claim 16, wherein the processor is configured to determine whether the generated resource is a subscribable resource type and whether the creator of the multi-level subscription resource has a right to create a subscription for the generated resource. A receiving device, characterized in that.
18. 18. The processor of claim 17, wherein if the generated resource is a subscribable resource type, and if the creator of the multi-level subscription resource has a right to create a subscription to the generated resource, the processor is further configured to generate the resource. And add an active indicator to a subscription link.

Images