CN107113225B - Method and entity for subscribing to notifications in a machine communication system - Google Patents

Abstract

The invention discloses a method and an entity for subscribing notification. The method comprises the following steps: a server entity receives a notification cancellation indication sent by a receiving end entity; when the receiving end entity has the right, the server end entity modifies the resource attribute according to the notification cancellation indication and stops sending the notification to the receiving end entity, wherein the resource attribute comprises a notification uniform resource identifier; the server entity sends a subscription modification notification message to the subscriber entity, wherein the subscription modification notification message is used for notifying the subscriber entity of the modification of the resource attribute by the server entity; the subscribing entity and the receiving entity are two different entities in the machine communication system, the subscribing entity is a subscription initiator of the notification, and the receiving entity is a receiver of the notification. The embodiment of the invention can improve the flexibility of subscription modification.

Description

Method and entity for subscribing to notifications in a machine communication system

technical field

Embodiments of the present invention relate to the field of communications, and more particularly, to a method and entity for subscribing to notifications in a machine communication system.

Background technique

Machine-to-Machine Communications (English: Machine-to-Machine Communications, M2M for short) is a networked application and service centered on machine intelligent interaction. By embedding wireless or wired communication modules and application processing logic inside the machine, machine communication can realize data communication without manual intervention to meet users' informatization needs for monitoring, command and dispatch, data collection and measurement.

The overall goal of the unified machine-to-machine (English: one Machine to Machine, oneM2M) standard organization for machine communication is to create an open standard for the business layer of M2M communication to promote the establishment of a future network that integrates various devices and services. The interoperability of M2M services also enables M2M applications to share basic services and be implemented independently of the network.

Currently, M2M communication can be based on wired and wireless methods. Wireless methods include cellular network and short-range, among which 3GPP cellular network is a widely used wireless method. In oneM2M, one entity can subscribe to notifications for several other entities, such as subscribing weather forecasts to the weather forecast platform for several other entities. However, since the receiver of the notification (several other entities) is not the subscription initiator, they cannot modify the resource corresponding to the notification.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide a method and entity for subscribing to notifications in a machine communication system, which can improve the flexibility of subscription modification.

In a first aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The server entity receives the notification cancellation instruction sent by the receiver entity;

When the receiver entity has the authority, the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, and the resource attribute includes the notification uniform resource identifier;

The server entity sends a subscription modification notification message to the subscriber entity, and the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the first aspect, in a first implementation manner of the first aspect, the server entity modifies the resource attributes according to the notification cancellation instruction, including:

The server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the notification cancellation instruction.

In combination with the first aspect and the above-mentioned implementation manner, in the second implementation manner of the first aspect, the server entity receives the notification cancellation indication sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification cancellation indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification cancellation indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification cancellation indication.

In a second aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The server entity receives the notification cancellation instruction sent by the receiver entity;

When the receiver entity has no authority, the server entity sends a notification cancellation instruction to the subscriber entity;

The server entity receives the update request message sent by the subscriber entity according to the notification cancellation instruction;

The server entity modifies the resource attribute according to the update request message, and stops sending notifications to the receiver entity, and the resource attribute includes the notification uniform resource identifier;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the second aspect, in a first implementation manner of the second aspect, the server entity modifies the resource attributes according to the update request message, including:

The server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the update request message.

In combination with the second aspect and the above-mentioned implementation manners, in a second implementation manner of the second aspect, the server entity receives the notification cancellation indication sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification cancellation indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification cancellation indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification cancellation indication.

In a third aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The recipient entity generates a notification cancellation indication;

The receiver entity sends a notification cancellation instruction to the server entity, so that the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, and the resource attribute includes the notification uniform resource identifier;

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

With reference to the third aspect, in a first implementation manner of the third aspect, the receiving-end entity sends a notification cancellation indication to the server-end entity, including:

The receiving-end entity sends an update message to the server-end entity, and the update message carries the notification cancellation indication; or

The receiver entity sends a notification response message to the server entity, and the notification response message carries the notification cancellation indication; or

The receiver entity sends a notification request message to the server entity, and the notification request message carries a notification cancellation indication.

In a fourth aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The subscriber entity receives the notification cancellation instruction sent by the server entity, and the notification cancellation instruction is sent by the receiver entity to the server entity;

The subscriber entity sends an update request message to the server entity according to the notification cancellation instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes the notification uniform resource identifier;

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

In a fifth aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The server entity receives the notification modification instruction sent by the receiver entity;

When the receiver entity has the authority, the server entity modifies the resource attribute according to the notification modification instruction, and sends a notification to the receiver entity based on the modified resource attribute, and the resource attribute includes the notification sending rule;

The server entity sends a subscription modification notification message to the subscriber entity, and the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the fifth aspect, in the first implementation manner of the fifth aspect, the server entity modifies the resource attribute according to the notification modification instruction, including:

The server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

With reference to the fifth aspect and the above-mentioned implementation manner, in the second implementation manner of the fifth aspect, the server entity receives the notification modification instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification modification indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification modification indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification modification indication.

With reference to the fifth aspect and the above implementation manners thereof, in a third implementation manner of the fifth aspect, before the server entity receives the notification modification instruction sent by the receiver entity, the method further includes:

The server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate a notification modification instruction according to the resource attribute.

With reference to the fifth aspect and the foregoing implementation manners thereof, in a fourth implementation manner of the fifth aspect, the sending rule includes one or more of a sending period, an information type, and an expiration time.

In a sixth aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The server entity receives the notification modification instruction sent by the receiver entity;

When the receiver entity has no authority, the server entity sends a notification modification instruction to the subscriber entity;

The server entity receives the update request message sent by the subscriber entity according to the notification modification instruction;

The server entity modifies the resource attribute according to the update request message, and sends a notification to the receiver entity based on the modified resource attribute, and the resource attribute includes the notification sending rule;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the sixth aspect, in the first implementation manner of the sixth aspect, the server entity modifies the resource attributes according to the notification modification instruction, including:

The server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

In combination with the sixth aspect and the above-mentioned implementation manners, in the second implementation manner of the sixth aspect, the server entity receives the notification modification instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification modification indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification modification indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification modification indication.

In combination with the sixth aspect and the above-mentioned implementation manner, in a third implementation manner of the sixth aspect, before the server entity receives the notification modification instruction sent by the receiver entity, the method further includes:

The server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate a notification modification instruction according to the resource attribute.

With reference to the sixth aspect and the above-mentioned implementation manners, in a fourth implementation manner of the sixth aspect, the sending rule includes one or more of a sending period, an information type, and an expiration time.

In a seventh aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The recipient entity generates a notification modification indication;

The receiver entity sends a notification modification instruction to the server entity, so that the server entity modifies the resource attribute according to the notification modification instruction, and sends a notification to the receiver entity based on the modified resource attribute, and the resource attribute includes the notification sending rule;

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

With reference to the seventh aspect, in a first implementation manner of the seventh aspect, the receiving-end entity sends a notification modification instruction to the server-end entity, including:

The receiving-end entity sends an update message to the server-end entity, and the update message carries the notification modification indication; or

The receiver entity sends a notification response message to the server entity, and the notification response message carries the notification modification indication; or

The receiver entity sends a notification request message to the server entity, and the notification request message carries a notification modification indication.

In combination with the seventh aspect and the above-mentioned implementation manner, in the second implementation manner of the seventh aspect, before the receiving-end entity generates the notification modification instruction, the method further includes:

The receiving-end entity receives the resource attributes sent by the server-end entity;

The receiving entity generates notification modification instructions, including:

The receiving-end entity generates a notification modification instruction according to the resource attribute.

In an eighth aspect, an embodiment of the present invention provides a method for subscribing to notifications in a machine communication system, including:

The subscriber entity receives the notification modification instruction sent by the server entity, and the notification modification instruction is sent by the receiver entity to the server entity;

The subscriber entity sends an update request message to the server entity according to the notification modification instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes the notification sending rule;

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

In a ninth aspect, an embodiment of the present invention provides a server entity for subscribing to notifications in a machine communication system, including:

a receiving unit, configured to receive a notification cancellation instruction sent by the receiving-end entity;

The processing unit, when the receiving-end entity has the authority, is used to modify the resource attribute according to the notification cancellation instruction, and stop sending the notification to the receiving-end entity, and the resource attribute includes the notification uniform resource identifier;

a sending unit, configured to send a subscription modification notification message to the subscriber entity, and the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the ninth aspect, in a first implementation manner of the ninth aspect, the processing unit is specifically configured to, according to the notification cancellation indication, delete the identifier of the receiving end entity in the notification uniform resource identifier.

In conjunction with the ninth aspect and the above-mentioned implementation manner, in the second implementation manner of the ninth aspect, the receiving unit is specifically used for,

Receive an update message sent by the receiver entity, and the update message carries a notification cancellation indication; or

Receive a notification response message sent by the receiver entity, and the notification response message carries a notification cancellation indication; or

Receive a notification request message sent by the receiver entity, where the notification request message carries a notification cancellation indication.

In a tenth aspect, an embodiment of the present invention provides a server entity for subscribing to notifications in a machine communication system, including:

a first receiving unit, configured to receive a notification cancellation indication sent by the receiving-end entity;

The sending unit, when the receiving-end entity has no authority, is used to send a notification cancellation instruction to the subscribing-end entity;

a second receiving unit, configured to receive an update request message sent by the subscriber entity according to the notification cancellation indication;

a processing unit, configured to modify the resource attribute according to the update request message, and stop sending the notification to the receiver entity, where the resource attribute includes the notification uniform resource identifier;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the tenth aspect, in a first implementation manner of the tenth aspect, the processing unit is specifically configured to delete the identifier of the receiving end entity in the notification uniform resource identifier according to the notification cancellation indication.

In combination with the tenth aspect and the above-mentioned implementation manner, in the second implementation manner of the tenth aspect, the first receiving unit is specifically configured to:

Receive an update message sent by the receiver entity, and the update message carries a notification cancellation indication; or

Receive a notification response message sent by the receiver entity, and the notification response message carries a notification cancellation indication; or

Receive a notification request message sent by the receiver entity, where the notification request message carries a notification cancellation indication.

In an eleventh aspect, an embodiment of the present invention provides a receiver entity for subscribing to notifications in a machine communication system, including:

a generating unit for generating a notification cancellation instruction;

a sending unit, configured to send a notification cancellation instruction to the server entity, so that the server entity can modify the resource attribute according to the notification cancellation instruction, and stop sending the notification to the receiving end entity, and the resource attribute includes the notification uniform resource identifier;

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

In conjunction with the eleventh aspect, in the first implementation manner of the eleventh aspect, the sending unit is specifically configured to:

Send an update message to the server entity, and the update message carries the notification cancellation indication; or

Send a notification response message to the server entity, and the notification response message carries the notification cancellation indication; or

Send a notification request message to the server entity, where the notification request message carries a notification cancellation indication.

In a twelfth aspect, an embodiment of the present invention provides a subscriber entity for subscribing to notifications in a machine communication system, including:

a receiving unit, configured to receive a notification cancellation instruction sent by the server entity, where the notification cancellation instruction is sent by the receiver entity to the server entity;

a sending unit, configured to send an update request message to the server entity according to the notification cancellation instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes the notification uniform resource identifier;

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

In a thirteenth aspect, an embodiment of the present invention provides a server entity for subscribing to notifications in a machine communication system, including:

a receiving unit, configured to receive a notification modification instruction sent by the receiving end entity;

The processing unit, when the receiving-end entity has the authority, is used to modify the resource attribute according to the notification modification instruction, and send a notification to the receiving-end entity based on the modified resource attribute, and the resource attribute includes the sending rule of the notification;

a sending unit, configured to send a subscription modification notification message to the subscriber entity, and the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity;

Among them, the subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the thirteenth aspect, in a first implementation manner of the thirteenth aspect, the processing unit is specifically configured to modify the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction.

In conjunction with the thirteenth aspect and the above-mentioned implementation manner, in the second implementation manner of the thirteenth aspect, the receiving unit is specifically configured to:

Receive an update message sent by the receiver entity, and the update message carries a notification modification indication; or

Receive a notification response message sent by the receiver entity, and the notification response message carries a notification modification indication; or

Receive a notification request message sent by the receiver entity, where the notification request message carries a notification modification indication.

In combination with the thirteenth aspect and the above-mentioned implementation manner, in a third implementation manner of the thirteenth aspect, the sending unit is further configured to send the resource attribute to the receiving-end entity, so that the receiving-end entity can generate a notification modification according to the resource attribute instruct.

With reference to the thirteenth aspect and the foregoing implementation manners thereof, in a fourth implementation manner of the thirteenth aspect, the sending rule includes one or more of a sending period, an information type, and an expiration time.

In a fourteenth aspect, an embodiment of the present invention provides a server entity for subscribing to notifications in a machine communication system, including:

a first receiving unit, configured to receive a notification modification instruction sent by the receiving-end entity;

The sending unit, when the receiving-end entity has no authority, is used to send a notification modification instruction to the subscribing-end entity;

a second receiving unit, configured to receive an update request message sent by the subscriber entity according to the notification modification instruction;

a processing unit, configured to modify the resource attribute according to the update request message, and send a notification to the receiver entity based on the modified resource attribute, where the resource attribute includes a notification sending rule;

The subscriber entity and the receiver entity are two different entities, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification, and is not the subscription initiator of the notification.

With reference to the fourteenth aspect, in a first implementation manner of the fourteenth aspect, the processing unit is specifically configured to modify the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction.

In combination with the fourteenth aspect and the above-mentioned implementation manner, in the second implementation manner of the fourteenth aspect, the first receiving unit is specifically configured to:

Receive an update message sent by the receiver entity, and the update message carries a notification modification indication; or

Receive a notification response message sent by the receiver entity, and the notification response message carries a notification modification indication; or

Receive a notification request message sent by the receiver entity, where the notification request message carries a notification modification indication.

In combination with the fourteenth aspect and the above-mentioned implementation manner, in a third implementation manner of the fourteenth aspect, the sending unit is further configured to send the resource attribute to the receiving-end entity, so that the receiving-end entity can generate a notification modification according to the resource attribute instruct.

With reference to the fourteenth aspect and the foregoing implementation manners thereof, in a fourth implementation manner of the fourteenth aspect, the sending rule includes one or more of a sending period, an information type, and an expiration time.

In a fifteenth aspect, an embodiment of the present invention provides a receiver entity for subscribing to notifications in a machine communication system, including:

a generating unit for generating a notification modification instruction;

The sending unit is used to send a notification modification instruction to the server entity, so that the server entity can modify the resource attribute according to the notification modification instruction, and send a notification to the receiving end entity based on the modified resource attribute, and the resource attribute includes the notification sending rule ;

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

In conjunction with the fifteenth aspect, in the first implementation manner of the fifteenth aspect, the sending unit is specifically configured to:

Send an update message to the server entity, and the update message carries the notification modification indication; or

Send a notification response message to the server entity, and the notification response message carries the notification modification indication;

Send a notification request message to the server entity, where the notification request message carries the notification modification indication.

In conjunction with the fifteenth aspect and the above-mentioned implementation manner, in a second implementation manner of the fifteenth aspect, the entity further includes a receiving unit,

a receiving unit, configured to receive the resource attribute sent by the server entity;

The generating unit is specifically configured to generate the notification modification instruction according to the resource attribute.

In a sixteenth aspect, an embodiment of the present invention provides a subscriber entity for subscribing to notifications in a machine communication system, including:

a receiving unit, configured to receive a notification modification instruction sent by the server entity, where the notification modification instruction is sent by the receiver entity to the server entity;

a sending unit, configured to send an update request message to the server entity according to the notification modification instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes the sending rule of the notification;

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification cancellation instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

FIG. 1 shows a schematic frame diagram of a unified machine-to-machine system according to an embodiment of the present invention.

FIG. 2 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to an embodiment of the present invention.

FIG. 3 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 4 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 5 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 6 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 7 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 8 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 9 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 10 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 11 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 12 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 13 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

FIG. 14 is a schematic block diagram of a server entity in a machine communication system according to an embodiment of the present invention.

FIG. 15 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention.

FIG. 16 is a schematic block diagram of a receiver entity in a machine communication system according to an embodiment of the present invention.

FIG. 17 is a schematic block diagram of a subscriber entity in a machine communication system according to an embodiment of the present invention.

FIG. 18 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention.

FIG. 19 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention.

FIG. 20 is a schematic block diagram of a receiver entity in a machine communication system according to another embodiment of the present invention.

FIG. 21 is a schematic block diagram of a subscriber entity in a machine communication system according to another embodiment of the present invention.

FIG. 22 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

FIG. 1 shows a schematic frame diagram of a unified machine-to-machine system according to an embodiment of the present invention. As shown in Figure 1, the oneM2M system is divided into an application layer, a public service layer and a network service layer. Among them, the application layer is managed by an application entity (Application Entity, "AE" for short) and is responsible for the relevant operation and storage of the application, and the application layer contains the instantiated end-to-end oneM2M solution. The public service layer is managed by the Common Services Entity (CSE for short), which is responsible for aggregating application layer information to form a resource pool, and at the same time coordinating the underlying network transmission. It is the core layer in oneM2M that plays the role of a platform. A series of instantiated public service functions. The network layer is managed by a network service entity (Network Services Entity, "NSE" for short), responsible for the transmission of the underlying network, and provides the public service layer with the capabilities that the underlying network can provide.

There are three types of reference points (ie interfaces) between the lower layers and the layers of the oneM2M system. Among them, Mca: the interface between the AE and the CSE, responsible for the communication between the AE and the CSE or between the CSE and the AE; Mcc/Mcc': two CSEs Interface between CSEs, responsible for communication between CSEs; Mcn: interface between CSE and NSE, responsible for communication between CSE to NSE or NSE to CSE. There is also a Mch reference point (not shown in the figure), which is the interface between the oneM2M system and the billing system.

The oneM2M system architecture is mainly divided into two domains: infrastructure domain (Infrastructure Domain, referred to as "IN") and field domain (Field Domain). A node (Application Service Node, referred to as "ASN" for short) and an application dedicated node (Application Dedicated Node, referred to as "AND" for short), the infrastructure domain includes public nodes. Except that the ADN node only includes AE, all other nodes include CSE.

It should be understood that, in this embodiment of the present invention, all entities in the oneM2M system, such as AE and CSE information and data information, may be represented by resources. The resource structure defines the representation of resources in detail, and defines the way to obtain these resources. These resources are individually addressable. The subscriber entity (originator) can subscribe to the server entity (hosting CSE) for notifications of resource or sub-resource changes for the receiver entity (notification receiver). For example, the subscriber entity sends a subscription creation request to the server entity, and the subscription creation request carries the identifier address of the resource or sub-resource under the server entity, the identifier of the recipient entity (notificationURI), and the content and type of the notification (notificationContentType). And the conditions that trigger the notification (eventNotificationCriteria), etc. The receiving entity creates the subscription sub-resource locally according to the subscription creation request. The embodiments of the present invention provide a method and entity for subscribing resources, which can improve the flexibility of subscription modification in the foregoing subscription process.

It should also be understood that, in this embodiment of the present invention, creating a resource can be considered as creating a resource that does not include attributes, or it can be considered as creating a resource including attributes, and updating a resource can be considered as creating an attribute under the resource, or it can be considered as creating an attribute under the resource. Updating the attribute value of an attribute under the resource may also delete an attribute under the resource, and, in this embodiment of the present invention, the "create" attribute and the "update" attribute are often used interchangeably, "storage" and "store" are often used interchangeably. "Create" and even "update" are often used interchangeably. Properties under resources, properties of resources, and properties included in resources represent the same meaning. Resources or properties can refer to information that has been created (or stored). It can also refer to information that has been determined but not yet created (or stored), which is not limited in the present invention.

The identifier in the present invention is the identifier of the entity or the address identifier, which is not limited in the present invention.

FIG. 2 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to an embodiment of the present invention. The method shown in FIG. 2 may be performed by a server entity (Hosting CSE). The method includes:

201. The server entity receives the notification cancellation indication sent by the receiver entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) no longer wants to receive notifications, it can actively send a notification cancellation instruction to the server entity. Specifically, the timing for initiating the notification cancellation indication may be in the process of receiving the notification, or before the notification is received, which is not limited in this embodiment of the present invention. In addition, it can also optionally carry the identifier or address of the receiving end entity.

202 , when the receiving-end entity has the authority, the server-end entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiving-end entity, and the resource attribute notifies a uniform resource identifier (notificationURI).

For example, the server can first determine whether the recipient entity has permission to modify the resource attributes. If the receiving-end entity has the right, the server-end entity may modify the resource attribute corresponding to the receiving-end entity according to the notification cancellation instruction. The resource attribute includes a receiver identifier (notificationURI).

203 , the server entity sends a subscription modification notification message to the subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity.

For example, when the server entity completes the modification of the resource attribute, it can notify the subscriber entity of the specific modification content of the resource attribute of the receiver entity. In this way, the subscriber entity can adjust the payment according to the modified content, etc. It should be understood that the subscription modification message should include the identifier of the receiver entity (notification receiver ID). Another optional implementation is that the subscription modification message contains the modified resource attribute including the receiver ID (notificationURI), so that the subscriber entity can Know which receiver entity has modified the subscription resource.

In addition, the subscription modification message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The subscriber entity and the receiver entity are two different entities in the machine communication system. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification criteria attribute in the subscription resource is satisfied.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification cancellation instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, when modifying the resource attribute according to the notification cancellation instruction, the server entity deletes the identifier of the recipient entity in the notification uniform resource identifier according to the notification cancellation instruction.

For example, when the server entity receives a subscription cancellation indication (stop receiving notification, or notification cancellation) sent by the receiver entity, it deletes the identifier (URI) of the receiver entity in the notification uniform resource identifier. At the same time, stop sending notification messages to the receiving entity.

Optionally, as another embodiment, when receiving the notification cancellation indication sent by the receiver entity, an update message sent by the receiver entity is received, and the update message carries the notification cancellation indication. Alternatively, the server entity receives a notification response message sent by the receiver entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification cancellation indication. Or, the server entity receives the notification request message generated by the receiver entity, and the notification request message carries the notification cancellation indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. Or, the receiving-end entity carries the notification cancellation indication in the notification response message (notify response) of the notification request (notify request) to the server entity. Alternatively, the recipient entity may send a notify request to the server entity.

FIG. 3 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in FIG. 3 may be performed by a hosting CSE. The method includes:

301. The server entity receives the notification cancellation indication sent by the receiver entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) no longer wants to receive notifications, it can actively send a notification cancellation instruction to the server entity. Specifically, the timing for initiating the notification cancellation indication may be in the process of receiving the notification, or before the notification is received, which is not limited in this embodiment of the present invention.

302 , when the receiver entity has no authority, the server entity sends a notification cancellation indication to the subscriber entity.

For example, the server entity may first determine whether the receiver entity has permission to modify the resource attributes. If the receiving-end entity does not have permission, the server-end entity may first send the notification cancellation instruction to the subscribing-end entity. Specifically, the notification cancellation indication may be carried in the notify request message.

303: The server entity receives the update request message sent by the subscriber entity according to the notification cancellation instruction.

In addition, the update request message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

304 , the server entity modifies the resource attribute according to the update request message, and stops sending the notification to the receiver entity, where the resource attribute includes a notification uniform resource identifier (notificationURI).

It should be noted that the subscriber entity determines whether to execute 303 and 304 after receiving the notification cancellation instruction from the server entity.

The subscriber entity and the receiver entity are two different entities in the machine communication system. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification rule (eventNotificationCriteria) attribute in the subscription resource is satisfied.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification cancellation indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification cancellation instruction, it sends a subscription resource modification request to the server, and the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, when the resource attribute is modified according to the update request message, the server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the update request message.

For example, when the server entity receives a subscription cancellation instruction (stop receiving notification, or notification cancellation) sent by the receiver entity, when the receiver entity has no authority, the server entity sends a notification cancellation instruction to the subscriber entity, and the subscriber entity sends a subscription The resource modification request is sent to the server, and the server deletes the identifier (URI) of the receiver entity in the resource attribute. At the same time, stop sending notification messages to the receiving entity.

Optionally, as another embodiment, when receiving the notification cancellation indication sent by the receiver entity, the server entity receives an update message sent by the receiver entity, where the update message carries the notification cancellation indication. Or, the server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification cancellation indication. Or, the server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification cancellation indication.

For example, the receiver entity carries a notification cancellation indication in a notify response message (notify response) of a notify request (notify request) to the server entity. The notification response is a notification response when the notification request is generated by the server entity when the event rule is satisfied, and the notification response message carries a notification cancellation indication. Or the server entity receives the notification request message generated by the receiver entity, and the notification response message carries the notification cancellation indication.

FIG. 4 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in Figure 4 may be performed by a notification receiver, such as AE or CSE. The method includes:

401. The receiving end entity generates a notification cancellation indication.

For example, in the scenario where the subscribing entity (AE or CSE) creates a subscription resource for the receiving entity, if the receiving entity (AE or CSE) wants to modify the subscribed resource (for example, it does not want to receive the subscribed resource again) notification), a notification cancellation indication can be generated first.

402 , the receiver entity sends a notification cancellation instruction to the server entity, so that the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, where the resource attribute includes the notification uniform resource identifier.

In addition, optionally, the notification cancellation indication may also carry the identifier or address of the receiving end entity.

Specifically, the timing when the receiving end entity initiates the notification cancellation indication may be in the process of receiving the subscription notification, or before receiving the subscription notification, which is not limited in this embodiment of the present invention

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

Based on the above technical solution, the receiver entity can actively initiate a notification cancellation instruction to the server entity, so that the server entity can modify the subscription resources according to the notification cancellation instruction. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, when sending the notification cancellation indication to the server entity, the receiving end entity may send an update message to the server entity, where the update message carries the notification cancellation indication. Alternatively, the receiver entity sends a notification response message to the server entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification cancellation indication. Alternatively, the receiver entity sends a notification request message to the server entity, and the notification response message carries a notification cancellation indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. Or, the receiving-end entity carries the notification cancellation indication in the notification response message (notify response) of the notification request (notify request) to the server entity. Or the receiving-end entity sends a notification request (notify request) to the server-end entity carrying the notification cancellation indication.

FIG. 5 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in FIG. 5 may be performed by a subscriber entity (originator), such as AE or CSE. The method includes:

501. The subscriber entity receives the notification cancellation indication sent by the server entity, and the notification cancellation indication is sent by the receiving end entity to the server entity.

For example, in the scenario where the subscriber entity (AE or CSE) subscribes to the notification for the receiver entity, if the receiver entity (AE or CSE) wants to modify the notification, it can actively initiate a notification cancellation instruction to the server entity . The server can first determine whether the recipient entity has permission to modify the subscription resource. If the receiving-end entity does not have permission, the server-end entity may first send a notification cancellation instruction to the subscribing-end entity.

502 , the subscriber entity sends an update request message to the server entity according to the notification cancellation instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes a notification uniform resource identifier (notificationURI).

For example, the update request message carries the updated notification uniform resource identifier notificationURI.

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification cancellation indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification cancellation instruction, it sends a subscription resource modification request to the server, and the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 6 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in FIG. 6 may be performed by a server entity (Hosting CSE). The method includes:

601. The server entity receives the notification modification indication sent by the receiver entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) wants to modify the resource attributes, it can actively initiate a notification modification instruction to the server entity . Specifically, the timing for initiating the notification modification indication may be in the process of receiving the subscription notification, or before receiving the subscription notification, which is not limited in this embodiment of the present invention.

It should be understood that the notification modification indication may be used to instruct the server entity to delete, add, or modify one or more attributes of the subscription resource, which is not limited in this embodiment of the present invention. In addition, a subscription reference may be sent at the same time as the notification modification indication is sent. The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

602 , when the receiver entity has the authority, the server entity modifies the resource attribute according to the notification modification instruction, and sends a notification to the receiver entity based on the modified resource attribute, where the resource attribute includes a notification sending rule.

For example, the server can first determine whether the recipient entity has permission to modify the resource attributes. If the receiving-end entity has the right, the server-end entity may modify the resource attribute corresponding to the receiving-end entity according to the notification cancellation instruction. The resource attribute includes a notification sending rule, such as one or more of a sending period, an information type, and an expiration time.

Specifically, the server entity may expand each attribute of the subscription resource into a list containing multiple values. Each value in the list corresponds to a receiver entity. In this way, the server entity can modify the corresponding resource attributes for the subscription modification request sent by each receiver entity respectively.

Alternatively, the server entity can create a new attribute modification strategy in the subscription resource attribute. Use this attribute to record the modification content of the subscribed resource by the receiver entity.

603: The server entity sends a subscription modification notification message to the subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity.

For example, when the server entity completes the modification of the resource attribute, it can notify the subscriber entity of the specific modification content of the resource attribute of the receiver entity. In this way, the subscriber entity can adjust the payment according to the modified content, etc.

In addition, the subscription modification notification message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The subscriber entity and the receiver entity are two different entities in the machine communication system. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification criteria attribute in the subscription resource is satisfied.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification modification instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, when modifying the resource attribute according to the notification modification instruction, the server entity may modify the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

For example, the notification modification indication includes one or more parameters of expiration time, transmission period and message type, and the identity of the recipient entity. In this way, the server entity modifies the attribute of the subscription resource of the receiver entity to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, when receiving the notification modification indication sent by the receiving end entity, the server entity receives an update message sent by the receiving end entity, where the update message carries the notification modification indication. Alternatively, the server entity receives a notification response message sent by the receiver entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification modification indication. Or the receiver entity sends a notification request message to the server entity, and the notification response message carries the notification modification indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification modification indication. Or, the receiving-end entity carries the notification modification indication in the notification response message (notify response) of the notification request (notify request) to the server entity. Alternatively, the receiving-end entity may send a notification request (notify request) to the server-end entity carrying the notification modification indication.

Optionally, as another embodiment, before receiving the notification modification instruction sent by the receiver entity, the server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate the notification modification instruction according to the resource attribute.

For example, before or after the receiving-end entity receives the notification request, the receiving-end entity obtains the attributes of the subscribed resources from the server-end entity, so that the receiving-end entity can generate a notification modification instruction according to the attributes of the subscribed resources.

Optionally, as another embodiment, the sending rule includes one or more of a sending period, an information type, and an expiration time.

FIG. 7 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in FIG. 7 may be performed by a server entity (Hosting CSE). The method includes:

701. The server entity receives the notification modification indication sent by the receiver entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) wants to modify the resource attributes, it can actively initiate a notification modification instruction to the server entity . Specifically, the timing for initiating the notification modification indication may be in the process of receiving the subscription notification, or before receiving the subscription notification, which is not limited in this embodiment of the present invention.

It should be understood that the notification modification indication may be used to instruct the server entity to delete, add, or modify one or more attributes of the subscription resource, which is not limited in this embodiment of the present invention.

702 , when the receiver entity has no authority, the server entity sends a notification modification indication to the subscriber entity.

For example, the server entity may first determine whether the receiver entity has permission to modify the resource attributes. If the receiving-end entity does not have the authority, the server-end entity may first send the notification modification indication to the subscribing-end entity. Specifically, the notification modification indication may be carried in a notify request message.

703. The server entity receives an update request message sent by the subscriber entity according to the notification modification instruction.

In addition, the update request message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

704, the server entity modifies the resource attribute according to the update request message, and sends a notification to the receiver entity based on the modified resource attribute. variety.

It should be noted that after receiving the modification instruction notified by the server entity, the subscriber entity determines whether to execute 703 and 704.

The subscriber entity and the receiver entity are two different entities. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification rule (eventNotificationCriteria) attribute in the subscription resource is satisfied.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification modification indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification modification instruction, it sends a subscription resource modification request to the server, and the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, when modifying the resource attribute according to the notification modification instruction, the server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

For example, the notification modification indication includes one or more parameters of expiration time, notification cycle, and notification content type, as well as the identity of the recipient entity. In this way, the server entity modifies the attribute of the subscription resource of the receiver entity to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, the server entity receives a notification response message sent by the receiver entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification modification instruction, The notification response message carries the notification modification indication. Or the server entity receives the notification request message generated by the receiver entity, and the notification response message carries the notification modification indication.

For example, the receiving-end entity carries a notification modification indication in a notify response message (notify response) of a notify request (notify request) to the server-end entity. Alternatively, the receiving-end entity sends a notification request (notify request) to the server-end entity carrying the notification modification indication.

Optionally, as another embodiment, before the server entity receives the notification modification instruction sent by the receiver entity, the server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate the notification modification instruction according to the resource attribute.

For example, before or after the receiving-end entity receives the notification request, the receiving-end entity obtains the attributes of the subscribed resources from the server-end entity, so that the receiving-end entity can generate a notification modification instruction according to the attributes of the subscribed resources.

FIG. 8 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in Figure 8 may be performed by a notification receiver, such as AE or CSE. The method includes:

801. The receiving end entity generates a notification modification indication.

For example, in the scenario where the subscriber entity (AE or CSE) creates a subscription resource for the receiver entity, if the receiver entity (AE or CSE) wants to modify the subscribed resource (a notification modification indication can be generated first) .

It should be understood that the notification modification indication may be used to instruct the server entity to delete, add, or modify one or more attributes of the subscription resource, which is not limited in this embodiment of the present invention.

802, the receiving-end entity sends a notification modification instruction to the server-end entity, so that the server-end entity can modify the resource attribute according to the notification modification instruction, and send a notification to the receiving-end entity based on the modified resource attribute, and the resource attribute includes the notification sending rule. .

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

Based on the above technical solution, the receiving-end entity can actively initiate a notification modification instruction to the server-end entity, so that the server-end entity can modify the subscription resource according to the notification modification instruction. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, when the notification modification indication is sent to the server entity, the receiving end entity sends an update message to the server entity, and the update message carries the notification modification indication. Alternatively, the receiver entity sends a notification response message to the server entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification modification indication. Or the server entity receives the notification request message generated by the receiver entity, and the notification response message carries the notification modification indication.

Optionally, before the receiving-end entity generates the notification modification indication, the receiving-end entity receives the resource attribute sent by the server-end entity. In this case, when the notification modification instruction is generated, the receiving-end entity generates the notification modification instruction according to the resource attribute.

For example, before or after the receiving-end entity receives the notification request, the receiving-end entity obtains the attributes of the subscribed resources from the server-end entity, so that the receiving-end entity can generate a notification modification instruction according to the attributes of the subscribed resources.

FIG. 9 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention. The method shown in FIG. 9 may be performed by a subscriber entity (originator), such as AE or CSE. The method includes:

901 , the subscriber entity receives the notification modification indication sent by the server entity, and the notification modification indication is sent by the receiver entity to the server entity.

For example, in the scenario where the subscriber entity (AE or CSE) subscribes to the notification for the receiver entity, if the receiver entity (AE or CSE) wants to modify the notification, it can actively initiate a notification modification instruction to the server entity . The server can first determine whether the recipient entity has permission to modify the subscription resource. If the receiving-end entity does not have permission, the server-end entity may first send a notification modification indication to the subscribing-end entity.

902. The subscriber entity sends an update request message to the server entity according to the notification modification instruction, so that the server entity can modify a resource attribute according to the update request message, where the resource attribute includes a notification sending rule.

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification modification indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification modification instruction, it sends a subscription resource modification request to the server, and the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

The embodiments of the present invention will be described in detail below with reference to specific examples. It should be noted that these examples are only for helping those skilled in the art to better understand the embodiments of the present invention, rather than limiting the scope of the embodiments of the present invention.

FIG. 10 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

S1001, the server entity sends a notification request (notify request) to the receiver entity.

For example, when a subscriber entity subscribes to notifications for a receiver entity, the server entity creates subscription resources locally. When the eventnotificationcriteria in the subscription resource is satisfied, the server entity generates a notification message and sends a notification request to the receiver entity.

S1002, the receiver entity sends a notification response to the server entity. The notification response carries a notification cancellation indication (stop receiving notification or notification cancellation). In addition, the notification response may also carry a subscription reference. The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

For example, when the receiving-end entity no longer wants to receive the subscription notification, a notification cancellation indication is carried in the notification response to request the server-end entity to stop sending notification messages to it. Optionally, it carries a receiving end identifier or an address identifier (URI).

S1003 , the server entity sends a notification message to the subscriber entity, where the notification message carries a notification cancellation indication (notification cancellation), which is used to notify the subscriber entity that the receiver entity cancels receiving the notification message. In addition, the notification message may also carry a subscription reference identifier (subscription reference) and a recipient identifier or address identifier (URI). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

S1004, after receiving the notification message, the subscriber entity sends a response message to the server entity.

S1005, the subscriber entity sends a subscription update request to the server entity to request the server entity to stop sending subscription notifications to the receiver entity.

S1006, the server entity deletes the identifier of the receiver entity in the resource attribute according to the subscription update request. The server entity returns a response message to the subscriber entity. In this way, the server entity will no longer send subscription notifications to the receiver entity.

It should be noted that after receiving the notification message of the server entity, the subscriber entity determines whether to execute S1005 and S1006.

In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 11 is a schematic flowchart of a method for subscribing to a notification according to another embodiment of the present invention.

S1101, the receiver entity sends a notification cancellation indication to the server entity.

For example, when the receiving-end entity no longer wants to receive subscription notifications, a notification cancellation indication is carried in the notify request message to request the server-end entity to stop sending subscription notifications to it.

S1102, the server entity sends a response message notifying the cancellation indication to the receiving entity.

S1103 , the server entity sends a notification message to the subscriber entity, where the notification message carries a notification cancellation indication (notification cancellation), which is used to notify the subscriber entity that the receiver entity cancels receiving the notification message. In addition, the notification message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

S1104, after receiving the notification message, the subscriber entity sends a response message to the server entity.

S1105, the subscriber entity sends a subscription update request to the server entity to request the server entity to stop sending subscription notifications to the receiver entity.

S1106, the server entity deletes the identifier of the receiver entity in the resource attribute according to the subscription update request. The server entity returns a response message to the subscriber entity. In this way, the server entity will no longer send subscription notifications to the receiver entity.

It should be noted that after receiving the notification message of the server entity, the subscriber entity determines whether to execute S1105 and S1106.

In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 12 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

S1201, the receiving-end entity sends an update request message to the server-end entity. The update request message carries the resource attribute that needs to be modified. Optionally, before step S1201, the receiving-end entity may first obtain attribute information of the subscription resource on the server-end entity. In this case, the receiving-end entity may determine the resource attribute to be modified according to the attribute information of the subscription resource on the server-end entity.

For example, when the subscriber entity requests the server entity to create a subscription resource, the server entity creates the subscription resource locally. At this time, the server entity can first send the properties of the subscription resource to the receiver entity, or the receiver can obtain the properties of the subscription resource on the server entity through a request to obtain the properties of the subscription resource, so that the receiver entity can generate the properties of the subscription resource according to the properties of the subscription resource. Update request message.

S1202, the server entity sends an update response message to the receiver entity.

S1203, the server entity modifies the corresponding resource attribute according to the resource attribute to be modified carried in the update request message. For example, the server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

S1204, the server entity sends a notification message to the subscriber entity, so as to notify the subscriber entity that the subscription resource has been modified. In addition, the notification message may also carry the identifier of the receiving end entity, the modified attribute value and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

S1205, the subscriber entity sends a response message to the notification message to the server entity.

In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 13 is a schematic flowchart of a method for subscribing to notifications in a machine communication system according to another embodiment of the present invention.

S1301, the receiver entity sends a notification request message to the subscriber entity. The request message carries the resource attribute that needs to be modified. Optionally, before step S1301, the receiving-end entity may first obtain attribute information of the subscription resource on the server-end entity. In this case, the receiving-end entity may determine the resource attribute to be modified according to the attribute information of the subscription resource on the server-end entity.

Specifically, the receiver entity may directly send the notification request message to the subscriber entity, or may choose to forward the notification request message through a CSE entity.

S1302, the subscriber entity sends a notification response message to the receiver entity.

S1303, the subscriber entity sends an update request message to the server entity, notifying that the request message carries the resource attribute that needs to be modified, so as to request the server entity to modify the corresponding resource attribute.

S1304, the server entity sends a response message of the update request to the subscriber entity.

S1305, the server entity modifies the corresponding resource attribute according to the update request message.

It should be noted that after receiving the notification message of the receiving end entity, the subscriber entity determines whether to execute S1303, S1304 and S1305.

In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 14 is a schematic block diagram of a server entity in a machine communication system according to an embodiment of the present invention. As shown in FIG. 14 , the server entity 140 includes a receiving unit 1401 , a processing unit 1402 and a sending unit 1403 .

The receiving unit 1401 is configured to receive the notification cancellation indication sent by the receiving end entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) no longer wants to receive notifications, it can actively send a notification cancellation instruction to the server entity. Specifically, the timing for initiating the notification cancellation indication may be in the process of receiving the notification, or before the notification is received, which is not limited in this embodiment of the present invention. In addition, it can also optionally carry the identifier or address of the receiving end entity.

The processing unit 1402 is configured to modify the resource attribute according to the notification cancellation instruction and stop sending the notification to the receiving end entity when the receiving end entity has the authority, where the resource attribute includes a notification uniform resource identifier (notificationURI).

For example, the server can first determine whether the recipient entity has permission to modify the resource attributes. If the receiving-end entity has the right, the server-end entity may modify the resource attribute corresponding to the receiving-end entity according to the notification cancellation instruction. The resource attribute includes a notification uniform resource identifier (notificationURI).

The sending unit 1403 is configured to send a subscription modification notification message to the subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity.

For example, when the server entity completes the modification of the resource attribute, it can notify the subscriber entity of the specific modification content of the resource attribute of the receiver entity. In this way, the subscriber entity can adjust the payment according to the modified content, etc. It should be understood that the subscription modification message should include the identifier of the receiver entity (notification receiver ID). Another optional implementation is that the subscription modification message contains the modified resource attribute including the receiver ID (notificationURI), so that the subscriber entity can Know which receiver entity has modified the subscription resource.

In addition, the subscription modification message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The subscriber entity and the receiver entity are two different entities in the machine communication system. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification criteria attribute in the subscription resource is satisfied.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification cancellation instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the processing unit 1402 is specifically configured to, according to the notification cancellation indication, delete the identifier of the recipient entity in the notification uniform resource identifier.

For example, when the server entity receives a subscription cancellation indication (stop receiving notification, or notification cancellation) sent by the receiver entity, it deletes the identifier (URI) of the receiver entity in the notification uniform resource identifier. At the same time, stop sending notification messages to the receiving entity.

Optionally, as another embodiment, the receiving unit 1402 is specifically configured to receive an update message sent by the receiving end entity, where the update message carries a notification cancellation indication. Or, receive a notification response message sent by the receiving-end entity, where the notification response message carries a notification cancellation indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. Or, the receiving-end entity carries the notification cancellation indication in the notification response message (notify response) of the notification request (notify request) to the server entity. Alternatively, the recipient entity may send a notify request to the server entity.

FIG. 15 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention. The server entity shown in FIG. 15 includes a first receiving unit 1501 , a sending unit 1502 , a second receiving unit 1503 and a processing unit 1504 .

The first receiving unit 1501 is configured to receive the notification cancellation indication sent by the receiving end entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) no longer wants to receive notifications, it can actively send a notification cancellation instruction to the server entity. Specifically, the timing for initiating the notification cancellation indication may be in the process of receiving the notification, or before the notification is received, which is not limited in this embodiment of the present invention.

The sending unit 1502 is configured to send a notification cancellation indication to the subscriber entity when the receiver entity has no authority.

For example, the server entity may first determine whether the receiver entity has permission to modify the resource attributes. If the receiving-end entity does not have permission, the server-end entity may first send the notification cancellation instruction to the subscribing-end entity. Specifically, the notification cancellation indication may be carried in the notify request message.

The second receiving unit 1503 is configured to receive an update request message sent by the subscriber entity according to the notification cancellation instruction.

In addition, the update request message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The processing unit 1504, if the instruction message indicates that the notification cancellation instruction is accepted, is configured to modify the resource attribute according to the notification cancellation instruction, and stop sending the notification to the recipient entity, where the resource attribute includes a notification uniform resource identifier (notificationURI).

The subscriber entity and the receiver entity are two different entities in the machine communication system. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification rule (eventNotificationCriteria) attribute in the subscription resource is satisfied.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification cancellation indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification cancellation instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the processing unit 1504 is specifically configured to, according to the update request message, delete the identifier of the recipient entity in the notification uniform resource identifier.

For example, when the server entity receives a subscription cancellation instruction (stop receiving notification, or notification cancellation) sent by the receiver entity, when the receiver entity has no authority, the server entity sends a notification cancellation instruction to the subscriber entity, and the subscriber entity sends a subscription The resource modification request is sent to the server, and the server deletes the identifier (URI) of the receiver entity in the resource attribute. At the same time, stop sending notification messages to the receiving entity.

Optionally, as another embodiment, the first receiving unit 1501 is specifically configured to receive an update message sent by the receiving end entity, where the update message carries a notification cancellation indication. Or, receive a notification response message sent by the receiving-end entity, where the notification response message carries a notification cancellation indication. Or, the server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification cancellation indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. The notification response is a notification response when the notification request is generated by the server entity when the event rule is satisfied, and the notification response message carries a notification cancellation indication. Or the server entity receives the notification request message generated by the receiver entity, and the notification response message carries the notification cancellation indication.

FIG. 16 is a schematic block diagram of a receiver entity in a machine communication system according to an embodiment of the present invention. The receiving-end entity 160 shown in FIG. 16 includes a generating unit 1601 and a sending unit 1602 .

The generating unit 1601 is configured to generate a notification cancellation instruction.

For example, in the scenario where the subscribing entity (AE or CSE) creates a subscription resource for the receiving entity, if the receiving entity (AE or CSE) wants to modify the subscribed resource (for example, it does not want to receive the subscribed resource again) notification), a notification cancellation indication can be generated first.

The sending unit 1602 is configured to send a notification cancellation instruction to the server entity, so that the server entity can modify the resource attribute according to the notification cancellation instruction and stop sending the notification to the receiver entity, where the resource attribute includes the notification uniform resource identifier.

In addition, optionally, the notification cancellation indication may also carry the identifier or address of the receiving end entity.

Specifically, the timing when the receiving end entity initiates the notification cancellation indication may be in the process of receiving the subscription notification, or before receiving the subscription notification, which is not limited in this embodiment of the present invention

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

Based on the above technical solution, the receiver entity can actively initiate a notification cancellation instruction to the server entity, so that the server entity can modify the subscription resources according to the notification cancellation instruction. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the sending unit 1602 is specifically configured to send an update message to the server entity, where the update message carries a notification cancellation indication. Alternatively, a notification response message is sent to the server entity, the notification response message carries a notification cancellation indication that the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries the notification cancellation indication. Alternatively, the receiver entity sends a notification request message to the server entity, and the notification response message carries a notification cancellation indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. Or, the receiving-end entity carries the notification cancellation indication in the notification response message (notify response) of the notification request (notify request) to the server entity. Or the receiving-end entity sends a notification request (notify request) to the server-end entity carrying the notification cancellation indication.

FIG. 17 is a schematic block diagram of a subscriber entity in a machine communication system according to an embodiment of the present invention. The subscriber entity 170 shown in FIG. 17 includes a receiving unit 1701 and a sending unit 1702 .

The receiving unit 1701 is configured to receive a notification cancellation indication sent by the server entity, where the notification cancellation indication is sent by the receiving end entity to the server entity.

For example, in the scenario where the subscriber entity (AE or CSE) subscribes to the notification for the receiver entity, if the receiver entity (AE or CSE) wants to modify the notification, it can actively initiate a notification cancellation instruction to the server entity . The server can first determine whether the recipient entity has permission to modify the subscription resource. If the receiving-end entity does not have permission, the server-end entity may first send a notification cancellation instruction to the subscribing-end entity.

The sending unit 1702 is configured to send an update request message to the server entity according to the notification cancellation instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes a notification uniform resource identifier (notificationURI).

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification cancellation indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification cancellation instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 18 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention. The server entity 180 shown in FIG. 18 includes a receiving unit 1801 , a processing unit 1802 and a sending unit 1803 .

The receiving unit 1801 is configured to receive the notification modification indication sent by the receiving end entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) wants to modify the resource attributes, it can actively initiate a notification modification instruction to the server entity . Specifically, the timing for initiating the notification modification indication may be in the process of receiving the subscription notification, or before receiving the subscription notification, which is not limited in this embodiment of the present invention.

It should be understood that the notification modification indication may be used to instruct the server entity to delete, add, or modify one or more attributes of the subscription resource, which is not limited in this embodiment of the present invention. In addition, a subscription reference may be sent at the same time as the notification modification indication is sent. The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The processing unit 1802, when the receiver entity has the authority, the server entity modifies the resource attribute according to the notification modification instruction, and sends a notification to the receiver entity based on the modified resource attribute, where the resource attribute includes the notification sending rule.

For example, the server can first determine whether the recipient entity has permission to modify the resource attributes. If the receiving-end entity has the right, the server-end entity may modify the resource attribute corresponding to the receiving-end entity according to the notification cancellation instruction. The resource attribute includes a notification sending rule, such as one or more of a sending period, an information type, and an expiration time.

Specifically, the server entity may expand each attribute of the subscription resource into a list containing multiple values. Each value in the list corresponds to a receiver entity. In this way, the server entity can modify the corresponding resource attributes for the subscription modification request sent by each receiver entity respectively.

Alternatively, the server entity can create a new attribute modification strategy in the subscription resource attribute. Use this attribute to record the modification content of the subscribed resource by the receiver entity.

The sending unit 1803 is configured to send a subscription modification notification message to the subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity.

For example, when the server entity completes the modification of the resource attribute, it can notify the subscriber entity of the specific modification content of the resource attribute of the receiver entity. In this way, the subscriber entity can adjust the payment according to the modified content, etc.

In addition, the subscription modification notification message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The subscriber entity and the receiver entity are two different entities in the machine communication system. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification criteria attribute in the subscription resource is satisfied.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification modification instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the processing unit 1802 is specifically configured to modify the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction.

For example, the notification modification indication includes one or more parameters of expiration time, transmission period and message type, and the identity of the recipient entity. In this way, the server entity modifies the attribute of the subscription resource of the receiver entity to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, the receiving unit 1801 is specifically configured to receive an update message sent by the receiving end entity, where the update message carries a notification modification indication. Or, receive a notification response message sent by the receiver entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification modification indication. Or the receiver entity sends a notification request message to the server entity, and the notification response message carries the notification modification indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. Or, the receiving-end entity carries the notification modification indication in the notification response message (notify response) of the notification request (notify request) to the server entity. Alternatively, the receiving-end entity may send a notification request (notify request) to the server-end entity carrying the notification modification indication.

Optionally, as another embodiment, the sending unit 1803 is further configured to send the resource attribute to the receiving-end entity, so that the receiving-end entity can generate a notification modification instruction according to the resource attribute.

For example, before or after the receiving-end entity receives the notification request, the receiving-end entity obtains the attributes of the subscribed resources from the server-end entity, so that the receiving-end entity can generate a notification modification instruction according to the attributes of the subscribed resources.

Optionally, as another embodiment, the sending rule includes one or more of a sending period, an information type, and an expiration time.

FIG. 19 is a schematic block diagram of a server entity in a machine communication system according to another embodiment of the present invention. The server 190 shown in FIG. 19 includes a first receiving unit 1901 , a sending unit 1902 , a second receiving unit 1903 and a processing unit 1904 .

The first receiving unit 1901 is configured to receive the notification modification indication sent by the receiving end entity.

For example, in a scenario where the subscriber entity (AE or CSE) subscribes to notifications for the receiver entity, if the receiver entity (AE or CSE) wants to modify the resource attributes, it can actively initiate a notification modification instruction to the server entity . Specifically, the timing for initiating the notification modification indication may be in the process of receiving the subscription notification, or before receiving the subscription notification, which is not limited in this embodiment of the present invention.

It should be understood that the notification modification indication may be used to instruct the server entity to delete, add, or modify one or more attributes of the subscription resource, which is not limited in this embodiment of the present invention.

The sending unit 1902 is configured to send a notification modification indication to the subscriber entity when the receiver entity has no authority.

For example, the server entity may first determine whether the receiver entity has permission to modify the resource attributes. If the receiving-end entity does not have the authority, the server-end entity may first send the notification modification indication to the subscribing-end entity. Specifically, the notification modification indication may be carried in a notify request message.

The second receiving unit 1903 is configured to receive an update request message sent by the subscriber entity according to the notification modification instruction.

In addition, the update request message may also carry the identifier of the receiving end entity and the subscription reference identifier (subscription reference). The subscription reference identifier indicates the subscription resource, so that the subscribing entity can know which subscription resource is requested in the scenario of subscribing to multiple resources.

The processing unit 1904 is configured to modify the resource attribute according to the update request message, and send a notification to the receiver entity based on the modified resource attribute. The resource attribute includes the sending rule of the notification, such as one of the sending period, information type and expiration time or more.

The subscriber entity and the receiver entity are two different entities. The subscriber entity is the subscription initiator of the notification, for example, the subscriber entity is the party that requests the server entity to create subscription resources. The receiver entity is the receiver of the notification and not the subscription initiator of the notification, for example, the receiver of the notification message generated when the event notification rule (eventNotificationCriteria) attribute in the subscription resource is satisfied.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification modification indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification modification instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the processing unit 1904 is specifically configured to modify the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction.

For example, the notification modification indication includes one or more parameters of expiration time, notification cycle, and notification content type, as well as the identity of the recipient entity. In this way, the server entity modifies the attribute of the subscription resource of the receiver entity to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, the server entity receives a notification response message sent by the receiver entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification modification instruction, The notification response message carries the notification modification indication. Or the server entity receives the notification request message generated by the receiver entity, and the notification response message carries the notification modification indication.

For example, the receiving-end entity may send an update message (update request) to the server-end entity, and the update message carries the notification cancellation indication. Or, the receiving-end entity carries the notification cancellation indication in the notification response message (notify response) of the notification request (notify request) to the server entity.

Optionally, as another embodiment, the sending unit 1902 is further configured to send the resource attribute to the receiving-end entity, so that the receiving-end entity can generate a notification modification instruction according to the resource attribute.

For example, before or after the receiving-end entity receives the notification request, the receiving-end entity obtains the attributes of the subscribed resources from the server-end entity, so that the receiving-end entity can generate a notification modification instruction according to the attributes of the subscribed resources. Alternatively, the receiving-end entity sends a notification request (notify request) to the server-end entity carrying the notification modification indication.

FIG. 20 is a schematic block diagram of a receiver entity in a machine communication system according to another embodiment of the present invention. The receiving-end entity 200 shown in FIG. 20 includes a generating unit 2001 and a sending unit 2002 .

The generating unit 2001 is configured to generate a notification modification instruction.

For example, in the scenario where the subscriber entity (AE or CSE) creates a subscription resource for the receiver entity, if the receiver entity (AE or CSE) wants to modify the subscribed resource (a notification modification indication can be generated first) .

It should be understood that the notification modification indication may be used to instruct the server entity to delete, add, or modify one or more attributes of the subscription resource, which is not limited in this embodiment of the present invention.

The sending unit 2002 is configured to send a notification modification instruction to the server entity, so that the server entity can modify the resource attribute according to the notification modification instruction, and send a notification to the receiving end entity based on the modified resource attribute, and the resource attribute includes the sending of the notification rule.

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

Based on the above technical solution, the receiving-end entity can actively initiate a notification modification instruction to the server-end entity, so that the server-end entity can modify the subscription resource according to the notification modification instruction. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the sending unit 2002 is specifically configured to send an update message to the server entity, where the update message carries a notification modification indication. Alternatively, a notification response message is sent to the server entity, where the notification response is a notification response to a notification request generated by the server entity when the event rule is satisfied, and the notification response message carries a notification modification indication. Or the server entity receives the notification request message generated by the receiver entity, and the notification response message carries the notification modification indication.

Optionally, as another embodiment, the receiving-end entity 200 further includes a receiving unit 2003 . The receiving unit 2003 is configured to receive the resource attribute sent by the server entity. In this case, the generating unit 2001 is specifically configured to generate a notification modification instruction according to the resource attribute.

FIG. 21 is a schematic block diagram of a subscriber entity in a machine communication system according to another embodiment of the present invention. The subscriber entity 210 shown in FIG. 21 includes a receiving unit 2101 and a sending unit 2102 .

The receiving unit 2101 is configured to receive a notification modification instruction sent by the server entity, where the notification modification instruction is sent by the receiver entity to the server entity.

For example, in the scenario where the subscriber entity (AE or CSE) subscribes to the notification for the receiver entity, if the receiver entity (AE or CSE) wants to modify the notification, it can actively initiate a notification modification instruction to the server entity . The server can first determine whether the recipient entity has permission to modify the subscription resource. If the receiving-end entity does not have permission, the server-end entity may first send a notification modification indication to the subscribing-end entity.

The sending unit 2102 is configured to send an update request message to the server entity according to the notification modification instruction, so that the server entity can modify a resource attribute according to the update request message, and the resource attribute includes a notification sending rule.

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification modification indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification modification instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

FIG. 22 is a schematic block diagram of entities in a machine communication system according to another embodiment of the present invention.

The entity 220 in FIG. 22 can be used to implement the steps and methods in the above method embodiments. In the embodiment of FIG. 22 , the entity 220 includes an antenna 2201 , a transmitter 2202 , a receiver 2203 , a processor 2204 and a memory 2205 . The processor 2204 controls the operation of the entity 220 and can be used to process signals. Memory 2205 may include read-only memory and random access memory, and provides instructions and data to processor 2204 . Transmitter 2202 and receiver 2203 may be coupled to antenna 2201. The various components of the entity 220 are coupled together through a bus system 2206, wherein the bus system 2206 includes a power bus, a control bus and a status signal bus in addition to a data bus. For clarity, however, the various buses are labeled as bus system 2206 in the figure. For example, the entity 220 may be a server entity, a subscription segment entity, or a receiver entity.

Optionally, when the entity 220 is a server entity, the memory 2205 can store instructions for performing the following processes:

The server entity receives the notification cancellation instruction sent by the receiver entity;

When the receiver entity has the authority, the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, and the resource attribute includes the notification uniform resource identifier;

The server entity sends a subscription modification notification message to the subscriber entity, and the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity;

The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification cancellation instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity modifies the resource attributes according to the notification cancellation instruction, including:

The server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the notification cancellation instruction.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity receives the notification cancellation instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification cancellation indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification cancellation indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification cancellation indication.

Optionally, when the entity 220 is a server entity, the memory 2205 can store instructions for performing the following processes:

The server entity receives the notification cancellation instruction sent by the receiver entity;

When the receiver entity has no authority, the server entity sends a notification cancellation instruction to the subscriber entity;

The server entity receives the update request message sent by the subscriber entity according to the notification cancellation instruction;

The server entity modifies the resource attribute according to the update request message, and stops sending notifications to the receiver entity, and the resource attribute includes the notification uniform resource identifier;

The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification cancellation indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification cancellation instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity modifies the resource attributes according to the update request message, including:

The server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the update request message.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity receives the notification cancellation instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification cancellation indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification cancellation indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification cancellation indication.

Optionally, when the entity 220 is a receiver entity, the memory 2205 can store instructions for performing the following processes:

The recipient entity generates a notification cancellation indication;

The receiver entity sends a notification cancellation instruction to the server entity, so that the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, and the resource attribute includes the notification uniform resource identifier;

The receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification.

Based on the above technical solution, the receiver entity can actively initiate a notification cancellation instruction to the server entity, so that the server entity can modify the subscription resources according to the notification cancellation instruction. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The receiving-end entity sends a notification cancellation instruction to the server-end entity, including:

The receiving-end entity sends an update message to the server-end entity, and the update message carries the notification cancellation indication; or

The receiver entity sends a notification response message to the server entity, and the notification response message carries the notification cancellation indication; or

The receiver entity sends a notification request message to the server entity, and the notification request message carries a notification cancellation indication.

Optionally, when the entity 220 is a subscriber entity, the memory 2205 can store instructions for performing the following processes:

The subscriber entity receives the notification cancellation instruction sent by the server entity, and the notification cancellation instruction is sent by the receiver entity to the server entity;

The subscriber entity sends an update request message to the server entity according to the notification cancellation instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes the notification uniform resource identifier;

The subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification cancellation indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification cancellation instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity modifies the resource attributes according to the notification modification instruction, including:

The server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity receives the notification modification instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification modification indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification modification indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification modification indication.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

Before the server entity receives the notification modification instruction sent by the receiver entity, the method further includes: the server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate the notification modification instruction according to the resource attribute.

Optionally, when the entity 220 is a server entity, the memory 2205 can store instructions for performing the following processes:

The server entity receives the notification modification instruction sent by the receiver entity;

When the receiver entity has the authority, the server entity modifies the resource attribute according to the notification modification instruction, and sends a notification to the receiver entity based on the modified resource attribute, and the resource attribute includes the notification sending rule;

The server entity sends a subscription modification notification message to the subscriber entity, and the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity;

The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification.

Based on the above technical solutions, when having the authority, the receiving-end entity can initiate the modification of the resource attributes to the server-end entity. Next, the server entity modifies the resource attribute according to the notification modification instruction, and notifies the subscriber entity of the specific modification content. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity modifies the resource attributes according to the notification modification instruction, including:

The server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity receives the notification modification instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification modification indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification modification indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification modification indication.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

Before the server entity receives the notification modification instruction sent by the receiver entity, the server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate the notification modification instruction according to the resource attribute.

Optionally, when the entity 220 is a server entity, specifically, the memory 2205 can store instructions for performing the following processes:

The server entity receives the notification modification instruction sent by the receiver entity;

When the receiver entity has no authority, the server entity sends a notification modification instruction to the subscriber entity;

The server entity receives the update request message sent by the subscriber entity according to the notification modification instruction;

The server entity modifies the resource attribute according to the update request message, and sends a notification to the receiver entity based on the modified resource attribute, and the resource attribute includes the notification sending rule;

The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification modification indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification modification instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity modifies the resource attributes according to the notification modification instruction, including:

The server entity modifies the resource attribute to the value corresponding to the parameter according to the parameter in the notification modification instruction.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

The server entity receives the notification modification instruction sent by the receiver entity, including:

The server entity receives the update message sent by the receiver entity, and the update message carries the notification modification indication; or

The server entity receives the notification response message sent by the receiver entity, and the notification response message carries the notification modification indication; or

The server entity receives the notification request message sent by the receiver entity, and the notification request message carries the notification modification indication.

Optionally, as another embodiment, the memory 2205 may also store instructions for performing the following processes:

Before the server entity receives the notification modification instruction sent by the receiver entity, the server entity sends the resource attribute to the receiver entity, so that the receiver entity can generate the notification modification instruction according to the resource attribute.

Optionally, when the entity 220 is a receiver entity, the memory 2205 can store instructions for performing the following processes:

The recipient entity generates a notification modification indication;

The receiver entity sends a notification modification instruction to the server entity, so that the server entity modifies the resource attribute according to the notification modification instruction, and sends a notification to the receiver entity based on the modified resource attribute, and the resource attribute includes the notification sending rule;

The receiver entity is the receiver of the notification and is not the subscription initiator of the notification.

Based on the above technical solution, the receiving-end entity can actively initiate a notification modification instruction to the server-end entity, so that the server-end entity can modify the subscription resource according to the notification modification instruction. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

The receiving-end entity sends a notification modification instruction to the server-end entity, including:

The receiver entity sends an update message to the server entity, and the update message carries the notification modification indication; or, the receiver entity sends a notification response message to the server entity, and the notification response message carries the notification modification indication, or the receiver entity sends a notification modification instruction to the server entity. The notification request message carries the notification modification indication.

Optionally, as an embodiment, the memory 2205 may also store instructions for performing the following processes:

Before the receiving-end entity generates the notification modification indication, the receiving-end entity receives the resource attribute sent by the server-end entity;

The receiving entity generates notification modification instructions, including:

The receiving-end entity generates a notification modification instruction according to the resource attribute.

Optionally, when the entity 220 is a subscriber entity, the memory 2205 can store instructions for performing the following processes:

The subscriber entity receives the notification modification instruction sent by the server entity, and the notification modification instruction is sent by the receiver entity to the server entity;

The subscriber entity sends an update request message to the server entity according to the notification modification instruction, so that the server entity can modify the resource attribute according to the update request message, and the resource attribute includes the notification sending rule;

The subscriber entity is the subscription initiator of the notification, and is not the recipient of the notification.

Based on the above technical solution, when the receiver does not have the authority, the server entity may send the notification modification indication sent by the receiver entity to the subscriber entity. If the subscriber entity receives the notification modification instruction, the server entity modifies the subscription resource according to the request. In this way, the embodiments of the present invention provide a method for a receiving end entity to modify subscription resources, which improves the flexibility of subscription modification and improves user experience.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, rather than the embodiments of the present invention. implementation constitutes any limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions in the embodiments of the present invention.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or a part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, referred to as: ROM), random access memory (English: Random Access Memory, referred to as: RAM), magnetic disks or optical disks, etc. A medium that can store program code.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of various equivalents within the technical scope disclosed by the present invention. Modifications or substitutions should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (46)

1. a method for subscribing to notification in a machine communication system, is characterized in that, comprising: The server entity receives the notification cancellation instruction sent by the receiver entity; When the receiver entity has the right, the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, where the resource attribute includes the notification uniform resource identifier; The server entity sends a subscription modification notification message to the subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 2. The method according to claim 1, wherein the server entity modifies the resource attribute according to the notification cancellation instruction, comprising: The server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the notification cancellation instruction. 3. The method according to claim 1 or 2, wherein the server entity receives a notification cancellation instruction sent by the receiver entity, comprising: The server entity receives an update message sent by the receiver entity, where the update message carries the notification cancellation indication; or The server entity receives a notification response message sent by the receiver entity, where the notification response message carries the notification cancellation indication; or The server entity receives a notification request message sent by the receiver entity, where the notification request message carries the notification cancellation indication. 4. A method for subscribing to a notification in a machine communication system, comprising: The server entity receives the notification cancellation instruction sent by the receiver entity; When the receiver entity has no authority, the server entity sends the notification cancellation indication to the subscriber entity; receiving, by the server entity, an update request message sent by the subscriber entity according to the notification cancellation instruction; The server entity modifies a resource attribute according to the update request message, and stops sending a notification to the receiver entity, where the resource attribute includes a notification uniform resource identifier; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 5. The method according to claim 4, wherein the server entity modifies resource attributes according to the update request message, comprising: The server entity deletes the identifier of the receiver entity in the notification uniform resource identifier according to the update request message. 6. The method according to claim 4 or 5, wherein the server entity receives a notification cancellation instruction sent by the receiver entity, comprising: The server entity receives an update message sent by the receiver entity, where the update message carries the notification cancellation indication; or The server entity receives a notification response message sent by the receiver entity, where the notification response message carries the notification cancellation indication; or The server entity receives a notification request message sent by the receiver entity, where the notification request message carries the notification cancellation indication. 7. A method for subscribing to a notification in a machine communication system, comprising: The receiving-end entity generates a notification cancellation indication; The receiver entity sends the notification cancellation instruction to the server entity, so that the server entity modifies the resource attribute according to the notification cancellation instruction, and stops sending the notification to the receiver entity, where the resource attribute includes the notification Uniform Resource Identifier; Wherein, the receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification. 8 . The method according to claim 7 , wherein the sending of the notification cancellation instruction by the receiving entity to the server entity comprises: 8 . The receiver entity sends an update message to the server entity, where the update message carries the notification cancellation indication; or The receiver entity sends a notification response message to the server entity, where the notification response message carries the notification cancellation indication; or The receiver entity sends a notification request message to the server entity, where the notification request message carries the notification cancellation indication. 9. A method for subscribing to a notification in a machine communication system, comprising: The subscriber entity receives the notification cancellation instruction sent by the server entity, and the notification cancellation instruction is sent by the receiver entity to the server entity; sending, by the subscriber entity, an update request message to the server entity according to the notification cancellation indication, so that the server entity can modify a resource attribute according to the update request message, where the resource attribute includes a notification uniform resource identifier; Wherein, the subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification. 10. A method for subscribing to notifications in a machine communication system, comprising: The server entity receives the notification modification instruction sent by the receiver entity; When the receiver entity has the right, the server entity modifies the resource attribute according to the notification modification instruction, and sends the notification to the receiver entity based on the modified resource attribute, where the resource attribute includes the rules for sending the notice; The server entity sends a subscription modification notification message to the subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 11. The method according to claim 10, wherein the server entity modifies the resource attribute according to the notification modification instruction, comprising: The server entity modifies the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction. 12. The method according to claim 10 or 11, wherein the server entity receives a notification modification instruction sent by the receiver entity, comprising: The server entity receives an update message sent by the receiver entity, where the update message carries the notification modification indication; or The server entity receives a notification response message sent by the receiver entity, where the notification response message carries the notification modification indication; or The server entity receives a notification request message sent by the receiver entity, where the notification request message carries the notification modification indication. 13. The method according to claim 10 or 11, wherein before the server entity receives the notification modification instruction sent by the receiver entity, the method further comprises: The server entity sends the resource attribute to the receiver entity, so that the receiver entity generates the notification modification instruction according to the resource attribute. 14. The method according to claim 10 or 11, wherein the sending rule comprises one or more of a sending period, an information type and an expiration time. 15. A method for subscribing to notifications in a machine communication system, comprising: The server entity receives the notification modification instruction sent by the receiver entity; When the receiver entity has no authority, the server entity sends the notification modification indication to the subscriber entity; receiving, by the server entity, an update request message sent by the subscriber entity according to the notification modification instruction; The server entity modifies a resource attribute according to the update request message, and sends the notification to the receiver entity based on the modified resource attribute, where the resource attribute includes a sending rule for the notification; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 16. The method according to claim 15, wherein the server entity modifies the resource attribute according to the notification modification instruction, comprising: The server entity modifies the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction. 17. The method according to claim 15 or 16, wherein the server entity receives a notification modification instruction sent by the receiver entity, comprising: The server entity receives an update message sent by the receiver entity, where the update message carries the notification modification indication; or The server entity receives a notification response message sent by the receiver entity, where the notification response message carries the notification modification indication; or The server entity receives a notification request message sent by the receiver entity, where the notification request message carries the notification modification indication. 18. The method according to claim 15 or 16, wherein before the server entity receives the notification modification instruction sent by the receiver entity, the method further comprises: The server entity sends the resource attribute to the receiver entity, so that the receiver entity generates the notification modification instruction according to the resource attribute. 19. The method according to claim 15 or 16, wherein the sending rule comprises one or more of sending period, message type and expiration time. 20. A method for subscribing to notifications in a machine communication system, comprising: The recipient entity generates a notification modification indication; The receiver entity sends the notification modification instruction to the server entity, so that the server entity modifies the resource attribute according to the notification modification instruction, and sends the modified resource attribute to the receiver entity based on the modified resource attribute. the notification, the resource attribute includes a sending rule of the notification; Wherein, the receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification. 21. The method according to claim 20, wherein the receiving entity sends the notification modification instruction to the server entity, comprising: The receiving-end entity sends an update message to the server-end entity, where the update message carries the notification modification indication; or The receiver entity sends a notification response message to the server entity, where the notification response message carries the notification modification indication; or The receiver entity sends a notification request message to the server entity, where the notification request message carries the notification modification indication. 22. The method according to claim 20 or 21, wherein before the receiving entity generates a notification modification indication, the method further comprises: receiving, by the receiver entity, the resource attribute sent by the server entity; The receiving end entity generates a notification modification instruction, including: The receiving-end entity generates the notification modification indication according to the resource attribute. 23. A method for subscribing to notifications in a machine communication system, comprising: The subscriber entity receives the notification modification instruction sent by the server entity, and the notification modification instruction is sent by the receiver entity to the server entity; The subscriber entity sends an update request message to the server entity according to the notification modification instruction, so that the server entity can modify a resource attribute according to the update request message, where the resource attribute includes the notification sending rule ; Wherein, the subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification. 24. A server entity for subscribing to notifications in a machine communication system, comprising: a receiving unit, configured to receive a notification cancellation instruction sent by the receiving-end entity; a processing unit, configured to modify a resource attribute according to the notification cancellation indication and stop sending a notification to the receiver entity when the receiver entity has the authority, where the resource attribute includes a notification uniform resource identifier; a sending unit, configured to send a subscription modification notification message to a subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 25. The entity according to claim 24, wherein the processing unit is specifically configured to, according to the notification cancellation indication, delete the identifier of the receiving-end entity in the notification uniform resource identifier. 26. The entity according to claim 24 or 25, wherein the receiving unit is specifically configured to: receiving an update message sent by the receiving-end entity, where the update message carries the notification cancellation indication; or receiving a notification response message sent by the recipient entity, where the notification response message carries the notification cancellation indication; or A notification request message sent by the receiver entity is received, where the notification request message carries the notification cancellation indication. 27. A server entity for subscribing to notifications in a machine communication system, characterized in that it comprises: a first receiving unit, configured to receive a notification cancellation indication sent by the receiving-end entity; a sending unit, configured to send the notification cancellation indication to the subscriber entity when the receiving entity has no authority; a second receiving unit, configured to receive an update request message sent by the subscriber entity according to the notification cancellation instruction; a processing unit, configured to modify a resource attribute according to the update request message, and stop sending a notification to the receiver entity, where the resource attribute includes a notification uniform resource identifier; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 28. The entity according to claim 27, wherein the processing unit is specifically configured to, according to the notification cancellation indication, delete the identifier of the receiving-end entity in the notification uniform resource identifier. 29. The entity according to claim 27 or 28, wherein the first receiving unit is specifically configured to: receiving an update message sent by the receiving-end entity, where the update message carries the notification cancellation indication; or receiving a notification response message sent by the recipient entity, where the notification response message carries the notification cancellation indication; or A notification request message sent by the receiver entity is received, where the notification request message carries the notification cancellation indication. 30. A receiver entity for subscribing to notifications in a machine communication system, comprising: a generating unit for generating a notification cancellation instruction; A sending unit, configured to send the notification cancellation instruction to the server entity, so that the server entity can modify the resource attribute according to the notification cancellation instruction, and stop sending the notification to the receiver entity, where the resource attribute includes the notification Uniform Resource Identifier; Wherein, the receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification. 31. The entity according to claim 30, wherein the sending unit is specifically configured to: sending an update message to the server entity, where the update message carries the notification cancellation indication; or Send a notification response message to the server entity, where the notification response message carries the notification cancellation indication; or Send a notification request message to the server entity, where the notification request message carries the notification cancellation indication. 32. A subscriber entity for subscribing to a notification in a machine communication system, characterized in that it comprises: a receiving unit, configured to receive a notification cancellation instruction sent by a server entity, where the notification cancellation instruction is sent by the receiver entity to the server entity; a sending unit, configured to send an update request message to the server entity according to the notification cancellation indication, so that the server entity can modify a resource attribute according to the update request message, where the resource attribute includes a notification uniform resource identifier; Wherein, the subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification. 33. A server entity for subscribing to notifications in a machine communication system, comprising: a receiving unit, configured to receive a notification modification instruction sent by the receiving end entity; a processing unit, configured to modify the resource attribute according to the notification modification instruction when the receiving-end entity has the authority, and send the notification to the receiving-end entity based on the modified resource attribute, where the resource attribute includes the rules for sending the notice; a sending unit, configured to send a subscription modification notification message to a subscriber entity, where the subscription modification notification message is used to notify the subscriber entity of the modification of the resource attribute by the server entity; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 34. The entity according to claim 33, wherein the processing unit is specifically configured to modify the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction. 35. The entity according to claim 33 or 34, wherein the receiving unit is specifically configured to: receiving an update message sent by the receiver entity, where the update message carries the notification modification indication; or receiving a notification response message sent by the recipient entity, where the notification response message carries the notification modification indication; or A notification request message sent by the receiving-end entity is received, where the notification request message carries the notification modification indication. 36. The entity according to claim 33 or 34, wherein the sending unit is further configured to send the resource attribute to the receiving-end entity, so that the receiving-end entity, according to the resource attribute, The notification modification indication is generated. 37. The entity of claim 33 or 34, wherein the sending rule includes one or more of a sending period, a message type and an expiration time. 38. A server entity for subscribing to notifications in a machine communication system, characterized in that it comprises: a first receiving unit, configured to receive a notification modification instruction sent by the receiving-end entity; a sending unit, configured to send the notification modification indication to the subscriber entity when the receiving entity has no authority; a second receiving unit, configured to receive an update request message sent by the subscriber entity according to the notification modification instruction; a processing unit, configured to modify a resource attribute according to the update request message, and send the notification to the receiver entity based on the modified resource attribute, where the resource attribute includes a sending rule for the notification; The subscriber entity and the receiver entity are two different entities in the machine communication system, the subscriber entity is the subscription initiator of the notification, and the receiver entity is the receiver of the notification . 39. The entity according to claim 38, wherein the processing unit is specifically configured to modify the resource attribute to a value corresponding to the parameter according to the parameter in the notification modification instruction. 40. The entity according to claim 38 or 39, wherein the first receiving unit is specifically configured to: receiving an update message sent by the receiver entity, where the update message carries the notification modification indication; or receiving a notification response message sent by the recipient entity, where the notification response message carries the notification modification indication; or A notification request message sent by the receiving-end entity is received, where the notification request message carries the notification modification indication. 41. The entity according to claim 38 or 39, wherein the sending unit is further configured to send the resource attribute to the receiving-end entity, so that the receiving-end entity, according to the resource attribute, The notification modification indication is generated. 42. The entity of claim 38 or 39, wherein the sending rules include one or more of a sending period, a message type and an expiration time. 43. A receiver entity for subscribing to a notification in a machine communication system, comprising: a generating unit for generating a notification modification instruction; The sending unit is configured to send the notification modification instruction to the server entity, so that the server entity can modify the resource attribute according to the notification modification instruction, and send the received entity based on the modified resource attribute. the notification, the resource attribute includes a sending rule of the notification; Wherein, the receiver entity is the receiver of the notification in the machine communication system, and is not the subscription initiator of the notification. 44. The entity according to claim 43, wherein the sending unit is specifically configured to: sending an update message to the server entity, where the update message carries the notification modification indication; or sending a notification response message to the server entity, where the notification response message carries the notification modification indication; or Send a notification request message to the server entity, where the notification request message carries the notification modification indication. 45. The entity according to claim 43 or 44, characterized in that the entity further comprises a receiving unit, the receiving unit, configured to receive the resource attribute sent by the server entity; The generating unit is specifically configured to generate the notification modification indication according to the resource attribute. 46. A subscriber entity for subscribing to a notification in a machine communication system, characterized in that it comprises: a receiving unit, configured to receive a notification modification instruction sent by a server entity, where the notification modification instruction is sent by the receiver entity to the server entity; A sending unit, configured to send an update request message to the server entity according to the notification modification instruction, so that the server entity can modify a resource attribute according to the update request message, where the resource attribute includes the notification sending rule ; Wherein, the subscriber entity is the subscription initiator of the notification in the machine communication system, and is not the recipient of the notification.

Images