WO2015117342A1 - 一种通知消息的发送方法、装置和系统 - Google Patents
一种通知消息的发送方法、装置和系统 Download PDFInfo
- Publication number
- WO2015117342A1 WO2015117342A1 PCT/CN2014/087616 CN2014087616W WO2015117342A1 WO 2015117342 A1 WO2015117342 A1 WO 2015117342A1 CN 2014087616 W CN2014087616 W CN 2014087616W WO 2015117342 A1 WO2015117342 A1 WO 2015117342A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- subscription
- notification
- notification message
- resource
- resources
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
Definitions
- the present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for transmitting a notification message.
- the M2M (Machine-To-Machine) communication network consists of various M2M nodes and bearer networks.
- the M2M nodes communicate with each other through a bearer network.
- An M2M node includes at least one application entity or one public service entity.
- An application entity is a logical unit that executes an actual M2M application
- a public service entity is a logical unit that manages and services an application.
- the application node is the end execution node, such as a smart meter, a temperature measurement and control sensor, a fire alarm, a smart home appliance, etc.
- the intermediate node is a middleware that connects the end execution node to the network side server, such as a gateway, and a base.
- the node is a server on the network side, and the application entity registered on the base node is usually a management software or management platform of the M2M service provider.
- the M2M system architecture diagram the communication between the M2M applications is implemented through the interaction between the CSE (Common Service Entity), and the premise of the communication is that the M2M application first needs to be registered in the local CSE ( For example, the application entity on the application node in the figure needs to register the CSE on the intermediate node, then the CSE on the intermediate node is the local CSE of the application entity on the application node, and then the interaction of the M2M application can be realized through the communication between the CSEs.
- CSE Common Service Entity
- the application node is a physical entity
- the application entity AE is a logical unit, which is a logical unit that actually executes an application on the physical entity of the application node.
- the application entity When the application entity is registered on the local CSE, the application entity needs to provide a security certificate that can identify its own legality and provide it to the local CSE for authentication. Only the authentication can be registered in the local CSE, and the application entity also needs to provide the application entity recommendation. Register the name for the local CSE reference.
- the registered application entity AE can also create an application-related resource on the local CSE as a sub-resource of the application resource.
- the local CSE creates a resource “application” after the AE is registered, and the application can also be applied to the resource in order to save the application data.
- the AE can subscribe to the message of whether a resource has changed. Subscription to resources is through AE
- the CSE wants to subscribe to the resource to create a sub-resource of type "subscription".
- the CSE where the resource is located may send a notification message to the AE to inform the resource concerned that the resource is concerned. edited.
- the CSE where the resource is located may send a notification message to the AE to inform the resource concerned that the resource is concerned. edited.
- the embodiment of the present invention provides a method, an apparatus, and a system for sending a notification message, so as to at least solve the technology in the related art that when a plurality of notification messages are sent, an important notification message or an urgent notification message cannot be sent due to network congestion. problem.
- an embodiment of the present invention provides a method for sending a notification message.
- the notification message is sent according to the notification message attribute corresponding to the subscription resource that has changed.
- the notification message attribute includes a notification priority and/or a notification validity time.
- the step of sending a notification message according to the notification message attribute corresponding to the subscription resource that is changed includes:
- the notification message is sent according to the difference value and the notification priority corresponding to each of the subscription resources in which the change occurs.
- the notification message attribute further includes a notification priority margin time
- the step of sending the notification message according to the difference value and the notification priority corresponding to each of the subscription resources that are changed includes:
- the notification message corresponding to the acquired subscription resource is sent according to the notification priority corresponding to the acquired subscription resource. Then, the notification message corresponding to the remaining changed subscription resource is sent according to the notification priority corresponding to the remaining changed subscription resource.
- the step of creating at least two subscription resources on a public service entity includes:
- the step of setting the notification message attribute corresponding to each of the subscription resources includes:
- the embodiment of the present invention further provides another method for sending a notification message, including the following steps:
- the application entity sends at least two create subscription requests to the public service entity, where the create subscription request includes setting information of the notification message attribute corresponding to the subscription resource;
- the public service entity receives the create subscription request
- the public service entity creates at least two subscription resources according to the creation subscription request, and one creation subscription request creates a subscription resource, and sets a notification message attribute corresponding to each subscription resource according to the setting information in each creation subscription request.
- the public service entity sends a notification message to the application entity according to the notification message attribute corresponding to the subscription resource that is changed;
- the application entity receives the notification message.
- the step of sending a notification message according to the notification message attribute corresponding to the subscription resource that is changed includes:
- the notification message is sent according to the difference value and the notification priority corresponding to each of the subscription resources in which the change occurs.
- the notification message attribute further includes a notification priority margin time
- the step of sending the notification message according to the difference value and the notification priority corresponding to each of the subscription resources that are changed includes:
- the notification message corresponding to the acquired subscription resource is sent according to the notification priority corresponding to the acquired subscription resource. Then, the notification message corresponding to the remaining changed subscription resource is sent according to the notification priority corresponding to the remaining changed subscription resource.
- the embodiment of the present invention further provides a sending device for a notification message, where the sending device includes a resource creation module, an attribute setting module, and a notification sending module:
- the resource creation module is configured to create at least two subscription resources on a common service entity
- the attribute setting module is configured to set a notification message attribute corresponding to each of the subscription resources
- the notification sending module is configured to send a notification message according to the notification message attribute corresponding to the changed subscription resource when at least two of the subscription resources are changed.
- the notification message attribute includes a notification priority and/or a notification validity time.
- the notification sending module includes a difference obtaining submodule and a notification sending submodule:
- the difference obtaining sub-module is configured to acquire a difference between a notification effective time and a current time corresponding to each of the subscription resources that are changed;
- the notification sending submodule is configured to send a notification message according to a difference value and a notification priority corresponding to each of the subscription resources in which the change occurs.
- the notification sending module further includes: determining the obtaining submodule:
- the determining the obtaining submodule is configured to obtain a subscription resource whose difference is less than or equal to the notification priority margin time
- the sending sub-module is further configured to first send the obtained notification message corresponding to the subscription resource according to the notification priority corresponding to the acquired subscription resource; and then, send the remaining changed subscription resource according to the notification priority corresponding to the remaining changed subscription resource. Corresponding notification message.
- the apparatus further includes a request receiving module:
- the request receiving module is configured to receive at least two create subscription requests
- the resource creation module is further configured to: create at least two subscription resources according to the received at least two creation subscription requests, and create a subscription request to create a subscription resource, where the creation subscription request includes setting information of a notification message attribute corresponding to the subscription resource;
- the attribute setting module is further configured to set a notification message attribute corresponding to each of the subscription resources according to the setting information in each creation subscription request.
- an embodiment of the present invention further provides a sending system for a notification message, where the sending system includes an application entity and a public service entity, where the application entity includes a request sending module and a notification receiving module, where the public service entity includes Request receiving module, resource creation module, attribute setting module, and notification sending module:
- the request sending module is configured to send at least two create subscription requests to the request receiving module, where the create subscription request includes setting information of a notification message attribute corresponding to the subscription resource;
- the request receiving module is configured to receive the create subscription request
- the resource creation module is configured to create at least two subscription resources according to the create subscription request, and create a subscription request to create a subscription resource;
- the attribute setting module is configured to set, according to the setting information in each creation subscription request, a notification message attribute corresponding to each of the subscription resources;
- the notification sending module is configured to: when the at least two of the subscription resources are changed, send a notification message to the notification receiving module according to the notification message attribute corresponding to the changed subscription resource;
- the notification receiving module is configured to receive the notification message.
- the method for sending the notification message in the embodiment of the present invention is specifically: creating at least two subscription resources on the public service entity, and setting a notification message corresponding to each subscription resource Attribute; when at least two subscription resources are changed, the notification message is sent according to the notification message attribute corresponding to the changed subscription resource.
- the embodiment of the present invention sends a notification message according to the notification message attribute corresponding to the subscription resource, and the notification message attribute can be set according to the needs of the user, for example, setting the notification priority and the notification message according to the importance degree of the notification message.
- the emergency setting notification effective time and the notification priority margin time, etc. so that the notification message can be sent according to the importance degree and urgency of the notification message corresponding to the subscription resource, so that the notification message with high degree of importance or the urgency is sent first. Avoid The important notification message or the urgently high notification message cannot be sent out, and the delivery efficiency of the provided notification message increases the user experience.
- FIG. 1 is a schematic structural diagram of an M2M network in the prior art
- FIG. 2 is a schematic flowchart of a method for sending a notification message according to Embodiment 1 of the present invention
- FIG. 3 is a schematic flowchart of a method for sending a notification message according to Embodiment 2 of the present invention.
- FIG. 4 is a schematic flowchart of a method for sending a notification message according to Embodiment 3 of the present invention.
- FIG. 5 is a schematic flowchart of a method for sending a notification message according to Embodiment 4 of the present invention.
- FIG. 6 is a schematic structural diagram of a first apparatus for sending a notification message according to Embodiment 6 of the present invention.
- FIG. 7 is a second schematic structural diagram of a device for sending a notification message according to Embodiment 6 of the present invention.
- FIG. 8 is a schematic structural diagram of a third apparatus for sending a notification message according to Embodiment 6 of the present invention.
- FIG. 9 is a schematic structural diagram of a fourth apparatus for sending a notification message according to Embodiment 6 of the present invention.
- FIG. 10 is a schematic structural diagram of a system for transmitting a notification message according to Embodiment 7 of the present invention.
- the method for sending the notification message in this embodiment includes the following steps:
- Step S101 Create at least two subscription resources on the public service entity
- the public service entity creates the subscription resource including creating a resource name, creating a resource type, creating a location and content, and the like, wherein the content includes an attribute that the cover resource needs to create.
- the creation of a subscription resource creates a resource, the creation of a resource attribute and its child resources, and the creation of a child resource attribute. For example, create a resource in the resource directory ⁇ CSEBase of the public service entity CSE, and set the resource name to "myApplication1", which is the resource type "Application". At the same time, the attribute of the resource "myApplication1" is also created.
- Step S102 setting a notification message attribute corresponding to each subscription resource
- the notification message attribute can reflect the importance of the notification message and/or the urgency of the notification message. For example, if the resource name is "myApplication1", create a child resource whose resource type is "mySubscription1", create an address of ⁇ CSEBase ⁇ myApplication1, set the name of the notification message attribute parameter, and set the attribute "notification priority".
- the notification priority can be set to 1, 2, 3, 4, etc., and can also be set to high, medium, low, etc., and other setting methods that can be used to reflect the priority of the notification message, and set the attribute "notification effective time" here.
- the effective time can be a specific time value, for example, 23:59 on May 24, 2014. Of course, it is not limited to the time value.
- the specific time value is set according to the specific situation.
- the notification effective time refers specifically to the save time of the notification message. That is, when the time exceeds this time, the notification message will be invalidated, that is, the notification message is deleted.
- the notification priority margin time here is a time value set before the notification message expires.
- the time value can be 5 minutes, 10 minutes, etc., and the specific time value is determined according to the specific situation. Settings.
- not only the notification priority, the notification validity time, and the notification priority margin time other attribute values that can be used to indicate the importance of the notification message and/or the urgency of the notification message can be implemented.
- Step S103 When at least two subscription resources are changed, the notification message is sent according to the notification message attribute corresponding to the changed subscription resource.
- the subscription resource changes in this step include when the subscription resource is changed in the attribute or the sub-resource, for example, the value of the attribute is modified, the sub-resource is deleted, or the sub-resource is newly created, and other conditions that may cause the subscription resource to be changed.
- the notification message is sent according to the notification message attribute corresponding to the changed subscription resource, mainly for the important notification message and/or the urgent notification message, and is not blocked due to limited network resources and is not sent out.
- the notification message attribute includes a notification priority and/or a notification effective time, that is, setting a notification priority and/or a notification effective time corresponding to each subscription resource, for example, creating a sub-resource under the resource “myApplication1”
- the priority is 2, the setting attribute "notification effective time” is 23:59 on May 22, 2014; the sub-resource “mySubscription3" is created under the resource "myApplication3", the attribute "notification priority” is set to 3, and the attribute is set.
- the notification validity time is 23:59 on May 24, 2014; the sub-resource "mySubscription4" is created under the resource “myApplication4", the setting attribute "notification priority” is 4, and the setting attribute "notification effective time” is May 2014. 23:59 on the 24th.
- the notification message is sent according to the notification message attribute corresponding to the changed subscription resource, specifically, when at least two subscription resources are changed, according to the change.
- the corresponding notification message may be sent according to their corresponding notification priority. If the higher the number of the notification priority is, the higher the priority is, the higher the importance of the corresponding notification message is.
- the notification message corresponding to the small effective time is sent first, if the above is the middle If the attributes or sub-resources of the resources "myApplication1", “myApplication2", “myApplication3” and “myApplication4" on the CSE are changed, the subscription resources “mySubscription1” and “" of the resources “myApplication1” and “myApplication2" are preferentially sent. Notification message generated by mySubscription2".
- the notification message may be sent according to the notification priority and the notification effective time corresponding to the changed subscription resource, and the urgency may be first determined to be sent in the judgment priority, that is, the notification effective time value is first determined, and then the judgment notification priority is sent.
- the notification message if the above attribute or sub-resource of the resources "myApplication1", “myApplication2", “myApplication3”, “myApplication4" on the CSE are changed, due to the notification of "myApplication1" and "myApplication2" The effective time is small, so the two of them are sent preferentially.
- the notification message generated by the subscription resource "mySubscription2" of the resource "myApplication2" is sent first.
- the priority of the notification can be determined first.
- step S101 at least two subscription resources are created according to the received at least two creation subscription requests, one creation subscription request creates a subscription resource, and the creation subscription request includes setting information of the notification message attribute corresponding to the subscription resource;
- the step of setting the notification message attribute corresponding to each subscription resource in the step S102 includes: setting the notification message attribute corresponding to each subscription resource according to the setting information in each creation subscription request.
- the CSE receives a create subscription request, which includes: resource name: "mySubscription1", resource type: “Subscription”, created to: ⁇ CSEBase ⁇ myApplication, content: name and value including the following parameters: notification Priority: set to 1; notification valid time: 23:59 on May 22, 2014; priority margin time: 10 minutes; CSE receives the permission to create a resource after receiving the request to create a subscription, if any, in the resource Create a sub-resource "mySubscription1" under “myApplication1", set the attribute "Notification Priority” to 1, set the attribute "Notification Valid Time” to 23:59 on May 22, 2014, and set the attribute "Notification Priority Remaining Time” to 10. minute.
- This embodiment is a method for sending a notification message when the notification message attribute includes a notification priority and a notification validity time. As shown in FIG. 3 in this example, the following steps are included:
- Step S201 Create at least two subscription resources on the public service entity
- step S101 the specific implementation is the same as step S101 described above.
- Step S202 setting a notification priority and a notification validity time corresponding to each subscription resource
- the specific implementation is the same as the above step S102, except that the notification message attribute corresponding to each subscription resource is set as the notification priority and the notification effective time.
- Step S203 When at least two subscription resources are changed, obtain a difference between a notification effective time and a current time corresponding to each subscription resource that has changed;
- the subscribed resource changes that is, when the subscription resource changes
- the subscription resource is changed in the attribute or the sub-resource, for example, the value of the attribute is modified, the sub-resource is deleted, or the sub-resource is newly created, and the like.
- the situation that caused the subscription resource to change The difference between the valid time of the notification corresponding to each subscription resource and the current time is obtained by calculation; for example, the sub-resource "mySubscription1" is created under the resource "myApplication1", the attribute "notification priority” is set to 1, and the attribute "notification effective time” is set.
- Step S204 Send a notification message according to the difference value and the notification priority corresponding to each subscription resource that has changed.
- the specific notification message according to the difference and the notification priority corresponding to each subscription resource that is changed may be used to determine whether the difference satisfies the preset time value, and if the preset time value is met, the first time The notification message is sent out, and if there are multiple satisfactions, it is further sent according to the corresponding notification priority. For example, if the preset time value is 1 day, the preset time values are “myApplication1” and “myApplication2”, and further, since the notification priority of “myApplication2” is high, the resource “myApplication2” is sent first.
- the notification message generated by the subscription resource "mySubscription2".
- the message is sent according to the corresponding notification priority.
- “myApplication3" and “myApplication4" preferentially send a notification message generated by the subscription resource "mySubscription4" of the resource "myApplication4".
- the time difference can be satisfied within a certain range and the priority is sent first within a certain range. It should be understood as a way to make an important and urgent notification message as soon as possible.
- the invention of the present application can be realized.
- the notification message attribute further includes a method for sending a notification message when the priority margin time is notified. As shown in FIG. 4, the method includes the following steps:
- Step S301 Create at least two subscription resources on the public service entity
- step S101 the specific implementation is the same as step S101 described above.
- Step S302 setting a notification priority and a notification effective time corresponding to each subscription resource
- the specific implementation is the same as the above step S102, except that the notification message attributes corresponding to each subscription resource are set as the notification priority, the notification effective time, and the notification priority margin time.
- Step S303 When at least two subscription resources are changed, obtain a difference between a notification effective time and a current time corresponding to each subscription resource that has changed;
- the subscribed resource changes that is, when the subscription resource changes
- the subscription resource is changed in the attribute or the sub-resource, for example, the value of the attribute is modified, the sub-resource is deleted, or the sub-resource is newly created, and the like.
- the situation that caused the subscription resource to change The difference between the valid time of the notification corresponding to each subscription resource and the current time is obtained by calculation; for example, the sub-resource "mySubscription1" is created under the resource "myApplication1", the attribute "notification priority” is set to 1, and the attribute "notification effective time” is set.
- Step S304 Obtain a subscription resource whose difference is less than or equal to the notification priority margin time
- the notification margin time is specific time.
- the value is set according to the specific conditions of each subscription resource, and the specific time values may be the same or different. If there is less than or equal to the notification priority margin time corresponding to each subscription resource, the notification message corresponding to the subscription resource is particularly urgent, and the subscription resources in which the difference between the subscription resources for sending the changes is less than or equal to the notification priority margin time are obtained.
- Step S305 First, the notification message corresponding to the acquired subscription resource is sent according to the notification priority corresponding to the acquired subscription resource. Then, the notification message corresponding to the remaining changed subscription resource is sent according to the notification priority corresponding to the remaining changed subscription resource.
- the queue transmission can be used, and the notification message corresponding to the subscription resource is sent first. Further, if there are multiple subscription resources that are less than or equal to the notification priority margin time corresponding to each subscription resource, then the notification message corresponding to the acquired subscription resource is sent according to the notification priority corresponding to the acquired subscription resource; The notification priority corresponding to the subscription resource sends the notification message corresponding to the remaining changed subscription resource, so that not only the notification message with high priority can be sent, but also the low priority with the expiration date is guaranteed before the expiration of the validity period.
- the queue is sent to avoid scenarios where low priority notification messages cannot be sent.
- the method for transmitting the notification message in this embodiment includes the following steps:
- Step S401 The application entity sends at least two create subscription requests to the public service entity, and the creation subscription request includes setting information of the notification message attribute corresponding to the subscription resource;
- Step S402 The public service entity receives a create subscription request.
- Step S403 The public service entity creates at least two subscription resources according to the creation subscription request, and one creation subscription request creates a subscription resource, and sets the notification message attribute corresponding to each subscription resource according to the setting information in each creation subscription request.
- Step S404 When at least two subscription resources are changed, the public service entity sends a notification message to the application entity according to the notification message attribute corresponding to the changed subscription resource;
- Step S405 The application entity is requested to receive the notification message.
- the step of sending the notification message according to the notification message attribute corresponding to the changed subscription resource includes:
- the notification message is sent according to the difference value and the notification priority corresponding to each subscription resource that has changed.
- the notification message attribute further includes a notification priority margin time
- the step of sending the notification message according to the difference value and the notification priority corresponding to each subscription resource that is changed includes:
- the notification message corresponding to the acquired subscription resource is sent according to the notification priority corresponding to the acquired subscription resource. Then, the notification message corresponding to the remaining changed subscription resource is sent according to the notification priority corresponding to the remaining changed subscription resource.
- the present embodiment is specifically described in conjunction with the public service entity CSE and the application entity AE including AE1, AE2, AE3, and AE4.
- AE1 sends a create resource request to the CSE, and the create resource request contains:
- Notification priority set to 1;
- the CSE After receiving the resource creation request of AE1, the CSE verifies that AE1 has the right to create a resource, creates a sub-resource "mySubscription1" under the resource "myApplication1", sets the attribute “notification priority” to 1, and sets the attribute “notification effective time” to 2014. At 23:59 on May 22nd, set the attribute "Priority Time” to 10 minutes.
- AE2 sends a create resource request to the CSE, and the create resource request contains:
- Notification priority set to 2;
- the CSE After receiving the resource creation request of AE2, the CSE verifies that AE2 has the right to create a resource, creates a sub-resource "mySubscription2" under the resource "myApplication2", sets the attribute "notification priority” to 2, and sets the attribute "notification effective time” to 2014. At 23:59 on May 22nd, set the attribute "Priority Time” to 5 minutes.
- AE3 sends a create resource request to the CSE, and the create resource request contains:
- Notification priority set to 3;
- the CSE After receiving the resource creation request of AE3, the CSE verifies that AE3 has the right to create a resource, creates a sub-resource "mySubscription3" under the resource "myApplication3", sets the attribute "notification priority” to 3, and sets the attribute "notification effective time” to 2014. At 23:59 on May 24th, set the attribute "Priority Time” to 10 minutes.
- AE4 sends a create resource request to the CSE, and the create resource request contains:
- Notification priority set to 4.
- the CSE After receiving the resource request of AE4, the CSE verifies that AE4 has the right to create a resource, creates a sub-resource "mySubscription4" under the resource "myApplication4", sets the attribute "notification priority” to 4, and sets the attribute “notification effective time” to 2014. At 23:59 on May 24th, set the attribute "Priority Time” to 10 minutes.
- priority 4 is the highest, priority 3 is higher, priority 2 is second, and priority 1 is the lowest;
- the CSE When the attributes or sub-resources of the resources "myApplication1”, “myApplication2”, “myApplication3”, and “myApplication4" on the CSE are changed, the CSE generates a notification message according to the subscription resources of the resources.
- the notification message generated by the subscription resource "mySubscription4" of the resource "myApplication4" is preferentially transmitted.
- the embodiment of the present invention further provides a sending device for a notification message.
- the sending device includes a resource creating module, an attribute setting module, and a notification sending module.
- the resource creation module is configured to create at least two subscription resources on the public service entity;
- the attribute setting module is configured to set a notification message attribute corresponding to each subscription resource;
- the notification sending module is configured to: when at least two subscription resources are changed, according to The notification message attribute corresponding to the subscription resource that has changed sends a notification message.
- the notification message attribute includes a notification priority and/or a notification validity time.
- the embodiment of the present invention further provides another sending device for the notification message.
- the notification sending module of the sending device includes a difference obtaining sub-module and a notification sending sub-module.
- the difference obtaining sub-module is configured to obtain a difference between the notification effective time and the current time corresponding to each subscription resource that has changed; the notification sending sub-module is configured to send according to the difference and the notification priority corresponding to each subscription resource that has changed. Notification message.
- the embodiment of the present invention further provides another sending device for the notification message.
- the notification sending module of the sending device further includes a determining acquisition sub-module.
- the determining the sub-module is configured to obtain the subscription resource whose difference is less than or equal to the notification priority margin time;
- the sending sub-module is further configured to first send the obtained notification message corresponding to the subscription resource according to the notification priority corresponding to the acquired subscription resource; Then, the notification message corresponding to the remaining changed subscription resource is sent according to the notification priority corresponding to the remaining changed subscription resource.
- the embodiment of the present invention further provides another sending device for the notification message.
- the transmitting device further includes a request receiving module.
- the request receiving module is configured to receive at least two create subscription requests;
- the resource creation module is further configured to: create at least two subscription resources according to the at least two created subscription requests, and create a subscription request to create a subscription resource, and the creation subscription request includes setting information of the notification message attribute corresponding to the subscription resource; the attribute setting module further It is set to set the notification message attribute corresponding to each subscription resource according to the setting information in each creation subscription request.
- the embodiment of the present invention further provides a sending system for a notification message.
- the sending system includes an application entity and a public service entity.
- the application entity includes a request sending module and a notification receiving module
- the public service entity includes a request receiving module and a resource creation. Module, property setting module, and notification sending module.
- the request sending module is configured to send at least two create subscription requests to the request receiving module, and the create subscription request includes setting information of the notification message attribute corresponding to the subscription resource;
- the request receiving module is configured to receive the create subscription request;
- the resource creation module is configured to Create a subscription request to create at least two subscription resources, one create a subscription request to create a subscription resource;
- the property setting module is set to set the corresponding correspondence of each subscription resource according to the setting information in each creation subscription request
- the notification sending attribute is configured to: when the at least two subscription resources are changed, send a notification message to the notification receiving module according to the notification message attribute corresponding to the changed subscription resource; and the notification receiving module is configured to receive the notification message.
- the embodiment of the present invention controls the sending of the notification message by adding the parameters related to the notification message, so that the terminal including the application entity and the public service entity can set different priorities for different subscription resources according to their own requirements, so that the CSE sends the notification message.
- the time is sent according to the priority, so that when a large number of notification messages are generated, the high priority notification message can be sent preferentially, preventing the high priority notification message from being transmitted due to network congestion, and also controlling the low validity period.
- the priority is sent out before the expiration of the validity period, avoiding the scenario where the low priority notification message cannot be sent.
- the notification message can be sent according to the importance degree and urgency of the notification message corresponding to the subscription resource, so that the importance is high.
- the notification message or the urgency is sent first, the important notification message to avoid or the urgency notification message cannot be sent out, the sending efficiency of the provided notification message increases the user experience.
Abstract
本发明实施例提供的通知消息的发送方法、装置和系统，属于通信领域。本发明实施例的通知消息的发送方法具体为：在公共业务实体上创建至少两个订阅资源，并设置各订阅资源对应的通知消息属性；当至少两个订阅资源发生变更时，根据发生变更的订阅资源对应的通知消息属性发送通知消息。本发明实施例通知消息属性可根据用户的需要进行设置，例如根据通知消息的重要程度设置通知优先级、通知消息紧急情况设置通知有效时间和通知优先余量时间等，使通知消息的重要程度和紧急程度进行通知消息的发送，让重要程度高的通知消息或者紧急程度高先发送出去，避免的重要通知消息或紧急程度高的通知消息无法发送出去的问题，提供的通知消息的发送效率。
Description
本发明涉及通信领域，特别涉及一种通知消息的发送方法、装置和系统。
M2M(Machine-To-Machine，机器对机器)通信网络由各个M2M节点和承载网络组成。M2M节点通过承载网络实现互相通信，一个M2M节点至少包含一个应用实体或者一个公共业务实体。
应用实体是执行实际M2M应用的逻辑单元，公共业务实体是对应用进行管理和服务的逻辑单元。
在M2M系统架构中，应用节点是末端的执行节点，例如智能电表，温度测控传感器，火警报警器，智能家电等等，中间节点是连接末端执行节点到网络侧服务器的中间件，例如网关，基础节点是网络侧的服务器，注册在基础节点上的应用实体通常是M2M服务商的管理软件或管理平台。
如下图1所示M2M系统架构图，M2M应用之间的通信是通过CSE(Common Service Entity，公共业务实体)之间的交互来实现，而通信的前提是M2M应用首先需要在本地CSE进行注册(例如图中应用节点上的应用实体需要注册在中间节点上的CSE，那么中间节点上的CSE就是应用节点上应用实体的本地CSE)，然后才能通过CSE之间的通信实现M2M应用的交互。
应用节点是物理实体，应用实体AE是逻辑单元，是在应用节点这个物理实体上真正执行应用的逻辑单元。
在应用实体注册在本地CSE上时，应用实体需要提供能标识自己合法性的安全证书，提供给本地CSE进行验证，只有验证通过才能在本地CSE进行注册，同时应用实体还需要提供应用实体建议的注册名称给本地CSE参考。
注册后的应用实体AE还可以在本地CSE上创建应用相关的资源，作为应用资源的子资源，例如AE注册后本地CSE创建资源“应用”，为了保存应用的数据，应用还可以在资源“应用”下创建资源“容器”，资源“容器”用来保存AE相关的数据。AE可以通过订阅的方式来获取某个资源是否变更的消息。对资源的订阅是通过AE在
CSE想要订阅的资源下上创建类型为“subscription”的子资源来实现的。被订阅的资源在属性或者子资源变更时，例如属性的值被修改，子资源被删除，或新创建了子资源等，该资源所在的CSE可以向AE发送通知消息，告知其关注的资源被修改了。当有多个通知消息需要发送时，往往由于网络资源有限导致重要的通知消息或者紧急的通知消息不能发送出去。
发明内容
本发明实施例提供了一种通知消息的发送方法、装置和系统，以至少解决相关技术中在多个通知消息发送时，由于网络拥塞导致重要的通知消息或者紧急的通知消息无法发送出去的技术问题。
为解决上述问题，本发明实施例提供一种通知消息的发送方法，
在公共业务实体上创建至少两个订阅资源；
设置各所述订阅资源对应的通知消息属性；
当至少两个所述订阅资源发生变更时，根据发生变更的所述订阅资源对应的通知消息属性发送通知消息。
在本发明实施例的一种实施例中，所述通知消息属性包括通知优先级和/或通知有效时间。
在本发明的一种实施例中，所述通知消息属性包括通知优先级和通知有效时间时，所述根据发生变更的所述订阅资源对应的通知消息属性发送通知消息的步骤包括：
获取发生变更的各所述订阅资源对应的通知有效时间与当前时间的差值；
根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息。
在本发明的一种实施例中，所述通知消息属性还包括通知优先余量时间，所述根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息的步骤包括：
获取差值小于或等于通知优先余量时间的订阅资源；
首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
在本发明的一种实施例中，所述在公共业务实体上创建至少两个订阅资源的步骤包括：
根据接收的至少两个创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；
所述设置各所述订阅资源对应的通知消息属性的步骤包括：
根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性。
为解决上述问题，本发明实施例还提供另外一种通知消息的发送方法，包括如下步骤：
应用实体发送至少两个创建订阅请求给公共业务实体，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；
所述公共业务实体接收所述创建订阅请求；
所述公共业务实体根据所述创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，并根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性；
当至少两个所述订阅资源发生变更时，所述公共业务实体根据发生变更的所述订阅资源对应的通知消息属性发送通知消息给所述应用实体；
所述请应用实体接收所述通知消息。
在本发明的一种实施例中，所述通知消息属性包括通知优先级和通知有效时间时，所述根据发生变更的所述订阅资源对应的通知消息属性发送通知消息的步骤包括：
获取发生变更的各所述订阅资源对应的通知有效时间与当前时间的差值；
根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息。
在本发明的一种实施例中，所述通知消息属性还包括通知优先余量时间，所述根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息的步骤包括：
获取差值小于或等于通知优先余量时间的订阅资源；
首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
为解决上述问题，本发明实施例还提供一种通知消息的发送装置，所述发送装置包括资源创建模块、属性设置模块和通知发送模块：
所述资源创建模块设置为在公共业务实体上创建至少两个订阅资源；
所述属性设置模块设置为设置各所述订阅资源对应的通知消息属性；
所述通知发送模块设置为当至少两个所述订阅资源发生变更时，根据发生变更的所述订阅资源对应的通知消息属性发送通知消息。
在本发明的一种实施例中，所述通知消息属性包括通知优先级和/或通知有效时间。
在本发明的一种实施例中，所述通知发送模块包括差值获取子模块和通知发送子模块：
所述差值获取子模块设置为获取发生变更的各所述订阅资源对应的通知有效时间与当前时间的差值；
所述通知发送子模块设置为根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息。
在本发明的一种实施例中，所述通知发送模块还包括判断获取子模块：
所述判断获取子模块设置为获取差值小于或等于通知优先余量时间的订阅资源；
所述发送子模块还设置为首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
在本发明的一种实施例中，所述装置还包括请求接收模块：
所述请求接收模块设置为接收至少两个创建订阅请求；
所述资源创建模块还设置为根据接收的至少两个创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；
所述属性设置模块还设置为根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性。
为解决上述问题，本发明实施例还提供一种通知消息的发送系统，所述发送系统包括应用实体和公共业务实体，所述应用实体包括请求发送模块和通知接收模块，所述公共业务实体包括请求接收模块、资源创建模块、属性设置模块和通知发送模块：
所述请求发送模块设置为发送至少两个创建订阅请求给所述请求接收模块，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；
所述请求接收模块设置为接收所述创建订阅请求；
所述资源创建模块设置为根据所述创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源；
所述属性设置模块设置为根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性；
所述通知发送模块设置为当至少两个所述订阅资源发生变更时，根据发生变更的所述订阅资源对应的通知消息属性发送通知消息给所述通知接收模块；
通知接收模块设置为接收所述通知消息。
本发明实施例的有益效果是：
本发明实施例提供的通知消息的发送方法和装置以及系统，本发明实施例的通知消息的发送方法具体为：在公共业务实体上创建至少两个订阅资源，并设置各订阅资源对应的通知消息属性；当至少两个订阅资源发生变更时，根据发生变更的订阅资源对应的通知消息属性发送通知消息。与现有技术相比，本发明实施例根据订阅资源对应的通知消息属性来发送通知消息，并且通知消息属性可根据用户的需要进行设置，例如根据通知消息的重要程度设置通知优先级、通知消息紧急情况设置通知有效时间和通知优先余量时间等，这样就可以根据订阅资源对应的通知消息的重要程度和紧急程度进行通知消息的发送，让重要程度高的通知消息或者紧急程度高先发送出去，避
免的重要通知消息或紧急程度高的通知消息无法发送出去的问题，提供的通知消息的发送效率，增加了用户体验度。
图1为现有技术中M2M网络的结构示意图；
图2为本发明实施例一提供的通知消息的发送方法流程示意图；
图3为本发明实施例二提供的通知消息的发送方法流程示意图；
图4为本发明实施例三提供的通知消息的发送方法流程示意图；
图5为本发明实施例四提供的通知消息的发送方法流程示意图；
图6为本发明实施例六提供的通知消息的发送装置第一种结构示意图；
图7为本发明实施例六提供的通知消息的发送装置第二种结构示意图；
图8为本发明实施例六提供的通知消息的发送装置第三种结构示意图；
图9为本发明实施例六提供的通知消息的发送装置第四种结构示意图；
图10为本发明实施例七提供的通知消息的发送系统结构示意图。
为使本领域技术人员更好地理解本发明的技术方案，下面结合附图和具体实施方式对本发明作进一步详细描述。
实施例一
本实施例的通知消息的发送方法，如图2所示，包括以下步骤：
步骤S101：在公共业务实体上创建至少两个订阅资源；
在该步骤中，公共业务实体创建订阅资源包括创建资源名称、创建资源类型、创建的位置和内容等，其中内容包括盖资源需要创建的属性。这里的创建订阅资源创建资源、资源属性和其子资源的创建以及子资源属性的创建等。例如在公共业务实体CSE的资源目录\\CSEBase下创建资源，并设置资源名称为“myApplication1”，这是资源类型为“Application”。同时，还创建资源“myApplication1”的属性。
步骤S102：设置各订阅资源对应的通知消息属性；
在步骤中，设置各订阅资源对应的通知消息属性即设置各订阅资源对应的通知消息的相关参数。通知消息属性能够体现通知消息的重要性和/或通知消息的紧急程度。例如在资源名称为“myApplication1”下创建子资源的资源类型为“mySubscription1”的子资源，创建地址为\\CSEBase\myApplication1，设置通知消息属性参数的名称和值为设置属性“通知优先级”，例如通知优先级可以设为1、2、3、4等，还可以设为高、中、低等以及其他可以用来体现通知消息的优先级的设置方法，设置属性“通知有效时间”这里的有效时间可以为具体的时间值，例如2014年5月24日23：59，当然不仅仅限于该时间值，具体的时间值根据具体情况进行设置，通知有效时间具体指对该通知消息的保存时间，也即当超过这个时间该通知消息就会失效，即删除该通知消息。设置属性“通知优先余量时间”这里的通知优先余量时间是指距离该通知消息失效前设置的一个时间值，该时间值可以为5分钟、10分钟等，具体时间值大小根据具体情况进行设置。当然，不仅仅限于通知优先级、通知有效时间和通知优先余量时间，其他可以用来表示通知消息的重要程度和/或通知消息紧急程度的属性值都可以实现。
步骤S103：当至少两个订阅资源发生变更时，根据发生变更的订阅资源对应的通知消息属性发送通知消息。
该步骤中的订阅资源发生变更包括订阅资源在属性或者子资源变更时，例如属性的值被修改，子资源被删除，或新创建了子资源等其他可以导致订阅资源发生变更的情况。这里的根据发生变更的订阅资源对应的通知消息属性发送通知消息，主要是为了是重要的通知消息和/或紧急的通知消息，不因为网络资源有限导致阻塞而没有发送出去。
进一步，在上述步骤S102中的，通知消息属性包括通知优先级和/或通知有效时间，即设置各订阅资源对应的通知优先级和/或通知有效时间，例如，在资源“myApplication1”下创建子资源“mySubscription1”，设置属性“通知优先级”为1，设置属性“通知有效时间”为2014年5月22日23：59；在资源“myApplication2”下创建子资源“mySubscription2”，设置属性“通知优先级”为2，设置属性“通知有效时间”为2014年5月22日23：59；在资源“myApplication3”下创建子资源“mySubscription3”，设置属性“通知优先级”为3，设置属性“通知有效时间”为2014年5月24日23：59；在资源“myApplication4”下创建子资源“mySubscription4”，设置属性“通知优先级”为4，设置属性“通知有效时间”为2014年5月24日23：59。在上述步骤103中，当至少两个订阅资源发生变更时，根据发生变更的订阅资源对应的通知消息属性发送通知消息具体为当至少两个订阅资源发生变更时，根据发生变更
的订阅资源对应的通知优先级和/或通知有效时间发送通知消息。例如，可以根据他们对应的通知优先级发送对应的通知消息，假如设定通知优先级的数字越高表示其优先级越高即对应的通知消息的重要性越高，那么就先发送优先级高对应的通知消息，假如当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”，“myApplication4”的属性或子资源都发生变更时，优先发送资源“myApplication4”的订阅资源“mySubscription4”产生的通知消息。也可以根据通知有效时间发送对应的通知消息，假如设定通知有效时间的值越小表示其对应的通知消息的紧急性越高，那么就先发送通知有效时间小对应的通知消息，假如上述中的假如当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”的属性或子资源都发生变更时，优先发送资源“myApplication1”和“myApplication2”的订阅资源“mySubscription1”和“mySubscription2”产生的通知消息。当然还可以根据发生变更的订阅资源对应的通知优先级和通知有效时间发送通知消息，可以先判断紧急程度在判断优先级进行发送，即先判断通知有效时间值，再进行判断通知优先级进行发送对应的通知消息，假如上述中的假如当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”，“myApplication4”的属性或子资源都发生变更时，由于“myApplication1”和“myApplication2”的通知有效时间小，所以优先发送他们两个，进一步由于“myApplication2”的通知优先级高，所以最先发送资源“myApplication2”的订阅资源“mySubscription2”产生的通知消息。当然不仅仅限于上述方式，还可先判断通知优先级，在判断通知有效时间，应该理解为只要能使重要的并且紧急的通知消息尽快发出去的方式都可实现本申请的发明。
进一步，在上述步骤S101中，根据接收的至少两个创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，创建订阅请求包括订阅资源对应的通知消息属性的设置信息；在上述步骤S102中设置各订阅资源对应的通知消息属性的步骤包括：根据各创建订阅请求中的设置信息设置各订阅资源对应的通知消息属性。例如，CSE接收一个创建订阅请求，该创建订阅请求中包含：资源名称：“mySubscription1”，资源类型：“Subscription”，创建到：\\CSEBase\myApplication，内容：包括以下参数的名称和值：通知优先级：设置为1；通知有效时间：2014年5月22日23：59；优先余量时间：10分钟；CSE接收到创建订阅请求后，验证是否具有创建资源的权限，如果有，在资源“myApplication1”下创建子资源“mySubscription1”，设置属性“通知优先级”为1，设置属性“通知有效时间”为2014年5月22日23：59，设置属性“通知优先余量时间”为10分钟。当然也可以为一个创建订阅请求，该创建订阅请求包括能至少创建两个订阅资源。
实施例二
本实施例为在通知消息属性包括通知优先级和通知有效时间时的通知消息的发送方法，本实例中的如图3所示，包括以下步骤：
步骤S201：在公共业务实体上创建至少两个订阅资源；
在该步骤中，具体的实现方式与上述步骤S101相同。
步骤S202：设置各订阅资源对应的通知优先级和通知有效时间；
在该步骤中，具体的实现方式与上述步骤S102相同，只是设置各订阅资源对应的通知消息属性为通知优先级和通知有效时间。
步骤S203：当至少两个订阅资源发生变更时，获取发生变更的各订阅资源对应的通知有效时间与当前时间的差值；
在该步骤中，当订阅的资源发生变更时，即订阅资源发生变更包括订阅资源在属性或者子资源变更时，例如属性的值被修改，子资源被删除，或新创建了子资源等其他可以导致订阅资源发生变更的情况。通过计算获取各订阅资源对应的通知有效时间与当前时间的差值；例如，在资源“myApplication1”下创建子资源“mySubscription1”，设置属性“通知优先级”为1，设置属性“通知有效时间”为2014年5月22日23：59；在资源“myApplication2”下创建子资源“mySubscription2”，设置属性“通知优先级”为2，设置属性“通知有效时间”为2014年5月22日23：59；在资源“myApplication3”下创建子资源“mySubscription3”，设置属性“通知优先级”为3，设置属性“通知有效时间”为2014年5月24日23：59；在资源“myApplication4”下创建子资源“mySubscription4”，设置属性“通知优先级”为4，设置属性“通知有效时间”为2014年5月24日23：59。假如当前时间为当前时间到2014年5月22日23：49分时，那么他们与当前时间的差值分别为10分钟、10分钟、2日10分钟和2日10分钟。
步骤S204：根据发生变更的各订阅资源对应的差值和通知优先级发送通知消息。
在该步骤中，具体的根据发生变更的各订阅资源对应的差值和通知优先级发送通知消息可以为先判断该差值是否满足预设时间值，如果满足预设时间值，则先将该通知消息发送出去，如果存在多个满足时，进一步根据对应的通知优先级发送出去。例如，预设时间值为1天，那么满足预设时间值为“myApplication1”和“myApplication2”，进一步由于“myApplication2”的通知优先级高，所以最先发送资源“myApplication2”
的订阅资源“mySubscription2”产生的通知消息。对应不满足的，在满足预设时间值得通知消息发送完后，根据对应的通知优先级进行发送。例如，“myApplication3”和“myApplication4”，优先发送资源“myApplication4”的订阅资源“mySubscription4”产生的通知消息。当然，不仅仅限于该种方式，例如可以使该时间差值满足一定范围内同时优先级在一定范围内最先发送出去，应该理解为只要能使重要的并且紧急的通知消息尽快发出去的方式都可实现本申请的发明。
实施例三
本实施例为在实施例2基础上，通知消息属性还包括通知优先余量时间时的通知消息的发送方法，如图4所示，包括以下步骤：
步骤S301：在公共业务实体上创建至少两个订阅资源；
在该步骤中，具体的实现方式与上述步骤S101相同。
步骤S302：设置各订阅资源对应的通知优先级和通知有效时间；
在该步骤中，具体的实现方式与上述步骤S102相同，只是设置各订阅资源对应的通知消息属性为通知优先级、通知有效时间和通知优先余量时间。
步骤S303：当至少两个订阅资源发生变更时，获取发生变更的各订阅资源对应的通知有效时间与当前时间的差值；
在该步骤中，当订阅的资源发生变更时，即订阅资源发生变更包括订阅资源在属性或者子资源变更时，例如属性的值被修改，子资源被删除，或新创建了子资源等其他可以导致订阅资源发生变更的情况。通过计算获取各订阅资源对应的通知有效时间与当前时间的差值；例如，在资源“myApplication1”下创建子资源“mySubscription1”，设置属性“通知优先级”为1，设置属性“通知有效时间”为2014年5月22日23：59，设置属性“通知优先余量时间”为10分钟；在资源“myApplication2”下创建子资源“mySubscription2”，设置属性“通知优先级”为2，设置属性“通知有效时间”为2014年5月22日23：59，设置属性“通知优先余量时间”为5分钟；在资源“myApplication3”下创建子资源“mySubscription3”，设置属性“通知优先级”为3，设置属性“通知有效时间”为2014年5月24日23：59，设置属性“通知优先余量时间”为10分钟；在资源“myApplication4”下创建子资源“mySubscription4”，设置属性“通知优先级”为4，设置属性“通知有效时间”为2014年5月24日23：59，设
置属性“通知优先余量时间”为10分钟。假如当前时间为当前时间到2014年5月22日23：49分时，那么他们与当前时间的差值分别为10分钟、10分钟、2日10分钟和2日10分钟。
步骤S304：获取差值小于或等于通知优先余量时间的订阅资源；
在该步骤中，具体的根据发生变更的各订阅资源对应的差值先判断该差值是否小于或等于各订阅资源对应的通知优先余量时间，值得注意的是各通知余量时间具体的时间值，根据各订阅资源具体情况进行设置，具体时间值可以相同也可以不同。如果有小于或等于各订阅资源对应的通知优先余量时间，表示该订阅资源对应的通知消息特别紧急，获取这些发送变更的订阅资源中差值小于或等于通知优先余量时间的订阅资源。例如，假如当前时间为当前时间为2014年5月22日23：49分时，那么他们与当前时间的差值分别为10分钟、10分钟、2日10分钟和2日10分钟。并且上述的“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”他们对应的通知优先余量时间分别为10分钟、5分钟、10分钟和10分钟。根据比较可以得知，“myApplication1”满足条件。例如，假如当前时间为当前时间到2014年5月22日23：54分时，那么他们与当前时间的差值分别为5分钟、5分钟、2日5分钟和2日5分钟。并且上述的“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”他们对应的通知优先余量时间分别为10分钟、5分钟、10分钟和10分钟。根据比较可以得知，“myApplication1”和“myApplication2”满足条件。
步骤S305：首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
该步骤中，那么就可以采用插队发送，最先让该订阅资源对应的通知消息发送出去。进一步，如果有多个订阅资源小于或等于各订阅资源对应的通知优先余量时间，那么就根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息，这样不仅能保证优先级高的通知消息能够发送出去，并且能够保证有效期快到的低优先级在有效期到期之前，插队发送，避免了低优先级的通知消息无法被发送的场景。例如，假如当前时间为当前时间为2014年5月22日23：49分时，“myApplication1”满足条件，优先发送资源“myApplication1”的订阅资源“mySubscription1”产生的通知消息。假如当前时间为当前时间到2014年5月22日23：54分时，“myApplication1”和“myApplication2”满足条件，进一步由于“myApplication2”通知优先级比“myApplication1”通知优先级高，那么优先发送资
源“myApplication2”的订阅资源“mySubscription2”产生的通知消息。将“myApplication1”和“myApplication2”的通知消息发送完后，根据通知优先级发送不满足条件的“myApplication3”和“myApplication4”，由于“myApplication4”的通知优先级比“myApplication3”通知优先级高，那么他们中优先发送资源“myApplication4”的订阅资源“mySubscription4”产生的通知消息。
实施例四
本实施例的通知消息的发送方法，如图5所示，包括以下步骤：
步骤S401：应用实体发送至少两个创建订阅请求给公共业务实体，创建订阅请求包括订阅资源对应的通知消息属性的设置信息；
步骤S402：公共业务实体接收创建订阅请求；
步骤S403：公共业务实体根据创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，并根据各创建订阅请求中的设置信息设置各订阅资源对应的通知消息属性；
步骤S404：当至少两个订阅资源发生变更时，公共业务实体根据发生变更的订阅资源对应的通知消息属性发送通知消息给应用实体；
步骤S405：请应用实体接收通知消息。
进一步，在上述步骤S404中，通知消息属性包括通知优先级和通知有效时间时，根据发生变更的订阅资源对应的通知消息属性发送通知消息的步骤包括：
获取发生变更的各订阅资源对应的通知有效时间与当前时间的差值；
根据发生变更的各订阅资源对应的差值和通知优先级发送通知消息。
进一步，在上述步骤S404中，通知消息属性还包括通知优先余量时间，根据发生变更的各订阅资源对应的差值和通知优先级发送通知消息的步骤包括：
获取差值小于或等于通知优先余量时间的订阅资源；
首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
实施例五
为了更详细说明本发明的过程，本实施例结合公共业务实体CSE和应用实体AE包括AE1、AE2、AE3和AE4来进行具体说明。
AE1发送创建资源请求给CSE，创建资源请求中包含：
1)资源名称：“mySubscription1”
2)资源类型：“Subscription”
3)创建到：\\CSEBase\myApplication
4)内容：包括以下参数的名称和值：
通知优先级：设置为1；
通知有效时间：2014年5月22日23：59；
优先余量时间：10分钟；
CSE接收到AE1的创建资源请求后，验证AE1具有创建资源的权限，在资源“myApplication1”下创建子资源“mySubscription1”，设置属性“通知优先级”为1，设置属性“通知有效时间”为2014年5月22日23：59，设置属性“优先余量时间”为10分钟。
AE2发送创建资源请求给CSE，创建资源请求中包含：
1)资源名称：“mySubscription2”
2)资源类型：“Subscription”
3)创建到：\\CSEBase\myApplication
4)内容：包括以下参数的名称和值：
通知优先级：设置为2；
通知有效时间：2014年5月22日23：59；
优先余量时间：5分钟；
CSE接收到AE2的创建资源请求后，验证AE2具有创建资源的权限，在资源“myApplication2”下创建子资源“mySubscription2”，设置属性“通知优先级”为2，设置属性“通知有效时间”为2014年5月22日23：59，设置属性“优先余量时间”为5分钟。
AE3发送创建资源请求给CSE，创建资源请求中包含：
1)资源名称：“mySubscription3”
2)资源类型：“Subscription”
3)创建到：\\CSEBase\myApplication
4)内容：包括以下参数的名称和值：
通知优先级：设置为3；
通知有效时间：2014年5月24日23：59；
优先余量时间：10分钟；
CSE接收到AE3的创建资源请求后，验证AE3具有创建资源的权限，在资源“myApplication3”下创建子资源“mySubscription3”，设置属性“通知优先级”为3，设置属性“通知有效时间”为2014年5月24日23：59，设置属性“优先余量时间”为10分钟。
AE4发送创建资源请求给CSE，创建资源请求中包含：
1)资源名称：“mySubscription4”
2)资源类型：“Subscription”
3)创建到：\\CSEBase\myApplication
4)内容：包括以下参数的名称和值：
通知优先级：设置为4；
通知有效时间：2014年5月24日23：59；
优先余量时间：10分钟；
CSE接收到AE4的创建资源请求后，验证AE4具有创建资源的权限，在资源“myApplication4”下创建子资源“mySubscription4”，设置属性“通知优先级”为4，设置属性“通知有效时间”为2014年5月24日23：59，设置属性“优先余量时间”为10分钟。
此时资源“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”称为被订阅的资源。
规则：优先级4最高，优先级3较高，优先级2其次，优先级1最低；
当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”的属性或子资源发生变更时，CSE根据个资源的订阅资源产生通知消息。
当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”的属性或子资源都发生变更时，优先发送资源“myApplication4”的订阅资源“mySubscription4”产生的通知消息。
当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”的属性或子资源都发生变更时，并且当前时间到2014年5月22日23：49分时，CSE优先发送资源“myApplication1”的订阅资源“mySubscription1”产生的通知消息。
当CSE上的资源“myApplication1”，“myApplication2”，“myApplication3”和“myApplication4”的属性或子资源都发生变更时，并且当前时间到2014年5月22日23：54分时，CSE优先发送资源“myApplication2”的订阅资源“mySubscription2”产生的通知消息。
实施例六
本发明实施例还提供通知消息的发送装置，如图6所示，该发送装置包括资源创建模块、属性设置模块和通知发送模块。其中，资源创建模块设置为在公共业务实体上创建至少两个订阅资源；属性设置模块设置为设置各订阅资源对应的通知消息属性；通知发送模块设置为当至少两个订阅资源发生变更时，根据发生变更的订阅资源对应的通知消息属性发送通知消息。
进一步，通知消息属性包括通知优先级和/或通知有效时间。
本发明实施例还提供另外一种通知消息的发送装置，如图7所示，该发送装置的通知发送模块包括差值获取子模块和通知发送子模块。其中，差值获取子模块设置为获取发生变更的各订阅资源对应的通知有效时间与当前时间的差值；通知发送子模块设置为根据发生变更的各订阅资源对应的差值和通知优先级发送通知消息。
本发明实施例还提供另外一种通知消息的发送装置，如图8所示，该发送装置的通知发送模块还包括判断获取子模块。其中，判断获取子模块设置为获取差值小于或等于通知优先余量时间的订阅资源；发送子模块还设置为首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
本发明实施例还提供另外一种通知消息的发送装置，如图9所示，该发送装置还包括请求接收模块。其中，请求接收模块设置为接收至少两个创建订阅请求；
资源创建模块还设置为根据接收的至少两个创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，创建订阅请求包括订阅资源对应的通知消息属性的设置信息；属性设置模块还设置为根据各创建订阅请求中的设置信息设置各订阅资源对应的通知消息属性。
实施例七
本发明实施例还提供通知消息的发送系统，如图10所示，该发送系统包括应用实体和公共业务实体，应用实体包括请求发送模块和通知接收模块，公共业务实体包括请求接收模块、资源创建模块、属性设置模块和通知发送模块。其中，请求发送模块设置为发送至少两个创建订阅请求给请求接收模块，创建订阅请求包括订阅资源对应的通知消息属性的设置信息；请求接收模块设置为接收创建订阅请求；资源创建模块设置为根据创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源；属性设置模块设置为根据各创建订阅请求中的设置信息设置各订阅资源对应的通
知消息属性；通知发送模块设置为当至少两个订阅资源发生变更时，根据发生变更的订阅资源对应的通知消息属性发送通知消息给通知接收模块；通知接收模块设置为接收通知消息。
本发明实施例通过增加通知消息相关的参数来控制通知消息的发送，使得终端包括应用实体和公共业务实体可以根据自己的需求为不同的订阅资源设置不同的优先级，使得CSE在发送通知消息的时候根据优先级进行发送，由此可以使得在产生大量通知消息时，高优先级的通知消息可以优先发送，避免高优先级的通知消息由于网络拥塞而不能发送，同时也控制有效期快到的低优先级在有效期到期之前，插队发送，避免了低优先级的通知消息无法被发送的场景。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，上述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本发明实施例不限制于任何特定形式的硬件和软件的结合。
以上实施例仅用以说明本发明实施例的技术方案而非限制，仅仅参照较佳实施例对本发明进行了详细说明。本领域的普通技术人员应当理解，可以对本发明实施例的技术方案进行修改或者等同替换，而不脱离本发明技术方案的精神和范围，均应涵盖在本发明的权利要求范围当中。
如上所述，本发明实施例提供的一种通知消息的发送方法、装置和系统具有以下有益效果：可以根据订阅资源对应的通知消息的重要程度和紧急程度进行通知消息的发送，让重要程度高的通知消息或者紧急程度高先发送出去，避免的重要通知消息或紧急程度高的通知消息无法发送出去的问题，提供的通知消息的发送效率，增加了用户体验度。
Claims (14)
- 一种通知消息的发送方法，在公共业务实体上创建至少两个订阅资源；设置各所述订阅资源对应的通知消息属性；当至少两个所述订阅资源发生变更时，根据发生变更的所述订阅资源对应的通知消息属性发送通知消息。
- 如权利要求1所述通知消息的发送方法，其中，所述通知消息属性包括通知优先级和/或通知有效时间。
- 如权利要求2所述通知消息的发送方法，其中，所述通知消息属性包括通知优先级和通知有效时间时，所述根据发生变更的所述订阅资源对应的通知消息属性发送通知消息的步骤包括：获取发生变更的各所述订阅资源对应的通知有效时间与当前时间的差值；根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息。
- 如权利要求3所述通知消息的发送方法，所述通知消息属性还包括通知优先余量时间，所述根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息的步骤包括：获取差值小于或等于通知优先余量时间的订阅资源；首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
- 如权利要求1至4中任一项所述通知消息的发送方法，其中，所述在公共业务实体上创建至少两个订阅资源的步骤包括：根据接收的至少两个创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；所述设置各所述订阅资源对应的通知消息属性的步骤包括：根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性。
- 一种通知消息的发送方法，包括如下步骤：应用实体发送至少两个创建订阅请求给公共业务实体，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；所述公共业务实体接收所述创建订阅请求；所述公共业务实体根据所述创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，并根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性；当至少两个所述订阅资源发生变更时，所述公共业务实体根据发生变更的所述订阅资源对应的通知消息属性发送通知消息给所述应用实体；所述请应用实体接收所述通知消息。
- 如权利要求6所述通知消息的发送方法，其中，所述通知消息属性包括通知优先级和通知有效时间时，所述根据发生变更的所述订阅资源对应的通知消息属性发送通知消息的步骤包括：获取发生变更的各所述订阅资源对应的通知有效时间与当前时间的差值；根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息。
- 如权利要求7所述通知消息的发送方法，所述通知消息属性还包括通知优先余量时间，所述根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息的步骤包括：获取差值小于或等于通知优先余量时间的订阅资源；首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
- 一种通知消息的发送装置，所述发送装置包括资源创建模块、属性设置模块和通知发送模块：所述资源创建模块设置为在公共业务实体上创建至少两个订阅资源；所述属性设置模块设置为设置各所述订阅资源对应的通知消息属性；所述通知发送模块设置为当至少两个所述订阅资源发生变更时，根据发生变更的所述订阅资源对应的通知消息属性发送通知消息。
- 如权利要求9所述通知消息的发送装置，其中，所述通知消息属性包括通知优先级和/或通知有效时间。
- 如权利要求10所述通知消息的发送装置，其中，所述通知发送模块包括差值获取子模块和通知发送子模块：所述差值获取子模块设置为获取发生变更的各所述订阅资源对应的通知有效时间与当前时间的差值；所述通知发送子模块设置为根据发生变更的各所述订阅资源对应的差值和通知优先级发送通知消息。
- 如权利要求11所述通知消息的发送装置，其中，所述通知发送模块还包括判断获取子模块：所述判断获取子模块设置为获取差值小于或等于通知优先余量时间的订阅资源；所述发送子模块还设置为首先根据获取的订阅资源对应的通知优先级发送获取的订阅资源对应的通知消息；然后，根据剩余发生变更的订阅资源对应的通知优先级发送剩余发生变更的订阅资源对应的通知消息。
- 如权利要求9至12中任一项所述通知消息的发送装置，其中，所述装置还包括请求接收模块：所述请求接收模块设置为接收至少两个创建订阅请求；所述资源创建模块还设置为根据接收的至少两个创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；所述属性设置模块还设置为根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性。
- 一种通知消息的发送系统，所述发送系统包括应用实体和公共业务实体，所述应用实体包括请求发送模块和通知接收模块，所述公共业务实体包括请求接收模块、资源创建模块、属性设置模块和通知发送模块：所述请求发送模块设置为发送至少两个创建订阅请求给所述请求接收模块，所述创建订阅请求包括订阅资源对应的通知消息属性的设置信息；所述请求接收模块设置为接收所述创建订阅请求；所述资源创建模块设置为根据所述创建订阅请求创建至少两个订阅资源，一个创建订阅请求创建一个订阅资源；所述属性设置模块设置为根据各创建订阅请求中的设置信息设置各所述订阅资源对应的通知消息属性；所述通知发送模块设置为当至少两个所述订阅资源发生变更时，根据发生变更的所述订阅资源对应的通知消息属性发送通知消息给所述通知接收模块；通知接收模块设置为接收所述通知消息。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410344883.8 | 2014-07-18 | ||
| CN201410344883.8A CN105263163B (zh) | 2014-07-18 | 2014-07-18 | 一种通知消息的发送方法、装置和系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2015117342A1 true WO2015117342A1 (zh) | 2015-08-13 |
Family
ID=53777169
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2014/087616 WO2015117342A1 (zh) | 2014-07-18 | 2014-09-26 | 一种通知消息的发送方法、装置和系统 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105263163B (zh) |
| WO (1) | WO2015117342A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111436027A (zh) * | 2019-01-14 | 2020-07-21 | 京东方科技集团股份有限公司 | 事件订阅通知方法、服务器、物联网系统和存储介质 |
| WO2021083075A1 (zh) * | 2019-11-01 | 2021-05-06 | 华为技术有限公司 | 用于订阅事件流的方法和装置 |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107395689A (zh) * | 2017-06-28 | 2017-11-24 | 湖南统科技有限公司 | 消防信息的分类推送方法及系统 |
| CN107770754A (zh) * | 2017-10-23 | 2018-03-06 | 中兴通讯股份有限公司 | 一种通知发送方法、装置和系统 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102377686A (zh) * | 2010-08-10 | 2012-03-14 | 阿里巴巴集团控股有限公司 | 一种消息订阅系统、消息订阅方法及装置 |
| WO2013155328A1 (en) * | 2012-04-12 | 2013-10-17 | Qualcomm Incorporated | Broadcast content via over the top delivery |
| CN103581307A (zh) * | 2013-10-17 | 2014-02-12 | 北京邮电大学 | 一种基于集群的发布/订阅系统及其可靠性保障方法 |
| CN103618800A (zh) * | 2013-12-05 | 2014-03-05 | 华为技术有限公司 | 订阅通知的实现方法和装置 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2869505C (en) * | 2012-05-14 | 2020-09-29 | Huawei Technologies Co., Ltd. | Method and system for group communication, group server, and group member device |
| CN103596117B (zh) * | 2012-08-13 | 2017-12-15 | 华为终端（东莞）有限公司 | 发现机器对机器业务的方法、设备及系统 |
| CN103596118B (zh) * | 2012-08-13 | 2017-06-20 | 华为终端有限公司 | 发现机器对机器业务的方法、设备及系统 |
-
2014
- 2014-07-18 CN CN201410344883.8A patent/CN105263163B/zh not_active Expired - Fee Related
- 2014-09-26 WO PCT/CN2014/087616 patent/WO2015117342A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102377686A (zh) * | 2010-08-10 | 2012-03-14 | 阿里巴巴集团控股有限公司 | 一种消息订阅系统、消息订阅方法及装置 |
| WO2013155328A1 (en) * | 2012-04-12 | 2013-10-17 | Qualcomm Incorporated | Broadcast content via over the top delivery |
| CN103581307A (zh) * | 2013-10-17 | 2014-02-12 | 北京邮电大学 | 一种基于集群的发布/订阅系统及其可靠性保障方法 |
| CN103618800A (zh) * | 2013-12-05 | 2014-03-05 | 华为技术有限公司 | 订阅通知的实现方法和装置 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111436027A (zh) * | 2019-01-14 | 2020-07-21 | 京东方科技集团股份有限公司 | 事件订阅通知方法、服务器、物联网系统和存储介质 |
| WO2021083075A1 (zh) * | 2019-11-01 | 2021-05-06 | 华为技术有限公司 | 用于订阅事件流的方法和装置 |
| US11863368B2 (en) | 2019-11-01 | 2024-01-02 | Huawei Technologies Co., Ltd. | Method and apparatus for subscribing to event streams |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105263163B (zh) | 2019-01-15 |
| CN105263163A (zh) | 2016-01-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10609533B2 (en) | Method and device for trigger management of a common service entity (CSE) and a network element of bearer network | |
| WO2015188440A1 (zh) | 资源订阅处理方法及装置 | |
| CN107113596B (zh) | 在多个物理和虚拟sim卡上提供服务许可聚合的系统和方法 | |
| WO2016173280A1 (zh) | 监控管理方法及装置 | |
| WO2020220783A1 (zh) | 一种代理订阅的授权方法及装置 | |
| WO2016054888A1 (zh) | 一种创建订阅资源的方法和装置 | |
| WO2015176365A1 (zh) | 通知消息的发送方法、装置及计算机存储介质 | |
| WO2015117342A1 (zh) | 一种通知消息的发送方法、装置和系统 | |
| WO2020238411A1 (en) | Method and apparatus for network exposure function discovery and selection | |
| WO2016184178A1 (zh) | 资源的控制方法和装置 | |
| EP3062544B1 (en) | Method, node and system for managing resources of machine type communication application | |
| US20240098631A1 (en) | Filters for bulk subscriptions | |
| WO2015192466A1 (zh) | 一种通知消息发送方法及装置、计算机存储介质 | |
| WO2015117446A1 (zh) | 控制资源变更通知消息发送方法及装置 | |
| WO2015168974A1 (zh) | 资源的创建方法及装置 | |
| WO2015154459A1 (zh) | 订阅资源变更通知的方法及装置 | |
| WO2016197783A2 (zh) | 控制消息的发送方法及装置 | |
| US11700189B2 (en) | Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing | |
| WO2016180223A1 (zh) | 一种无线通信设备的管理方法及无线通信设备 | |
| EP3148133B1 (en) | Load control method and apparatus for notification messages | |
| WO2016082492A1 (zh) | 一种原始资源通告的方法及相应的节点 | |
| US10659938B2 (en) | Registration method and communication method for application dedicated node (ADN), and nodes | |
| CN107113597B (zh) | 在多个设备sim卡上提供服务许可聚合的系统和方法 | |
| CN106714199B (zh) | 获取承载网的网络状态信息的方法及装置 | |
| WO2016090933A1 (zh) | 应用通告资源的创建方法及装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14881527 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 14881527 Country of ref document: EP Kind code of ref document: A1 |