WO2015081786A1 - 订阅通知的实现方法和装置 - Google Patents

订阅通知的实现方法和装置 Download PDF

Info

Publication number
WO2015081786A1
WO2015081786A1 PCT/CN2014/091492 CN2014091492W WO2015081786A1 WO 2015081786 A1 WO2015081786 A1 WO 2015081786A1 CN 2014091492 W CN2014091492 W CN 2014091492W WO 2015081786 A1 WO2015081786 A1 WO 2015081786A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
notification message
latest
subscription
notification
Prior art date
Application number
PCT/CN2014/091492
Other languages
English (en)
French (fr)
Inventor
肖芳英
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2016527381A priority Critical patent/JP6275837B2/ja
Priority to EP14867548.1A priority patent/EP3043530B1/en
Priority to KR1020167010322A priority patent/KR101806257B1/ko
Priority to AU2014359963A priority patent/AU2014359963B2/en
Publication of WO2015081786A1 publication Critical patent/WO2015081786A1/zh
Priority to US15/090,401 priority patent/US20160219125A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/827—Aggregation of resource allocation or reservation requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H04L67/5651—Reducing the amount or size of exchanged application data
    • 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]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications

Definitions

  • the present invention relates to the field of Machine-to-Machine Communications (M2M) technology, and in particular, to a method and an apparatus for implementing subscription notification.
  • M2M Machine-to-Machine Communications
  • Machine-to-Machine Communications is a networked application and service centered on machine intelligence interaction. It embeds wireless or wired communication modules and application processing logic inside the machine to realize data communication without manual intervention to meet the information needs of users for monitoring, command and dispatch, data acquisition and measurement.
  • FIG. 1 is a typical M2M system architecture.
  • various terminals such as sensors
  • various applications such as power meter reading, intelligent transportation, etc.
  • the gateway and the platform are both Common Service Entities (CSE).
  • CSE Common Service Entities
  • the application on the terminal can be registered to the gateway connected to the terminal. All gateways need to be registered to the service platform.
  • the CSE receiving the registration is called the local CSE.
  • the local CSE of application 1 in FIG. 1 is gateway A
  • the local CSE of application 2 is gateway B
  • the local CSE of gateways A and B is a service platform.
  • the application 2 on the terminal b wishes to continuously understand the state change of the application 1 on the other terminal a, but does not want to frequently query the application 1.
  • TS102 690 and TS 102 921 developed by the European Telecommunications Standards Institute (ETSI)
  • ETSI European Telecommunications Standards Institute
  • a subscription notification mechanism is provided. That is, the application 2 subscribes to the registration resource of the application 1 on its local CSE (ie, gateway A); when the application 1 changes, it goes to its local CSE, ie, the network.
  • the gateway A updates the registered resource status, and the gateway A sends a notification message to the application 2 according to the status update of the registered resource.
  • the application 2 is called a subscriber, and the registration resource of the application 1 on its local CSE is called a subscribed resource, and the CSE where the subscribed resource is located is called a hosting public service entity (Hosting CSE).
  • the Hosting CSE will create a subscription resource based on the subscription request of the subscriber (ie, Application 2), and the subscription resource is used to describe the subscription relationship.
  • the specific content of the subscription resource may include: a subscribed resource identifier, a notification sending address, and optionally, a subscription condition. At the same time, the relationship between the subscribed resource and the subscribed resource is saved in the subscribed resource.
  • the notification message reported by the gateway A is forwarded to the gateway B through the other CSEs.
  • the notification message is forwarded to the gateway B through a CSE (that is, the service platform).
  • the platform determines that if it is a non-emergency message, it caches it locally.
  • the service platform establishes a connection with the gateway B, and sends the cached message together.
  • the mechanism for receiving messages from other CSEs and forwarding them to another CSE after being cached locally for a period of time is called a Store and Forward (SAF) mechanism, and the CSE of the store-and-forward mechanism is executed during the message transmission process.
  • SAF Store and Forward
  • the CSE of the store-and-forward mechanism is executed during the message transmission process.
  • the time that the message is buffered at the intermediate node is called the store-and-forward delay.
  • the application 1 is used to generate weather information
  • the application 2 is used to provide a life reminder for the user according to the weather
  • the weather change information needs to be known in real time, so the application 1 is subscribed, thereby creating the subscription resource 1.
  • the weather department gateway A sends a notification message to the application 2 according to the subscription resource 1. Since the notification about the weather change belongs to the non-emergency notification message, when the notification message arrives at the service platform, the service platform caches the notification message according to the store-and-forward policy.
  • the service platform will receive the gateway A to the new notification message sent to the application 2 according to the subscription resource 1.
  • the two notification messages may reach the application 2 in one connection, that is, the subscriber may receive the same subscription in one connection. Read multiple notification messages sent by the resource.
  • Application 2 only cares about the latest weather information, so the notification message sent earlier is invalid, resulting in wasted network resources and subscriber computing resources.
  • the method and apparatus for implementing the subscription notification provided by the embodiment of the present invention can avoid waste of network resources and computing resources because a plurality of notification messages sent according to the same subscription resource are simultaneously sent to the subscriber in one connection.
  • the hosting public service entity hosting CSE that implements the subscription notification provided by the embodiment of the present invention includes: a receiving unit, configured to receive a subscription subscription resource request of the subscriber, where the creation subscription resource request includes a unique identifier of the subscribed resource a resource creation unit, configured to create a subscription resource according to the request for creating a subscription resource received by the receiving unit, and a determining unit, configured to determine that the subscriber needs to obtain an latest state of the subscribed resource; After the determining unit determines that the subscriber needs to obtain the latest state of the subscribed resource, allocate a latest state identifier to the subscription resource created by the resource creation unit, where the latest state identifier is used to indicate The subscriber needs to obtain the latest state of the subscribed resource; the generating unit is configured to generate a notification message according to the subscription resource created by the resource creation unit when the status of the subscribed resource is updated, the notification The message includes a status of the updated subscribed resource and the allocation unit The latest state identifier, so that after the intermediate no
  • the determining unit configured to determine that the subscriber needs to obtain the latest state of the subscribed resource, specifically includes: the determining unit, according to the determining The indication information included in the create subscription resource request determines that the subscriber needs to obtain the latest status of the subscribed resource.
  • the determining unit is configured to determine the subscription
  • the determining, by the determining unit, the determining unit is configured to determine, according to the locally saved indication information included in the subscriber-related policy information, that the subscriber needs to obtain State the latest status of the subscribed resource.
  • the intermediate node that implements the subscription notification includes: a receiving unit, configured to receive a notification message, where the notification message includes a status of the updated subscribed resource; and a determining unit, configured to determine the The notification message received by the receiving unit includes a latest status identifier, a saving unit, configured to save the notification message received by the receiving unit, and a determining unit, configured to determine a locally saved notification message generated according to the subscription resource.
  • the latest notification message; the sending unit is configured to send only the latest notification message when the message sending condition is met according to the latest status identifier.
  • the intermediate node further includes a searching unit, configured to find that other notification messages are locally saved, and the other notification messages and the notification message are based on the same subscription resource.
  • the saving unit is configured to save the notification message that is received by the receiving unit, where the saving unit is configured to replace the notification message received by the receiving unit with the searching unit.
  • the determining unit is further configured to: the determining unit is further configured to determine that the latest notification message in the notification message generated according to the subscription resource that is locally saved is specifically: the determining unit is further used The notification message generated according to the subscription resource saved locally is determined to be the latest notification message.
  • the intermediate node further includes a searching unit, configured to find that other notification messages are locally saved, and the other notification messages and the notification message are based on the same subscription resource.
  • the determining unit is further configured to determine that the latest notification message in the notification message generated according to the subscription resource that is locally saved is specifically: the determining unit is further configured to determine the locally saved notification message and the searching The latest notification message among the other notification messages that the unit finds.
  • the latest state identifier is a globally unique identifier for identifying the subscription resource;
  • the searching unit is configured to find that other notification messages are saved locally, and the other notification messages and the notification messages are generated according to the same subscription resource: the searching unit is configured to find other locally saved notification messages.
  • the notification message received by the receiving unit is the same as the latest status identifier included in the other notification message.
  • the latest status identifier is used to identify the subscription resource and is unique on the hosting public service entity hosting CSE
  • the locating unit is configured to find that other notification messages are saved locally, and the other notification messages and the notification messages are generated according to the same subscription resource: the searching unit is configured to find the local The other notification message that is saved, the notification message received by the receiving unit and the latest status identifier and the message sending source address included in the other notification message are the same.
  • the searching unit is configured to find that other notification messages are saved locally, the other notification messages and the The notification message is generated according to the same subscription resource: the searching unit is configured to search for other notification messages saved locally, and the notification message received by the receiving unit and the subscription resource included in the other notification message
  • the Universal Resource Identifier (URI) is the same.
  • the method for implementing the subscription notification includes: receiving a subscription subscription resource request of the subscriber, where the creation subscription resource request includes a unique identifier of the subscribed resource; and creating a subscription resource according to the creating the subscription request.
  • the latest notification message generated according to the subscription resource is only sent to the subscriber when the message is sent.
  • the determining that the subscriber needs to obtain the latest state of the subscribed resource is specifically: determining, according to the indication information included in the creating a subscription resource request What the subscriber needs to obtain is the latest status of the subscribed resource.
  • the determining, by the subscriber, that the subscribed resource needs to obtain the latest state of the subscribed resource is specifically: according to the locally saved policy information related to the subscriber The indication information determines that the subscriber needs to obtain the latest status of the subscribed resource.
  • the method for implementing the subscription notification includes: receiving a notification message, where the notification message includes an updated status of the subscribed resource, determining that the notification message includes an latest status identifier; and saving the receiving a notification message to the destination; determining a latest notification message in the locally saved notification message generated according to the subscription resource; and according to the latest status identifier, only sending the latest notification message when the message transmission condition is met.
  • the saving the received notification message specifically includes: after finding that other notification messages are locally saved, the other notification messages and the notification message are according to the same And generating, by the subscription resource, the received notification message is saved to the local device in a manner of replacing the other notification message; and determining the latest notification message in the locally saved notification message generated according to the subscription resource specifically includes: determining local The saved notification message generated according to the subscription resource is the latest notification message.
  • the determining, by the locally saved, the latest notification message in the notification message generated according to the subscription resource specifically includes: after finding that other notification messages are locally saved, the other notification message And the notification message is generated according to the same subscription resource, and determines the locally saved notification message and the latest notification message of the other notification messages.
  • the latest status identifier is a globally unique identifier for identifying the subscription resource; the lookup saves other notification messages locally, and the other notification messages and the notification message are based on the same subscription resource.
  • the generated specificity is: finding other locally saved notification messages, and the notification messages and the other notification messages contain the same latest status identifier.
  • the latest state identifier is used to identify the subscription resource and is unique on the hosting public service entity hosting CSE
  • the identifier is stored locally, and the other notification message is saved locally, and the other notification message and the notification message are generated according to the same subscription resource: searching for other locally saved notification messages, the notification message and the The other status messages included in the other notification messages are the same as the source address of the message.
  • the searching for the local saves another notification message, where the other notification message and the notification message are based on the same
  • the subscription resource is generated by: finding another locally saved notification message, and the notification message and the other notification message contain the same subscription resource universal resource identifier (URI).
  • URI subscription resource universal resource identifier
  • the technical solution provided by the embodiment of the present invention can be used to create a subscription resource request according to the subscription creation request, and create a subscription resource according to the creation subscription request; and determine that the subscriber needs to obtain the subscribed resource.
  • a latest state the latest status identifier is allocated to the created subscription resource; when the status of the subscribed resource is updated, a notification message is generated according to the subscription resource and sent to the intermediate node, where the notification message includes the latest status
  • the intermediate node receives the notification message, sending only the latest notification message generated according to the subscription resource to the subscriber according to the latest state identifier.
  • FIG. 1 is a schematic structural diagram of a prior art M2M system
  • FIG. 2 is a structural diagram of a system for implementing subscription notification according to an embodiment of the present invention
  • FIG. 3 is a structural diagram of a Hosting CSE implementing subscription notification according to an embodiment of the present invention
  • FIG. 4 is a structural diagram of an intermediate node for implementing subscription notification according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for implementing a subscription notification according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for implementing a subscription notification according to another embodiment of the present invention.
  • FIG. 7 is a flowchart of implementing signaling of subscription notification according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of implementing signaling of a subscription notification according to another embodiment of the present invention.
  • FIG. 9 is a structural diagram of a Hosting CSE based on a computer system according to an embodiment of the present invention.
  • FIG. 10 is a structural diagram of an intermediate node based on a computer system according to an embodiment of the present invention.
  • the embodiment of the present invention provides a system for implementing a subscription notification.
  • the implementation system 200 for the subscription notification includes:
  • the hosting public service entity hosting CSE 201 is configured to receive a subscriber's create subscription resource request, where the create subscription resource request includes a unique identifier of the subscribed resource; create a subscription resource according to the create subscription request; and determine the subscriber needs Obtaining the latest status of the subscribed resource,
  • the created subscription resource is configured with an latest status identifier, where the latest status identifier is used to indicate that the subscriber needs to obtain the latest status of the subscribed resource; when the status of the subscribed resource is updated, according to the
  • the subscription resource generation notification message is sent to the intermediate node, and the notification message includes the status of the updated subscribed resource and the latest status identifier, so that after the intermediate node receives the notification message,
  • the latest status identifier sends only the latest notification message generated according to the subscription resource to the subscriber when the message sending condition is satisfied; and
  • the intermediate node 202 is configured to receive a notification message, where the notification message includes a status of the updated subscribed resource, determine that the notification message includes a latest status identifier, save the received notification message, and determine a locally saved subscription according to the subscription.
  • the intermediate nodes in the subscription notification implementation system 200 may have one or more, that is, the intermediate nodes may be connected to other intermediate nodes, and they perform the same operations in the subscription notification implementation process of the present invention.
  • An embodiment of the present invention provides a hosting public service entity Hosting CSE for implementing subscription notification.
  • the Hosting CSE 300 includes:
  • the receiving unit 301 is configured to receive a subscription subscription resource request of the subscriber, where the create subscription resource request includes a unique identifier of the subscribed resource.
  • a resource creation unit 302 configured to create a subscription resource according to the request for creating a subscription resource received by the receiving unit 301;
  • the determining unit 303 is configured to determine that the subscriber needs to obtain the latest state of the subscribed resource
  • the allocating unit 304 is configured to allocate, after the determining unit 303, that the subscriber needs to obtain the latest state of the subscribed resource, to allocate the latest state identifier to the subscription resource created by the resource creating unit 302, the latest The status identifier is used to indicate that the subscriber needs to obtain the subscribed resource.
  • Latest state of affairs
  • a generating unit 305 configured to: when the status of the subscribed resource is updated, generate a notification message according to the subscription resource created by the resource creation unit, where the notification message includes a status of the updated subscribed resource and the The latest status identifier allocated by the allocation unit, so that after the intermediate node receives the notification message, according to the latest status identifier, only the latest notification message generated according to the subscription resource is sent to the subscriber when the message sending condition is met;
  • the sending unit 306 is configured to send the notification message generated by the generating unit 305 to the intermediate node.
  • the determining unit 303 is configured to determine that the subscriber needs to obtain the latest state of the subscribed resource, and the determining unit 303 is configured to determine, according to the indication information included in the create a subscription resource request, What the subscriber needs to get is the latest status of the subscribed resource.
  • the determining unit 303 is configured to determine that the subscriber needs to obtain the latest state of the subscribed resource, where the determining unit 303 is configured to: according to the locally saved policy information related to the subscriber, The indication information determines that the subscriber needs to obtain the latest status of the subscribed resource.
  • the allocating unit 304 is configured to: after the determining unit determines that the subscriber needs to acquire the latest state of the subscribed resource, allocate a latest state identifier to the subscription resource created by the resource creating unit, The latest status identifier is used to indicate that the subscriber needs to obtain the latest status of the subscribed resource.
  • the method further includes: the latest status identifier is a globally unique identifier for identifying the subscription resource.
  • the allocating unit 304 is configured to: after the determining unit determines that the subscriber needs to acquire the latest state of the subscribed resource, allocate a latest state identifier to the subscription resource created by the resource creating unit, The latest status identifier is used to indicate that the subscriber needs to obtain the latest status of the subscribed resource.
  • the method further includes: the latest status identifier is a unique identifier for identifying the subscription resource and hosted on the hosting public service entity. logo.
  • the allocating unit 304 is configured to: after the determining unit determines that the subscriber needs to obtain the latest state of the subscribed resource, allocate a latest state, the latest state, to the subscription resource created by the resource creating unit.
  • the status identifier is used to indicate that the subscriber needs to obtain the latest status of the subscribed resource, and further includes: all subscription resources have the same latest status identifier.
  • the sending, by the sending unit 306, the sending the notification message generated by the generating unit to the intermediate node specifically includes: the sending unit 306, configured to directly encapsulate the notification message generated by the generating unit 305 in an HTTP message.
  • the sending unit 306, configured to directly encapsulate the notification message generated by the generating unit 305 in an HTTP message.
  • the resource expression is encapsulated in a Restful message and sent to the intermediate node.
  • An embodiment of the present invention provides an intermediate node for implementing subscription notification.
  • the intermediate node 400 includes:
  • the receiving unit 401 is configured to receive a notification message, where the notification message includes a status of the updated subscribed resource.
  • a determining unit 402 configured to determine that the notification message received by the receiving unit 401 includes a latest status identifier
  • a saving unit 404 configured to save the notification message received by the receiving unit 401;
  • the determining unit 402 is further configured to determine a latest notification message in the locally saved notification message generated according to the subscription resource;
  • the sending unit 405 is configured to send only the latest notification message when the message sending condition is met according to the latest state identifier.
  • the intermediate node 400 further includes a searching unit 403, configured to find that other notification messages are locally saved, and the other notification messages and the notification message received by the receiving unit 401 are generated according to the same subscription resource.
  • the saving unit 404 configured to save the notification message received by the receiving unit 401, specifically: the saving unit 404, configured to receive the received by the receiving unit 401
  • the notification message is saved to the local device in a manner of replacing the other notification message that is found by the searching unit 403.
  • the determining unit 402 is further configured to determine a latest notification message in the locally saved notification message generated according to the subscription resource. Specifically, the determining unit 402 is further configured to determine that the locally saved notification message generated according to the subscription resource is the latest notification message.
  • the intermediate node 400 further includes a searching unit 403, configured to find that other notification messages are locally saved, and the other notification messages and the notification message received by the receiving unit 401 are generated according to the same subscription resource;
  • the determining unit 402 is further configured to determine that the latest notification message in the notification message generated according to the subscription resource that is locally saved is specifically: the determining unit 402 is further configured to determine the locally saved notification message and the searching unit 403 The latest notification message among the other notification messages found.
  • the latest status identifier is a globally unique identifier for identifying the subscription resource
  • the searching unit 403 is configured to find that other notification messages are saved locally, the other notification message and the notification.
  • the message is generated according to the same subscription resource.
  • the search unit 403 is configured to search for other notification messages that are saved locally, and the notification message received by the receiving unit 401 and the latest information included in the other notification message.
  • the status ID is the same.
  • the latest status identifier is an identifier that is used to identify the subscription resource and is unique on the hosting public service entity hosting CSE;
  • the searching unit 403 is configured to find that other notification messages are locally saved, The other notification message and the notification message are generated according to the same subscription resource.
  • the searching unit 403 is configured to search for other notification messages that are saved locally, and the notification message and the received by the receiving unit 401.
  • the other status messages included in the other notification messages are the same as the source address of the message.
  • the searching unit 403 is configured to find that other notification messages are saved locally, where the other notification messages and the notification messages are generated according to the same subscription resource: the searching unit 403 is configured to: Finding other locally saved notification messages, the notification message received by the receiving unit 401 and the subscription resource universal resource identifier (Universal) included in the other notification message Resource Identifier, URI) is the same.
  • the searching unit 403 is configured to: Finding other locally saved notification messages, the notification message received by the receiving unit 401 and the subscription resource universal resource identifier (Universal) included in the other notification message Resource Identifier, URI) is the same.
  • Universal universal resource identifier
  • the M2M service platform can be a computer, a device with a processor.
  • M2M gateways and M2M terminals.
  • devices that make gateways can also be used as terminals.
  • various terminal devices such as mobile phones, computers, PDAs, notebook computers, remote controllers, household appliances, and various Instrumentation, sensors, etc. can be used as gateways or terminals for M2M networks.
  • each module included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding function can be implemented; in addition, the specific names of the functional modules are only for convenience. They are distinguished from each other and are not intended to limit the scope of protection of the present invention.
  • the embodiment of the present invention provides a method for implementing a subscription notification, which is applied to a hosted public service entity Hosting CSE that deploys a subscribed resource.
  • the method includes:
  • Step 501 Receive a subscription subscription resource request of the subscriber, where the create subscription resource request includes a unique identifier of the subscribed resource.
  • Step 502 Create a subscription resource according to the create subscription request.
  • Step 503 Determine that the subscriber needs to obtain the latest state of the subscribed resource, and allocate the latest state identifier to the created subscription resource, where the latest state identifier is used to indicate that the subscriber needs to obtain the State the latest status of the subscribed resource.
  • determining that the subscriber needs to obtain the latest state of the subscribed resource may be: determining, according to the indication information included in the create subscription resource request, that the subscriber needs to obtain the subscribed resource. The latest state, or determining, according to the locally saved indication information included in the subscriber-related policy information, that the subscriber needs to obtain the latest state of the subscribed resource.
  • the latest status identifier may be a globally unique identifier for identifying the subscription resource, or the latest status identifier may be one for identifying the subscription resource and being hosted.
  • the public service entity hosts a unique identifier on the CSE, or all subscription resources have the same latest status identifier.
  • Step 504 When the status of the subscribed resource is updated, generate a notification message according to the subscription resource and send the notification message to the intermediate node, where the notification message includes the status of the updated subscribed resource and the latest status identifier. After the intermediate node receives the notification message, according to the latest state identifier, only the latest notification message generated according to the subscription resource is sent to the subscriber when the message sending condition is met.
  • generating the notification message according to the subscription resource and sending the notification message to the intermediate node may be: generating a notification message according to the subscription resource, and directly encapsulating the notification message in an HTTP message, sending the message to the intermediate node, or according to the notification
  • the message generates a resource representation of the store-and-forward resource, and the resource expression is encapsulated in a Restful message and sent to the intermediate node.
  • Another embodiment of the present invention provides a method for implementing a subscription notification, which is applied to an intermediate node that forwards a notification message.
  • the method includes:
  • Step 601 Receive a notification message, where the notification message includes a status of the updated subscribed resource, and determine that the notification message includes a latest status identifier.
  • Step 602 Save the received notification message.
  • Step 603 Determine a latest notification message in the locally saved notification message generated according to the subscription resource.
  • the saving the received notification message in step 602 specifically includes: after finding that other notification messages are saved locally, the other notification messages and the notification message are generated according to the same subscription resource, and the The received notification message is saved locally to replace the other notification message.
  • the step is specifically: determining that the locally saved notification message generated according to the subscription resource is the latest notification message.
  • the step is specifically: after finding that other notification messages are saved locally, the other The notification message and the notification message are generated according to the same subscription resource, and determine the locally saved notification message and the latest notification message among the other notification messages.
  • the latest status identifier is specifically a globally unique identifier for identifying the subscription resource, and the search saves other notification messages locally, and the other notification messages and the notification message are based on the same subscription resource.
  • the generated specific information is: finding another locally saved notification message, where the notification message and the other notification message contain the same latest status identifier; or the latest status identifier is specifically used to identify the subscription resource and
  • the hosted public service entity hosts a unique identifier on the CSE, and the search saves other notification messages locally, and the other notification messages and the notification message are generated according to the same subscription resource: finding other notifications saved locally a message, the latest status identifier and the message sending source address included in the notification message and the other notification message are the same; or, the finding is stored locally with other notification messages, and the other notification messages and the notification message are the same according to the same
  • the subscription resource is generated by: finding the locally saved He notification message, the notification message and the notification message subscription resource contains additional universal resource identifier (Universal Resource Identifier, URI) the
  • Step 604 According to the latest status identifier, only the latest notification message is sent when the message sending condition is met.
  • the method further includes deleting the locally saved notification message generated according to the subscription resource.
  • the embodiment of the present invention provides a signaling flowchart for implementing subscription notification, which is shown in FIG. 7.
  • App1 registers with its local CSE, which creates a registration resource for App1, assigns an ID to the registered resource, then generates a URI of the registered resource, and returns the registered resource URI to App1.
  • the registered resource ID is a globally unique string, such as application1
  • the registered resource URI is composed of a registered resource ID and a URI of the local CSE. Therefore, the registration resource URI is also a globally unique string, and both the registration resource ID and the registration resource URI can be unique to the registered resource.
  • logo For example, in this embodiment, the local CSE URI of App1 is http://example.com/gateway1, and the registered resource URI is http://example.com/gateway1/application1.
  • App1 sets the access rights of the registered resource after the registration process or registration, and allows other users including App2 to access and subscribe to the registered resource.
  • the local CSE is called Hosting CSE of App1. Therefore, when App2 accesses the Hosting CSE, the registration resource of App1 on the Hosting CSE can be found, and the registered resource is subscribed after obtaining the unique identifier of the registered resource, and the subscriber App2 wants to receive the registration each time. The latest status of the resource.
  • the specific implementation process is as follows:
  • Step 701 The subscriber App2 sends a create subscription resource request to its own registration gateway CSE2, where the create subscription resource request includes a unique identifier of the subscribed resource and a unique identifier of the subscriber App2.
  • the subscribed resource is the registration resource of App1 on the Hosting CSE. Therefore, the unique identifier of the subscribed resource is the unique identifier of the registered resource of App1 on the Hosting CSE.
  • the subscription subscription resource request may further include a subscription condition.
  • App2 includes indication information in the request to create a subscription resource to indicate that the subscriber needs to obtain the latest state of the subscribed resource; or App2 accesses the setting system of the M2M service provider in advance, in the configuration policy information. Adding the indication information; or App2 agrees that App2 only obtains the latest status information of the subscribed resource when the contract is signed with the M2M service provider, and the M2M service provider adds the indication information to the configuration policy information; or, for the subscribed resource
  • the newly generated data is meaningful, such as the data used to display the status of the electrical switch in the smart home, so that the Hosting CSE or M2M service provider where the subscribed resource is located will add indication information to the configuration policy information to indicate that App2 needs to obtain The latest status of the subscribed resource, the configuration policy information can be saved on the Hosting CSE.
  • the configuration policy information includes indication information, to indicate that the subscriber needs to obtain the latest state of the subscribed resource, which may be specifically: by creating Add a parameter RepeatCheck in the subscription resource request or the configuration policy information, and the value of the parameter is a specified valid value to indicate that the subscriber needs to obtain the latest state of the subscribed resource, which may be a Boolean, an integer, or a string type. Or other type.
  • the added parameter RepeatCheck is a Boolean type, and when the parameter value is TRUE, the subscriber only obtains the latest state of the subscribed resource.
  • Step 702 After receiving the request for creating a subscription resource, the CSE2 forwards the create subscription request to the Hosting CSE with the registered resource (ie, the subscribed resource) of App1 according to the create subscription request. Specifically, the CSE2 forwards the unique identifier of the subscribed resource carried in the created subscription resource request to the Hosting CSE having the subscribed resource.
  • the CSE2 After receiving the request for creating a subscription resource, the CSE2 forwards the create subscription request to the Hosting CSE with the registered resource (ie, the subscribed resource) of App1 according to the create subscription request. Specifically, the CSE2 forwards the unique identifier of the subscribed resource carried in the created subscription resource request to the Hosting CSE having the subscribed resource.
  • Step 703 The Hosting CSE creates a subscription resource after receiving the request to create a subscription resource, and allocates a latest state identifier to the subscription resource after determining that the subscriber needs to obtain the latest state of the subscribed resource.
  • a subscription resource ID is assigned to the subscription resource and a subscription resource URI is generated, and an association relationship between the subscription resource and the subscribed resource is saved.
  • the assigned subscription resource ID is a unique string in the Hosting CSE, for example, subscriptionB
  • the subscription resource URI is composed of the subscribed resource URI and the subscription resource ID, because the subscribed resource URI is a globally unique string, so the subscription
  • the resource URI is also a globally unique string.
  • the value of the subscription resource URI is http://example.com/gateway1/application1/subscriptionB.
  • the association relationship between the subscriptionB and the application1 is saved by using the created subscription resource subscriptionB as a child node of the resource tree of the subscribed resource application1.
  • the created subscription resource includes a unique identifier of the subscribed resource carried in the create subscription resource request and a unique identifier of App2.
  • the subscription resource further includes the subscription condition.
  • the Hosting CSE determines that the latest state of the subscribed resource that the subscriber needs to obtain is specifically: determining, according to the indication information included in the request for creating the subscription resource, that the App2 needs to be acquired.
  • the latest state of the subscribed resource is determined by the latest state of the subscribed resource, or according to the locally saved information indicating the information related to the App2.
  • the Hosting CSE determines whether the App2 needs to obtain the latest state of the subscribed resource by checking whether the parameter of the created subscription resource or the policy information has a parameter RepeatCheck and whether the parameter is a specified valid value. For example, in the present embodiment, it is determined that the App2 needs to acquire the latest state of the subscribed resource by determining to carry the Boolean parameter RepeatCheck and its value is True.
  • the latest status identifier is a globally unique identifier for identifying the subscription resource.
  • the globally unique latest state identifier may be a subscription resource URI or other string.
  • the latest status identifier is an identifier that identifies the subscription resource and is unique on the hosting public service entity hosting CSE.
  • the unique latest state identifier may be a subscription resource ID or other string.
  • the latest state identifier may be a specified string.
  • the Hosting CSE may use the latest state identifier as an attribute of the subscription resource or create a table to save the association relationship between the subscription resource and the latest state identifier.
  • Step 704 When the status update of App1 occurs, a status update request is sent to the Hosting CSE.
  • App1 status update includes application logout and App1 attribute changes.
  • the status update request includes a registration resource URI allocated by the Hosting CSE for the registered resource of App1.
  • the registration resource URI is also the subscribed resource URI.
  • Step 705 The Hosting CSE updates the status of the subscribed resource after receiving the status update request, generates a first notification message according to the subscription resource, and sends the status to the intermediate node, and includes the update after the first notification message is included.
  • the status of the subscribed resource and the latest status ID The status of the subscribed resource and the latest status ID.
  • the step includes: after receiving the status update request, the Hosting CSE is configured according to the The subscribed resource URI carried in the status update request updates the status of the subscribed resource. And the Hosting CSE finds the subscription resource according to the corresponding relationship between the subscribed resource and the subscription resource, and determines that the subscription resource includes the latest state identifier, and generates a first notification message according to the subscription resource, where the first notification message includes Transmitting a source address (ie, a Hosting CSE URI) and a recipient address (ie, an App2 URI) and a subscription resource URI, and including, in the first notification message, a status of the updated subscribed resource and the latest status identifier .
  • a source address ie, a Hosting CSE URI
  • a recipient address ie, an App2 URI
  • the first notification message may be a message in a primitive format, where the sending source address Hosting CSE URI, the receiving party address App2 URI, and the latest state identifier are included in the attribute part of the first notification message, the subscription resource URI, and the update.
  • the status of the subscribed resource is included in the resource part of the first notification message.
  • the resource part of the first notification message may include the updated subscribed resource.
  • the first notification message is generated.
  • the receiver address may be obtained according to the ContactURI of the subscription resource.
  • the Hosting CSE determines the delivery manner of the first notification message according to the locally saved configuration information. Specifically, the following two delivery modes are available: Directly sending the first notification message in an HTTP-Hypertext Transfer Protocol (HTTP) message, for example, sending the first notification message by using an HTTP POST, and preferably, the first format of the primitive
  • HTTP Hypertext Transfer Protocol
  • the attribute part of a notification message is encapsulated into a message header of the HTTP, and the resource part of the first notification message is encapsulated into the message body of the HTTP; and the generated storage is generated after the resource representation of the store-and-forward resource is generated according to the first notification message.
  • the resource description of the forwarding resource is encapsulated and sent in the Restful message.
  • the resource representation of the ⁇ delivery> is generated, and the first notification message is used as the data attribute value of the resource of the ⁇ delivery>, and then the resource of the ⁇ delivery> is expressed.
  • the encapsulation is delivered in the Restful Create message.
  • Step 706 The intermediate node receives the first notification message and determines that the first notification message includes After the latest status identifier, it is checked whether other notification messages generated according to the same subscription resource as the first notification message are saved locally. In an embodiment, since this is the first status update after App1 is subscribed, the other notification message generated by the same subscription resource according to the first notification message is not saved locally, and the first notification message is saved. locally.
  • the latest state identifier is a globally unique identifier for identifying the subscription resource
  • the intermediate node checks whether the first notification message is saved locally.
  • the other notification message generated according to the same subscription resource is specifically: determining whether the intermediate node stores other notification messages that contain the same latest state identifier as the first notification message.
  • the latest state identifier is an identifier for identifying the subscription resource and unique on the hosting public service entity hosting CSE
  • the intermediate node checks whether the local storage is saved.
  • the other notification message generated by the first notification message according to the same subscription resource is specifically: determining whether the intermediate node stores other notification messages including the latest state identifier and the message sending source address, which are the same as the first notification message.
  • the intermediate node checks whether the local notification is saved with other notifications generated according to the same subscription resource as the first notification message.
  • the message is specifically: determining whether the intermediate node stores other notification messages that contain the same subscription resource URI as the first notification message.
  • the third manner may also be used to check whether other notification messages generated by the first notification message according to the same subscription resource are saved locally.
  • the first step of the first notification message includes the latest status identifier, Further obtaining the source address of the message included in the first notification message, and for each other notification message, parsing the content of the message to obtain the latest
  • the status identifier and the message sending source address are determined twice, that is, whether the acquired latest state identifier is the same as the latest state identifier included in the first notification message, and whether the obtained message sending source address and the first notification message are included.
  • the message sending source address is the same.
  • the notification message is to be parsed once to obtain the subscription resource URI and to make a judgment, that is, to determine whether the acquired subscription resource URI is the same as the subscription resource URI included in the first notification message; therefore, in comparison,
  • the first example of this embodiment has the highest processing efficiency.
  • the check whether the local notification message is stored according to the same subscription resource that is generated by the first notification message is specifically: checking whether the cache queue is saved. And the other notification message generated by the first notification message according to the same subscription resource; the saving the first notification message locally: storing the first notification message in a cache queue of the intermediate node.
  • the intermediate node includes multiple cache queues, each cache queue is used to save the same notification message of the next hop CSE, and an associated timer is set for the cache queue according to the forwarding storage policy of the intermediate node; when the buffer queue is When the notification message is stored, if it is the first notification message in the cache queue, the timer of the cache queue is started after the notification message is stored.
  • the check whether the local notification message is saved according to the same subscription resource that is generated by the first notification message is specifically: checking whether to save in the store-and-forward resource. And the other notification message generated by the first notification message according to the same subscription resource; the saving the first notification message locally: creating a store-and-forward resource in the intermediate node, saving the first notification message In the attributes of the store-and-forward resource, for example, a ⁇ delivery> resource is created, and the first notification message is saved in the data attribute of the ⁇ delivery> resource.
  • the intermediate node sets a unified timer for the notification message with the same next hop CSE according to the forwarding storage policy, and records the association between the timer and the CSE and the storage and forwarding resources including the notification message; Determining a notification message included in the store-and-forward resource when storing and forwarding a resource After the next hop is the CSE, the association between the timer and the store-and-forward resource is added to the record information; when the association between the timer and the store-and-forward resource is added to the record information, if the record information is The first store-and-forward resource in the program starts the timer.
  • Step 707 App1 again updates the status and sends a status update request to the Hosting CSE.
  • Step 708 The Hosting CSE updates the status of the subscribed resource after receiving the status update request, generates a second notification message according to the subscription resource, and sends the status to the intermediate node, and includes the update after the second notification message is included.
  • the status of the subscribed resource and the latest status ID The status of the subscribed resource and the latest status ID.
  • step 705. For a description of the status of the updated subscription resource in the step, refer to step 705.
  • the Hosting CSE generates a second notification message according to the subscription resource, and includes the updated subscribed resource in the second notification message.
  • the description of the status and the latest status identifier is the same as the operation of the first notification message in step 705.
  • the manner in which the Hosting CSE sends the second notification message is the same as the manner in which the first notification message is sent in step 705.
  • Step 707 After receiving the second notification message and determining that the latest state identifier is included, the intermediate node checks whether other notification messages generated by the second notification message according to the same subscription resource are saved locally. In this embodiment, the foregoing first notification message has been saved, and the intermediate node determines that the first notification message and the second notification message are generated according to the same subscription resource, and replaces the second notification message with the second notification message. A notification message.
  • the intermediate node checks whether the implementation of the other notification message generated by the second notification message according to the same subscription resource is saved locally, and in step 706, it is checked whether the local subscription is saved according to the same subscription as the first notification message.
  • Other notification messages generated by the resource are implemented in the same way.
  • the replacing the second notification message with the first notification message is specifically: the first notification message in the cache queue is to be sent.
  • the replacing the first notification message with the first notification message is specifically: replacing the first notification message in the storage and forwarding resource with the second notification message.
  • Step 710 When the message sending condition is met, the intermediate node sends the locally saved notification message to the next hop CSE.
  • the second notification message is locally saved, and the intermediate node sends the second notification message. Give CSE2.
  • step 706 the method directly proceeds to step 710, that is, after receiving the other notification message generated according to the subscription resource, the message sending condition is satisfied, and the first notification message is locally saved, and the intermediate node A notification message is sent to CSE2.
  • the intermediate node receives one or more other notification messages generated according to the subscription resource, where the last one of the other notification messages is saved locally, and the intermediate node sends the other notification message. The last one is sent to CSE2.
  • the step is specifically: when the timer associated with the cache queue expires, the notification message saved in the cache queue is sent to the next hop CSE, and The timer associated with the cache queue is cleared and the notification message in the cache queue is deleted.
  • the step is specifically: when the timer associated with the storage and forwarding resource expires, the notification message included in all the storage and forwarding resources recorded in the record information is sent to The next hop CSE clears the timer associated with the store-and-forward resource and deletes the store-and-forward resource.
  • the intermediate node sends the second notification message to the CSE2 before passing through the second intermediate node, and the second intermediate node performs the same operation as the intermediate node, and details are not described herein again.
  • Step 711 The CSE2 sends the second notification message to the App2.
  • the gateway CSE2 determines that the App2 is registered on the gateway according to the address of the receiver of the second notification message, and directly sends the second notification message to App2.
  • the notification message sent to the intermediate node includes the latest status identifier, so that the intermediate node replaces the locally saved and the notification message according to the same subscription resource after determining that the received notification message includes the latest status identifier.
  • the generated existing notification message can ensure that the intermediate node only forwards the latest notification message generated according to the subscription resource, thereby preventing the subscriber from receiving multiple notification messages sent according to the same subscription resource in one connection, thereby saving the network. Resources and computing resources.
  • FIG. 1 Another embodiment of the present invention provides a signaling flowchart for implementing subscription notification, which is illustrated in FIG.
  • the process of registering the App1 to its local CSE and setting the access authority of the registered resource refers to the detailed description of the corresponding embodiment of FIG. 7.
  • the registration resource of App1 on the Hosting CSE can be found.
  • the registered resource is subscribed, and the subscriber App2 hopes to receive the latest registration of the registered resource each time. status.
  • the specific implementation process is as follows:
  • Step 801 - Step 805 Refer to Step 701 - Step 705 of the corresponding embodiment of FIG.
  • Step 806 The intermediate node saves the first notification message locally.
  • step 706 of the corresponding embodiment of FIG. 7 the implementation manner of saving the first notification message locally is described in step 706 of the corresponding embodiment of FIG. 7 to save the first notification message in a local description.
  • Step 807-Step 808 Refer to steps 707-708 of the corresponding embodiment of FIG.
  • Step 809 The intermediate node saves the second notification message locally.
  • the method for saving the second notification message in the local implementation manner saves the first notification message in a local description in step 706 of the corresponding embodiment of FIG. 7 .
  • Step 810 When the message sending condition is met, the intermediate node determines whether the locally saved first notification message includes the latest state identifier, and checks whether the local saves another notification message generated by the first notification message according to the same subscription resource. The latest notification message and the latest notification message in the first notification message are sent to the next hop CSE. In this embodiment, the first notification message and the second notification message are saved locally, and after the intermediate node determines that the second notification message is the latest notification message, the second notification is cancelled. The message is sent to CSE2.
  • step 806 proceed directly to step 810, that is, after receiving the other notification message generated according to the subscription resource, the message sending condition is satisfied, and only the first notification message is saved locally, and the intermediate node A notification message is sent to CSE2.
  • the intermediate node receives one or more other notification messages generated according to the subscription resource, where the first notification message, the second notification message, and the other notification message are locally saved.
  • the node sends the latest notification message in the first notification message, the second notification message, and other notification messages to CSE2.
  • the specific time is: when the timer associated with the cache queue expires.
  • the time is: when the timer associated with the store-and-forward resource expires.
  • the notification message includes timestamp information
  • the sending the latest notification message and the latest notification message in the first notification message to the next hop CSE is specifically: according to the other notification message and the first notification message.
  • the included timestamp information is sent to the next hop CSE by the other notification message and the latest notification message in the first notification message.
  • the step further includes deleting the other locally saved notification message and the first notification message.
  • the intermediate node sends the second notification message to the CSE2 before passing through the second intermediate node, and the second intermediate node performs the same operation as the intermediate node, and details are not described herein again.
  • Step 811 Refer to step 711 of the corresponding embodiment of FIG.
  • the notification message sent to the intermediate node includes the latest status identifier, and the intermediate node saves the notification message when the notification is needed.
  • the intermediate node determines that the notification message includes the latest status identifier, searches for other notification messages that are locally saved and generated by the notification message according to the same subscription resource, and the latest notification in the notification message and other notification messages.
  • the message is delivered, and the intermediate node can only forward the latest notification generated according to the subscription resource, thereby preventing the subscriber from receiving multiple notifications sent according to the same subscription resource in one connection, thereby saving network resources and computing resources.
  • the Hosting CSE in the embodiment of the present invention may be implemented based on a computer system, and the methods shown in FIG. 5, FIG. 7, and FIG. 8 may all be implemented in a Hosting CSE based on a computer system.
  • Figure 9 illustrates an embodiment of a Hosting CSE implemented based on a computer system.
  • the Hosting CSE in this embodiment may include: a processor 901, a memory 902, and a communication interface 903, where:
  • a communication interface 903 is configured to communicate with subscribers and intermediate nodes. The messages exchanged between the Hosting CSE and the subscribers and intermediate nodes are all sent and received through the communication interface 903.
  • the communication interface 903 is configured to receive a subscription subscription resource request of the subscriber and send a notification message to the intermediate node;
  • the memory 902 is configured to store the program instruction;
  • the processor 901 is configured to: after the communication interface 903 receives the subscription resource request from the subscriber Calling the program instructions stored in the memory 902, performing the following operations: creating a subscription resource according to the create subscription request; determining that the subscriber needs to obtain the latest state of the subscribed resource, and creating the subscribed resource Allocating a latest status identifier, the latest status identifier is used to indicate that the subscriber needs to obtain the latest status of the subscribed resource; when the subscribed resource is updated, generating a notification message according to the subscription resource and sending To the intermediate node, the notification message includes the status of the updated subscribed resource and the latest status identifier, so that after
  • the processor 901 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or the like.
  • the Hosting CSE in this embodiment may include a bus 904.
  • the processor 901, the memory 902, and the communication interface 903 can be connected and communicated via a bus 904.
  • the memory 902 may include: a random access memory (RAM), a read-only memory (ROM), a disk and the like having a storage function.
  • the processor 901 can also be used to perform the steps of the Hosting CSE described in FIG. 5, FIG. 7 and FIG. 8 in the method embodiment, and the embodiments of the present invention are not described in detail herein.
  • the intermediate nodes in the embodiments of the present invention may be implemented based on a computer system, and the methods shown in FIG. 6, FIG. 7, and FIG. 8 may all be implemented in an intermediate node based on a computer system.
  • Figure 10 illustrates an embodiment of an intermediate node implemented based on a computer system.
  • the intermediate node in this embodiment may include: a processor 1001, a memory 1002, and a communication interface 1003, where:
  • the communication interface 1003 is configured to communicate with the last hop CSE. Messages between the intermediate node and the last hop CSE are sent and received through the communication interface 1003. Specifically, the communication interface 1003 is configured to receive a notification message from the last hop CSE; the memory 1002 is configured to store program instructions; and the processor 1001 is configured to invoke the program stored in the memory 1002 after the communication interface 1003 receives the notification message from the last hop CSE.
  • the processor 1001 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or the like.
  • the intermediate node in this embodiment may include a bus 1004.
  • the processor 1001, the memory 1002, and the communication interface 1003 can be connected and communicated via the bus 1004.
  • the memory 1002 may include: random access memory (RAM), read-only memory (ROM), magnetic An entity such as a disk that has a storage function.
  • the processor 1001 can also be used to perform the steps of the intermediate nodes described in FIG. 6 , FIG. 7 and FIG. 8 in the method embodiment, and the embodiments of the present invention are not described in detail herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明提供了一种订阅通知的实现方法和装置，所述方法包括：接收订阅者的创建订阅资源请求；根据所述创建订阅资源请求创建订阅资源；确定所述订阅者需要获取的是所述被订阅资源的最新状态，为所述创建的订阅资源分配最新状态标识；当所述被订阅资源的状态发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述更新后的被订阅资源的状态以及所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息。使用本发明，能够避免因为在一个连接中将多个根据同一订阅资源发送的通知发送给订阅者造成网络资源和计算资源的浪费。

Description

订阅通知的实现方法和装置 技术领域
本发明涉及机器通信(Machine-to-Machine Communications,M2M)技术领域，尤其涉及订阅通知的实现方法和装置。
背景技术
机器通信(Machine-to-Machine Communications,M2M)是一种以机器智能交互为核心的、网络化的应用与服务。它通过在机器内部嵌入无线或有线通信模块以及应用处理逻辑，实现无需人工干预的数据通信，以满足用户对监控、指挥调度、数据采集和测量等方面的信息化需求。
图1是一种典型的M2M系统架构。其中，各种终端(如传感器)经过网关远程接入到业务平台，而各种装载在终端上的应用(如电力抄表、智能交通等)则通过业务平台所提供的业务能力获取其他终端采集的数据或对其他终端进行远程的控制和管理。网关和平台都是公共服务实体(Common Services Entity，CSE)，终端上的应用可以注册到与该终端连接的网关上，所有网关均需要注册到业务平台上，该接收注册的CSE称为本地CSE，例如，图1中应用1的本地CSE是网关A，应用2的本地CSE是网关B，网关A和B的本地CSE是业务平台。注册成功后，本地CSE将为注册者创建注册资源。
在某些M2M应用场景中，终端b上应用2希望持续了解另一终端a上的应用1的状态变化，但又不希望频繁的去询问应用1。在目前的欧洲电信标准化协会(European Telecommunications Standards Institute，ETSI)所制定的M2M规范TS102 690及TS 102 921中，提供了一种订阅通知机制。即应用2订阅应用1在其本地CSE(即网关A)上的注册资源；当应用1产生改变时，向其本地CSE、即网 关A更新注册资源状态，网关A根据所述注册资源的状态更新向应用2发送通知消息。其中，应用2称为订阅者，应用1在其本地CSE上的注册资源称为被订阅资源，该被订阅资源所在的CSE称为托管公共服务实体(Hosting CSE)。Hosting CSE将根据订阅者(即应用2)的订阅请求创建订阅资源，订阅资源用于描述订阅关系。订阅资源的具体内容可以包括：被订阅资源标识、通知发送地址；可选的，还包含订阅条件等。同时在被订阅资源中保存该被订阅资源与订阅资源之间的关联关系。
上述场景中，网关A上报的通知消息经过其他CSE转发给网关B，这里以通知消息只经过一个CSE(即业务平台)转发给网关B为例，为了减少业务平台与网关B的连接开销，业务平台在接收到来自网关A的上报信息后，确定如果是非紧急消息，将其在本地缓存。当接收到其他发送给网关B的紧急消息或缓存时间到期时，业务平台与网关B建立连接，将缓存的消息一并发送。这种接收到来自其他CSE的消息并在本地缓存一段时间后再转发到另一CSE的机制称为存储转发(Store and Forward，SAF)机制，在消息的发送过程中执行存储转发机制的CSE称为中间节点，例如该场景中的业务平台，消息在中间节点所缓存的时间称为存储转发时延。
由于存储转发机制的存在，使得不同时间发送的多条通知消息可能在一个连接中到达订阅者。例如：在上述的场景中，应用1用于产生天气信息，应用2用于根据天气为用户提供生活提醒，需要实时了解天气变化信息，因此订阅应用1，从而创建订阅资源1。当天气信息发生更新时，气象部门网关A根据订阅资源1向应用2发送通知消息。由于关于天气变化的通知属于不紧急的通知消息，当通知消息到达业务平台时，业务平台根据存储转发策略缓存该通知消息。在通知消息的缓存期间，若天气发生变化，业务平台会接收网关A到根据订阅资源1发送给应用2的新通知消息。现有订阅通知机制中，这两条通知消息可能在一个连接中达到应用2，即订阅者在一个连接中可能接收到根据同一个订 阅资源发送的多条通知消息。但是，对某些订阅者，应用2只关心最新的天气信息，因此较早时间发送的通知消息无效，从而导致网络资源和订阅者计算资源浪费。
发明内容
本发明的实施例提供的订阅通知的实现方法和装置，能够避免因为在一个连接中将多个根据同一订阅资源发送的通知消息同时发送给订阅者造成网络资源和计算资源的浪费。
第一方面，本发明实施例提供的实现订阅通知的托管公共服务实体hosting CSE包括：接收单元，用于接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识；资源创建单元，用于根据所述接收单元接收到的创建订阅资源请求而创建订阅资源；确定单元，用于确定所述订阅者需要获取的是所述被订阅资源的最新状态；分配单元，用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态；生成单元，用于当所述被订阅资源的状态发生更新时，根据所述资源创建单元创建的订阅资源生成通知消息，所述通知消息包含所述更新后的被订阅资源的状态以及所述分配单元分配的最新状态标识，以便于中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息；发送单元，用于将所述生成单元生成的通知消息发送给所述中间节点。
在第一方面的第一种可能的实现方式中，所述确定单元用于确定所述订阅者需要获取的是所述被订阅资源的最新状态具体包括：所述确定单元，用于根据所述创建订阅资源请求中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
在第一方面的第二种可能的实现方式中，所述确定单元用于确定所述订阅 者需要获取的是所述被订阅资源的最新状态具体包括：所述确定单元，用于根据本地保存的与所述订阅者相关策略信息中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
第二方面，本发明实施例提供的实现订阅通知的中间节点包括：接收单元，用于接收到通知消息，所述通知消息包含更新后的被订阅资源的状态；确定单元，用于确定所述接收单元接收到的所述通知消息包含最新状态标识；保存单元，用于保存所述接收单元接收到的所述通知消息；确定单元，还用于确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；发送单元，用于根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
在第二方面的第一种可能的实现方式中，所述中间节点还包括查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的；所述保存单元，用于保存所述接收单元接收到的所述通知消息具体为：所述保存单元，用于将所述接收单元接收到的所述通知消息以替换所述查找单元查找到的所述其他通知消息的方式保存到本地；所述确定单元，还用于确定本地保存的根据所述订阅资源生成的通知消息中的最新通知消息具体为：所述确定单元，还用于确定本地保存的根据所述订阅资源生成的通知消息为最新通知消息。
在第二方面的第二种可能的实现方式中，所述中间节点还包括查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的；所述确定单元，还用于确定本地保存的根据订阅资源生成的通知消息中的最新通知消息具体为：所述确定单元，还用于确定本地保存的所述通知消息和所述查找单元查找到的所述其他通知消息中的最新通知消息。
结合第二方面的第一可能和第二可能的实现方式，在第三种可能的实现方式中，所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识；所述 查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元，用于查找到本地保存的其他通知消息，所述接收单元接收到的所述通知消息和所述其他通知消息包含的最新状态标识相同。
结合第二方面的第一可能和第二可能的实现方式，在第四种可能的实现方式中，所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识；所述查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元，用于查找到本地保存的其他通知消息，所述接收单元接收到的所述通知消息和所述其他通知消息包含的最新状态标识以及消息发送源地址相同。
结合第二方面的第一可能和第二可能的实现方式，在第五种可能的实现方式中，所述查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源的生成具体为：所述查找单元，用于查找到本地保存的其他通知消息，所述接收单元接收到的所述通知消息和所述其他通知消息包含的订阅资源通用资源标识符(Universal Resource Identifier，URI)相同。
第三方面，本发明实施例提供的订阅通知的实现方法包括：接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识；根据所述创建订阅请求创建订阅资源；确定所述订阅者需要获取的是所述被订阅资源的最新状态，为所述创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态；当所述被订阅资源的状态发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述更新后的被订阅资源的状态以及所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识在满 足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息。
在第三方面的第一种可能的实现方式中，所述确定所述订阅者需要获取的是所述被订阅资源的最新状态具体为：根据所述创建订阅资源请求中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
在第三方面的第二种可能的实现方式中，所述确定所述订阅者需要获取的是所述被订阅资源的最新状态具体为：根据本地保存的与所述订阅者相关策略信息中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
第四方面，本发明实施例提供的订阅通知的实现方法包括：接收到通知消息，所述通知消息包含更新后的被订阅资源的状态，确定所述通知消息包含最新状态标识；保存所述接收到的通知消息；确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
在第四方面的第一种可能的实现方式中，所述保存所述接收到的通知消息具体包括：查找到本地保存有其他通知消息后，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的，将所述接收到的通知消息以替换所述其他通知消息的方式保存到本地；所述确定本地保存的根据订阅资源生成的通知消息中的最新通知消息具体包括：确定本地保存的根据所述订阅资源生成的通知消息为最新通知消息。
在第四方面的第二种可能的实现方式中，所述确定本地保存的根据订阅资源生成的通知消息中的最新通知消息具体包括：查找到本地保存有其他通知消息后，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的，确定本地保存的所述通知消息和所述其他通知消息中的最新通知消息。
结合第四方面的第一可能和第二可能的实现方式，在第三种可能的实现方 式中，所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识；所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的最新状态标识相同。
结合第四方面的第一可能和第二可能的实现方式，在第四种可能的实现方式中，所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识；所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的最新状态标识以及消息发送源地址相同。
结合第四方面的第一可能和第二可能的实现方式，在第五种可能的实现方式中，所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的订阅资源通用资源标识符(Universal Resource Identifier，URI)相同。
由上述本发明的实施例提供的技术方案可以看出，通过接收订阅者的创建订阅资源请求，根据所述创建订阅请求创建订阅资源；确定所述订阅者需要获取的是所述被订阅资源的最新状态，为所述创建的订阅资源分配最新状态标识；当所述被订阅资源的状态发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识向订阅者只发送根据所述订阅资源生成的最新通知消息。对于只关心被订阅资源最新状态的订阅者，可以避免在一个连接中将多个根据同一订阅资源发送的通知消息同时发送给该订阅者，从而节省网络资源和该订阅者的计算资源。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为现有技术M2M系统结构示意图；
图2为本发明实施例提供的订阅通知的实现系统结构图；
图3为本发明实施例提供的实现订阅通知的Hosting CSE结构图；
图4为本发明实施例提供的实现订阅通知的中间节点结构图；
图5为本发明一个实施例提供的订阅通知的实现方法流程图；
图6为本发明另一个实施例提供的订阅通知的实现方法流程图；
图7为本发明一个实施例提供的订阅通知的实现信令流程图；
图8为本发明另一个实施例提供的订阅通知的实现信令流程图；
图9为本发明实施例提供的基于计算机系统的Hosting CSE结构图；
图10为本发明实施例提供的基于计算机系统的中间节点结构图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例提供了一种订阅通知的实现系统，参考图2，所述订阅通知的实现系统200包括：
托管公共服务实体hosting CSE 201，用于接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识；根据所述创建订阅请求创建订阅资源；确定所述订阅者需要获取的是所述被订阅资源的最新状态，为 所述创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态；当所述被订阅资源的状态发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述更新后的被订阅资源的状态以及所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息；和
中间节点202，用于接收到通知消息，所述通知消息包含更新后的被订阅资源的状态，确定所述通知消息包含最新状态标识；保存所述接收到的通知消息；确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
其中，所述订阅通知的实现系统200中的中间节点可以有一个或者多个，即中间节点可以连接到其他的中间节点，且它们在本发明的订阅通知实现过程中执行的操作一样。
本发明一个实施例提供了用于实现订阅通知的托管公共服务实体Hosting CSE，请参照图3，该Hosting CSE 300包括：
接收单元301，用于接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识；
资源创建单元302，用于根据所述接收单元301接收到的创建订阅资源请求而创建订阅资源；
确定单元303，用于确定所述订阅者需要获取的是所述被订阅资源的最新状态；
分配单元304，用于在所述确定单元303确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元302创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源 的最新状态；
生成单元305，用于当所述被订阅资源的状态发生更新时，根据所述资源创建单元创建的订阅资源生成通知消息，所述通知消息包含所述更新后的被订阅资源的状态以及所述分配单元分配的最新状态标识，以便于中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息；
发送单元306，用于将所述生成单元305生成的通知消息发送给所述中间节点。
可选的，确定单元303用于确定所述订阅者需要获取的是所述被订阅资源的最新状态具体包括：确定单元303，用于根据所述创建订阅资源请求中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
可选的，确定单元303用于确定所述订阅者需要获取的是所述被订阅资源的最新状态具体包括：确定单元303，用于根据本地保存的与所述订阅者相关策略信息中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
可选的，分配单元304用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态进一步包括：所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识。
可选的，分配单元304用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态进一步包括：所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识。
可选的，分配单元304用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态进一步包括：所有的订阅资源具有相同的最新状态标识。
可选的，发送单元306用于将所述生成单元生成的通知消息发送给所述中间节点具体包括：所述发送单元306，用于将所述生成单元305生成的通知消息直接封装在HTTP消息中发送给所述中间节点，或者在根据所述通知消息生成存储转发资源的资源表述后，将所述资源表述封装在Restful消息中发送给所述中间节点。
本发明一个实施例提供了用于实现订阅通知的中间节点，请参照图4，该中间节点400包括：
接收单元401，用于接收到通知消息，所述通知消息包含更新后的被订阅资源的状态；
确定单元402，用于确定所述接收单元401接收到的所述通知消息包含最新状态标识；
保存单元404，用于保存所述接收单元401接收到的所述通知消息；
确定单元402，还用于确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；
发送单元405，用于根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
可选的，所述中间节点400还包括查找单元403，用于查找到本地保存有其他通知消息，所述其他通知消息和所述接收单元401接收到的通知消息是根据相同的订阅资源生成的；所述保存单元404，用于保存所述接收单元401接收到的所述通知消息具体为：所述保存单元404，用于将所述接收单元401接收到的所述 通知消息以替换所述查找单元403查找到的所述其他通知消息的方式保存到本地；所述确定单元402，还用于确定本地保存的根据所述订阅资源生成的通知消息中的最新通知消息具体为：所述确定单元402，还用于确定本地保存的根据所述订阅资源生成的通知消息为最新通知消息。
可选的，中间节点400还包括查找单元403，用于查找到本地保存有其他通知消息，所述其他通知消息和所述接收单元401接收到的通知消息是根据相同的订阅资源生成的；所述确定单元402，还用于确定本地保存的根据订阅资源生成的通知消息中的最新通知消息具体为：所述确定单元402，还用于确定本地保存的所述通知消息和所述查找单元403查找到的所述其他通知消息中的最新通知消息。
可选的，所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识；所述查找单元403，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元403，用于查找到本地保存的其他通知消息，所述接收单元401接收到的所述通知消息和所述其他通知消息包含的最新状态标识相同。
可选的，所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识；所述查找单元403，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元403，用于查找到本地保存的其他通知消息，所述接收单元401接收到的所述通知消息和所述其他通知消息包含的最新状态标识以及消息发送源地址相同。
可选的，所述查找单元403，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元403，用于查找到本地保存的其他通知消息，所述接收单元401接收到的所述通知消息和所述其他通知消息包含的订阅资源通用资源标识符(Universal  Resource Identifier，URI)相同。
在M2M网络中，M2M业务平台可以是各计算机，具有处理器的设备。M2M网关和M2M终端在设备上没有严格的区分，比如做网关的设备也可以做为终端，此外为各种终端设备，如手机，计算机，PDA，笔记本电脑，远程控制器，家用电器，各种仪器仪表、传感器等都可以做为M2M网络的网关或终端。在上述模块实施例中，所包括的各个模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能模块的具体名称也只是为了便于相互区分，并不用于限制本发明的保护范围。
本发明实施例提供了订阅通知的实现方法，应用于部署被订阅资源的托管公共服务实体Hosting CSE，请参照图5，该方法包括：
步骤501：接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识。
步骤502：根据所述创建订阅请求创建订阅资源。
步骤503：确定所述订阅者需要获取的是所述被订阅资源的最新状态，为所述创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态。
具体的，确定所述订阅者需要获取的是所述被订阅资源的最新状态可以为：根据所述创建订阅资源请求中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态，或者，根据本地保存的与所述订阅者相关策略信息中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
具体的，所述最新状态标识可以是一个用于识别所述订阅资源且全局唯一的标识，或者，所述最新状态标识可以是一个用于识别所述订阅资源且在托管 公共服务实体hosting CSE上唯一的标识，或者，所有的订阅资源具有相同的最新状态标识。
步骤504：当所述被订阅资源的状态发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述更新后的被订阅资源的状态以及所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息。
具体的，根据所述订阅资源生成通知消息并发送给中间节点可以为：根据所述订阅资源生成通知消息，并将所述通知消息直接封装在HTTP消息中发送给中间节点，或者根据所述通知消息生成存储转发资源的资源表述，将所述资源表述封装在Restful消息中发送给中间节点。
本发明另一个实施例提供了订阅通知的实现方法，应用于转发通知消息的中间节点，请参照图6，该方法包括：
步骤601：接收到通知消息，所述通知消息包含更新后的被订阅资源的状态，确定所述通知消息包含最新状态标识。
步骤602：保存所述接收到的通知消息。
步骤603：确定本地保存的根据订阅资源生成的通知消息中的最新通知消息。
可选的，当步骤602中保存所述接收到的通知消息具体包括：查找到本地保存有其他通知消息后，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的，将所述接收到的通知消息以替换所述其他通知消息的方式保存到本地；本步骤具体为：确定本地保存的根据所述订阅资源生成的通知消息为最新通知消息。
可选的，本步骤具体为：查找到本地保存有其他通知消息后，所述其他通 知消息和所述通知消息是根据相同的订阅资源生成的，确定本地保存的所述通知消息和所述其他通知消息中的最新通知消息。
其中，所述最新状态标识具体为一个用于识别所述订阅资源且全局唯一的标识，所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的最新状态标识相同；或者，所述最新状态标识具体为一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识，所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的最新状态标识以及消息发送源地址相同；或者，所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的订阅资源通用资源标识符(Universal Resource Identifier，URI)相同。
步骤604：根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
在所述满足消息发送条件时只发送所述最新通知消息之后，还包括将本地保存的根据所述订阅资源生成的通知消息删除。
本发明实施例提供了实现订阅通知的信令流程图，请参照图7示。
在本实施例中，App1注册到其本地CSE上，该CSE为App1创建注册资源，并为该注册资源分配ID，然后生成该注册资源的URI，并将该注册资源URI返回给App1。其中该注册资源ID是一个全局唯一的字符串，例如application1，注册资源URI由注册资源ID和该本地CSE的URI组成。因此，该注册资源URI也是一个全局唯一的字符串，注册资源ID和注册资源URI均可以是该注册资源的唯一 标识。例如，在本实施例中App1的本地CSE URI是http://example.com/gateway1，则该注册资源URI是http://example.com/gateway1/application1。并且，App1在注册过程或注册结束后设置该注册资源的访问权限，允许包含App2的其他用户访问、订阅该注册资源。在此，该本地CSE被称作App1的Hosting CSE。因此，当App2访问该Hosting CSE时，可以发现App1在Hosting CSE上的注册资源，在获取所述注册资源的唯一标识后订阅所述注册资源，并且订阅者App2希望每次接收到的是该注册资源的最新状态。具体的实现过程如下：
步骤701：订阅者App2向自身的注册网关CSE2发送创建订阅资源请求，该创建订阅资源请求中包含被订阅资源的唯一标识以及订阅者App2的唯一标识。
在本实施中，上述的被订阅资源也就是App1在Hosting CSE上的注册资源，因此，上述被订阅资源的唯一标识，也就是App1在Hosting CSE上的注册资源的唯一标识。
可选的，该创建订阅资源请求中还可以包括订阅条件。
可选的，App2通过在所述创建订阅资源请求中包含指示信息，以指示订阅者需要获取的是被订阅资源的最新状态；或者App2事先访问M2M业务提供商的设置系统，在配置策略信息中添加指示信息；又或App2在与M2M业务提供商签约时，约定App2只获取被订阅资源的最新状态信息，M2M业务提供商在配置策略信息中添加指示信息；又或，对被订阅资源来说其最新产生的数据才有意义，比如智能家居中用于显示电器开关的状态的数据，这样被订阅资源所在的Hosting CSE或M2M业务提供商会在配置策略信息中添加指示信息，以指示App2需要获取的是被订阅资源的最新状态，所述配置策略信息可以保存在Hosting CSE上。
其中，在所述创建订阅资源请求中或配置策略信息包含指示信息，以指示订阅者需要获取的是被订阅资源的最新状态，具体的可以是：通过在所述创建 订阅资源请求中或者配置策略信息中增加一个参数RepeatCheck且该参数的值为指定的有效值来指示订阅者需要获取的是被订阅资源的最新状态，该参数可以是布尔型、整形、字符串类型或其他类型。例如，在本实施例中，增加的参数RepeatCheck为布尔型，当参数值为TRUE指示订阅者只获取被订阅资源的最新状态。
步骤702：CSE2接收到所述创建订阅资源请求后，根据所述创建订阅请求将所述创建订阅请求转发到具有App1的注册资源(即被订阅资源)的Hosting CSE。具体的，CSE2通过该创建订阅资源请求中携带的被订阅资源唯一标识转发到具有该被订阅资源的Hosting CSE。
步骤703：Hosting CSE接收到所述创建订阅资源请求后创建订阅资源，并在确定订阅者需要获取的是被订阅资源的最新状态后，为所述订阅资源分配最新状态标识。为该订阅资源分配订阅资源ID并生成订阅资源URI，并保存该订阅资源和被订阅资源之间的关联关系。
其中，分配的订阅资源ID是一个在Hosting CSE中唯一的字符串，例如subscriptionB，订阅资源URI由被订阅资源URI和订阅资源ID组成，因为被订阅资源URI是一个全局唯一的字符串，故订阅资源URI也是一个全局唯一的字符串。例如，在本实施例中，订阅资源URI的值是http://example.com/gateway1/application1/subscriptionB。具体的，通过将创建的订阅资源subscriptionB作为被订阅资源application1的资源树的子节点来保存subscriptionB和application1两者之间的关联关系。其中，所述创建的订阅资源包括所述创建订阅资源请求中携带的被订阅资源的唯一标识和App2的唯一标识。可选的，当该创建订阅资源请求中包含订阅条件时，订阅资源还包含该订阅条件。
其中，所述Hosting CSE确定订阅者需要获取的是被订阅资源的最新状态具体为：根据所述创建订阅资源请求中包含的指示信息确定App2需要获取的是被 订阅资源的最新状态，或者根据本地保存的与所述App2相关策略信息中包含的指示信息确定App2需要获取的是被订阅资源的最新状态。具体的，所述Hosting CSE通过检查所述创建订阅资源请求中或所述策略信息中是否具有参数RepeatCheck并且该参数是否为指定的有效值来判断App2需要获取的是被订阅资源的最新状态。例如，在本实施例中，通过确定携带布尔型参数RepeatCheck且其值为True来确定App2需要获取被订阅资源的最新状态。
在本实施例的第一个例子中，所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识。具体的，该全局唯一的最新状态标识可以是订阅资源URI，也可以是其他的字符串。
在本实施例的第二个例子中，所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识。具体的，该唯一的最新状态标识可以是订阅资源ID，也可以是其他的字符串。
在本实施例的第三个例子中，所有的订阅资源具有相同的最新状态标识，具体的，该最新状态标识可以是一个指定字符串。
其中，在为所述订阅资源分配最新状态标识后，Hosting CSE可以将该最新状态标识作为该订阅资源的属性或者创建一张表以保存该订阅资源与该最新状态标识的关联关系。
步骤704：当App1发生状态更新时，向Hosting CSE发送状态更新请求。
具体的，App1发生状态更新包括应用注销和App1属性发生改变。具体的，所述状态更新请求中包含Hosting CSE为App1的注册资源所分配的注册资源URI。在本发明实施例中，所述注册资源URI也就是被订阅资源URI。
步骤705：Hosting CSE接收到所述状态更新请求后更新被订阅资源的状态，根据所述订阅资源生成第一通知消息后发送给中间节点，并且在所述第一通知消息中包含所述更新后的被订阅资源的状态以及最新状态标识。
具体地，该步骤包括：Hosting CSE接收到所述状态更新请求后，根据所述 状态更新请求中携带的被订阅资源URI，更新所述被订阅资源的状态。并且，Hosting CSE根据被订阅资源与订阅资源的对应关系找到所述订阅资源，确定所述订阅资源包含最新状态标识后，根据所述订阅资源生成第一通知消息，所述第一通知消息中包含发送源地址(即Hosting CSE URI)以及接收方地址(即App2 URI)以及订阅资源URI，并且，在所述第一通知消息中包含所述更新后的被订阅资源的状态以及所述最新状态标识。具体的，该第一通知消息可以为原语格式的消息，其中发送源地址Hosting CSE URI、接收方地址App2 URI以及最新状态标识包含在所述第一通知消息的属性部分，订阅资源URI以及更新后的被订阅资源的状态包含在所述第一通知消息的资源部分，可选的，所述第一通知消息的资源部分可以包含所述更新后的被订阅资源。可选的，当所述订阅资源中包含订阅条件时，确定被订阅资源状态的改变满足所述订阅条件后才生成所述第一通知消息。其中，接收方地址可以是根据所述订阅资源的ContactURI获取的。Hosting CSE在生成第一通知消息后，查询路由表获取下一跳为中间节点后，将所述第一通知消息发送到所述中间节点。
本步骤中，在将第一通知消息发送给中间节点之前，Hosting CSE根据本地保存的发送配置信息确定第一通知消息的下发方式，具体的，可以采用以下两种下发方式：方式1、直接将第一通知消息封装在超文本转移协议(HTTP-Hypertext transfer protocol，HTTP)消息中下发，例如，通过HTTP POST发送所述第一通知消息，优选的，将所述原语格式的第一通知消息的属性部分封装到HTTP的消息头中，第一通知消息的资源部分封装到HTTP的消息体中；方式2、根据第一通知消息生成存储转发资源的资源表述后，将生成的存储转发资源的资源表述封装在Restful消息中下发，例如，生成<delivery>的资源表述，将第一通知消息作为<delivery>的资源表述的data属性值，然后将所述<delivery>的资源表述封装在Restful Create消息中下发。
步骤706：中间节点接收到所述第一通知消息并确定该第一通知消息中包含 最新状态标识后，检查本地是否保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息。在实施例中，由于这是App1被订阅后第一次状态更新，因此，本地未保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息，将所述第一通知消息保存在本地。
在上述提到的本实施例的第一个例子中，所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识，则中间节点检查本地是否保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息具体为：确定中间节点是否保存有和所述第一通知消息包含相同的最新状态标识的其他通知消息。
在上述提到的本实施例的第二个例子中，所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识，则中间节点检查本地是否保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息具体为：确定中间节点是否保存有和所述第一通知消息包含相同的最新状态标识以及消息发送源地址的其他通知消息。
在上述提到的本实施例的第三个例子中，所有的订阅资源具有相同的最新状态标识，则中间节点检查本地是否保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息具体为：确定中间节点是否保存有和所述第一通知消息包含相同的订阅资源URI的其他通知消息。而且，在本实施例的第一个例子或第二个例子中，也可以采用该第三种方式检查本地是否保存有和所述第一通知消息根据相同订阅资源生成的其他通知消息。
在本实施例的第一个例子中，本步骤首先判断出第一通知消息包含最新状态标识后，对于每个其他通知消息，要对该消息内容进行一次解析以获取最新状态标识并进行一次判断、即判断该获取到的最新状态标识是否和第一通知消息包含的最新状态标识相同；在本实施例的第二个例子中，本步骤首先判断出第一通知消息包含最新状态标识后，要进一步获取第一通知消息包含的消息发送源地址，对于每个其他通知消息，要对该消息内容进行一次解析以获取最新 状态标识和消息发送源地址并进行两次判断、即判断该获取到的最新状态标识是否和第一通知消息包含的最新状态标识相同以及该获取到的消息发送源地址是否和第一通知消息包含的消息发送源地址相同；在本实施例的第三个例子中，本步骤首先判断出第一通知消息包含最新状态标识后，要进一步获取第一通知消息包含的订阅资源URI，对于每个其他通知消息，要对该消息内容进行一次解析以获取订阅资源URI并进行一次判断、即判断该获取到的订阅资源URI是否和第一通知消息包含的订阅资源URI相同；因此，相比较而言，本实施例的第一个例子处理效率最高。
在步骤705中采用方式1下发第一通知消息时，所述检查本地是否保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息具体为：在缓存队列中检查是否保存有和所述第一通知消息根据相同的订阅资源生成的其他通知消息；所述将所述第一通知消息保存在本地具体为：将第一通知消息保存在中间节点的缓存队列中。中间节点包含多个缓存队列，每个缓存队列用于保存下一跳CSE相同的通知消息，并且根据中间节点的转发存储策略为所述缓存队列设置关联的定时器；当向所述缓存队列中存放通知消息时，如果是该缓存队列中的第一个通知消息，则在存放该通知消息后启动所述缓存队列的定时器。
在步骤705中采用方式2下发第一通知消息时，所述检查本地是否保存有与所述第一通知消息根据相同的订阅资源生成的其他通知消息具体为：在存储转发资源中检查是否保存有和所述第一通知消息根据相同的订阅资源生成的其他通知消息；所述将所述第一通知消息保存在本地具体为：在中间节点创建存储转发资源，将所述第一通知消息保存在所述存储转发资源的属性中，例如，创建<delivery>资源，将第一通知消息保存在<delivery>资源的data属性中。中间节点会根据转发存储策略为具有相同下一跳CSE的通知消息设置统一的定时器，并记录所述定时器与所述CSE、包含所述通知消息的存储转发资源的关联关系；每创建一个存储转发资源时，确定所述存储转发资源中包含的通知消息的 下一跳为所述CSE后，在记录信息中增加所述定时器与所述存储转发资源的关联关系；当在记录信息中增加定时器与存储转发资源的关联关系时、如果是该记录信息中的第一个存储转发资源则启动所述定时器。
步骤707：App1再次发生状态更新，向Hosting CSE发送状态更新请求。
该步骤的实现参考步骤704的详细描述。
步骤708：Hosting CSE接收到所述状态更新请求后更新被订阅资源的状态，根据所述订阅资源生成第二通知消息后发送给中间节点，并且在所述第二通知消息中包含所述更新后的被订阅资源的状态以及最新状态标识。
其中，该步骤中更新被订阅资源状态的描述参见步骤705；其中，Hosting CSE根据所述订阅资源生成第二通知消息、并且在所述第二通知消息中包含所述更新后的被订阅资源的状态以及最新状态标识的描述和步骤705中对第一通知消息的操作方式相同。
其中，Hosting CSE发送第二通知消息的方式和步骤705中发送第一通知消息的方式相同。
步骤707：中间节点接收到所述第二通知消息并确定包含最新状态标识后，检查本地是否保存有和所述第二通知消息根据相同的订阅资源生成的其他通知消息。在本实施例中，前述已经保存了第一通知消息，中间节点确定所述第一通知消息和所述第二通知消息根据相同的订阅资源生成后，将所述第二通知消息替换所述第一通知消息。
其中，中间节点检查本地是否保存有和所述第二通知消息根据相同的订阅资源生成的其他通知消息的实现方式，和步骤706中检查本地是否保存有和所述第一通知消息根据相同的订阅资源生成的其他通知消息的实现方式相同。
其中，当步骤708采用步骤705中的方式1下发第二通知消息时，所述将所述第二通知消息替换所述第一通知消息具体为：将缓存队列中的所述第一通知消息替换为所述第二通知消息；当步骤708采用步骤705中的方式2下发第二通知消 息时，所述将所述第二通知消息替换所述第一通知消息具体为：将存储转发资源中的所述第一通知消息替换为所述第二通知消息。
步骤710：当满足消息发送条件时，中间节点将本地保存的通知消息发送给下一跳CSE，在本实施例中，本地保存的是第二通知消息，中间节点将所述第二通知消息发送给CSE2。
可选的，步骤706之后直接进入步骤710，即步骤706之后没有收到根据所述订阅资源生成的其他通知消息就满足消息发送条件，本地保存的是第一通知消息，中间节点将所述第一通知消息发送给CSE2。
可选的，本步骤之前中间节点又接收到根据所述订阅资源生成的一个或多个其他通知消息，本地保存的是所述其他通知消息中的最后一个，中间节点将所述其他通知消息中的最后一个发送给CSE2。
当步骤705中采用方式1下发第一通知消息时，该步骤具体为：当缓存队列关联的定时器到期后，将所述缓存队列中保存的通知消息发送给下一跳CSE，并将所述缓存队列关联的定时器清零以及将所述缓存队列中的通知消息删除。
当步骤705中采用步骤2下发第一通知消息时，该步骤具体为：当存储转发资源关联的定时器到期后，将所述记录信息中记录的所有存储转发资源包含的通知消息发送给下一跳CSE，并将所述存储转发资源关联的定时器清零以及将所述存储转发资源删除。
可选的，该中间节点将第二通知消息发送给CSE2前将经过第二中间节点，该第二中间节点将执行和本中间节点同样的操作，这里不再赘述。
步骤711：CSE2接收到第二通知消息后发送给App2。
具体的，网关CSE2根据第二通知消息的接收方地址判断App2注册在该网关上，直接将第二通知消息发送给App2。
在该实施例中，通过Hosting CSE确定订阅者需要获取的是被订阅资源的最 新状态后，在发送给中间节点的通知消息中包含最新状态标识，以便中间节点在确定接收到的通知消息中包含最新状态标识后，替换掉本地保存的和所述通知消息根据相同的订阅资源生成的已有通知消息，可以保证中间节点只转发根据所述订阅资源生成的最新通知消息，从而避免了订阅者在一个连接中接收到根据同一个订阅资源发送的多条通知消息，节省了网络资源和计算资源。
本发明另一个实施例提供了实现订阅通知的信令流程图，请参照图8示。
在本实施例中，App1注册到其本地CSE上、设置注册资源的访问权限的过程参考图7对应实施例的详细描述。当App2访问Hosting CSE时，可以发现App1在Hosting CSE上的注册资源，在获取所述注册资源的唯一标识后订阅所述注册资源，并且订阅者App2希望每次接收到的是该注册资源的最新状态。具体的实现过程如下：
步骤801-步骤805：参考图7对应实施例的步骤701-步骤705。
步骤806：中间节点将所述第一通知消息保存在本地。
具体的，所述将所述第一通知消息保存在本地的实现方式参考图7对应实施例的步骤706中将第一通知消息保存在本地的描述。
步骤807-步骤808：参考图7对应实施例的步骤707-步骤708。
步骤809：中间节点将所述第二通知消息保存在本地。
具体的，所述将所述第二通知消息保存在本地的实现方式参考图7对应实施例的步骤706中将第一通知消息保存在本地的描述。
步骤810：当满足消息发送条件时，中间节点确定本地保存的第一通知消息包含最新状态标识后，检查本地是否保存有和所述第一通知消息根据相同的订阅资源生成的其他通知消息，将所述其他通知消息和第一通知消息中的最新通知消息发送给下一跳CSE。在本实施例中，本地保存的是第一通知消息和第二通知消息，中间节点确定第二通知消息是最新通知消息后，将所述第二通知消 息发送给CSE2。
可选的，步骤806之后直接进入步骤810，即步骤806之后没有收到根据所述订阅资源生成的其他通知消息就满足消息发送条件，本地只保存有第一通知消息，中间节点将所述第一通知消息发送给CSE2。
可选的，本步骤之前中间节点又收到根据所述订阅资源生成的一个或多个其他通知消息，本地保存的是所述第一通知消息、第二通知消息和所述其他通知消息，中间节点将所述第一通知消息、第二通知消息和其他通知消息中的最新通知消息发送给CSE2。
当步骤805中采用方式1下发第一通知消息时，所述当满足消息发送条件时具体为：当缓存队列关联的定时器到期后。
当步骤805中采用方式2下发第一通知消息时，所述当满足消息发送条件时具体为：当存储转发资源关联的定时器到期后。
具体的，所述检查本地是否保存有和所述第一通知消息根据相同的订阅资源生成的其他通知消息的实现参考图7对应实施例的步骤706中对该操作的描述。
具体的，通知消息中包含时间戳信息，所述将所述其他通知消息和第一通知消息中的最新通知消息发送给下一跳CSE具体为：根据所述其他通知消息以及第一通知消息中包含的时间戳信息，将所述其他通知消息和第一通知消息中的最新通知消息发送给下一跳CSE。
具体的，该步骤中在将所述其他通知消息和第一通知消息中的最新通知消息发送给下一跳CSE之后，还包括将本地保存的所述其他通知消息和第一通知消息删除
可选的，该中间节点将第二通知消息发送给CSE2前将经过第二中间节点，该第二中间节点将执行和本中间节点同样的操作，这里不再赘述。
步骤811：参考图7对应实施例的步骤711。
在该实施例中，通过Hosting CSE确定订阅者需要获取的是被订阅资源的最新状态后，在发送给中间节点的通知消息中包含最新状态标识，中间节点保存所述通知消息，当需要发送所述通知消息时，中间节点确定所述通知消息中包含最新状态标识后，查找本地保存的和该通知消息根据相同的订阅资源生成的其他通知消息，将该通知消息和其他通知消息中最新的通知消息下发，可以保证中间节点只转发根据所述订阅资源生成的最新通知，从而避免了订阅者在一个连接中接收到根据同一个订阅资源发送的多条通知，节省了网络资源和计算资源。
本发明实施例中的Hosting CSE可以基于计算机系统来实现，图5、图7、图8所示的方法均可在基于计算机系统的Hosting CSE来实现。图9示出了基于计算机系统来实现的Hosting CSE的实施例。本实施例中Hosting CSE可以包括：处理器901、存储器902和通信接口903，其中：
通信接口903，用于与订阅者和中间节点通信。Hosting CSE与订阅者、中间节点之间交互的消息均通过通信接口903发送和接收。具体地，通信接口903用于接收订阅者的创建订阅资源请求以及向中间节点发送通知消息；存储器902用于存储程序指令；处理器901用于通信接口903从订阅者接收到创建订阅资源请求之后，调用存储器902中存储的程序指令，执行以下操作：根据所述创建订阅请求创建订阅资源；确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态；当所述被订阅资源发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述更新后的被订阅资源的状态以及所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息。
其中，处理器901可以是中央处理器(central processing unit,CPU)、专用集成电路(application-specific integrated circuit,ASIC)等。其中，本实施例中的Hosting CSE可以包括总线904。处理器901、存储器902以及通信接口903之间可通过总线904连接并通信。其中，存储器902可以包括：随机存取存储器(random access memory,RAM)，只读存储器(read-only memory,ROM)，磁盘等具有存储功能的实体。
处理器901还可以用于执行方法实施例中图5、图7、图8描述的Hosting CSE的各步骤，本发明实施例在此不再详述。
本发明实施例中的中间节点可以基于计算机系统来实现，图6、图7、图8所示的方法均可在基于计算机系统的中间节点来实现。图10示出了基于计算机系统来实现的中间节点的实施例。本实施例中中间节点可以包括：处理器1001、存储器1002和通信接口1003，其中：
通信接口1003，用于与上一跳CSE通信。中间节点与上一跳CSE之间交互的消息均通过通信接口1003发送和接收。具体地，通信接口1003用于从上一跳CSE接收通知消息；存储器1002用于存储程序指令；处理器1001用于通信接口1003从上一跳CSE接收通知消息之后，调用存储器1002中存储的程序指令，执行以下操作：确定所述通知消息包含最新状态标识；保存所述接收到的通知消息；确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
其中，处理器1001可以是中央处理器(central processing unit,CPU)、专用集成电路(application-specific integrated circuit,ASIC)等。其中，本实施例中的中间节点可以包括总线1004。处理器1001、存储器1002以及通信接口1003之间可通过总线1004连接并通信。其中，存储器1002可以包括：随机存取存储器(random access memory,RAM)，只读存储器(read-only memory,ROM)，磁 盘等具有存储功能的实体。
处理器1001还可以用于执行方法实施例中图6、图7、图8描述的中间节点的各步骤，本发明实施例在此不再详述。
以上所述，仅为本发明较佳的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应该以权利要求的保护范围为准。

Claims (28)

  1. 一种实现订阅通知的托管公共服务实体hosting CSE，其特征在于，所述hosting CSE包括：
    接收单元，用于接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识；
    资源创建单元，用于根据所述接收单元接收到的创建订阅资源请求而创建订阅资源；
    确定单元，用于确定所述订阅者需要获取的是所述被订阅资源的最新状态；
    分配单元，用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态；
    生成单元，用于当所述被订阅资源的状态发生更新时，根据所述资源创建单元创建的订阅资源生成通知消息，所述通知消息包含所述更新后的被订阅资源的状态以及所述分配单元分配的最新状态标识，以便于中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时向所述订阅者只发送根据所述订阅资源生成的最新通知消息；
    发送单元，用于将所述生成单元生成的通知消息发送给所述中间节点。
  2. 根据权利要求1所述的托管公共服务实体hosting CSE，其特征在于，所述确定单元用于确定所述订阅者需要获取的是所述被订阅资源的最新状态具体包括：所述确定单元，用于根据所述创建订阅资源请求中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
  3. 根据权利要求1所述的托管公共服务实体hosting CSE，其特征在于，所述确定单元用于确定所述订阅者需要获取的是所述被订阅资源的最新状态具体 包括：所述确定单元，用于根据本地保存的与所述订阅者相关策略信息中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
  4. 根据权利要求1-3中任一所述的托管公共服务实体hosting CSE，其特征在于，所述分配单元用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态进一步包括：所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识。
  5. 根据权利要求1-3中任一所述的托管公共服务实体hosting CSE，其特征在于，所述分配单元用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态进一步包括：所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识。
  6. 根据权利要求1-3中任一所述的托管公共服务实体hosting CSE，其特征在于，所述分配单元用于在所述确定单元确定所述订阅者需要获取的是所述被订阅资源的最新状态后，为所述资源创建单元创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态进一步包括：所有的订阅资源具有相同的最新状态标识。
  7. 根据权利要求1-6中任一所述的托管公共服务实体hosting CSE，其特征在于，所述发送单元用于将所述生成单元生成的通知消息发送给所述中间节点具体包括：所述发送单元，用于将所述生成单元生成的通知消息直接封装在HTTP消息中发送给所述中间节点，或者在根据所述通知消息生成存储转发资源的资源表述后，将所述资源表述封装在Restful消息中发送给所述中间节点。
  8. 一种实现订阅通知的中间节点，其特征在于，所述中间节点包括：
    接收单元，用于接收到通知消息，所述通知消息包含更新后的被订阅资源的状态；
    确定单元，用于确定所述接收单元接收到的所述通知消息包含最新状态标识；
    保存单元，用于保存所述接收单元接收到的所述通知消息；
    确定单元，还用于确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；
    发送单元，用于根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
  9. 根据权利要求8所述的中间节点，其特征在于，
    所述中间节点还包括查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述接收单元接收到的通知消息是根据相同的订阅资源生成的；
    所述保存单元，用于保存所述接收单元接收到的所述通知消息具体为：所述保存单元，用于将所述接收单元接收到的所述通知消息以替换所述查找单元查找到的所述其他通知消息的方式保存到本地；
    所述确定单元，还用于确定本地保存的根据所述订阅资源生成的通知消息中的最新通知消息具体为：所述确定单元，还用于确定本地保存的根据所述订阅资源生成的通知消息为最新通知消息。
  10. 根据权利要求8所述的中间节点，其特征在于，
    所述中间节点还包括查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述接收单元接收到的通知消息是根据相同的订阅资源生成的；
    所述确定单元，还用于确定本地保存的根据订阅资源生成的通知消息中的最 新通知消息具体为：所述确定单元，还用于确定本地保存的所述通知消息和所述查找单元查找到的所述其他通知消息中的最新通知消息。
  11. 根据权利要求9或10所述的中间节点，其特征在于，
    所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识；
    所述查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元，用于查找到本地保存的其他通知消息，所述接收单元接收到的所述通知消息和所述其他通知消息包含的最新状态标识相同。
  12. 根据权利要求9或10所述的中间节点，其特征在于，
    所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识；
    所述查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：所述查找单元，用于查找到本地保存的其他通知消息，所述接收单元接收到的所述通知消息和所述其他通知消息包含的最新状态标识以及消息发送源地址相同。
  13. 根据权利要求9或10所述的中间节点，其特征在于，所述查找单元，用于查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源的生成具体为：所述查找单元，用于查找到本地保存的其他通知消息，所述接收单元接收到的所述通知消息和所述其他通知消息包含的订阅资源通用资源标识符(Universal Resource Identifier，URI)相同。
  14. 根据权利要求8所述的中间节点，其特征在于，所述中间节点还包括删除单元，用于在所述发送单元只发送所述最新通知消息之后将所述本地保存的根据所述订阅资源生成的通知消息删除。
  15. 一种订阅通知的实现方法，其特征在于，所述方法包括：
    接收订阅者的创建订阅资源请求，所述创建订阅资源请求中包含被订阅资源的唯一标识；
    根据所述创建订阅资源请求创建订阅资源；
    确定所述订阅者需要获取的是所述被订阅资源的最新状态，为所述创建的订阅资源分配最新状态标识，所述最新状态标识用于指示所述订阅者需要获取的是所述被订阅资源的最新状态；
    当所述被订阅资源的状态发生更新时，根据所述订阅资源生成通知消息并发送给中间节点，所述通知消息包含所述更新后的被订阅资源的状态以及所述最新状态标识，以便于所述中间节点接收到所述通知消息后，根据所述最新状态标识在满足消息发送条件时所述订阅者只发送根据所述订阅资源生成的最新通知消息。
  16. 根据权利要求15所述的方法，其特征在于，所述确定所述订阅者需要获取的是所述被订阅资源的最新状态具体为：根据所述创建订阅资源请求中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
  17. 根据权利要求15所述的方法，其特征在于，所述确定所述订阅者需要获取的是所述被订阅资源的最新状态具体为：根据本地保存的与所述订阅者相关策略信息中包含的指示信息确定所述订阅者需要获取的是所述被订阅资源的最新状态。
  18. 根据权利要求15-17中任一所述的方法，其特征在于，所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识。
  19. 根据权利要求15-17中任一所述的方法，其特征在于，所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识。
  20. 根据权利要求15-17中任一所述的方法，其特征在于，所有的订阅资源具有相同的最新状态标识。
  21. 根据权利要求15-20中任一所述的方法，其特征在于，所述根据所述订阅资源生成通知消息并发送给中间节点包括：根据所述订阅资源生成通知消息，并将所述通知消息直接封装在HTTP消息中发送给中间节点，或者根据所述通知消息生成存储转发资源的资源表述，将所述资源表述封装在Restful消息中发送给中间节点。
  22. 一种订阅通知的实现方法，其特征在于，所述方法包括：
    接收到通知消息，所述通知消息包含更新后的被订阅资源的状态，确定所述通知消息包含最新状态标识；
    保存所述接收到的通知消息；
    确定本地保存的根据订阅资源生成的通知消息中的最新通知消息；
    根据所述最新状态标识，在满足消息发送条件时只发送所述最新通知消息。
  23. 根据权利要求22中所述的方法，其特征在于，
    所述保存所述接收到的通知消息具体包括：查找到本地保存有其他通知消息后，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的，将所述接收到的通知消息以替换所述其他通知消息的方式保存到本地；
    所述确定本地保存的根据订阅资源生成的通知消息中的最新通知消息具体包括：确定本地保存的根据所述订阅资源生成的通知消息为最新通知消息。
  24. 根据权利要求22中所述的方法，其特征在于，所述确定本地保存的根据订阅资源生成的通知消息中的最新通知消息具体包括：查找到本地保存有其他通知消息后，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的，确定本地保存的所述通知消息和所述其他通知消息中的最新通知消息。
  25. 根据权利要求23或24所述的方法，其特征在于，
    所述最新状态标识是一个用于识别所述订阅资源且全局唯一的标识；
    所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息 是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的最新状态标识相同。
  26. 根据权利要求23或24所述的方法，其特征在于，
    所述最新状态标识是一个用于识别所述订阅资源且在托管公共服务实体hosting CSE上唯一的标识；
    所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的最新状态标识以及消息发送源地址相同。
  27. 根据权利要求23或24所述的方法，其特征在于，所述查找到本地保存有其他通知消息，所述其他通知消息和所述通知消息是根据相同的订阅资源生成的具体为：查找到本地保存的其他通知消息，所述通知消息和所述其他通知消息包含的订阅资源通用资源标识符(Universal Resource Identifier，URI)相同。
  28. 根据权利要求22中所述的方法，其特征在于，所述方法之后还包括：
    将所述本地保存的根据所述订阅资源生成的通知消息删除。
PCT/CN2014/091492 2013-12-05 2014-11-19 订阅通知的实现方法和装置 WO2015081786A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2016527381A JP6275837B2 (ja) 2013-12-05 2014-11-19 サブスクリプション通知を実施するための方法および装置
EP14867548.1A EP3043530B1 (en) 2013-12-05 2014-11-19 Method and apparatus for implementing subscription notification
KR1020167010322A KR101806257B1 (ko) 2013-12-05 2014-11-19 가입 통지를 구현하기 위한 방법 및 장치
AU2014359963A AU2014359963B2 (en) 2013-12-05 2014-11-19 Method and apparatus for implementing subscription notification
US15/090,401 US20160219125A1 (en) 2013-12-05 2016-04-04 Method and apparatus for implementing subscription notification

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310655509.5A CN103618800B (zh) 2013-12-05 2013-12-05 订阅通知的实现方法和装置
CN201310655509.5 2013-12-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/090,401 Continuation US20160219125A1 (en) 2013-12-05 2016-04-04 Method and apparatus for implementing subscription notification

Publications (1)

Publication Number Publication Date
WO2015081786A1 true WO2015081786A1 (zh) 2015-06-11

Family

ID=50169504

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/091492 WO2015081786A1 (zh) 2013-12-05 2014-11-19 订阅通知的实现方法和装置

Country Status (7)

Country Link
US (1) US20160219125A1 (zh)
EP (1) EP3043530B1 (zh)
JP (1) JP6275837B2 (zh)
KR (1) KR101806257B1 (zh)
CN (3) CN103618800B (zh)
AU (1) AU2014359963B2 (zh)
WO (1) WO2015081786A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017198088A1 (zh) * 2016-05-19 2017-11-23 华为技术有限公司 资源订阅方法、资源订阅装置和资源订阅系统
KR20190002674A (ko) * 2016-05-19 2019-01-08 후아웨이 테크놀러지 컴퍼니 리미티드 자원 구독 방법, 자원 구독 장치, 및 자원 구독 시스템
US11108870B2 (en) 2015-12-31 2021-08-31 Huawei Technologies Co., Ltd. Resource acquiring method and apparatus

Families Citing this family (72)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103618800B (zh) * 2013-12-05 2017-11-03 华为技术有限公司 订阅通知的实现方法和装置
CN104104713B (zh) * 2014-02-24 2018-03-23 中兴通讯股份有限公司 设备触发消息处理方法、承载网网元、m2m节点及系统
CN104936199A (zh) * 2014-03-20 2015-09-23 中兴通讯股份有限公司 一种资源通告管理的方法及公共业务实体
CN105025458B (zh) 2014-04-24 2020-08-11 中兴通讯股份有限公司 一种资源通告的方法、设备和系统
CN105101412A (zh) * 2014-05-21 2015-11-25 中兴通讯股份有限公司 通知消息的发送方法及装置
CN105338586B (zh) * 2014-05-29 2018-09-25 青岛海尔智能家电科技有限公司 一种用于资源控制消息的路由方法及装置
CN105228111A (zh) * 2014-06-13 2016-01-06 中兴通讯股份有限公司 资源订阅处理方法及装置
CN105323186B (zh) * 2014-06-20 2020-04-21 中兴通讯股份有限公司 一种通知消息的负载控制方法和装置
CN105208654B (zh) * 2014-06-20 2020-09-01 中兴通讯股份有限公司 一种通知消息发送方法及装置
CN105323743A (zh) * 2014-07-14 2016-02-10 中兴通讯股份有限公司 订阅资源变更通知的方法及装置
CN105263163B (zh) * 2014-07-18 2019-01-15 中兴通讯股份有限公司 一种通知消息的发送方法、装置和系统
CN105407505B (zh) * 2014-07-18 2019-05-17 青岛海尔智能家电科技有限公司 一种资源控制消息的处理方法及装置
CN105282118B (zh) * 2014-07-21 2019-01-29 中兴通讯股份有限公司 控制资源变更通知消息发送方法及装置
CN105282682B (zh) * 2014-07-25 2020-06-30 中兴通讯股份有限公司 一种实现资源属性通告的方法和公共业务实体
CN105282728B (zh) * 2014-07-25 2019-05-24 中兴通讯股份有限公司 一种删除通告资源的方法和公共业务实体
WO2016026098A1 (zh) * 2014-08-20 2016-02-25 华为技术有限公司 中间节点、基础设施节点及m2m业务消息转发方法
WO2016026145A1 (zh) * 2014-08-22 2016-02-25 华为技术有限公司 标识配置方法、终端管理服务器及基础节点
CN105376706B (zh) * 2014-08-29 2019-12-31 青岛海尔智能家电科技有限公司 一种订阅设备位置信息的方法和装置
CN105406953B (zh) * 2014-09-15 2019-09-06 青岛海尔智能家电科技有限公司 一种聚合通知消息的方法及装置
CN105491620A (zh) * 2014-09-19 2016-04-13 中兴通讯股份有限公司 一种m2m中管理应用资源的方法和注册节点
CN105491507B (zh) * 2014-09-19 2020-10-27 中兴通讯股份有限公司 一种m2m中管理应用资源的方法和注册节点
CN105578381A (zh) * 2014-10-10 2016-05-11 中兴通讯股份有限公司 一种创建订阅资源的方法和装置
CN105592400A (zh) * 2014-10-24 2016-05-18 中兴通讯股份有限公司 一种应用专有节点的注册方法、通信方法和节点
EP3213205A1 (en) 2014-10-31 2017-09-06 Convida Wireless, LLC Managing application relationships in machine-to-machine systems
CN105611484B (zh) 2014-11-03 2020-07-10 中兴通讯股份有限公司 一种m2m节点的管理方法和装置
CN105681210A (zh) 2014-11-14 2016-06-15 中兴通讯股份有限公司 组资源更新处理方法、装置、系统及cse
WO2016074455A1 (zh) * 2014-11-14 2016-05-19 中兴通讯股份有限公司 组资源更新处理方法、装置、系统及cse
CN105722040B (zh) * 2014-12-03 2019-10-25 华为技术有限公司 一种业务消息的传输方法、装置及系统
CN105791000A (zh) * 2014-12-26 2016-07-20 阿尔卡特朗讯 一种用于配置应用的方法与设备
CN104507054B (zh) * 2014-12-29 2020-03-06 海尔优家智能科技（北京）有限公司 一种群组成员信息更新的方法及相关设备
CN105828273A (zh) * 2015-01-06 2016-08-03 中兴通讯股份有限公司 组资源的管理方法及装置
CN107113225B (zh) * 2015-01-09 2020-01-17 华为技术有限公司 机器通信系统中订阅通知的方法和实体
US9992258B2 (en) * 2015-01-13 2018-06-05 Whatsapp Inc. Techniques for managing a remote web client from an application on a mobile device
CN104602180B (zh) * 2015-01-20 2017-12-22 西安工程大学 创建订阅资源系统及创建订阅资源的方法
CN104639429B (zh) * 2015-02-12 2019-06-28 青岛海尔智能家电科技有限公司 一种云平台的消息通知方法及装置
CN105992123B (zh) * 2015-02-12 2020-11-20 中兴通讯股份有限公司 一种控制获取m2m节点位置信息的方法、装置和系统
CN106161196A (zh) * 2015-04-17 2016-11-23 阿尔卡特朗讯 一种获取http消息状态的方法、设备与系统
CN106162715A (zh) * 2015-04-28 2016-11-23 中兴通讯股份有限公司 监控管理方法及装置
CN107950038B (zh) * 2015-05-20 2021-03-23 康维达无线有限责任公司 用于分析和群聚服务层订阅和通知以提高效率的方法和设备
CN106331041A (zh) * 2015-07-01 2017-01-11 中兴通讯股份有限公司 一种刷新通知的方法和装置
CN106534054A (zh) * 2015-09-15 2017-03-22 中兴通讯股份有限公司 多方会话的处理方法及装置
CN105376325A (zh) * 2015-12-07 2016-03-02 青岛农业大学 获取http消息状态的方法、设备与系统
CN114245351A (zh) 2016-07-14 2022-03-25 康维达无线有限责任公司 订阅和通知服务
CN113159910A (zh) * 2016-07-29 2021-07-23 京东方科技集团股份有限公司 进行通知的方法、装置和系统
CN109964495B (zh) * 2016-10-06 2022-06-10 康维达无线有限责任公司 应用的服务层移动性管理
KR101960608B1 (ko) * 2016-10-07 2019-03-20 주식회사 케이티 M2m 시스템에서 응답 메시지를 수신하는 방법 및 그 장치
KR20180039551A (ko) * 2016-10-07 2018-04-18 주식회사 케이티 Receiver CSE에서 효율적인 자원관리 위해 flexBlocking communication method를 처리하는 방법
CN108112007B (zh) * 2016-11-25 2020-08-11 京东方科技集团股份有限公司 信息通知方法、装置及系统
CN108235281B (zh) * 2016-12-12 2023-09-22 京东方科技集团股份有限公司 应用实体创建资源和注册方法、通信节点设备及终端设备
WO2018182065A1 (ko) * 2017-03-30 2018-10-04 전자부품연구원 M2m 시스템에서 다중 리소스 구독 연관 방법
CN109309654B (zh) * 2017-07-28 2022-01-21 京东方科技集团股份有限公司 创建资源的方法及相应的注册方法、服务器和客户端装置
CN107770754A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种通知发送方法、装置和系统
CN109788011B (zh) * 2017-11-13 2021-11-26 京东方科技集团股份有限公司 对资源进行关联的方法、通信终端和通信节点设备
CN108347362B (zh) * 2018-01-09 2020-12-22 海尔优家智能科技（北京）有限公司 一种发现新设备的方法及桥接设备和系统中设备
CN108111630B (zh) * 2018-01-22 2021-11-02 北京奇艺世纪科技有限公司 一种Zookeeper集群系统及其连接方法和系统
CN110167080A (zh) * 2018-02-13 2019-08-23 中兴通讯股份有限公司 订阅信息更新的方法及装置
CN110351111B (zh) 2018-04-04 2021-04-09 中国移动通信有限公司研究院 一种订阅处理方法、网络节点及用户数据库
CN110505591B (zh) * 2018-05-18 2022-09-30 京东方科技集团股份有限公司 订阅服务实体、订阅终端及信息订阅方法和系统
CN110839011A (zh) * 2018-08-17 2020-02-25 视联动力信息技术股份有限公司 监控资源信息的上报方法和装置
KR102137882B1 (ko) * 2018-10-24 2020-07-24 전자부품연구원 구독 만료 관리 방법 및 이를 적용한 m2m 시스템
US12028430B2 (en) 2018-11-28 2024-07-02 Beijing Boe Technology Development Co., Ltd. Event notification method, server device, apparatus and computer storage medium
CN111245875B (zh) * 2018-11-28 2022-03-04 京东方科技集团股份有限公司 事件通知方法、设备、装置和计算机存储介质
KR102434673B1 (ko) 2018-12-13 2022-08-22 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 구독 메시지의 처리 방법, 장치, 컴퓨터 장치 및 저장 매체
US20210360074A1 (en) * 2019-01-29 2021-11-18 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for subscription update
US11102320B2 (en) * 2019-09-03 2021-08-24 International Business Machines Corporation Post-delivery dynamic control of notifications in a push notification life-cycle
WO2021102691A1 (zh) * 2019-11-26 2021-06-03 Oppo广东移动通信有限公司 资源订阅方法、装置、计算机设备和存储介质
CN111125126A (zh) * 2019-11-29 2020-05-08 浪潮(北京)电子信息产业有限公司 一种存储状态管理方法、系统、电子设备及存储介质
CN111427699B (zh) * 2020-03-02 2023-04-11 福建省天奕网络科技有限公司 消息提醒方法、存储介质
CN114520832B (zh) * 2020-11-19 2023-08-25 腾讯科技（深圳）有限公司 一种数据流处理方法、装置、设备及计算机存储介质
CN113271337B (zh) * 2021-04-22 2023-08-18 深圳蓝蛙网络技术有限公司 一种计算机消息订阅方法和装置
CN114731340A (zh) * 2021-04-30 2022-07-08 商汤国际私人有限公司 交互信息的处理方法、装置、设备及存储介质
KR20240080956A (ko) * 2022-11-30 2024-06-07 한국전자기술연구원 신규 데이터 인스턴스 생성을 위한 구독/통지 방법

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102904960A (zh) * 2012-10-19 2013-01-30 北京奇虎科技有限公司 一种基于rss的信息同步系统及方法
CN102984688A (zh) * 2012-11-13 2013-03-20 华为软件技术有限公司 一种订阅资源的清除方法和服务器
CN103209162A (zh) * 2012-01-16 2013-07-17 中国科学院声学研究所 一种Web类业务部署方法及装置
CN103618800A (zh) * 2013-12-05 2014-03-05 华为技术有限公司 订阅通知的实现方法和装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US102690A (en) * 1870-05-03 Improvement in pipe-tongs
CN1783849A (zh) * 2004-12-03 2006-06-07 腾讯科技（深圳）有限公司 一种基于即时通讯平台的消息订阅方法和系统
GB0521355D0 (en) * 2005-10-19 2005-11-30 Ibm Publish/subscribe system and method for managing subscriptions
CN101170522A (zh) * 2007-12-03 2008-04-30 华为技术有限公司 一种发布历史事件的方法及系统
GB2469695A (en) * 2009-04-21 2010-10-27 Ibm Keeping subscriber applications up-to-date
CN101998348A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种计费系统及其进行计费的方法
CN102195985B (zh) * 2011-05-19 2013-08-21 北京邮电大学 一种对呈现业务网络载荷进行控制的系统和方法
WO2014088340A1 (ko) * 2012-12-05 2014-06-12 엘지전자 주식회사 무선 통신 시스템에서 접근 권한 인증을 위한 방법 및 장치
CN104995889B (zh) * 2013-02-19 2019-01-01 Lg电子株式会社 用于修改m2m服务设置的方法及其装置
JP6240312B2 (ja) * 2013-05-16 2017-11-29 エルジー エレクトロニクス インコーポレイティド Ｍ２ｍ通信システムにおいて購読及び通知のための方法及びそのための装置
CN103414589B (zh) * 2013-08-13 2016-11-23 华为技术有限公司 一种管理资源信息的方法及装置
CN105580327B (zh) * 2013-09-27 2018-12-18 Lg电子株式会社 用于在m2m系统中传送通知消息的方法及其装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103209162A (zh) * 2012-01-16 2013-07-17 中国科学院声学研究所 一种Web类业务部署方法及装置
CN102904960A (zh) * 2012-10-19 2013-01-30 北京奇虎科技有限公司 一种基于rss的信息同步系统及方法
CN102984688A (zh) * 2012-11-13 2013-03-20 华为软件技术有限公司 一种订阅资源的清除方法和服务器
CN103618800A (zh) * 2013-12-05 2014-03-05 华为技术有限公司 订阅通知的实现方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3043530A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11108870B2 (en) 2015-12-31 2021-08-31 Huawei Technologies Co., Ltd. Resource acquiring method and apparatus
WO2017198088A1 (zh) * 2016-05-19 2017-11-23 华为技术有限公司 资源订阅方法、资源订阅装置和资源订阅系统
KR20190002674A (ko) * 2016-05-19 2019-01-08 후아웨이 테크놀러지 컴퍼니 리미티드 자원 구독 방법, 자원 구독 장치, 및 자원 구독 시스템
US10637794B2 (en) 2016-05-19 2020-04-28 Huawei Technologies Co., Ltd. Resource subscription method, resource subscription apparatus, and resource subscription system
KR102158654B1 (ko) 2016-05-19 2020-09-22 후아웨이 테크놀러지 컴퍼니 리미티드 자원 구독 방법, 자원 구독 장치, 및 자원 구독 시스템

Also Published As

Publication number Publication date
JP2017504854A (ja) 2017-02-09
JP6275837B2 (ja) 2018-02-07
EP3043530A1 (en) 2016-07-13
US20160219125A1 (en) 2016-07-28
EP3043530B1 (en) 2020-03-25
CN106603394A (zh) 2017-04-26
CN106603394B (zh) 2020-02-14
KR20160060118A (ko) 2016-05-27
AU2014359963A1 (en) 2016-04-28
CN106790676B (zh) 2020-07-07
CN106790676A (zh) 2017-05-31
EP3043530A4 (en) 2016-09-21
CN103618800A (zh) 2014-03-05
CN103618800B (zh) 2017-11-03
AU2014359963B2 (en) 2017-11-30
KR101806257B1 (ko) 2017-12-07

Similar Documents

Publication Publication Date Title
WO2015081786A1 (zh) 订阅通知的实现方法和装置
US11805441B2 (en) Method and system for group communication, group server, and group member device
CN108353094B (zh) 用于m2m服务层的跨资源订阅
US9438601B2 (en) Operating group resources in sub-groups and nested groups
CN106797400B (zh) 用于使得能够经由服务层访问第三方服务的系统和方法
CN105519071A (zh) 使用逻辑信道进行通信的电子装置
WO2014067311A1 (zh) 资源订阅方法及装置
EP3163798B1 (en) Method for processing request messages in wireless communication system, and device for same
US20180316755A1 (en) Method and apparatus for interworking between heterogeneous systems
WO2015117391A1 (zh) 一种实现资源属性通告的方法和公共业务实体
KR102500594B1 (ko) 통신 네트워크에서의 서비스 계층 메시지 템플릿들
WO2015168981A1 (zh) 属性的操作方法及装置
CN113424608B (zh) 用于为网络提供外部服务的实体
CN113709677A (zh) 加入组播广播业务mbs会话的方法及装置
CN114126085B (zh) 工业现场总线通信方法、装置、电子设备及存储介质
Li et al. Efficient oneM2M protocol conversion platform based on NB-IoT access
WO2016109972A1 (zh) 机器到机器系统中宣告属性的方法、公共服务实体和应用实体
KR20220055259A (ko) Nf 서비스 연동 지원장치 및 nf 서비스 연동 지원장치의 동작 방법
KR20240099420A (ko) 하나의 ue의 다중 세션에 대한 동일한 이벤트 구독을 위한 방법 및 장치

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

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2014867548

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014867548

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20167010322

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2014359963

Country of ref document: AU

Date of ref document: 20141119

Kind code of ref document: A

Ref document number: 2016527381

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE