CN105871963B - Method and device for processing resource operation request - Google Patents
Method and device for processing resource operation request Download PDFInfo
- Publication number
- CN105871963B CN105871963B CN201510036108.0A CN201510036108A CN105871963B CN 105871963 B CN105871963 B CN 105871963B CN 201510036108 A CN201510036108 A CN 201510036108A CN 105871963 B CN105871963 B CN 105871963B
- Authority
- CN
- China
- Prior art keywords
- resource
- entity
- attribute
- request message
- operation 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.)
- Expired - Fee Related
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
Abstract
The invention provides a method and a device for processing a resource operation request, wherein the method comprises the following steps: the first entity obtains the attribute value of the effective time attribute of the target resource in the second entity; when the first entity judges that the parameter value used for indicating the operation execution time of the target resource 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 a resource operation request message used for indicating the operation of the target resource; or, when the first entity judges that the parameter value used for indicating the target resource operation execution time is not within the attribute value, the first entity suspends executing the resource operation request. The invention solves the problem that the operation request fails because the resource is invalid and the operation request is still not executed in the related technology, and ensures that the resource operation request is effectively executed under the condition that the resource is not invalid.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for processing a resource operation request.
Background
A Machine to Machine (Machine to Machine abbreviated as M2M) communication system consists of individual M2M nodes and an underlying network. The M2M nodes communicate with each other through the infrastructure Network (underlay Network), and an M2M node at least contains an Application Entity (AE) or a Common Services Entity (CSE). AE is the logical unit that executes the actual M2M application and CSE is the logical unit that manages and services the application. An underlying Network Service Entity (NSE) provides Services such as device management, location service, device triggering and the like for the CSE, for example, a Home Subscriber Server (HSS), an MTC interactive Function (MTC-InterWorking Function (MTC-IWF) Entity and the like.
The communication between the M2M applications is realized through the interaction between the CSEs, the M2M application needs to be registered to the CSEs, and the CSEs also need to be registered with each other, so that the interaction between the M2M applications can be realized through the communication between the CSEs, and the M2M system architecture is shown in fig. 1.
In the M2M system architecture, the application node is an end execution node, such as a smart meter, a temperature measurement and control sensor, a fire alarm, a smart appliance, and the like; a Middle Node (Middle Node, abbreviated as MN) is middleware, such as a gateway, connecting an end execution Node to a network side server; the base Node (IN) is a server on the network side, and the application registered on the base Node, i.e. IN-AE, may be a management platform of an M2M service provider (M2M SP).
Fig. 1 is a structural diagram of a related art M2M system, and as shown in fig. 1, application nodes can be divided into two types according to different functions: nodes that contain CSEs and nodes that do not contain CSEs. Wherein, the Application specific node (ADN) at least contains one AE and does not contain CSE; the Application Service Node (ASN for short) at least comprises an AE and a CSE.
In the related art, when an AE or a CSE needs to perform operations such as acquisition or update on resources on a target CSE, an operation request message needs to be sent to the target CSE, where the request message includes an "operation execution time" parameter indicating an execution time of the operation; on the other hand, the resource on the target CSE includes an "effective time" attribute indicating the effective time of the resource. However, in the related art, there is a case where the resource has been lost and the operation request has not yet been executed, thereby causing a failure of the operation request.
In the related art, an effective solution is not provided for the problem that the operation request fails because the resource has failed and the operation request is still not executed.
Disclosure of Invention
The present invention provides a method and an apparatus for processing a resource operation request, so as to solve at least the problem in the related art that the operation request is still not executed due to the failure of the resource, which results in the failure of the operation request.
According to an aspect of the present invention, there is provided a method for processing a resource operation request, including: the first entity obtains the attribute value of the effective time attribute of the target resource in the second entity; when the first entity judges that the parameter value used for indicating the operation execution time of the target resource 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 a resource operation request message used for indicating the operation of the target resource; or, when the first entity determines that the parameter value for indicating the target resource operation execution time is not within the attribute value, the first entity suspends executing the resource operation request.
Further, the first entity updating the parameter in accordance with the attribute value by: and the first entity updates the parameter value according to the service logic.
Further, the obtaining, by the first entity, the attribute value of the target resource validity time attribute in the second entity includes: the first entity sends a resource acquisition request message to the second entity, wherein the resource acquisition request message carries an attribute name for indicating that the acquired content is the valid time attribute of the target resource; and the first entity receives a response message of the second entity responding to the resource acquisition request message, wherein the response message carries the attribute value of the effective time attribute.
Further, the obtaining, by the first entity, the attribute value of the target resource validity time attribute in the second entity includes: the first entity receives a request message for creating the announcement resource sent by the second entity, wherein the request message for creating the announcement resource carries an attribute value of the effective time attribute of the target resource; and the first entity creates the announcement resource of the target resource according to the creation announcement resource request message.
Further, before the first entity obtains the attribute value of the target resource valid time attribute in the second entity, the method includes: the first entity detects whether the resource operation request message carries the parameter value; and when the detection result is yes, the first entity caches the resource operation request message.
According to another aspect of the present invention, there is provided a processing apparatus for a resource operation request, located at a first entity side, including: an obtaining module, configured to obtain an attribute value of an effective time attribute of a target resource in a second entity; an updating module, configured to update a parameter value used for indicating the target resource operation execution time according to the attribute value when the first entity determines that the parameter value is not within the attribute value, where the parameter value is carried in a resource operation request message used for indicating to operate the target resource; or, the suspending module is configured to suspend executing the resource operation request when the first entity determines that the parameter value indicating the target resource operation execution time is not within the attribute value.
Further, the updating module is further configured to update the parameter value according to the service logic.
Further, the obtaining module includes: an obtaining unit, configured to send a resource obtaining request message to the second entity, where the resource obtaining request message carries an attribute name used to indicate that an obtained content is a target resource valid time attribute; a receiving unit, configured to receive a response message from the second entity in response to the resource obtaining request message, where the response message carries an attribute value of the valid time attribute.
Further, the obtaining module includes: a receiving module, configured to receive a request message for creating an announcement resource, where the request message for creating an announcement resource carries an attribute value of an effective time attribute of the target resource; and the creating module is used for creating the announcement resource of the target resource according to the announcement resource creating request message.
Further, the apparatus further comprises: a detection module, configured to detect whether the resource operation request message carries the parameter value; and the caching module is used for caching the resource operation request message when the detection result is yes.
According to the invention, after the first entity obtains the attribute value used for indicating the effective time of the target resource in the second entity, when the first entity judges that the parameter value of the operation execution time in the resource operation request message is no longer within the attribute value, 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 stops executing the resource operation request message; by the embodiment, the problem that the operation request fails because the resource fails and the operation request is still not executed in the related art is solved, and the resource operation request is effectively executed under the condition that the resource does not fail.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a block diagram of a structure of an M2M system in the related art;
FIG. 2 is a flow diagram of a method for processing a resource operation request according to an embodiment of the invention;
FIG. 3 is a block diagram of a device for processing a resource operation request according to an embodiment of the present invention;
FIG. 4 is a block diagram of an alternative structure of a device for processing a resource operation request according to an embodiment of the present invention;
FIG. 5 is a block diagram of an alternative structure of a resource operation request processing apparatus according to an embodiment of the present invention; and the number of the first and second groups,
fig. 6 is a block diagram of an alternative structure of a resource operation request processing device according to an embodiment of the present invention.
Detailed Description
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
This embodiment provides a method for processing a resource operation request, and 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 method includes the steps of:
step S202: the first entity obtains an attribute value used for indicating the effective time attribute of the target resource in the second entity;
step S204: when the parameter value used for indicating the operation execution time of the target resource is not within the attribute value, the first entity updates the parameter value according to the attribute value; alternatively, the first entity aborts executing the resource operation request.
Wherein, the parameter value is carried in a resource operation request message for indicating the operation of the target resource;
in this embodiment, after obtaining the attribute value used for indicating the target resource valid time in the second entity, when the first entity determines that the parameter value of the operation execution time in the resource operation request message is no longer within the attribute value, 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 terminates the resource operation request, that is, the first entity stops sending the resource operation request message to the second entity, that is, the operation execution time in the resource operation request message sent by the first entity to the second entity is definitely within the target resource valid time; by the embodiment, the problem that the operation request fails because the resource fails and the operation request is still not executed in the related art is solved, and the resource operation request is effectively executed under the condition that the resource does not fail.
It should be noted that, for the present embodiment, the first entity and the second entity may be AE or CSE.
In this embodiment, there are various ways for the first entity to update the parameter according to the attribute value, and in an optional implementation manner of this embodiment, updating the parameter value may be implemented by: the first entity updates the parameter values according to the business logic.
In this embodiment, the way in which the first entity obtains the attribute value of the second entity for indicating the target resource valid time attribute in step S202 has two layers, where the first layer is that the first entity actively obtains the attribute value of the resource valid time attribute in the second entity, and this way may be implemented by the following steps in an optional implementation manner of this embodiment:
step S11: a first entity sends a resource acquisition request message to a second entity, wherein the resource acquisition request message carries an attribute name for indicating that the acquired content is a target resource valid time attribute;
step S12: and the first entity receives a response message of the second entity responding to the resource acquisition request message, wherein the response message carries the attribute value of the effective time attribute.
For the way of actively acquiring the attribute value of the target resource valid time attribute, the first entity may be AE or CSE, and the second entity may be CSE.
However, in this embodiment, as for the second layer meaning of the manner in which the first entity obtains the attribute value of the attribute value used for indicating the target resource valid time attribute in the second entity in step S202, it is the attribute value of the resource valid time in the second entity obtained by the first entity, and this manner may be implemented in the following manner in an optional implementation manner of this embodiment:
step S21: a first entity receives a request message for creating an announcement resource sent by a second entity, wherein the request message for creating the announcement resource carries an attribute value for indicating an announcement resource valid time attribute of a target resource;
step S22: the first entity creates an announcement resource of the target resource according to the create announcement resource request message, wherein the announcement resource comprises part or all of the attributes of the target resource announced to the remote entity.
For the passive way of obtaining the attribute value of the target resource valid time attribute, both the first entity and the second entity may be CSEs.
In addition, in another optional implementation manner of this embodiment, before the first entity obtains the attribute value used for indicating the valid time of the target resource in the second entity, the method of this embodiment may further include:
step S31: the first entity detects whether the resource operation request message carries a parameter value;
step S32: and when the detection result is yes, the first entity caches the resource operation request message.
In this embodiment, a device for processing a resource operation request is further provided, where the device is used to implement the foregoing embodiment and optional embodiments, and details are not repeated for what has been described. As used hereinafter, the terms "module" and "unit" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 3 is a block diagram of a device for processing a resource operation request according to an embodiment of the present invention, which is located on a first entity side, as shown in fig. 3, and includes: an obtaining module 32, configured to obtain an attribute value in the second entity, which is used to indicate the valid time attribute of the target resource; an updating module 34, coupled to the obtaining module 32, configured to update a parameter value used for indicating the execution time of the target resource operation according to the attribute value when the parameter value is not within the attribute value, where the parameter value is carried in a resource operation request message used for indicating to operate the target resource; or the like, or, alternatively,
a suspending module 36, coupled to the obtaining module 32, configured to suspend the execution of the resource operation request message when the first entity determines that the parameter value indicating the target resource operation execution time is not within the attribute value.
For the updating module 34 involved in this embodiment, in an optional implementation manner of this embodiment, the updating module may be further configured to update the parameter according to the business logic.
Fig. 4 is a block diagram of an alternative structure of a resource operation request processing apparatus according to an embodiment of the present invention, as shown in fig. 4, the obtaining module 32 includes: an obtaining unit 42, configured to send a resource obtaining request message to a second entity, where the resource obtaining request message carries an attribute name of an attribute used to indicate that the obtained content is the valid time of the target resource; a receiving unit 44, coupled to the obtaining unit 42, configured to receive a response message of the second entity responding to the resource obtaining request message, where the response message carries the attribute value of the valid time attribute.
Fig. 5 is a block diagram of an alternative structure of a resource operation request processing apparatus according to an embodiment of the present invention, and as shown in fig. 5, the obtaining module 32 may further include: a receiving module 52, configured to receive a request message for creating an announcement resource sent by a second entity, where the request message for creating an announcement resource carries an attribute value for indicating an announcement resource valid time attribute of a target resource; a creating module 54, coupled to the receiving module 52, for creating an advertised resource of the target resource according to the create advertised resource request message.
Fig. 6 is a block diagram of an alternative structure of a device for processing a resource operation request according to an embodiment of the present invention, and as shown in fig. 6, the device may further include: the detection module 62 is coupled to the cache module 64 and configured to detect whether the resource operation request message carries a parameter value; and the caching module 62 is coupled to the obtaining module 32, and configured to cache the resource operation request message when the detection result is yes.
The invention will now be illustrated with reference to an alternative embodiment thereof;
the optional embodiment provides a method for processing a resource operation request, which can effectively avoid the disorder between the effective time of a resource and the operation execution time, thereby ensuring that the resource operation request can be effectively executed.
The following describes the present optional embodiment in detail in two ways that the local CSE may obtain the effective time attribute value of the target resource of the remote CSE through an active obtaining or passive obtaining manner;
alternative embodiment one (active acquisition)
Step S202: before the AE or local CSE (equivalent to the first entity) sends a resource operation request to the remote CSE (equivalent to the second entity), the AE or local CSE checks whether the request message contains an "operation execution time" parameter.
Step S204: if the checking result is yes, the AE or the local CSE caches the resource operation request and sends a resource acquisition request to the remote CSE, wherein the resource acquisition request message includes: the attribute of the target resource to be acquired is set to the "effective time" attribute.
Step S206: the remote CSE retrieves the "effective time" attribute of the target resource, reads the attribute value, and feeds back to the AE or local CSE via the response of the resource acquisition request message.
Step S208: and the AE or the local CSE judges 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: and if the judgment result is negative, 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.
Alternative embodiment two (passively available)
Step S302: the remote CSE sends a request for creating an announcement resource to the local CSE, wherein the request message comprises: the attribute of the original resource (target resource) that needs to be created has its value set to the "validity time" attribute.
Step S304: the local CSE creates an advertised resource for the original resource and creates a "validity time" attribute in the advertised resource.
Step S306: before the local CSE sends a resource operation request to the remote CSE, the local CSE checks whether the request message contains an "operation execution time" parameter.
Step S308: and if so, the local CSE searches the attribute of the effective time in the notice resource of the target resource, reads the attribute value and judges whether the operation execution time of the resource operation request is within the duration of the effective time of the resource.
Step S310: and if the judgment result is negative, 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 resource, or cancels the resource operation request.
The following illustrates the alternative embodiment with reference to specific embodiments thereof;
the first embodiment is as follows:
the embodiment is described with respect to a manner in which an AE or a local CSE actively acquires a resource valid time attribute value; the steps of this approach include:
step S402: when the AE or the local CSE needs to operate the Resource "Resource 1" on the remote CSE, the AE or the local CSE checks whether the operation request message of the Resource contains the parameter of "operation execution time".
Step S404: if the checking result is yes, the AE or the local CSE caches an operation request message of the Resource "Resource 1" and sends a Resource acquisition request to the remote CSE, where the Resource acquisition request message includes: the address of the Resource, the value of which is set to the uniform Resource identifier URI of the Resource "Resource 1"; an attribute for indicating the Resource "Resource 1" that needs to be acquired, the value of which is set to the "validity time" attribute.
Step S406: after the remote CSE passes authorization authentication of the AE or the local CSE, the Resource "Resource 1" is located according to the URI of the Resource "Resource 1" contained in the request message, the attribute of "effective time" of the Resource "Resource 1" is retrieved according to the attribute which is indicated to be acquired in the request message, the attribute value is read, and the request response is fed back to the AE or the local CSE through the Resource acquisition, wherein the response message contains: the attribute of the Resource "Resource 1" that needs to be acquired has its value set to the attribute value of the attribute "valid time".
Step S408: after receiving the acquisition operation response, the AE or CSE analyzes the content information contained in the response message, reads the attribute value of the "effective time" attribute of the Resource "Resource 1", and determines whether the operation execution time of the operation request for the Resource "Resource 1" is within the duration of the effective time of the Resource "Resource 1".
Step S410: if the result is yes, the AE or the local CSE adjusts the operation execution time of the operation request for the Resource "Resource 1" according to the service logic, that is, updates the "operation execution time" parameter in the cached Resource operation request message, and then sends the Resource operation request message to the remote CSE.
Step S412: after receiving the Resource operation request, the remote CSE caches the request message, sends a Resource operation response to the AE or the local CSE, and confirms that the operation request for the Resource "Resource 1" is received.
Step S414: the remote CSE sets a 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 executes an operation request for Resource "Resource 1" and feeds back an operation response to the AE or the local CSE, the result of the execution of the operation being contained in the response message.
Step S416: after receiving the Resource operation response, the AE or the local CSE processes the cached operation request message for the Resource "Resource 1" according to the operation result for the Resource "Resource 1" contained in the response message; and if the execution result indicates that the operation is successful, removing the cache message.
Example two:
the second embodiment explains the way of obtaining the attribute value of the effective time of the resource passively by AE or local CSE; the steps of this approach include:
step S502: the remote CSE sends a request for creating an announcement Resource to the local CSE, and announces a Resource 'Resource 2' to the local CSE, wherein the request message comprises: the attribute of Resource2 that needs to be created has its value set to the "validity time" attribute.
Step S504: after the local CSE passes the authorization authentication of the remote CSE, an announcement Resource "Resource 2 Annc" is created for the Resource "Resource 2", an attribute of "effective time" is created in the announcement Resource "Resource 2 Annc", and an attribute value of the attribute of "effective time" is set according to the content information in the request message.
Step S506: when the local CSE needs to operate the Resource 'Resource 2' on the remote CSE, whether the operation request message for the Resource contains the 'operation execution time' parameter is checked.
Step S508: if the result of the check is yes, the local CSE caches the operation request message for the Resource "Resource 2", retrieves the announcement Resource "Resource 2 Annc" of the Resource "Resource 2" according to the identifier of the Resource "Resource 2", reads the attribute value of the attribute of "effective time" of the Resource, and judges whether the operation execution time of the operation request for the Resource "Resource 2" is within the duration of the effective time of the Resource "Resource 2".
Step S510: if the result is yes, the local CSE adjusts the operation execution time of the operation request for the Resource "Resource 2" according to the service logic, that is, updates the "operation execution time" parameter in the cached operation request message for the Resource, and then sends the request message to the remote CSE.
Step S512: after the remote CSE passes the authorization authentication of the local CSE, the remote CSE caches the request message, sends a Resource operation response to the local CSE and confirms that the operation request of the Resource 'Resource 2' is accepted.
Step S514: the remote CSE sets a 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 executes an operation request for the Resource "Resource 2" and feeds back an operation response to the local CSE, wherein the execution result of the operation is contained in the response message.
Step S516: after receiving the Resource operation response, the local CSE processes the operation request message of the cached Resource 'Resource 2' according to the operation result of the Resource 'Resource 2' contained in the response message; if the execution result indicates that the operation failed, the buffered message is retransmitted.
By means of the optional embodiment, disorder between the resource effective time and the operation execution time is avoided, and the resource operation request can be effectively executed.
In another embodiment, a software is provided, and the software is used for executing the technical solutions described in the above embodiments and optional implementation manners.
In another embodiment, a storage medium is provided, in which the software is stored, and the storage medium includes but is not limited to: optical disks, floppy disks, hard disks, erasable memory, etc.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only an alternative embodiment of the present invention and is not intended to limit the present invention, and various modifications and variations of the present invention may occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A method for processing a resource operation request is characterized by comprising the following steps:
the first entity obtains the attribute value of the effective time attribute of the target resource in the second entity;
when the first entity judges that the parameter value used for indicating the operation execution time of the target resource 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 a resource operation request message used for indicating the operation of the target resource; or the like, or, alternatively,
when the first entity judges that a parameter value used for indicating the target resource operation execution time is not within the attribute value, the first entity suspends executing the resource operation request;
the obtaining, by the first entity, the attribute value of the target resource valid time attribute in the second entity includes:
the first entity sends a resource acquisition request message to the second entity, wherein the resource acquisition request message carries an attribute name for indicating that the acquired content is the valid time attribute of the target resource;
and the first entity receives a response message of the second entity responding to the resource acquisition request message, wherein the response message carries the attribute value of the effective time attribute.
2. The method of claim 1, wherein the first entity updating the parameter in accordance with the attribute value by:
and the first entity updates the parameter value according to the service logic.
3. The method of claim 1, wherein obtaining, by the first entity, the attribute value of the target resource validity time attribute in the second entity comprises:
the first entity receives a request message for creating the announcement resource sent by the second entity, wherein the request message for creating the announcement resource carries an attribute value of the effective time attribute of the target resource;
and the first entity creates the announcement resource of the target resource according to the creation announcement resource request message.
4. The method according to claim 1 or 3, comprising, before the first entity obtains the attribute value of the target resource validity time attribute in the second entity:
the first entity detects whether the resource operation request message carries the parameter value;
and when the detection result is yes, the first entity caches the resource operation request message.
5. An apparatus for processing a resource operation request, located at a first entity side, comprising:
an obtaining module, configured to obtain an attribute value of an effective time attribute of a target resource in a second entity;
an updating module, configured to update a parameter value used for indicating the target resource operation execution time according to the attribute value when the first entity determines that the parameter value is not within the attribute value, where the parameter value is carried in a resource operation request message used for indicating to operate the target resource; or the like, or, alternatively,
a suspension module, configured to suspend executing the resource operation request when the first entity determines that a parameter value indicating the target resource operation execution time is not within the attribute value;
wherein the obtaining module comprises:
an obtaining unit, configured to send a resource obtaining request message to the second entity, where the resource obtaining request message carries an attribute name used to indicate that an obtained content is a target resource valid time attribute;
a receiving unit, configured to receive a response message from the second entity in response to the resource obtaining request message, where the response message carries an attribute value of the valid time attribute.
6. The apparatus of claim 5, wherein the updating module is further configured to update the parameter value according to business logic.
7. The apparatus of claim 5, wherein the obtaining module comprises:
a receiving module, configured to receive a request message for creating an announcement resource, where the request message for creating an announcement resource carries an attribute value of an effective time attribute of the target resource;
and the creating module is used for creating the announcement resource of the target resource according to the announcement resource creating request message.
8. The apparatus of claim 5 or 7, further comprising:
a detection module, configured to detect whether the resource operation request message carries the parameter value;
and the caching module is used for caching the resource operation request message when the detection result is yes.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510036108.0A CN105871963B (en) | 2015-01-23 | 2015-01-23 | Method and device for processing resource operation request |
| PCT/CN2015/087410 WO2016115885A1 (en) | 2015-01-23 | 2015-08-18 | Method and apparatus for processing resource operation request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510036108.0A CN105871963B (en) | 2015-01-23 | 2015-01-23 | Method and device for processing resource operation request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105871963A CN105871963A (en) | 2016-08-17 |
| CN105871963B true CN105871963B (en) | 2020-05-19 |
Family
ID=56416374
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510036108.0A Expired - Fee Related CN105871963B (en) | 2015-01-23 | 2015-01-23 | Method and device for processing resource operation request |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105871963B (en) |
| WO (1) | WO2016115885A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106953791B (en) * | 2016-11-30 | 2021-01-26 | 创新先进技术有限公司 | Information sending method and device |
| CN110769017A (en) * | 2018-07-27 | 2020-02-07 | 北京国双科技有限公司 | Data request processing method and device, storage medium and processor |
| CN110531972B (en) * | 2019-09-05 | 2024-02-06 | 无锡华云数据技术服务有限公司 | Editing method and device for resource arrangement resource attribute |
| US11954532B2 (en) * | 2020-05-29 | 2024-04-09 | Pollen, Inc. | Reconciling resource management platforms |
| CN112115303B (en) * | 2020-09-02 | 2023-10-03 | 北京达佳互联信息技术有限公司 | Data processing method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101059999A (en) * | 2006-04-19 | 2007-10-24 | 欧丽旺电机株式会社 | Information processing device including manipulation task reservation function |
| CN101997878A (en) * | 2010-11-23 | 2011-03-30 | 蓝汛网络科技（北京）有限公司 | Method, device and system for verifying domain name link |
| CN102186164A (en) * | 2011-02-18 | 2011-09-14 | 华为技术有限公司 | Method and management device for operating device resource |
| CN103299601A (en) * | 2010-11-19 | 2013-09-11 | 交互数字专利控股公司 | Machine-to-machine (M2M) interface procedures for announce and de-announce of resources |
| US8856325B2 (en) * | 2012-04-17 | 2014-10-07 | Robert Hansen | Network element failure detection |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346460B (en) * | 2011-05-27 | 2013-11-13 | 运软网络科技(上海)有限公司 | Transaction-based service control system and method |
| CN103810046A (en) * | 2012-11-15 | 2014-05-21 | 百度在线网络技术（北京）有限公司 | Method and system for managing resources in single machine |
| CN104113939A (en) * | 2013-04-17 | 2014-10-22 | 中兴通讯股份有限公司 | Method and device for processing operation on terminal peripheral |
-
2015
- 2015-01-23 CN CN201510036108.0A patent/CN105871963B/en not_active Expired - Fee Related
- 2015-08-18 WO PCT/CN2015/087410 patent/WO2016115885A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101059999A (en) * | 2006-04-19 | 2007-10-24 | 欧丽旺电机株式会社 | Information processing device including manipulation task reservation function |
| CN103299601A (en) * | 2010-11-19 | 2013-09-11 | 交互数字专利控股公司 | Machine-to-machine (M2M) interface procedures for announce and de-announce of resources |
| CN101997878A (en) * | 2010-11-23 | 2011-03-30 | 蓝汛网络科技（北京）有限公司 | Method, device and system for verifying domain name link |
| CN102186164A (en) * | 2011-02-18 | 2011-09-14 | 华为技术有限公司 | Method and management device for operating device resource |
| US8856325B2 (en) * | 2012-04-17 | 2014-10-07 | Robert Hansen | Network element failure detection |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016115885A1 (en) | 2016-07-28 |
| CN105871963A (en) | 2016-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10666661B2 (en) | Authorization processing method and device | |
| CN105871963B (en) | Method and device for processing resource operation request | |
| US9479477B2 (en) | Method and apparatus for registering terminal | |
| US10506432B2 (en) | Method and apparatus for authenticating access authority for specific resource in wireless communication system | |
| US10638496B2 (en) | Method and apparatus for group management during machine-to-machine communication | |
| US10231107B2 (en) | Resource subscription processing method and device | |
| US10270811B2 (en) | Security domain management method, apparatus, and system | |
| EP3206422A1 (en) | Method and device for creating subscription resource | |
| CN110460978B (en) | Resource access method and device | |
| CN104683968A (en) | Machine type communication application resource management method, node and system | |
| US10070408B2 (en) | Application registration methods and apparatuses | |
| CN105282682B (en) | Method for realizing resource attribute notification and public service entity | |
| KR20170033267A (en) | Method for processing request message in wireless communication system and apparatus therefor | |
| JP2018511206A (en) | Certificate management method, device, and system | |
| CN105323186B (en) | Notification message load control method and device | |
| US11012830B2 (en) | Automated activation and onboarding of connected devices | |
| CN105791339B (en) | Method and device for processing resource operation request | |
| US20220053030A1 (en) | Enhancements for secure updating in communication networks | |
| US20230115969A1 (en) | Method and device for synchronization for resource offloading in m2m system | |
| CN110430268A (en) | Static resource method for routing and device based on Distributed Services | |
| CN115996377A (en) | Slice authentication and authorization method and device, terminal and network equipment | |
| US20170149754A1 (en) | Login Processing Method and Device of Machine-to-Machine/Man Communication Terminal Equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200519 Termination date: 20220123 |