WO2016115885A1 - 资源操作请求的处理方法及装置 - Google Patents

资源操作请求的处理方法及装置 Download PDF

Info

Publication number
WO2016115885A1
WO2016115885A1 PCT/CN2015/087410 CN2015087410W WO2016115885A1 WO 2016115885 A1 WO2016115885 A1 WO 2016115885A1 CN 2015087410 W CN2015087410 W CN 2015087410W WO 2016115885 A1 WO2016115885 A1 WO 2016115885A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
entity
attribute
request message
operation request
Prior art date
Application number
PCT/CN2015/087410
Other languages
English (en)
French (fr)
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 WO2016115885A1 publication Critical patent/WO2016115885A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for processing a resource operation request.
  • the Machine to Machine (M2M) communication system consists of various M2M nodes and a basic network.
  • the M2M nodes communicate with each other through an underlying network.
  • An M2M node includes at least one application entity (Application Entity referred to as AE) or a public service entity (Common Services Entity referred to as CSE).
  • AE is the logical unit that performs the actual M2M application
  • CSE is the logical unit that manages and services the application.
  • the underlying Network Services Entity (NSE) provides services such as device management, location services, and device triggering for the CSE.
  • HSS Home Subscriber Server
  • MTC-InterWorking Function MTC-InterWorking Function
  • the communication between the M2M applications is realized through the interaction between the CSEs.
  • the M2M applications need to be registered to the CSE, and the CSEs need to be registered with each other in order to realize the interaction of the M2M applications through communication between the CSEs.
  • the M2M system architecture is as follows. Figure 1 shows.
  • the application node is the end execution node, such as a smart meter, a temperature measurement and control sensor, a fire alarm, a smart home appliance, etc.; an intermediate node (Middle Node for short) is a connection end execution node to a network side server.
  • a middleware such as a gateway;
  • an infrastructure node (IN) is a server on the network side, and an application registered to the base node, that is, the IN-AE may be a management platform of the M2M service provider (M2M SP).
  • FIG. 1 is a structural diagram of a related art M2M system. As shown in FIG. 1, an application node may be classified into two types according to functions: a node including a CSE and a node not including a CSE.
  • the Application Dedicated Node (ADN) contains at least one AE and does not include the CSE.
  • the Application Service Node (ASN) contains at least one AE and one CSE.
  • an AE or a CSE when an AE or a CSE needs to perform an operation such as acquiring or updating a resource on a target CSE, it is required to send an operation request message to the target CSE, where the request message includes an “operation execution time” parameter indicating execution of the operation. Time; on the other hand, the resource on the target CSE contains the "effective time” attribute, indicating the effective time of the resource.
  • the resource has expired and the operation request is still not executed, thereby causing the failure of the operation request.
  • the main purpose of the embodiments of the present invention is to provide a method and an apparatus for processing a resource operation request, so as to at least solve the problem that the resource in the related art has failed and the operation request is still not executed, thereby causing the operation request to fail.
  • a method for processing a resource operation request including: obtaining, by a first entity, an attribute value of a target resource validity time attribute in a second entity; When the parameter value of the target resource operation execution time is not within the attribute value, the first entity updates the parameter value according to the attribute value, wherein the parameter value is carried in indicating to perform the target resource The resource operation request message of the operation; or, when the first entity determines that the parameter value used to indicate the execution time of the target resource operation is not within the attribute value, the first entity aborts execution of the resource operation request .
  • the updating, by the first entity, the parameter according to the attribute value by: the first entity updating the parameter value according to a service logic.
  • the method before the first entity obtains the attribute value of the target resource validity time attribute in the second entity, the method includes: the first entity detecting whether the parameter value is carried in the resource operation request message; The first entity caches the resource operation request message.
  • a processing apparatus for a resource operation request where the first entity side includes: an obtaining module, configured to obtain an attribute value of a target resource effective time attribute in the second entity; and an update module And setting, when the first entity determines that the parameter value used to indicate the execution time of the target resource operation is not within the attribute value, updating the parameter value according to the attribute value, where the parameter value carries Bringing in a resource operation request message for indicating operation on the target resource; or, the aborting module, configured to determine, at the first entity, a parameter value indicating that the target resource operation execution time is not in the attribute When the value is within, the resource operation request is aborted.
  • the update module is further configured to update the parameter value according to the business logic.
  • the obtaining module includes: an obtaining unit, configured to send a resource acquisition request message to the second entity, where the resource acquisition request message carries an attribute for indicating that the acquired content is a target resource effective time attribute a receiving unit, configured to receive a response message of the second entity in response to the resource acquisition request message, where the response message carries an attribute value of the valid time attribute.
  • the obtaining module includes: a receiving module, configured to receive a create advertisement resource request message sent by the second entity, where the create advertisement resource request message carries a valid time attribute of the target resource An attribute value, configured to create an advertisement resource of the target resource according to the create an advertisement resource request message.
  • the device further includes: a detecting module, configured to detect whether the resource operation request message carries the parameter value; and a cache module, configured to cache the resource operation request message when the detection result is yes .
  • the parameter value of the operation execution time in the resource operation request message is no longer determined by the first entity.
  • the first entity updates the parameter value of the operation execution time according to the attribute value, or the first entity does not update the parameter value of the operation execution time, and the execution of the resource operation request message is suspended; The problem that the resource in the related art has been invalidated and the operation request is still not executed, thereby causing the operation request to fail, ensures that the resource operation request is effectively executed without the resource failing.
  • FIG. 1 is a structural block diagram of an M2M system in the related art
  • FIG. 2 is a flowchart of a processing method of a resource operation request according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of a processing apparatus for a resource operation request according to an embodiment of the present invention
  • FIG. 4 is a block diagram of an optional structure of a processing device for resource operation request according to an embodiment of the present invention.
  • FIG. 5 is a block diagram 2 of an optional structure of a processing device for resource operation request according to an embodiment of the present invention.
  • FIG. 6 is a block diagram 3 of an optional structure of a processing device for resource operation request according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for processing a resource operation request according to an embodiment of the present invention. As shown in FIG. 2, the steps of the method include:
  • Step S202 The first entity obtains an attribute value in the second entity for indicating a valid time attribute of the target resource.
  • Step S204 When the parameter value for indicating the execution time of the target resource operation is not within the attribute value, the first entity updates the parameter value according to the attribute value; or the first entity suspends the execution of the resource operation request.
  • the parameter value is carried in a resource operation request message for indicating operation on the target resource
  • the first entity determines that the parameter value of the operation execution time in the resource operation request message is no longer the attribute.
  • the first entity updates the parameter value of the operation execution time according to the attribute value, or the first entity does not update the parameter value of the operation execution time, and the resource operation request is suspended, that is, the first entity stops
  • the second entity sends the resource operation request message, that is, the operation execution time in the resource operation request message sent by the first entity to the second entity is surely within the effective time of the target resource; The failure and the operation request is still not executed, which leads to the failure of the operation request, and ensures that the resource operation request is effectively executed without the resource failing.
  • first entity and the second entity involved in this embodiment may be an AE or a CSE.
  • the first entity updates the parameter according to the attribute value.
  • updating the parameter value may be implemented by: the first entity according to the service logic. Update parameter values.
  • the method for obtaining the attribute value of the second entity in the second entity for indicating the effective time attribute of the target resource has two meanings for the first entity in the step S202.
  • the first layer is that the first entity actively acquires the resource effective time attribute in the second entity.
  • the attribute value can be implemented in the optional implementation manner of this embodiment by the following steps:
  • Step S11 The first entity sends a resource acquisition request message to the second entity, where the resource acquisition request message carries an attribute name indicating that the acquired content is a target resource effective time attribute;
  • Step S12 The first entity receives a response message of the second entity in response to the resource acquisition request message, where the response message carries the attribute value of the valid time attribute.
  • the first entity may be an AE or a CSE
  • the second entity may be a CSE
  • this mode can be implemented in the following manner in the optional implementation manner of this embodiment:
  • Step S21 The first entity receives an advertisement resource request message sent by the second entity, where the advertisement creation advertisement resource request message carries an attribute value indicating an advertisement resource validity time attribute of the target resource.
  • Step S22 The first entity creates an advertisement resource of the target resource according to the create advertisement resource request message, where the advertisement resource includes some or all attributes of the target resource advertised to the remote entity.
  • both the first entity and the second entity may be CSE.
  • the method in this embodiment may further include:
  • Step S31 The first entity detects whether the resource operation request message carries a parameter value.
  • Step S32 When the detection result is YES, the first entity caches the resource operation request message.
  • the processing device for the resource operation request is further provided, and the device is used to implement the foregoing embodiment and the optional implementation manner, and details are not described herein.
  • the term “module” "unit” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of a processing apparatus for a resource operation request according to an embodiment of the present invention.
  • the device is located on a first entity side.
  • the apparatus includes: an obtaining module 32, configured to obtain a target resource in a second entity.
  • the update module 34 is coupled to the obtaining module 32, and is configured to update the parameter value according to the attribute value when the parameter value for indicating the execution time of the target resource operation is not within the attribute value, wherein the parameter The value is carried in a resource operation request message for indicating operation on the target resource; or,
  • the suspension module 36 is coupled to the obtaining module 32, and is configured to suspend the execution of the resource operation request when the first entity determines that the parameter value indicating the execution time of the target resource operation is not within the attribute value. interest.
  • the parameter may also be used to update parameters according to the service logic.
  • FIG. 4 is a block diagram of an optional structure of a processing device for resource operation request according to an embodiment of the present invention.
  • the obtaining module 32 includes: an obtaining unit 42 configured to send a resource acquisition request message to a second entity, where The resource acquisition request message carries an attribute name for indicating that the content is the effective time of the target resource.
  • the receiving unit 44 is coupled to the obtaining unit 42 and configured to receive a response message of the second entity in response to the resource acquisition request message.
  • the response message carries the attribute value of the valid time attribute.
  • FIG. 5 is a block diagram of an optional structure of a processing device for resource operation request according to an embodiment of the present invention.
  • the obtaining module 32 may further include: a receiving module 52, configured to receive a notification sent by the second entity for creating an advertisement. a resource request message, where the advertisement creation advertisement resource request message carries an attribute value indicating an advertisement resource validity time attribute of the target resource; the creation module 54 is coupled to the receiving module 52 and configured to create a target according to the creation advertisement resource request message. Resource notification resource.
  • FIG. 6 is a block diagram 3 of an optional structure of a processing device for resource operation request according to an embodiment of the present invention.
  • the device may further include: a detecting module 62 coupled to the cache module 64 and configured to detect a resource operation request message. Whether the parameter value is carried in the cache module 62, coupled to the obtaining module 32, is set to cache the resource operation request message when the detection result is yes.
  • the optional embodiment provides a processing method for the resource operation request, by which the disorder between the resource effective time and the operation execution time can be effectively avoided, thereby ensuring that the resource operation request can be effectively executed.
  • the local CSE can obtain the remote CSE target resource effective time attribute value by means of active acquisition or passively obtaining the detailed description of the optional embodiment
  • Optional implementation method 1 active acquisition
  • Step S202 Before the AE or the local CSE (equivalent to the first entity) sends the resource operation request to the remote CSE (equivalent to the second entity), whether the AE or the local CSE check request message includes an "operation execution time" parameter.
  • Step S204 If the check result is yes, the AE or the local CSE caches the resource operation request, and sends a resource acquisition request to the remote CSE, where the resource acquisition request message includes: an attribute of the target resource that needs to be acquired, The value is set to the "Effective Time" property.
  • Step S206 The remote CSE retrieves the "effective time" attribute of the target resource, reads the attribute value, and feeds back the response to the AE or the local CSE through the response of the resource acquisition request message.
  • Step S208 The AE or the local CSE determines whether the operation execution time of the resource operation request is within the duration of the effective time of the target resource according to the attribute value of the "effective time" attribute of the target resource.
  • Step S210 When the determination result is no, the AE or the local CSE updates the “operation execution time” parameter of the resource operation request according to the attribute value of the “effective time” attribute of the target resource, or cancels the resource operation request.
  • Step S302 The remote CSE sends a request for creating an advertisement resource to the local CSE, where the request message includes: an attribute of the original resource (target resource) to be created, and the value is set to a “valid time” attribute.
  • Step S304 The local CSE creates an advertisement resource for the original resource, and creates a "effective time" attribute in the advertisement resource.
  • Step S306 Before the local CSE sends the resource operation request to the remote CSE, the local CSE checks whether the request operation message includes an "operation execution time" parameter.
  • Step S308 When the check result is YES, the local CSE searches for the "effective time" attribute in the notification resource of the target resource, reads the attribute value, and determines whether the operation execution time of the resource operation request is within the duration of the effective time of the resource.
  • Step S310 When the judgment result is no, the local CSE updates the “operation execution time” parameter of the resource operation request according to the attribute value of the “valid time” attribute of the resource, or cancels the resource operation request.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the first embodiment is a description of the manner in which the AE or the local CSE actively obtains the resource effective time attribute value; the steps of the method include:
  • Step S402 When the AE or the local CSE needs to operate the resource “Resource1” on the remote CSE, the AE or the local CSE checks whether the operation request message of the resource includes an “operation execution time” parameter.
  • Step S404 When the check result is YES, the AE or the local CSE caches the operation request message of the resource “Resource1”, and sends a resource acquisition request to the remote CSE, where the resource acquisition request message includes: an address of the resource, where The value is set to the Uniform Resource Identifier URI of the resource "Resource1”; the attribute of the resource "Resource1” indicating the need to be obtained, and its value is set to the "Effective Time” attribute.
  • Step S406 After the remote CSE authenticates the AE or the local CSE, locate the resource “Resource1” according to the URI of the resource “Resource1” included in the request message, and retrieve the resource “Resource1” according to the attribute indicated in the request message.
  • the "effective time” attribute is used to read the attribute value and feed back to the AE or the local CSE through the resource acquisition request response, where the response message includes: the attribute of the resource "Resource1" to be acquired, and the value is set to the attribute "effective time” Attribute value.
  • Step S408 After receiving the acquisition operation response, the AE or CSE parses the content information included in the response message, reads the attribute value of the "effective time” attribute of the resource "Resource1", and determines the operation request for the resource "Resource1". Whether the operation execution time is within the duration of the resource "Resource1".
  • Step S410 When the determination result is yes, the AE or the local CSE adjusts the operation execution time of the operation request for the resource “Resource1” according to the service logic, that is, after updating the “operation execution time” parameter in the cached resource operation request message, Send a resource operation request message to the remote CSE.
  • Step S412 After receiving the resource operation request, the remote CSE caches the request message, and sends a resource operation response to the AE or the local CSE to confirm accepting the operation request for the resource “Resource1”.
  • Step S414 The remote CSE sets the timer T1 locally, and sets the time value of T1 according to the “operation execution time” parameter in the request message; when T1 expires, the remote CSE performs an operation request for the resource “Resource1”, and feedback
  • the operation response is sent to the AE or the local CSE, and the response message contains the execution result of the operation.
  • Step S416 After receiving the resource operation response, the AE or the local CSE processes the cached operation request message for the resource “Resource1” according to the operation result of the resource “Resource1” included in the response message; if the execution result indicates that the operation is successful, then the operation is performed. In addition to caching messages.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the second embodiment describes the manner in which the AE or the local CSE passively obtains the resource effective time attribute value; the steps of the method include:
  • Step S502 The remote CSE sends a request to create a notification resource to the local CSE, and advertises the resource “Resource2” to the local CSE, where the request message includes: an attribute of the resource “Resource2” to be created, and the value is set to “effective time”. Attributes.
  • Step S504 After the local CSE authenticates the remote CSE, create an advertisement resource "Resource2Annc" for the resource "Resource2”, and create a "valid time” attribute in the advertisement resource "Resource2Annc”, and set according to the content information in the request message.
  • the attribute value of the Valid Time attribute After the local CSE authenticates the remote CSE, create an advertisement resource "Resource2Annc" for the resource "Resource2”, and create a "valid time” attribute in the advertisement resource "Resource2Annc”, and set according to the content information in the request message.
  • Step S506 When the local CSE needs to operate on the resource “Resource2” on the remote CSE, it is checked whether the “operation execution time” parameter is included in the operation request message for the resource.
  • Step S508 When the check result is YES, the local CSE caches the operation request message for the resource "Resource2", and retrieves the notification resource "Resource2Annc” of the resource "Resource2” according to the identifier of the resource "Resource2”, and reads the "valid” of the resource.
  • the attribute value of the time attribute and it is judged whether the operation execution time of the operation request of the resource "Resource2" is within the duration of the effective time of the resource "Resource2".
  • Step S510 When the determination result is yes, the local CSE adjusts the operation execution time of the operation request for the resource “Resource2” according to the service logic, that is, after updating the “operation execution time” parameter in the cached operation request message for the resource, Request a message to the remote CSE.
  • Step S512 After the remote CSE authenticates the local CSE, the request message is cached, and the resource operation response is sent to the local CSE, and the operation request for the resource “Resource2” is accepted.
  • Step S514 The remote CSE sets the timer T2 locally, and sets the time value of T2 according to the “operation execution time” parameter in the request message; when T2 expires, the remote CSE performs the operation request for the resource “Resource2”, and feedback operation In response to the local CSE, the response message contains the execution result of the operation.
  • Step S516 After receiving the resource operation response, the local CSE processes the operation request message of the cached resource “Resource2” according to the operation result of the resource “Resource2” included in the response message; if the execution result indicates that the operation fails, the cached message is resent .
  • the disorder between the resource effective time and the operation execution time is avoided, and the resource operation request can be effectively executed.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device for execution by the computing device and, in some cases, may be performed in a different order than herein.
  • the steps shown or described are either made separately into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the parameter value of the operation execution time in the resource operation request message is determined by the first entity is no longer the attribute.
  • the first entity updates the parameter value of the operation execution time according to the attribute value, or the first entity does not update the parameter value of the operation execution time, and the execution of the resource operation request message is suspended;
  • the resource has expired and the operation request is still not executed, thereby causing the operation request to fail, and the resource operation request is effectively executed without the resource failing.

Abstract

本发明提供了一种资源操作请求的处理方法及装置，其中该方法包括：第一实体获得第二实体中目标资源有效时间属性的属性值；在第一实体判断用于指示目标资源操作执行时间的参数值不在属性值以内时，第一实体依据属性值更新该参数值，其中，该参数值携带在用于指示对目标资源进行操作的资源操作请求消息中；或，在第一实体判断用于指示目标资源操作执行时间的参数值不在属性值以内时，第一实体中止执行资源操作请求。通过本发明，解决了相关技术中资源已经失效而操作请求仍然没有被执行，进而导致操作请求失败的问题，保证了在资源不失效的情况下，有效地执行资源操作请求。

Description

资源操作请求的处理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种资源操作请求的处理方法及装置。
背景技术
机器到机器(Machine to Machine简称为M2M)通信系统由各个M2M节点和基础网络组成。M2M节点通过基础网络(Underlying Network)实现互相通信，一个M2M节点至少包含一个应用实体(Application Entity简称为AE)或者一个公共业务实体(Common Services Entity简称为CSE)。AE是执行实际M2M应用的逻辑单元，CSE是对应用进行管理和服务的逻辑单元。基础网络业务实体(underlying Network Services Entity简称为NSE)为CSE提供设备管理、位置服务、设备触发等业务，例如归属用户服务器(Home Subscriber Server简称为HSS)、MTC交互功能(MTC-InterWorking Function简称为MTC-IWF)实体等。
M2M应用之间的通信是通过CSE之间的交互来实现的，M2M应用需要注册到CSE，CSE之间也需要相互注册，进而才能通过CSE之间的通信实现M2M应用的交互，M2M系统架构如图1所示。
在M2M系统架构中，应用节点是末端的执行节点，例如智能电表，温度测控传感器，火警报警器，智能家电等等；中间节点(Middle Node简称为MN)是连接末端执行节点到网络侧服务器的中间件，例如网关；基础节点(Infrastructure Node简称为IN)是网络侧的服务器，注册到基础节点上的应用，即IN-AE可以是M2M服务提供商(M2M SP)的管理平台。
图1是相关技术M2M系统的结构图，如图1所示，应用节点根据功能不同可以划分为两类：包含CSE的节点和不包含CSE的节点。其中，应用专有节点(Application Dedicated Node简称为ADN)至少包含一个AE，不包含CSE；应用业务节点(Application Service Node简称为ASN)至少包含一个AE和一个CSE。
在相关技术中，当AE或CSE需要对目标CSE上的资源进行获取或更新等操作时，需要发送操作请求消息到目标CSE，在请求消息中，包含“操作执行时间”参数，指示操作的执行时间；另一方面，在目标CSE上的资源中，包含“有效时间”属性，指示资源的有效时间。然而在相关技术中存在资源已经失效而操作请求仍然没有被执行的情况，进而导致操作请求的失败。
针对相关技术中资源已经失效而操作请求仍然没有被执行，进而导致操作请求失败的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例的主要目的在于提供一种资源操作请求的处理方法及装置，以至少解决相关技术中资源已经失效而操作请求仍然没有被执行，进而导致操作请求失败的问题。
根据本发明实施例的一个方面，提供了一种资源操作请求的处理方法，包括：第一实体获得第二实体中目标资源有效时间属性的属性值；在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，所述第一实体依据所述属性值更新所述参数值，其中，所述参数值携带在用于指示对所述目标资源进行操作的资源操作请求消息中；或，在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，所述第一实体中止执行所述资源操作请求。
可选地，所述第一实体通过以下方式依据所述属性值更新所述参数包括：所述第一实体根据业务逻辑更新所述参数值。
可选地，第一实体获得第二实体中目标资源有效时间属性的属性值包括：所述第一实体向所述第二实体发送资源获取请求消息，其中，所述资源获取请求消息中携带有用于指示获取内容为目标资源有效时间属性的属性名称；所述第一实体接收所述第二实体响应于所述资源获取请求消息的响应消息，其中，所述响应消息中携带有所述有效时间属性的属性值。
可选地，第一实体获得第二实体中目标资源有效时间属性的属性值包括：所述第一实体接收所述第二实体发送的创建通告资源请求消息，其中，所述创建通告资源请求消息中携带有所述目标资源的有效时间属性的属性值；所述第一实体依据所述创建通告资源请求消息创建所述目标资源的通告资源。
可选地，在第一实体获得第二实体中目标资源有效时间属性的属性值之前包括：所述第一实体检测所述资源操作请求消息中是否携带有所述参数值；在检测结果为是时，所述第一实体缓存所述资源操作请求消息。
根据本发明实施例的另一个方面，提供了一种资源操作请求的处理装置，位于第一实体侧，包括：获得模块，设置为获得第二实体中目标资源有效时间属性的属性值；更新模块，设置为在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，依据所述属性值更新所述参数值，其中，所述参数值携 带在用于指示对所述目标资源进行操作的资源操作请求消息中；或，中止模块，设置为在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，中止执行所述资源操作请求。
可选地，所述更新模块还设置为，根据业务逻辑更新所述参数值。
可选地，所述获得模块包括：获取单元，设置为向所述第二实体发送资源获取请求消息，其中，所述资源获取请求消息中携带有用于指示获取内容为目标资源有效时间属性的属性名称；接收单元，设置为接收所述第二实体响应于所述资源获取请求消息的响应消息，其中，所述响应消息携带有所述有效时间属性的属性值。
可选地，所述获得模块包括：接收模块，设置为接收所述第二实体发送的创建通告资源请求消息，其中，所述创建通告资源请求消息中携带有所述目标资源的有效时间属性的属性值；创建模块，设置为依据所述创建通告资源请求消息创建所述目标资源的通告资源。
可选地，所述装置还包括：检测模块，设置为检测所述资源操作请求消息中是否携带有所述参数值；缓存模块，设置为在检测结果为是时，缓存所述资源操作请求消息。
通过本发明实施例，采用第一实体在获得第二实体中用于指示目标资源有效时间的属性值之后，在该第一实体判断到资源操作请求消息中的操作执行时间的参数值不再该属性值以内时，该第一实体依据该属性值更新该操作执行时间的参数值，或者，该第一实体不更新该操作执行时间的参数值，中止执行该资源操作请求消息；通过本实施例，解决了相关技术中资源已经失效而操作请求仍然没有被执行，进而导致操作请求失败的问题，保证了在资源不失效的情况下，有效地执行资源操作请求。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中M2M系统的结构框图；
图2是根据本发明实施例的资源操作请求的处理方法流程图；
图3是根据本发明实施例的资源操作请求的处理装置结构框图；
图4是根据本发明实施例的资源操作请求的处理装置可选结构框图一；
图5是根据本发明实施例的资源操作请求的处理装置可选结构框图二；以及，
图6是根据本发明实施例的资源操作请求的处理装置可选结构框图三。
具体实施方式
需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本发明。
本实施例提供了一种资源操作请求的处理方法，图2是根据本发明实施例的资源操作请求的处理方法流程图，如图2所示，该方法的步骤包括：
步骤S202：第一实体获得第二实体中用于指示目标资源有效时间属性的属性值；
步骤S204：在用于指示目标资源操作执行时间的参数值不在属性值以内时，第一实体依据属性值更新参数值；或，第一实体中止执行资源操作请求。
其中，该参数值携带在用于指示对目标资源进行操作的资源操作请求消息中；
在本实施例中，第一实体在获得第二实体中用于指示目标资源有效时间的属性值之后，在该第一实体判断到资源操作请求消息中的操作执行时间的参数值不再该属性值以内时，该第一实体依据该属性值更新该操作执行时间的参数值，或者，该第一实体不更新该操作执行时间的参数值，中止该资源操作请求，即第一实体停止向第二实体发送资源操作请求消息，也就是说第一实体发送到第二实体的资源操作请求消息中的操作执行时间肯定在目标资源有效时间以内的；通过本实施例，解决了相关技术中资源已经失效而操作请求仍然没有被执行，进而导致操作请求失败的问题，保证了在资源不失效的情况下，有效地执行资源操作请求。
需要说明的是，对于本实施例涉及到的第一实体和第二实体可以是AE或CSE。
在本实施例中第一实体依据属性值更新参数的方式有多种，而在本实施例的一个可选实施方式中，更新该参数值可以通过如下方式来实现：该第一实体根据业务逻辑更新参数值。
对于本实施例中步骤S202第一实体获得第二实体中用于指示目标资源有效时间属性的属性值方式有两层含义，第一层是该第一实体主动获取第二实体中资源有效时间属性的属性值，该方式在本实施例的可选实施方式中可以通过如下步骤来实现：
步骤S11：第一实体向第二实体发送资源获取请求消息，其中，资源获取请求消息中携带有用于指示获取内容为目标资源有效时间属性的属性名称；
步骤S12：第一实体接收第二实体响应于资源获取请求消息的响应消息，其中，响应消息携带有该有效时间属性的属性值。
对于主动获取到目标资源有效时间属性的属性值的方式，该第一实体可以是AE或CSE，而第二实体可以是CSE。
而对于本实施例中步骤S202总第一实体获得第二实体中用于指示目标资源有效时间属性的属性值方式的第二层含义，则是第一实体得到第二实体中资源有效时间的属性值，该方式在本实施例的可选实施方式中，可以通过如下方式来实现：
步骤S21：第一实体接收第二实体发送的用于创建通告资源请求消息，其中，通告创建通告资源请求消息中携带有用于指示目标资源的通告资源有效时间属性的属性值；
步骤S22：第一实体依据创建通告资源请求消息创建目标资源的通告资源，其中，该通告资源包括通告到远程实体的目标资源的部分或全部属性。
对于被动得到目标资源有效时间属性的属性值的方式中，该第一实体和第二实体都可以是CSE。
此外，在本实施例的另一个可选实施方式中，该在第一实体获得第二实体中用于指示目标资源有效时间的属性值之前，本实施例的方法还可以包括：
步骤S31：第一实体检测资源操作请求消息中是否携带有参数值；
步骤S32：在检测结果为是时，第一实体缓存资源操作请求消息。
在本实施例中还提供了一种资源操作请求的处理装置，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”“单元”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的资源操作请求的处理装置结构框图，位于第一实体侧，如图3所示，该装置包括：获得模块32，设置为获得第二实体中用于指示目标资源有效时间属性的属性值；更新模块34，与获得模块32耦合连接，设置为在用于指示目标资源操作执行时间的参数值不在属性值以内时，依据该属性值更新该参数值，其中，参数值携带在用于指示对目标资源进行操作的资源操作请求消息中；或，
中止模块36，与获得模块32耦合连接，设置为在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，中止执行资源操作请求消 息。
对于本实施例中涉及到的更新模块34，在本实施例的一个可选实施方式中还可以用于根据业务逻辑更新参数。
图4是根据本发明实施例的资源操作请求的处理装置可选结构框图一，如图4所示，该获得模块32包括：获取单元42，设置为向第二实体发送资源获取请求消息，其中，资源获取请求消息中携带有用于指示获取内容为目标资源有效时间的属性的属性名称；接收单元44，与获取单元42耦合连接，设置为接收第二实体响应于资源获取请求消息的响应消息，其中，该响应消息中携带有该有效时间属性的属性值。
图5是根据本发明实施例的资源操作请求的处理装置可选结构框图二，如图5所示，获得模块32还可以包括：接收模块52，设置为接收第二实体发送的用于创建通告资源请求消息，其中，通告创建通告资源请求消息中携带有用于指示目标资源的通告资源有效时间属性的属性值；创建模块54，与接收模块52耦合连接，设置为依据创建通告资源请求消息创建目标资源的通告资源。
图6是根据本发明实施例的资源操作请求的处理装置可选结构框图三，如图6所示，装置还可以包括：检测模块62，与缓存模块64耦合连接，设置为检测资源操作请求消息中是否携带有参数值；缓存模块62，与获得模块32耦合连接，设置为在检测结果为是时，缓存资源操作请求消息。
下面结合本发明的可选实施例对本发明进行举例说明；
本可选实施例提供了一种资源操作请求的处理方法，通过该方法可以有效避免资源有效时间与操作执行时间之间的紊乱，进而保证了资源操作请求能被有效的执行。
下面通过本地CSE可以通过主动获取或被动得到的方式来获得远程CSE目标资源有效时间属性值两种方式对本可选实施例进行详细的说明；
可选实施方式一(主动获取)
步骤S202：在AE或本地CSE(相当于第一实体)发送资源操作请求到远程CSE(相当于第二实体)之前，AE或本地CSE检查请求消息中是否包含“操作执行时间”参数。
步骤S204：如果检查结果为是时，则该AE或本地CSE缓存该资源操作请求，并发送资源获取请求到远程CSE，其中，该资源获取请求消息中包含：需要获取的目标资源的属性，其值设置为“有效时间”属性。
步骤S206：远程CSE检索目标资源的“有效时间”属性，读取属性值，并通过资源获取请求消息的响应反馈给该AE或本地CSE。
步骤S208：该AE或本地CSE根据目标资源的“有效时间”属性的属性值判断资源操作请求的操作执行时间是否在目标资源的有效时间的时长以内。
步骤S210：在判断结果为否时，该AE或本地CSE根据目标资源的“有效时间”属性的属性值更新资源操作请求的“操作执行时间”参数，或者取消资源操作请求。
可选实施方式二(被动得到)
步骤S302：远程CSE发送创建通告资源请求到本地CSE，其中，该请求消息中包含：需要创建的原始资源(目标资源)的属性，其值设置为“有效时间”属性。
步骤S304：本地CSE为原始资源创建通告资源，并在通告资源中创建“有效时间”属性。
步骤S306：在本地CSE发送资源操作请求到远程CSE之前，本地CSE检查请求消息中是否包含“操作执行时间”参数。
步骤S308：在检查结果为是时，本地CSE在目标资源的通告资源中检索“有效时间”属性，读取属性值，并判断资源操作请求的操作执行时间是否在资源的有效时间的时长以内。
步骤S310：在判断结果为否时，本地CSE根据资源的“有效时间”属性的属性值更新资源操作请求的“操作执行时间”参数，或者取消该资源操作请求。
下面结合本可选实施例的具体实施例对本可选实施例进行举例说明；
实施例一：
实施例一是针对AE或本地CSE主动获取资源有效时间属性值的方式进行说明；该方式的步骤包括：
步骤S402：当AE或本地CSE需要对远程CSE上的资源“Resource1”进行操作时，AE或本地CSE检查资源的操作请求消息中是否包含有“操作执行时间”参数。
步骤S404：在检查结果为是时，该AE或本地CSE缓存该资源“Resource1”的操作请求消息，并发送资源获取请求到远程CSE，其中，该资源获取请求消息中包含：资源的地址，其值设置为资源“Resource1”的统一资源标识URI；用于指示需要获取的资源“Resource1”的属性，其值设置为“有效时间”属性。
步骤S406：远程CSE通过对AE或本地CSE的授权认证后，根据请求消息中包含的资源“Resource1”的URI定位资源“Resource1”，并根据请求消息中指示需要获取的属性检索资源“Resource1”的“有效时间”属性，读取属性值，并通过资源获取请求响应反馈给AE或本地CSE，其中，该响应消息中包含：需要获取的资源“Resource1”的属性，其值设置为属性“有效时间”的属性值。
步骤S408：该AE或CSE接收到获取操作响应后，解析响应消息中包含的内容信息，读取资源“Resource1”的“有效时间”属性的属性值，并判断对资源“Resource1”的操作请求的操作执行时间是否在资源“Resource1”的有效时间的时长以内。
步骤S410：在判断结果为是时，该AE或本地CSE根据业务逻辑调整对资源“Resource1”的操作请求的操作执行时间，即更新缓存的资源操作请求消息中的“操作执行时间”参数后，发送资源操作请求消息到远程CSE。
步骤S412：远程CSE接收到资源操作请求后，缓存请求消息，并发送资源操作响应给AE或本地CSE，确认接受对资源“Resource1”的操作请求。
步骤S414：远程CSE在本地设置计时器T1，并根据请求消息中的“操作执行时间”参数设置T1的时值；当T1到期时，远程CSE执行对资源“Resource1”的操作请求，并反馈操作响应给AE或本地CSE，响应消息中包含操作的执行结果。
步骤S416：AE或本地CSE接收到资源操作响应后，根据响应消息中包含的对资源“Resource1”的操作结果处理缓存的对资源“Resource1”的操作请求消息；如果执行结果指示操作成功，则移除缓存消息。
实施例二：
实施例二是针对AE或本地CSE被动得到资源有效时间属性值的方式进行说明；该方式的步骤包括：
步骤S502：远程CSE发送创建通告资源请求到本地CSE，将资源“Resource2”通告到本地CSE，其中，该请求消息中包含：需要创建的资源“Resource2”的属性，其值设置为“有效时间”属性。
步骤S504：本地CSE通过对远程CSE的授权认证后，为资源“Resource2”创建通告资源“Resource2Annc”，并在通告资源“Resource2Annc”中创建“有效时间”属性，以及根据请求消息中的内容信息设置“有效时间”属性的属性值。
步骤S506：当本地CSE需要对远程CSE上的资源“Resource2”进行操作时，检查对资源的操作请求消息中是否包含有“操作执行时间”参数。
步骤S508：在检查结果为是时，本地CSE缓存的对资源“Resource2”的操作请求消息，并根据资源“Resource2”的标识检索资源“Resource2”的通告资源“Resource2Annc”，读取资源的“有效时间”属性的属性值，并判断对资源“Resource2”的操作请求的操作执行时间是否在资源“Resource2”的有效时间的时长以内。
步骤S510：在判断结果为是时，本地CSE根据业务逻辑调整对资源“Resource2”的操作请求的操作执行时间，即更新缓存的对资源的操作请求消息中的“操作执行时间”参数后，发送请求消息到远程CSE。
步骤S512：远程CSE通过对本地CSE的授权认证后，缓存请求消息，并发送资源操作响应给本地CSE，确认接受对资源“Resource2”的操作请求。
步骤S514：远程CSE在本地设置计时器T2，并根据请求消息中的“操作执行时间”参数设置T2的时值；当T2到期时，远程CSE执行对资源“Resource2”操作请求，并反馈操作响应给本地CSE，响应消息中包含操作的执行结果。
步骤S516：本地CSE接收到资源操作响应后，根据响应消息中包含的对资源“Resource2”的操作结果处理缓存的资源“Resource2”的操作请求消息；如果执行结果指示操作失败，则重发缓存消息。
通过本可选实施例的方式，避免了资源有效时间与操作执行时间之间的紊乱，保证了资源操作请求能被有效的执行。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及可选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
显然，本领域的技术人员应该明白，上述本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
上述仅为本发明的可选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何 修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
在本发明中，采用第一实体在获得第二实体中用于指示目标资源有效时间的属性值之后，在该第一实体判断到资源操作请求消息中的操作执行时间的参数值不再该属性值以内时，该第一实体依据该属性值更新该操作执行时间的参数值，或者，该第一实体不更新该操作执行时间的参数值，中止执行该资源操作请求消息；通过本发明，解决了相关技术中资源已经失效而操作请求仍然没有被执行，进而导致操作请求失败的问题，保证了在资源不失效的情况下，有效地执行资源操作请求。

Claims (10)

  1. 一种资源操作请求的处理方法，包括：
    第一实体获得第二实体中目标资源有效时间属性的属性值；
    在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，所述第一实体依据所述属性值更新所述参数值，其中，所述参数值携带在用于指示对所述目标资源进行操作的资源操作请求消息中；或，
    在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，所述第一实体中止执行所述资源操作请求。
  2. 根据权利要求1所述的方法，其中，所述第一实体通过以下方式依据所述属性值更新所述参数包括：
    所述第一实体根据业务逻辑更新所述参数值。
  3. 根据权利要求1所述的方法，其中，第一实体获得第二实体中目标资源有效时间属性的属性值包括：
    所述第一实体向所述第二实体发送资源获取请求消息，其中，所述资源获取请求消息中携带有用于指示获取内容为目标资源有效时间属性的属性名称；
    所述第一实体接收所述第二实体响应于所述资源获取请求消息的响应消息，其中，所述响应消息中携带有所述有效时间属性的属性值。
  4. 根据权利要求1所述的方法，其中，第一实体获得第二实体中目标资源有效时间属性的属性值包括：
    所述第一实体接收所述第二实体发送的创建通告资源请求消息，其中，所述创建通告资源请求消息中携带有所述目标资源的有效时间属性的属性值；
    所述第一实体依据所述创建通告资源请求消息创建所述目标资源的通告资源。
  5. 根据权利要求3或4所述的方法，其中，在第一实体获得第二实体中目标资源有效时间属性的属性值之前包括：
    所述第一实体检测所述资源操作请求消息中是否携带有所述参数值；
    在检测结果为是时，所述第一实体缓存所述资源操作请求消息。
  6. 一种资源操作请求的处理装置，位于第一实体侧，包括：
    获得模块，设置为获得第二实体中目标资源有效时间属性的属性值；
    更新模块，设置为在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，依据所述属性值更新所述参数值，其中，所述参数值携带在用于指示对所述目标资源进行操作的资源操作请求消息中；或，
    中止模块，设置为在所述第一实体判断用于指示所述目标资源操作执行时间的参数值不在所述属性值以内时，中止执行所述资源操作请求。
  7. 根据权利要求6所述的装置，其中，所述更新模块还设置为，根据业务逻辑更新所述参数值。
  8. 根据权利要求6所述的装置，其中，所述获得模块包括：
    获取单元，设置为向所述第二实体发送资源获取请求消息，其中，所述资源获取请求消息中携带有用于指示获取内容为目标资源有效时间属性的属性名称；
    接收单元，设置为接收所述第二实体响应于所述资源获取请求消息的响应消息，其中，所述响应消息中携带有所述有效时间属性的属性值。
  9. 根据权利要求6所述的装置，其中，所述获得模块包括：
    接收模块，设置为接收所述第二实体发送的创建通告资源请求消息，其中，所述创建通告资源请求消息中携带有所述目标资源的有效时间属性的属性值；
    创建模块，设置为依据所述创建通告资源请求消息创建所述目标资源的通告资源。
  10. 根据权利要求8或9所述的装置，其中，所述装置还包括：
    检测模块，设置为检测所述资源操作请求消息中是否携带有所述参数值；
    缓存模块，设置为在检测结果为是时，缓存所述资源操作请求消息。
PCT/CN2015/087410 2015-01-23 2015-08-18 资源操作请求的处理方法及装置 WO2016115885A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510036108.0 2015-01-23
CN201510036108.0A CN105871963B (zh) 2015-01-23 2015-01-23 资源操作请求的处理方法及装置

Publications (1)

Publication Number Publication Date
WO2016115885A1 true WO2016115885A1 (zh) 2016-07-28

Family

ID=56416374

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/087410 WO2016115885A1 (zh) 2015-01-23 2015-08-18 资源操作请求的处理方法及装置

Country Status (2)

Country Link
CN (1) CN105871963B (zh)
WO (1) WO2016115885A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110531972A (zh) * 2019-09-05 2019-12-03 无锡华云数据技术服务有限公司 资源编排资源属性的编辑方法及装置
US20210373960A1 (en) * 2020-05-29 2021-12-02 Pollen, Inc. Reconciling resource management platforms

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106953791B (zh) * 2016-11-30 2021-01-26 创新先进技术有限公司 一种信息发送方法及装置
CN110769017A (zh) * 2018-07-27 2020-02-07 北京国双科技有限公司 数据请求的处理方法、装置、存储介质和处理器
CN112115303B (zh) * 2020-09-02 2023-10-03 北京达佳互联信息技术有限公司 数据处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102346460A (zh) * 2011-05-27 2012-02-08 运软网络科技(上海)有限公司 一种基于事务的服务控制系统及其控制方法
WO2013158679A1 (en) * 2012-04-17 2013-10-24 Robert Hansen Network element failure detection
CN103810046A (zh) * 2012-11-15 2014-05-21 百度在线网络技术（北京）有限公司 一种单机资源管理方法及系统
CN104113939A (zh) * 2013-04-17 2014-10-22 中兴通讯股份有限公司 对终端外设的操作的处理方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007287007A (ja) * 2006-04-19 2007-11-01 Orion Denki Kk 操作タスク予約機能を備えた情報処理装置及び操作タスク予約処理プログラム及び操作タスクの予約処理方法
US20130336222A1 (en) * 2010-11-19 2013-12-19 Interdigital Patent Holdings, Inc. Machine-To-Machine (M2M) Interface Procedures For Announce and De-Announce of Resources
CN101997878A (zh) * 2010-11-23 2011-03-30 蓝汛网络科技（北京）有限公司 一种验证域名链接的方法、装置及系统
CN102186164B (zh) * 2011-02-18 2014-04-02 华为技术有限公司 操作设备资源的方法和管理装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102346460A (zh) * 2011-05-27 2012-02-08 运软网络科技(上海)有限公司 一种基于事务的服务控制系统及其控制方法
WO2013158679A1 (en) * 2012-04-17 2013-10-24 Robert Hansen Network element failure detection
CN103810046A (zh) * 2012-11-15 2014-05-21 百度在线网络技术（北京）有限公司 一种单机资源管理方法及系统
CN104113939A (zh) * 2013-04-17 2014-10-22 中兴通讯股份有限公司 对终端外设的操作的处理方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110531972A (zh) * 2019-09-05 2019-12-03 无锡华云数据技术服务有限公司 资源编排资源属性的编辑方法及装置
CN110531972B (zh) * 2019-09-05 2024-02-06 无锡华云数据技术服务有限公司 资源编排资源属性的编辑方法及装置
US20210373960A1 (en) * 2020-05-29 2021-12-02 Pollen, Inc. Reconciling resource management platforms
US11954532B2 (en) * 2020-05-29 2024-04-09 Pollen, Inc. Reconciling resource management platforms

Also Published As

Publication number Publication date
CN105871963A (zh) 2016-08-17
CN105871963B (zh) 2020-05-19

Similar Documents

Publication Publication Date Title
WO2016115885A1 (zh) 资源操作请求的处理方法及装置
JP6803779B2 (ja) ドメインにわたるサービス層リソース伝搬
KR101806257B1 (ko) 가입 통지를 구현하기 위한 방법 및 장치
US10506432B2 (en) Method and apparatus for authenticating access authority for specific resource in wireless communication system
US10666661B2 (en) Authorization processing method and device
US10231107B2 (en) Resource subscription processing method and device
JP6743195B2 (ja) サブスクリプションを終了するための方法およびエンティティ
US9615346B2 (en) Method and apparatus for notifying information change in wireless communication system
KR20160130306A (ko) M2m 네트워크에 있어서의 리소스 및 속성 관리
US20150305008A1 (en) Method and apparatus for updating information regarding specific resource in wireless communication system
CN108769931B (zh) 一种机器通信中群组管理的方法和装置
WO2014180438A1 (zh) M2m应用的远程注册方法、装置、系统及存储介质
KR20130076808A (ko) 장치 관리 서버가 직접 접근할 수 없는 장치들을 관리하기 위한 기술들
WO2016054888A1 (zh) 一种创建订阅资源的方法和装置
CN110460978B (zh) 一种资源访问的方法和装置
KR20170033267A (ko) 무선 통신 시스템에서 요청 메시지를 처리하기 위한 방법 및 이를 위한 장치
WO2015117391A1 (zh) 一种实现资源属性通告的方法和公共业务实体
WO2016026282A1 (zh) 应用的注册方法及装置
WO2014183668A1 (zh) 一种机器类型通信应用的资源管理方法、节点和系统
WO2015117482A1 (zh) 更新资源通告的方法、本地公共业务实体及系统
WO2016023348A1 (zh) 用户设备的注册方法、实体、系统及计算机存储介质
WO2015154459A1 (zh) 订阅资源变更通知的方法及装置
WO2012174829A1 (zh) 短消息处理方法及装置
WO2017136979A1 (zh) 一种远程访问的实现方法、装置和系统
CN105323186B (zh) 一种通知消息的负载控制方法和装置

Legal Events

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

Ref document number: 15878555

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15878555

Country of ref document: EP

Kind code of ref document: A1