WO2017175954A1 - Procédé destiné à traiter les souscriptions destinées aux multiples ressources dans un système de communication sans-fil et appareil associé - Google Patents

Procédé destiné à traiter les souscriptions destinées aux multiples ressources dans un système de communication sans-fil et appareil associé Download PDF

Info

Publication number
WO2017175954A1
WO2017175954A1 PCT/KR2016/015212 KR2016015212W WO2017175954A1 WO 2017175954 A1 WO2017175954 A1 WO 2017175954A1 KR 2016015212 W KR2016015212 W KR 2016015212W WO 2017175954 A1 WO2017175954 A1 WO 2017175954A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
subscription
level
generated
child
Prior art date
Application number
PCT/KR2016/015212
Other languages
English (en)
Korean (ko)
Inventor
정승명
김성윤
김동주
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2017175954A1 publication Critical patent/WO2017175954A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor

Definitions

  • 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.
  • 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.
  • 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. .
  • the level of the subscription resource may be set to an integer rather than a positive integer.
  • 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.
  • the subscription link may include an identifier of the generated multi-level subscription resource.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the level of the subscription resource may be set to an integer rather than a positive integer.
  • 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.
  • the subscription link may include an identifier of the generated multi-level subscription resource.
  • 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.
  • 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.
  • 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.
  • 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.
  • the processor is configured to It can be configured to add an activity indicator to a subscription link.
  • a notification service for multiple resources is possible.
  • FIG. 1 illustrates a functional structure in an M2M communication system.
  • FIG 2 illustrates a configuration supported by the M2M communication system based on the M2M function structure.
  • FIG. 3 illustrates a common service function provided in an M2M communication system.
  • FIG. 4 illustrates a resource structure present in an M2M application service node and an M2M infrastructure node.
  • M2M application service nodes eg, M2M devices
  • M2M infrastructure nodes e.g. M2M devices
  • FIG. 6 illustrates a procedure of exchanging request and response messages used in an M2M communication system.
  • FIG. 9 illustrates operations associated with a subscription service.
  • FIG. 10 illustrates operations associated with a subscription service.
  • 11 illustrates a monitoring range according to a subscription resource or service.
  • FIG. 12 illustrates a notification in accordance with a multi-level subscription setting according to an embodiment of the present invention.
  • FIG. 13 illustrates a multi-level subscription setting or a new resource generation procedure using the same according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 17 shows a block diagram of an apparatus configured to perform embodiment (s) of the present invention.
  • a device for device-to-device communication 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.
  • 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.
  • M2M applications can be installed or mounted on M2M devices, M2M gateways, or M2M servers.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • CSE Common Service Entity
  • 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.
  • CSF Common Services Functions
  • Some CSFs in a CSE must be present and some may optionally be present.
  • 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.)
  • 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.)
  • 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.
  • 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 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.
  • 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.
  • the M2M communication system is not limited to the illustrated configuration and can support more diverse configurations.
  • the concept of a node which is important for understanding the illustrated configuration, will be described.
  • ADN Application Dedicated Node
  • 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.
  • 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 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):
  • ASNs One or more application service nodes (ASNs);
  • MNs Middle nodes
  • One infrastructure node (IN).
  • the MN may be connected through the ADN and the Mca reference point. MN may be present in the M2M gateway.
  • 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);
  • 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.)
  • FIG. 3 illustrates a common service function provided in an M2M communication system.
  • M2M service functions ie, common service functions
  • 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.
  • CMDH Communication Management and Delivery Handling
  • DMR Data Management and Repository
  • DMG Device Management: 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.
  • DIS Discovery
  • GCG Group Management
  • a group can be created by grouping resources, M2M devices, or gateways. It manages requests related to groups.
  • AID Addressing and Identification
  • LOC Location
  • NSE Network Service Exposure, Service Execution and Triggering
  • Registration 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.
  • SEC Handles sensitive data such as security keys, establishes security associations, authenticates, authorizes, and protects identity.
  • SCA Service Charging and Accounting
  • Session Management Manages M2M sessions for end-to-end communication.
  • Subscription and Notification When a subscription is made to a specific resource, it plays a role in notifying that the resource is changed.
  • 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.
  • 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).
  • NSE Underlying Network Service Entity
  • 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 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.
  • FIG. 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.
  • 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.
  • 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.
  • M2M application service nodes eg, M2M devices
  • M2M infrastructure nodes e.g. M2M devices
  • an AE application2 registered in an M2M infrastructure node reads a sensor value of an M2M device
  • the sensor usually refers to a physical device
  • 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).
  • CSE1 container resource in the registered CSE
  • the AE existing on the M2M device must be registered in the CSE existing in the M2M device first.
  • M2M application related information registered in the form of cseBaseCSE1 / application1 resource is stored as shown in FIG. 5.
  • the AE registered in the infrastructure node may access the value.
  • the AE registered in the infrastructure node 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.
  • application1 communicates with CSE1 and CSE2 in the middle instead of directly with application2. To do this, CSE1 must be 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.
  • resource discovery refers to a process of discovering a resource in a remote CSE.
  • Resource search is done through a RETRIEVE request.
  • 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.
  • 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).
  • CSE common service entity
  • M2M system 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.
  • 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.
  • Type of operation to be executed (either Create / Retrieve / Update / Delete / Notify)
  • the ID of the entity to receive the request (ie the ID of the receiver)
  • 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
  • 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)
  • 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).
  • 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.
  • 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.
  • 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.
  • the attributes are set as RO (Read Only), RW (Read and Write), and WO (Write Only) according to characteristics at the time of creation.
  • the ⁇ container> resource may have ⁇ container>, ⁇ contentInstance>, and ⁇ subscription> as child resources.
  • 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.
  • 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.
  • 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.
  • 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.).
  • 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.)).
  • 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.
  • 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.
  • 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>.
  • 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).
  • 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.
  • HeatingMonitoring App-ID One WO
  • 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).
  • 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
  • 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.
  • all privileges defined in the access control policy also relate to location, time window and IP address.
  • the permissions for accessing that resource are defined by the permissions defined in the ⁇ accessControlPolicy> resource.
  • FIG. 7 shows the structure of a ⁇ accessControlPolicy> resource.
  • the following table shows the attributes of the ⁇ accessControlPolicy> resource.
  • URI link
  • 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.
  • 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.
  • RETRIEVE RETRIEVE
  • 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.
  • the originatorPrivileges includes information as shown in the following table.
  • Table 5 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.
  • 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.
  • 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.
  • 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.
  • both the AE and the CSE mean a registration target and the registrar is a CSE.
  • the information on the registrant CSE is also stored in the target CSE.
  • FIG. 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).
  • FIG. 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).
  • 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.
  • a ⁇ subscription> resource is represented as a child resource of a subscribed resource.
  • 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.
  • the ⁇ subscription> resource has a child resource, its name is notificationSchedule and is of type ⁇ schedule>.
  • 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.
  • notificationURI 1 L
  • the URI (s) in this list may not represent a resource subscriber entity.
  • 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.
  • 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.
  • 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.
  • 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”.
  • 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.
  • 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".
  • 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.
  • 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.
  • eventType is “Creation of a direct child of the subscribed-to resource”
  • 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 resource
  • eventType is “Creation of a direct child of the subscribed-to resource”
  • 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
  • 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.
  • 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.
  • This attribute is the attribute name of the resource types.
  • 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).
  • a specific event of entity 1 e.g. a change of a specific resource value of entity 1).
  • entity 2 may create or set a subscription for the specific event in entity 1 (S910), and receive a response thereto (S920).
  • entity 1 may notify entity 2 (S930).
  • 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).
  • 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.
  • 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.
  • a single subscription setting for multiple resources may include information on how many levels of subordinate resources are included from the "parent" resource.
  • 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.
  • the resource owner responsible 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • level -1 or 0
  • 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).
  • the notification message 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.
  • the notification message of step 3 may include relative path information on a subscription target resource, such as “/ child_2 / grandchild_1 / greategrandchild_1”.
  • FIG. 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.
  • 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).
  • 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
  • S1304a may be added (S1304a).
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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).
  • activeSubLink active subscription link
  • the procedure is terminated.
  • 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.
  • the hosting CSE may add a subscription link value.
  • the whole and own level information can be added.
  • the Hosting CSE 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.
  • the hosting CSE 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.
  • 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.
  • 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.
  • multi-level subscription resource related information eg, subLink
  • 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.
  • 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).
  • FIG. 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
  • 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.
  • firmware or software 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.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • 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.
  • 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.
  • RS reference signal
  • 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.
  • MIMO multi-input multi-output
  • the terminal or the UE operates as the transmitter 10 in the uplink and the receiver 20 in the downlink.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon la présente invention, un procédé destiné au traitement d'une demande de génération de ressource associée à une souscription à niveau multiple dans un système de communication sans fil conformément à un mode de réalisation de la présente invention est réalisé au moyen d'un dispositif de réception et peut comprendre les étapes consistant : à recevoir une demande de génération de ressource à partir d'un dispositif source; à générer une ressource conformément à la demande de génération de ressource; et lorsque la ressource générée constitue une ressource de souscription de niveau multiple, à ajouter un lien de souscription à une ressource enfant de la ressource de souscription correspondante satisfaisant un niveau indiquant la couverture de la ressource de souscription à niveau multiple.
PCT/KR2016/015212 2016-04-05 2016-12-23 Procédé destiné à traiter les souscriptions destinées aux multiples ressources dans un système de communication sans-fil et appareil associé WO2017175954A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662318223P 2016-04-05 2016-04-05
US62/318,223 2016-04-05

Publications (1)

Publication Number Publication Date
WO2017175954A1 true WO2017175954A1 (fr) 2017-10-12

Family

ID=60001607

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/015212 WO2017175954A1 (fr) 2016-04-05 2016-12-23 Procédé destiné à traiter les souscriptions destinées aux multiples ressources dans un système de communication sans-fil et appareil associé

Country Status (1)

Country Link
WO (1) WO2017175954A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130179557A1 (en) * 2011-02-18 2013-07-11 Huawei Technologies Co., Ltd. Method and management apparatus for performing operation on device resource
US20140215043A1 (en) * 2013-01-29 2014-07-31 Kt Corporation Resource change management in machine to machine network
WO2014200292A1 (fr) * 2013-06-12 2014-12-18 엘지전자 주식회사 Procédé permettant de mesurer une position dans un système m2m et appareil associé
US20150055640A1 (en) * 2012-01-13 2015-02-26 Interdigital Patent Holdings, Inc. Method and apparatus for supporting machine-to-machine communications
US20160088420A1 (en) * 2013-05-16 2016-03-24 Lg Electronics Inc. Method for subscription and notification in m2m communication system and apparatus for same

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130179557A1 (en) * 2011-02-18 2013-07-11 Huawei Technologies Co., Ltd. Method and management apparatus for performing operation on device resource
US20150055640A1 (en) * 2012-01-13 2015-02-26 Interdigital Patent Holdings, Inc. Method and apparatus for supporting machine-to-machine communications
US20140215043A1 (en) * 2013-01-29 2014-07-31 Kt Corporation Resource change management in machine to machine network
US20160088420A1 (en) * 2013-05-16 2016-03-24 Lg Electronics Inc. Method for subscription and notification in m2m communication system and apparatus for same
WO2014200292A1 (fr) * 2013-06-12 2014-12-18 엘지전자 주식회사 Procédé permettant de mesurer une position dans un système m2m et appareil associé

Similar Documents

Publication Publication Date Title
WO2017073876A1 (fr) Procédé pour traiter une requête de service dans un système de communication sans fil et appareil associé
WO2015069038A1 (fr) Procédé d'abonnement et de notification dans un système de communication m2m et dispositif associé
WO2014185754A1 (fr) Procédé d'abonnement et de notification dans un système de communications m2m et appareil associé
WO2015046960A1 (fr) Procédé de délivrance d'un message de notification dans un système m2m et dispositifs associés
WO2016195199A1 (fr) Procédé de traitement de requête par un canal d'interrogation dans un système de communication sans fil et appareil associé
WO2016126021A1 (fr) Procédé et appareil de traitement de requête pour l'arrêt de réception de notification dans un système de communication sans fil
WO2016068548A1 (fr) Procédé de traitement d'un message de notification dans un système de communication sans fil et appareil associé
WO2020197288A1 (fr) Procédé et dispositif pour fournir une connectivité à un terminal afin d'utiliser un service informatique périphérique
WO2016064235A2 (fr) Procédé de gestion d'une ressource enfant d'un membre d'un groupe dans un système de communication sans fil, et dispositif associé
WO2019199028A1 (fr) Procédé et dispositif utilisant un découpage de réseau dans un système de communication mobile
WO2018143774A1 (fr) Procédé de gestion d'enregistrement pour un terminal accédant à un réseau 5g au moyen d'un accès non 3 gpp
WO2022146014A1 (fr) Procédé et système autorisant un service akma dans un scénario d'itinérance
WO2014200292A1 (fr) Procédé permettant de mesurer une position dans un système m2m et appareil associé
WO2013025085A2 (fr) Appareil et procédé permettant de prendre en charge un nuage de famille dans un système informatique en nuage
WO2014109597A1 (fr) Procédé de changement de passerelle dans un système machine à machine (m2m) et dispositif correspondant
WO2021091307A1 (fr) Appareil et procédé d'établissement d'une session de service mbs pour fourniture de service mbs dans un système de communication sans fil
WO2016003248A1 (fr) Appareil et procédé de fourniture de connexion de service par l'intermédiaire d'une couche d'accès dans un système de communication sans fil
WO2021167277A1 (fr) Dispositif et procédé pour fournir un service selon un type de réseau de communication sans fil dans un système informatique périphérique
WO2012153971A2 (fr) Procédé et appareil d'envoi de données de multidiffusion à des dispositifs m2m dans un système d'accès sans fil
WO2016013846A1 (fr) Procédé de traitement de message de demande dans un système de communications sans fil, et appareil associé
WO2022060147A1 (fr) Procédé et appareil destinés à des opération multi-usim
WO2017082506A1 (fr) Procédé de traitement d'une demande d'arrêt de réception de notification dans un système de communication sans fil, et dispositif associé
WO2020111759A1 (fr) Procédé et appareil de gestion de ressources et d'exécution d'un délestage de ressources dans un système m2m
WO2017014381A1 (fr) Procédé de maintien de synchronisation de ressources dans un système de communication sans fil, et appareil associé
WO2013066131A2 (fr) Procédé de configuration de réseau personnel (pn) sur la base d'informations d'utilisation de réseau personnel dans un réseau hétérogène

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16898057

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16898057

Country of ref document: EP

Kind code of ref document: A1