WO2017155161A1 - Procédé de reciblage de requête et appareil associé dans un système de communication sans fil - Google Patents

Procédé de reciblage de requête et appareil associé dans un système de communication sans fil Download PDF

Info

Publication number
WO2017155161A1
WO2017155161A1 PCT/KR2016/007130 KR2016007130W WO2017155161A1 WO 2017155161 A1 WO2017155161 A1 WO 2017155161A1 KR 2016007130 W KR2016007130 W KR 2016007130W WO 2017155161 A1 WO2017155161 A1 WO 2017155161A1
Authority
WO
WIPO (PCT)
Prior art keywords
targeting
resource
address
filter
request
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2016/007130
Other languages
English (en)
Korean (ko)
Other versions
WO2017155161A9 (fr
Inventor
김성윤
정승명
김동주
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
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 LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2017155161A1 publication Critical patent/WO2017155161A1/fr
Publication of WO2017155161A9 publication Critical patent/WO2017155161A9/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present invention relates to a method and apparatus for the same for re-targeting a request in a wireless communication system.
  • RESTful representational state transfer
  • IoT Internet of things
  • the IoT service platform may request that specific logic of an application be performed, and each application divides specific logic according to a specific request into a separate address, that is, re-targeted address, thereby separating the logic for each address. I would like to propose a different way.
  • the present invention proposes a method for filtering a received request as needed to receive the retargeted address.
  • a method for re-targeting a request in a wireless communication system comprising requesting a request indicating a specific resource from an originating device.
  • Receiving Determining whether re-targeting for transmitting the received request to a re-targeting address rather than a resource indicated by the received request is necessary; If the re-targeting is necessary, checking whether a re-targeting filter exists; Checking whether the received request satisfies a condition of the re-targeting filter; And if the condition of the re-targeting filter is satisfied, transmitting the re-targeting request corresponding to the received request to the re-targeting address.
  • determining whether the received request requires re-targeting may include determining whether re-targeting is needed, re-targeting address, and / or re-targeting to the resource indicated by the received request.
  • the method may include determining whether an address of the filter information is set.
  • determining whether the received request requires re-targeting includes whether re-targeting is required for parent resources of the resource indicated by the received request, re-targeting address, and / or
  • the method may include determining whether an address of filter information for re-targeting is set.
  • the attribute value indicated by the parent resource closest to the resource indicated by the received request in a tree structure may be used to determine whether the re-targeting is necessary.
  • determining whether the re-targeting filter exists includes re-targeting the filter to a child resource or attribute of the resource indicated by the re-targeting target address set in the resource indicated by the received request. It may include the step of confirming the existence.
  • checking whether the re-targeting filter exists includes checking whether the re-targeting filter exists at the address of the filter information for re-targeting set in the resource indicated by the received request. It may include.
  • condition of the re-targeting filter is set to a sum or product operation of some of all information that can be included in the received request, and a target to receive the received request through re-targeting. It can be set by.
  • the re-targeting request corresponding to the received request may include the same or some modified information as the received request.
  • the re-targeting address may be determined by an address indicated by information associated with the re-targeting filter or by an address of a target to receive the received request through re-targeting.
  • the information related to the re-targeting filter may be stored with the re-targeting filter or stored in a separate resource.
  • an apparatus configured to re-target a request in a wireless communication system, comprising: a radio frequency (RF) unit; And a processor configured to control the RF unit, wherein the processor receives a request indicating a specific resource from an originating device and sends the received request to a retargeting address that is not a resource indicated by the received request.
  • RF radio frequency
  • the processor may be configured to determine whether the received request requires re-targeting, whether to re-target the resource indicated by the received request, re-targeting address, and / or re-targeting. It may be configured to determine whether the address of the filter information for targeting is set.
  • the processor may be configured to determine whether the received request requires re-targeting, whether to re-target to parent resources of the resource indicated by the received request, a re-targeting address, And / or determine whether an address of filter information for re-targeting is set.
  • the attribute value indicated by the parent resource closest to the resource indicated by the received request in a tree structure may be used to determine whether the re-targeting is necessary.
  • the processor re-configures a child resource or attribute of a resource indicated by a retargeting target address set in a resource indicated by the received request, to determine whether the retargeting filter exists. It may be configured to check whether the targeting filter exists.
  • the processor may determine whether the re-targeting filter exists at the address of the filter information for re-targeting set in the resource indicated by the received request, to determine whether the re-targeting filter exists. It may be configured to confirm.
  • condition of the re-targeting filter is set to a sum or product operation of some of all information that can be included in the received request, and a target to receive the received request through re-targeting. It can be set by.
  • the re-targeting request corresponding to the received request may include the same or some modified information as the received request.
  • the re-targeting address may be determined by an address indicated by information associated with the re-targeting filter or by an address of a target to receive the received request through re-targeting.
  • the information related to the re-targeting filter may be stored with the re-targeting filter or stored in a separate resource.
  • 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.
  • FIG 11 illustrates an operation according to an embodiment of the present invention.
  • FIG. 13 shows a block diagram of an apparatus configured to perform embodiment (s) of the present invention.
  • a device for device-to-device communication that is, an M2M device or device may be fixed or mobile, and various devices for transmitting and receiving user data and / or various control information by communicating with a server for device-to-device communication, that is, an M2M server. Belong to this.
  • the M2M device or 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), It may be called a wireless modem, a handheld device, or the like.
  • an M2M server generally refers to a fixed station that communicates with M2M devices or devices, and / or other M2M servers, and communicates with M2M devices or devices and / or other M2M servers. Exchange various data and control information.
  • M2M applications can be installed or mounted on M2M devices / 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).
  • Table 1 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 identifier of the parent of this child resource. This identifier uses a non-hierarchical URI representation.
  • the resource “...” The value of the parent ID of the AE resource with the 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 appropriate 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.
  • 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 instances currently in the resource. (Current number of instances in a ⁇ container> resource.It is limited by the maxNrOfInstances).
  • 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.
  • 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.
  • the operationFlags of Table 4 include the same information as 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 accessControlPolicyIDs (URIs of the access control policy resource) of the access control policy resource. Therefore, M2M entities should refer to accessControlPolicyIDs to determine the access control policies for 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.
  • the ⁇ 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 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.) groupName 0..1 RW
  • 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.
  • 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.
  • EventType 0..n Describes the type of event. Possible event types include:-updating the properties of a subscribed resource-deleting a subscribed resource-creating a direct child of a subscribed resource-deleting a direct child of a subscribed resource 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 immediate child resources of 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 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 the created child resource or 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 1 may perform a subscription process for a specific resource of another entity 2. This ensures that when a change (creation of a child resource, deletion of a child resource, update of a child resource, update of the resource, deletion of the resource) occurs for the resource or the lower level (ie child) resource (s) of the resource,
  • the notification message can be delivered.
  • Subscribers can subscribe to specific resources through specific commands. Or, the subscriber can subscribe by creating or modifying a specific child resource of the resource. Alternatively, the subscriber may have a subscription method that monitors for various other resource changes.
  • the entity to be notified can be any entity with an address. Accordingly, the target receiving the notification message may be an entity requesting a subscription according to an address (eg, “notificationURI”) set in the subscription process, or may be a third other entity.
  • an address eg, “notificationURI”
  • a notification message is sent, and there may be a filter (eg, "eventNotificationCriteria") for the resource change. If a filter does not exist, a notification message is sent as soon as a change occurs to the resource or a lower level resource (s) of the resource, and if a filter exists, a notification message is sent when the filter conditions are met. Shows a flow chart for the process.
  • Entity 1 establishes a subscription to a specific resource of entity 2 (S1010).
  • the filter for the subscription may be set together.
  • entity 1 may separately set a filter for the subscription (S1020).
  • S1020 may occur before or after the corresponding S1010 or at the same time as S1010.
  • the specific resource for which the subscription of the entity 2 is set may be changed, and the entity 2 may detect this (S1030).
  • the entity 2 may check whether a filter condition for sending a notification message according to the subscription is satisfied (S1040). If the filter condition is satisfied, entity 2 may transmit a notification message to entity 1 (S1050).
  • notification messages may include: 1) resource content (all, only modified parts, or resource identifiers), 2) changed resources (resources that triggered the notification event), 3) subscription resource identifiers, or 4) Notification event information (eg, child resource creation, child resource deletion, child resource update, the corresponding resource update, the corresponding resource deletion) is possible.
  • the platform can ask the AE to perform the specific logic of the AE.
  • the AE received only the AE address ("point of access") so that the AE received all the logic for the AE to perform this. It should be stored where the address corresponds.
  • each request requires a technique that can be sent to the address that has the logic corresponding to the request.
  • FIG. 11 illustrates a re-targeting procedure of notification according to an embodiment of the present invention.
  • An event that satisfies a condition for generating a notification specified in a particular subscription resource may occur in that subscribed resource (s).
  • the subscription resource owning CSE may check whether the event has occurred (S1101).
  • the subscription resource owning CSE may transmit a notification request to the subscriber's manager (AE registrar CSE) of the subscription (S1102).
  • Information transmitted through the notification request may include the following.
  • Resource identifier (eg, the parent resource identifier (address) from which the resource was created or the identifier (address) of the created resource at the time of resource creation)
  • Event information satisfying the condition for generating the notification e.g., information about resource generation in case of event generated by resource generation, resource (or attribute) value (s) changed by resource update in case of event caused by resource update), resource update Information such as commands
  • Child child resources including (or excluding) the parent resource of the subscription resource, may be included.
  • the AE registrar CSE may receive the notification request. Then, the AE registrar CSE may notify the re-targeting filter (or notification re-targeting filter (s), notifications) to perform re-targeting to the target of the notification request (eg, the AE resource specified in the "to" parameter). It may be checked whether there is a notification re-targeting filter that satisfies among the filter information (s) for re-targeting (S1103).
  • the notification re-targeting filter will be described later with reference to FIG. 11.
  • the AE registrar CSE may determine whether the notification request is re-targeted according to whether the notification re-targeting filter is satisfied (S1104).
  • the AE registrar CSE may transmit a re-targeting notification request to an address determined according to the notification re-targeting filter (S1105).
  • the content of the re-targeting notification request may be the same as the notification request, or may include information that manipulates some information of the notification request.
  • the AE registrar CSE may receive a response to the re-targeting notification request from a subscriber (ie, AE) (S1106).
  • the AE registrar CSE may transmit a response to the notification request (received at S1102) to the subscription resource owning CSE (S1107).
  • S1107 may be sent as a result after the notification re-targeting procedure according to S1103 to S1106 as shown, or after S1102, may be sent independently of S1103 to S1106.
  • the notification re-targeting filter or conditions thereof may be set only by the subscriber, that is, AE.
  • the AE may set a condition of the notification re-targeting filter through an AND or OR operation of all information used when setting up a subscription to a specific subscription resource.
  • the AE may set a condition of the notification re-targeting filter through an AND or OR operation of all the information included in the previously received notification request.
  • the condition of the notification re-targeting filter may be that the identifier (address) of the subscription resource of the notification request is set to a specific address. That is, if the identifier (address) of the subscription resource is the specific address, the notification retargeting filter may be determined to be satisfied.
  • the condition of the notification re-targeting filter may be a resource (ie, a subscribed resource) in which an event (i.e., a subscribed resource) in which an identifier (address) of a subscription resource of the notification request satisfies a specific address (AND) and a condition for generating the notification request.
  • -to resource can be set to a specific address. That is, when the identifier (address) of the subscription resource and the identifier (address) of the subscribed resource respectively correspond to a value set as the notification re-targeting filter, the notification re-targeting filter may be determined to be satisfied.
  • the condition of the notification re-targeting filter is that the identifier (address) of the subscription resource of the notification request corresponds to the specific address and (AND) of the resource (that is, the subscribed resource) where the event occurs that satisfies the condition that generates the notification request. It may be set to update or generate a child resource of the subscribed resource. That is, if the identifier (address) of the subscription resource is the specific address and the event corresponds to the case of updating the subscribed resource or generating a child resource of the subscribed resource, the notification re-targeting filter is determined to be satisfied. Can be.
  • the AE can obtain the effect of branching or classifying the notification request coming to it and treating each of them with separate logic.
  • the notification re-targeting filter may be stored as a child resource of an AE resource stored in the AE registrar CSE.
  • the address (identifier) of the resource in which the notification re-targeting filter is stored may be stored in the AE resource, and the notification re-targeting filter may be stored in the corresponding resource.
  • the notification re-targeting filter related information may be stored in the notification re-targeting filter.
  • the notification re-targeting filter related information may specify how notification re-targeting should be performed when the notification re-targeting filter is satisfied or not satisfied.
  • the following table illustrates the notification re-targeting filter related information.
  • re-targeting may be performed only on the matching one, or if all of the conditions of the notification re-targeting filter match. Re-targeting may occur.
  • the retargeting may be omitted (or may not exist), and when omitted (when not present), retargeting may or may not always be performed. If re-targeting address is specified, re-targeting may be performed.
  • the retargeting address is the address used to send to the AE.
  • the actual address is determined by
  • the retargeting address is:
  • the re-targeting address is:
  • the notification re-targeting filter related information may be stored together with the notification re-targeting filter, and an address (identifier) of the notification re-targeting filter related information is stored separately so that the resource corresponds to the corresponding address (identifier). It may be stored in. Alternatively, the notification re-targeting filter related information may be stored in a child resource of the notification re-targeting filter.
  • FIG. 12 illustrates a re-targeting procedure of a request according to another embodiment of the present invention.
  • the AE registrar CSE may receive a request from the sender (S1201).
  • the AE registrar CSE may find a resource related to the request and determine whether re-targeting of the corresponding resource is necessary (S1202).
  • the AE registrar CSE may perform an operation according to the request on a resource related to the request and transmit a response thereto to the sender (S1203).
  • the AE registrar CSE determines whether there is a re-targeting filter (s) (or filter (s) for re-targeting, filter information (s) for re-targeting). It can be confirmed (S1204). Then, the AE registrar CSE may check whether the request satisfies the stored conditions of the re-targeting filters (S1205). The AE registrar CSE may determine whether to re-target the request according to whether the re-targeting filters satisfy the condition (S1206).
  • the AE registrar CSE may send the re-targeting request to an address determined according to the conditions of the re-targeting filters (S1207).
  • the content of the re-targeting request may be the same as the request, or some information of the request may include manipulated information.
  • the AE registrar CSE may receive a response to the re-targeting request from the AE (S1208).
  • the AE registrar CSE may transmit a response to the request (S1209).
  • S1209 may be sent as a result after the notification re-targeting procedure according to S1204 to S1208 as shown, or after S1202, may be sent independently of S1204 to S1208.
  • the AE registrar CSE is a registrar CSE and a resource-owned CSE of the AE.
  • the sender may be AE or CSE.
  • re-targeting is required for a resource related to the request of S1201 (ie, a resource indicated by a "to" parameter) and / or a target address is set when re-targeting and / or an address of filter information for re-targeting is set. If so, retargeting of the request may be made, or
  • re-targeting is required among parent resources (parent resource of the resource related to the request, or parent resource of the parent resource, etc.) related to the request of S1201 and / or a target address at the time of re-targeting is set and / or Alternatively, when the address of the filter information for re-targeting is set, the re-targeting of the request may be performed.
  • the AE registrant CSE indicates the attribute indicated by the resource that generated the request (ie, the subscribed resource) and the parent resource of the nearest level in the resource tree. Determining by (s) value
  • the re-targeting related information can be determined.
  • the target address in the re-targeting may be an identifier indicating an AE registered in the AE registrar CSE, such as an AE resource address or an identifier (address) indicating an AE registered in the AE registrar CSE as an ID of the AE. have.
  • only one of the target address and the address of the filter information for re-targeting may be set.
  • the target address when re-targeting may be stored as an attribute of the subscribed resource.
  • the AE registrar CSE checks whether the address can specify one AE resource, and if it is specified, it is set to AE. Check that the re-targeting filter information (s) exists.
  • the AE registrar CSE checks whether the re-targeting filter information corresponding to the address exists.
  • the retargeting filter or the condition may be set only by the subscriber, that is, AE.
  • the AE may set a condition of the re-targeting filter through an AND or OR operation of all information used when setting up a subscription to a specific subscription resource.
  • the AE may set a condition of the re-targeting filter through an AND or OR operation of all the information included in the previously received notification request.
  • the condition of the re-targeting filter is that the operation indicated by the request is RETRIEVE
  • the "to" parameter may be set to the address of a specific resource.
  • the condition of the re-targeting filter is that the operation indicated by the request is CREATE
  • the "to" parameter may be set to the address of a specific resource.
  • the condition of the re-targeting filter may be set when the operation indicated by the request is RETRIEVE, and modifiedAfter is equal to or less than or equal to a specific value or a specific value as a filterCriteria.
  • the setting of the corresponding re-targeting filter (condition) can be set only by the AE itself.
  • the re-targeting filter may be stored as a child resource of the AE resource.
  • an address (identifier) of a resource in which the re-targeting filter is stored may be stored in the AE resource, and the re-targeting filter may be stored in the corresponding resource.
  • the AE can obtain the effect of branching or classifying the request coming to it and treating each as a separate logic.
  • Information related to the re-targeting filter may be stored together with the re-targeting filter.
  • the information may specify how to perform the re-targeting when the re-targeting filter is satisfied or not satisfied. This setting allows only the AE to set the re-targeting filter for its AE resources.
  • re-targeting of re-targeting filter related information may be omitted (or not present at all), and when omitted (or not present), re-targeting may always be performed, or always It may not be performed. Alternatively, if the re-targeting address is specified, the re-targeting may be performed.
  • the retargeting address is the address used to send to the AE.
  • the actual address is determined by
  • the retargeting address is:
  • the re-target address is:
  • the re-targeting filter related information may be stored together with the re-targeting filter, and an address (identifier) of the re-targeting filter related information is separately stored and stored in a resource corresponding to the corresponding address (identifier). There may be. Alternatively, the retargeting filter related information may be stored in a child resource of the retargeting filter.
  • the transmitter 10 and the receiver 20 are radio frequency (RF) units 13 and 23 capable of transmitting or receiving radio signals carrying information and / or data, signals, messages, and the like, and in a wireless communication system.
  • the apparatus 12 is operatively connected to components such as the memory 12 and 22, the RF unit 13 and 23, and the memory 12 and 22, which store various kinds of information related to communication, and controls the components so that the apparatus is controlled.
  • a processor 11, 21 configured to control the memory 12, 22 and / or the RF units 13, 23, respectively, to perform at least one of the embodiments of the invention 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.
  • application specific integrated circuits ASICs
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • the firmware or software when implementing the present invention using 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.
  • each AE, CSE, sender, subscriber or entity may operate as the devices on which they are installed or mounted, that is, the transmitting device 10 or the receiving device 20. .
  • each AE, CSE, sender, subscriber or entity such as a receiver or a transmitter
  • the specific configuration of each AE, CSE, sender, subscriber or entity may be independently applied or two or more implementations described in various embodiments of the present invention described above with reference to the accompanying drawings.
  • the example can be implemented to be applied at the same time.
  • 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 un mode de réalisation de la présente invention, un procédé de reciblage de requête dans un système de communication sans fil est mis en œuvre par un appareil de réception et comprend les étapes consistant : à recevoir une requête indiquant une ressource spécifique depuis un appareil d'émission; à déterminer si un reciblage est nécessaire, la requête reçue étant transmise à une adresse reciblée qui n'est pas une ressource indiquée par la requête reçue; si un reciblage est nécessaire, à vérifier ensuite si un filtre de reciblage existe; à inspecter si la requête reçue satisfait ou non une condition du filtre de reciblage; et si la condition du filtre de reciblage est satisfaite, à transmettre ensuite une requête de reciblage correspondant à la requête reçue à l'adresse reciblée.
PCT/KR2016/007130 2016-03-09 2016-07-01 Procédé de reciblage de requête et appareil associé dans un système de communication sans fil Ceased WO2017155161A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662306032P 2016-03-09 2016-03-09
US62/306,032 2016-03-09

Publications (2)

Publication Number Publication Date
WO2017155161A1 true WO2017155161A1 (fr) 2017-09-14
WO2017155161A9 WO2017155161A9 (fr) 2017-11-23

Family

ID=59789490

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/007130 Ceased WO2017155161A1 (fr) 2016-03-09 2016-07-01 Procédé de reciblage de requête et appareil associé dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2017155161A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113875209A (zh) * 2019-05-13 2021-12-31 现代自动车株式会社 用于在m2m系统中删除资源的方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015034337A1 (fr) * 2013-09-09 2015-03-12 엘지전자 주식회사 Procédé et dispositif pour le traitement d'un message de requête spécifique dans un système de communication sans fil
WO2015046961A1 (fr) * 2013-09-27 2015-04-02 엘지전자 주식회사 Procédé de remise de messages de notification dans un système m2m et dispositifs à cet effet
WO2015069038A1 (fr) * 2013-11-08 2015-05-14 엘지전자 주식회사 Procédé d'abonnement et de notification dans un système de communication m2m et dispositif associé
US20150327130A1 (en) * 2013-01-29 2015-11-12 Lg Electronics Inc. Method and apparatus for transmitting indicator in wireless communication system
WO2016003071A1 (fr) * 2014-06-30 2016-01-07 엘지전자 주식회사 Procédé pour traiter un message de demande dans un système de communication sans fil, et appareil associé

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150327130A1 (en) * 2013-01-29 2015-11-12 Lg Electronics Inc. Method and apparatus for transmitting indicator in wireless communication system
WO2015034337A1 (fr) * 2013-09-09 2015-03-12 엘지전자 주식회사 Procédé et dispositif pour le traitement d'un message de requête spécifique dans un système de communication sans fil
WO2015046961A1 (fr) * 2013-09-27 2015-04-02 엘지전자 주식회사 Procédé de remise de messages de notification dans un système m2m et dispositifs à cet effet
WO2015069038A1 (fr) * 2013-11-08 2015-05-14 엘지전자 주식회사 Procédé d'abonnement et de notification dans un système de communication m2m et dispositif associé
WO2016003071A1 (fr) * 2014-06-30 2016-01-07 엘지전자 주식회사 Procédé pour traiter un message de demande dans un système de communication sans fil, et appareil associé

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113875209A (zh) * 2019-05-13 2021-12-31 现代自动车株式会社 用于在m2m系统中删除资源的方法和装置

Also Published As

Publication number Publication date
WO2017155161A9 (fr) 2017-11-23

Similar Documents

Publication Publication Date Title
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
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é
WO2019199028A1 (fr) Procédé et dispositif utilisant un découpage de réseau dans un système de communication mobile
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é
WO2014185754A1 (fr) Procédé d'abonnement et de notification dans un système de communications m2m et appareil associé
WO2016068548A1 (fr) Procédé de traitement d'un message de notification dans un système de communication sans fil et appareil associé
WO2020091310A1 (fr) Procédé et appareil de gestion de faisceaux de plateforme sécurisée intelligente
WO2015046961A1 (fr) Procédé de remise de messages de notification dans un système m2m et dispositifs à cet effet
WO2015069038A1 (fr) Procédé d'abonnement et de notification dans un système de communication m2m et dispositif associé
WO2022225295A1 (fr) Procédé et appareil d'authentification parmi des dispositifs de réseau central dans un système de communication mobile
WO2020231117A1 (fr) Procédé et appareil pour obtenir et gérer des informations de localisation d'un terminal mobile dans un système informatique en périphérie
WO2014200292A1 (fr) Procédé permettant de mesurer une position dans un système m2m et appareil associé
WO2016013846A1 (fr) Procédé de traitement de message de demande dans un système de communications sans fil, et appareil associé
WO2017073876A1 (fr) Procédé pour traiter une requête de service dans un système de communication sans fil et appareil associé
WO2020167095A1 (fr) Procédé et appareil permettant d'enregistrer des entités de fonction de domaine de fournisseur d'api sur une entité de fonction de noyau capif
WO2018101565A1 (fr) Structure de gestion de sécurité dans un environnement de virtualisation de réseau
WO2014030893A1 (fr) Procédé de gestion de profil par module d'authentification d'abonné intégré dans un dispositif terminal, et dispositif d'authentification d'abonné l'utilisant
WO2022102949A1 (fr) Serveur de configuration de bord, serveur de validation de bord et procédé de commande associé
WO2014077544A1 (fr) Procédé de configuration d'un profil de module d'authentification de souscripteur intégré et installé dans un dispositif de terminal, et appareil l'utilisant
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
WO2022045869A1 (fr) Appareil et procédé de gestion d'événements dans un système de communication
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é
WO2019088671A1 (fr) Procédé de fourniture de service de sécurité de réseau et appareil pour cela
WO2020111761A1 (fr) Procédé et dispositif de transmission répétée de message dans un système m2m
WO2017155161A9 (fr) Procédé de reciblage de requête et appareil associé dans un système de communication sans fil

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: 16893676

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16893676

Country of ref document: EP

Kind code of ref document: A1