WO2022161284A1 - 一种订阅应用的方法、设备和介质 - Google Patents

一种订阅应用的方法、设备和介质 Download PDF

Info

Publication number
WO2022161284A1
WO2022161284A1 PCT/CN2022/073217 CN2022073217W WO2022161284A1 WO 2022161284 A1 WO2022161284 A1 WO 2022161284A1 CN 2022073217 W CN2022073217 W CN 2022073217W WO 2022161284 A1 WO2022161284 A1 WO 2022161284A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
action
application entity
monitored application
entity
Prior art date
Application number
PCT/CN2022/073217
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 US18/273,294 priority Critical patent/US20240118947A1/en
Publication of WO2022161284A1 publication Critical patent/WO2022161284A1/zh

Links

Images

Classifications

    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y10/00—Economic sectors
    • G16Y10/75—Information technology; Communication
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y20/00—Information sensed or collected by the things
    • G16Y20/10—Information sensed or collected by the things relating to the environment, e.g. temperature; relating to location
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y20/00—Information sensed or collected by the things
    • G16Y20/30—Information sensed or collected by the things relating to resources, e.g. consumed power
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y40/00—IoT characterised by the purpose of the information processing
    • G16Y40/10—Detection; Monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/508—Monitor

Definitions

  • the present disclosure relates to the field of Internet of Things, and in particular, to a method, device and medium for a new type of subscription application.
  • IoT technology is a networked application and service centered on machine intelligent interaction. By embedding wireless or wired communication modules and application processing logic in IoT devices, it can meet users' informatization requirements for monitoring, command and dispatch, data collection and measurement.
  • IoT devices also known as entities
  • the Internet of Things manages various IoT devices by building an IoT management platform.
  • the IoT management platform generates resources corresponding to IoT devices to represent IoT devices, and controls IoT devices by operating the resources.
  • a smart home platform is a common IoT management platform.
  • the physical household appliances are connected to the smart home platform through wired or wireless means, the smart home platform generates virtual household appliances (that is, resources) for the physical household appliances, and the application terminal accesses the virtual household appliances through the smart home platform, and then Realize remote monitoring and control of household appliances.
  • the application terminal can create different smart scenarios through an IoT management platform (such as a smart home platform) and associate IoT devices in the smart scenarios, so as to further manage and control IoT devices.
  • IoT management platform such as a smart home platform
  • the combination between the action resources and subscription resources of the Internet of Things is not close enough, and it is necessary to further improve the process control of the Internet of Things.
  • the present disclosure provides a method, device and medium for a novel subscription application.
  • the new method for subscribing to applications provided by the present disclosure, it is possible to subscribe to changes in the attributes of the resources of the Internet of Things device, and when the attributes of the resources are changed, send a notification associated with the Internet of Things device to the notified application entity.
  • Subscription notifications for action resources so that users can timely know the relevant action resources and whether they are valid, and can also independently decide whether some related action resources continue to be valid or invalid, which is more in line with the actual operation practice of users.
  • Embodiments in accordance with the present disclosure provide a method for subscribing to notifications performed by a generic service entity, comprising: creating, based at least in part on action resources associated with the monitored application entity, a Subscribing to resources; and sending a subscription notification corresponding to the action resource associated with the monitored application entity to the notified application entity in the case of a change in the resource attribute of the monitored application entity.
  • a plurality of action resources associated with a plurality of application entities are created on the general service entity, and the monitored application entity is one of the plurality of application entities.
  • the creation of the action resource associated with the monitored application entity includes: in response to receiving a request to create an action resource, creating the action resource, the action resource being associated with the monitored application entity association.
  • the subscription resource includes an event notification standard attribute
  • the event notification standard of the subscription resource includes a registration monitoring attribute
  • the creating a subscription resource associated with the monitored application entity further The method includes: adding the identifier of the monitored application entity to the subscription monitoring list corresponding to the registered monitoring attribute.
  • the creating a subscription resource associated with the monitored application entity includes: in response to receiving a request to create a subscription resource for the monitored application entity, creating a subscription resource for the monitored application entity. Subscribing to the resource associated with the resource of the application entity, and adding the identifier of the monitored application entity to the subscription monitoring list.
  • the value of the activation state attribute of the action resource is set to enable monitoring of the action resource.
  • after the sending a subscription notification corresponding to the action resource associated with the monitored application entity to the notified application entity further includes: in response to receiving the monitored application entity The value of the activation state attribute of the action resource is set to disable the monitoring of the action resource.
  • the determining of the resource attribute change of the monitored application entity includes: receiving a re-registration request of the monitored application entity; comparing the resource attribute of the re-registered monitored application entity with the monitored application entity The monitored application entity compares the resource attributes before re-registration to determine whether the resource attributes of the monitored application entity are changed.
  • the determining of the resource attribute change of the monitored application entity further includes: in response to receiving a request to change the resource attribute of the monitored application entity, determining that the monitored application entity is changed The resource properties of the entity are changed.
  • the action resource associated with the monitored application entity is created after the monitored application entity completes initial registration.
  • the subscription notification is used for at least one of the following: a notification about the failure of the current action resource of the monitored application entity, about a list of action resources associated with the monitored application entity notification, and notification about the revalidation of the action resource of the monitored application entity.
  • a method performed by a terminal for the Internet of Things comprising: displaying an interface for setting an action of the Internet of Things device, the interface including the setting for setting the action of the Internet of Things device button; in response to the setting button being triggered, an enable button for enabling monitoring of property changes of the IoT device is displayed; in response to the enable button being triggered, a subscription corresponds to the property change of the IoT device
  • the subscription notification of the IoT device wherein the property change of the IoT device causes the IoT device to behave abnormally.
  • the displaying the interface for setting the action of the IoT device includes: displaying an action creation interface for creating an action associated with the IoT device, the action creation interface comprising: At least one of the following items: a selection box for setting the content of the action, a selection box for setting an effective condition of the action, and a selection box for setting an attribute of an IoT device associated with the action.
  • the displaying an interface for creating an action associated with the Internet of Things device comprises: displaying a registration interface for registering the Internet of Things device, the registration interface comprising initiating a request to the Internet of Things device Button for registering IoT devices.
  • the subscription notification is triggered by a property change of the IoT device caused by re-registration of the IoT device.
  • the subscription notification is used for at least one of the following: a notification about the failure of a current action resource of the IoT device, a notification about a list of action resources associated with the IoT device A notification, and a notification about the revalidation of the action resource of the IoT device.
  • a method performed by an Internet of Things system includes: a general service entity, a monitored application entity, and a notified application entity, and the method includes: the monitored application entity
  • the application entity sends a registration request to the general service entity; the general service entity receives the registration request of the monitored application entity, and sends a registration success response to the monitored application entity;
  • the notified application entity Send a registration request to the general service entity;
  • the general service entity receives the registration request of the notified application entity, and sends a registration success response to the notified application entity;
  • the notified application entity sends a registration request to the notified application entity.
  • the general service entity sends an action resource creation request, and the action resource is associated with the monitored application entity; the general service entity receives the action resource creation request sent by the notified application entity, and sends the action resource to the monitored application entity.
  • the notified application entity sends a creation success response; the general service entity, based at least in part on the action resource associated with the monitored application entity, creates a subscription resource associated with the monitored application entity; and in the When the resource attribute of the monitored application entity changes, the general service entity sends a subscription notification corresponding to the action resource associated with the monitored application entity to the notified application entity.
  • An apparatus for performing subscription notification comprising: a subscription resource creation module configured to create a monitored application entity based at least in part on an action resource associated with the monitored application entity Associated subscription resources; a notification module, configured to send a notification corresponding to the action resource associated with the monitored application entity to the notified application entity when the resource attribute of the monitored application entity changes. Subscribe to notifications.
  • a plurality of action resources associated with a plurality of application entities are created on the general service entity, and the monitored application entity is one of the plurality of application entities.
  • the creation of the action resource associated with the monitored application entity includes: in response to receiving a request to create an action resource, creating the action resource, the action resource being associated with the monitored application entity association.
  • the subscription resource includes an event notification standard attribute
  • the event notification standard of the subscription resource includes a registration monitoring attribute
  • the creating a subscription resource associated with the monitored application entity further The method includes: adding the identifier of the monitored application entity to the subscription monitoring list corresponding to the registered monitoring attribute.
  • the subscription resource creation module includes: in response to receiving a request to create a subscription resource for the monitored application entity, creating a subscription resource associated with the resource of the monitored application entity, and adding the identifier of the monitored application entity to the subscription monitoring list.
  • the value of the activation state attribute of the action resource is set to enable monitoring of the action resource.
  • after the sending a subscription notification corresponding to the action resource associated with the monitored application entity to the notified application entity further includes: in response to receiving the monitored application entity The value of the activation state attribute of the action resource is set to disable the monitoring of the action resource.
  • the determining of the resource attribute change of the monitored application entity includes: receiving a re-registration request of the monitored application entity; comparing the resource attribute of the re-registered monitored application entity with the monitored application entity The monitored application entity compares the resource attributes before re-registration to determine whether the resource attributes of the monitored application entity are changed.
  • the determining of the resource attribute change of the monitored application entity further includes: in response to receiving a request to change the resource attribute of the monitored application entity, determining that the monitored application entity is changed The resource properties of the entity are changed.
  • the action resource associated with the monitored application entity is created after the monitored application entity completes the initial registration.
  • the subscription notification is used for at least one of the following: a notification about the failure of the current action resource of the monitored application entity, about a list of action resources associated with the monitored application entity notification, and notification about the revalidation of the action resource of the monitored application entity.
  • a terminal for the Internet of Things comprising: a display action setting module configured to display an interface for setting actions of the Internet of Things device, the interface including the action of the Internet of Things device a setting button for setting; a display property change module configured to display an enable button for enabling monitoring of property changes of the Internet of Things device in response to the setting button being triggered; a subscription notification module configured to respond When the enable button is triggered, a subscription notification corresponding to the property change of the IoT device is subscribed, wherein the property change of the IoT device causes an abnormal action of the IoT device.
  • the displaying the interface for setting the action of the IoT device includes: displaying an action creation interface for creating an action associated with the IoT device, the action creation interface comprising: At least one of the following items: a selection box for setting the content of the action, a selection box for setting an effective condition of the action, and a selection box for setting an attribute of an IoT device associated with the action.
  • the displaying an interface for creating an action associated with the Internet of Things device comprises: displaying a registration interface for registering the Internet of Things device, the registration interface comprising initiating a request to the Internet of Things device Button for registering IoT devices.
  • the subscription notification is triggered by a property change of the IoT device caused by re-registration of the IoT device.
  • the subscription notification is used for at least one of the following: a notification about the failure of a current action resource of the IoT device, a notification about a list of action resources associated with the IoT device A notification, and a notification about the revalidation of the action resource of the IoT device.
  • an electronic device for performing subscription notification including: a processor; and a memory, where the memory stores computer instructions, and when the computer instructions are executed by the processor, the above-mentioned method is implemented.
  • a computer-readable storage medium having computer instructions stored thereon, the computer instructions implementing the above-described method when executed by a processor.
  • Embodiments of the present disclosure provide a method, device, and medium for a novel subscription application. Since it is possible to respond to the property change of the resource of the IoT device, a subscription notification of the action resource associated with the IoT device can be sent to the notified application entity in time, so that the user can be informed of the relevant action resource in time and can be autonomously or automatically controlled by the IoT device.
  • the network management platform determines whether the relevant action resources continue to take effect or fail, so as to be more in line with the user's actual operation practice and enhance the user's IoT experience.
  • FIG. 1A shows a schematic architecture diagram of the Internet of Things according to an embodiment of the present disclosure
  • FIG. 1B shows a schematic diagram of connections between various devices according to an embodiment of the present disclosure
  • FIG. 1C shows an interface diagram of ASN-AE according to an embodiment of the present disclosure
  • 1D shows a schematic diagram of the temperature sensor before and after moving according to an embodiment of the present disclosure
  • FIG. 2 shows a flowchart of a method for subscribing to notifications performed by an application entity in an application service node according to an embodiment of the present disclosure
  • FIG. 3 shows a flowchart of a method for subscribing to notifications performed by a general service entity according to an embodiment of the present disclosure
  • FIG. 4 shows a flow chart of registration of an application entity (AE) or an application program (APP) or a node (Node) with a common service entity (CSE).
  • AE application entity
  • APP application program
  • Node node
  • CSE common service entity
  • FIG. 5A shows a flowchart of a method performed by a terminal for the Internet of Things according to an embodiment of the present disclosure
  • FIG. 5B shows a schematic diagram of an interface of action settings according to an embodiment of the present disclosure
  • 5C shows a schematic diagram of an attribute change monitoring interface according to an embodiment of the present disclosure
  • FIG. 6 shows an interaction diagram between a general service entity and an application entity according to an embodiment of the present disclosure
  • FIG. 7 shows a structural diagram of an electronic device 700 according to an embodiment of the present disclosure.
  • the Internet of Things uses communication technologies such as local networks or the Internet to connect sensors, controllers, machines, people, and things in new ways to form the connection between people and things, and things and things.
  • the Internet of Things is an extension of the Internet. It includes the Internet and all resources on the Internet, and is compatible with all applications on the Internet. With the application of IoT technology in various fields, various new application fields such as smart home, smart transportation, and smart health have emerged.
  • FIG. 1A shows a schematic architecture diagram of the Internet of Things according to an embodiment of the present disclosure.
  • FIG. 1B shows a schematic diagram of connections between various devices according to an embodiment of the present disclosure.
  • 1C shows an interface diagram of ASN-AE according to an embodiment of the present disclosure.
  • Figure 1D shows schematic views of the temperature sensor before and after movement according to an embodiment of the present disclosure.
  • FIG. 1A discloses a schematic architecture diagram of the Internet of Things according to an embodiment of the present disclosure.
  • client devices of various terminals access the network and access the general service layer through the network, and the general service layer supports various applications, thus forming a terminal + network + application architecture.
  • LAN local area network
  • FIG. 1A discloses a schematic architecture diagram of the Internet of Things according to an embodiment of the present disclosure.
  • client devices of various terminals access the network and access the general service layer through the network, and the general service layer supports various applications, thus forming a terminal + network + application architecture.
  • LAN local area network
  • FIG. 1A discloses a schematic architecture diagram of the Internet of Things according to an embodiment of the present disclosure.
  • client devices of various terminals access the network and access the general service layer through the network, and the general service layer supports various applications, thus forming a terminal + network + application architecture.
  • various household devices can use a local area network (LAN) to access a general service platform, and such local area network access can be done in a
  • the local area network can be a personal area network (PAN), for example, taking a wireless personal area network (WPAN) as an example, various technologies such as Bluetooth, IrDA, Home RF, ZigBee, or UWB (Ultra-Wideband Radio) can be used to achieve access.
  • PAN personal area network
  • WPAN wireless personal area network
  • technologies such as Bluetooth, IrDA, Home RF, ZigBee, or UWB (Ultra-Wideband Radio) can be used to achieve access.
  • an IoT entity eg, an IoT terminal device or a software module in a node device
  • the data or information can be stored as a separate resource.
  • the Internet of Things entity may send a request to the general service entity, thereby updating the resource corresponding to the Internet of Things entity stored on the general service entity, so as to reflect the state of the device operated by the Internet of Things entity.
  • This update can be real-time or periodic, or it can be triggered by a certain condition.
  • other IoT entities communicating with the general service entity can learn the status of the device corresponding to the IoT entity by accessing the updated resources; or, other IoT entities communicating with the general service entity can update the resources to operate.
  • the resources referred to here include resources of various entities (eg, can be embodied as software modules in IoT devices, such as AE, CSE, etc.).
  • An entity may represent a software module of a communication device, and a generic service entity may represent a software module of a service platform, which may be local or remote.
  • the operation on the updated resource includes, for example, obtaining the information of the updated resource, deleting the information of the updated resource, notifying the third party of the information of the updated resource, or performing operations on other resources based on the information of the updated resource. operate.
  • a resource may include attributes and sub-resources, where the attributes are used to store information related to the resource (for example, the identifier of the resource, the physical location of the AE corresponding to the resource, the state information of the resource, etc.), and the sub-resource is the next level of the resource
  • a resource includes an index to the next-level resource.
  • the application entity AE may include the application entity ASN-AE in the application service node and the application entity ADN-AE in the application specific node.
  • the application entity ADN-AE can be a temperature sensor, a humidity sensor, an air evolver, a smart light bulb, and the like.
  • the application entity ASN-AE can be TVs, smart home appliances (such as smart refrigerators, smart microwave ovens, etc.), charging cars, desktop computers, notebook computers, smart phones, tablet computers, music players (such as mp3 players, etc.) and other Terminals (eg, mobile terminals, smart terminals) that include a processor and memory.
  • IoT-related applications can be installed on the application entity ASN-AE to set the operation of the application entity ADN-AE through the common service entity CSE.
  • the application entity ASN-AE may send a request to create a subscription of the relevant application entity ADN-AE to the general service entity CSE.
  • the general service entity CSE, the application entity ASN-AE (eg, mobile terminal) in the application service node, the first application entity in the application dedicated node and the second application entity in the application dedicated node may be connected through a network.
  • the above-mentioned devices can communicate with each other directly or indirectly, for example, send and receive data and/or signals with each other through a network.
  • the network can be the Internet of Things (Internet of Things) based on the Internet and/or a telecommunication network, which can be a wired network or a wireless network, for example, it can be a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) ), cellular data communication networks and other electronic networks that can realize the function of information exchange.
  • Internet of Things Internet of Things
  • a telecommunication network which can be a wired network or a wireless network, for example, it can be a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) ), cellular data communication networks and other electronic networks that can realize the function of information exchange.
  • the application entity ADN-AE may be a small IoT device such as a thermometer, an air conditioner, a fan, and a lamp.
  • the CSE can create corresponding resources on them. The CSE controls these ADN-AEs through the operation of the corresponding resources.
  • the operator performs an operation in the ASN-AE (eg, edits a smart scene) and sends a request to the CSE to create a smart scene (eg, a request to create a process management resource, a request to create an action resource, a request to create a state resource) etc.), thereby enabling each ADN-AE to be linked.
  • ASN-AE can set up a smart scene as shown in Figure 1C to control IoT devices, including temperature sensors, air conditioners, and fans. Temperature sensors, air conditioning equipment and fan equipment are placed in the living room. For example, such a smart home scenario can be set: when the temperature sensor detects that the ambient temperature is greater than 31 degrees Celsius, the air conditioner is turned on, the fan is adjusted to the first gear of natural wind, and the head is turned on.
  • the air conditioner in the living room will be turned on, the fan will be adjusted to the first gear of natural wind and the head will be turned on, thereby reducing the ambient temperature in the living room to meet the user's cooling purpose.
  • the user moves the temperature sensor to the balcony, and unchecks the location of the temperature sensor "living room” through ASN-AE (such as a terminal device (such as a mobile phone APP)), and unchecks it. Select “balcony” to complete the change of the location information in the resource properties of the temperature sensor.
  • ASN-AE will not receive any subscription notification to inform the user that the smart scene set before may change accordingly, resulting in this time.
  • the smart scene actually becomes "turn on the air conditioner in the living room when the balcony temperature is greater than 31 degrees Celsius", which is inconsistent with the original intention of the smart home scene set by the user, does not conform to the actual operation practice of the user, and brings a bad experience to the user. .
  • embodiments of the present disclosure provide a new method for subscribing to applications.
  • the new method for subscribing to applications provided by the present disclosure, it is possible to subscribe to changes in the attributes of the resources of the Internet of Things device, and when the attributes of the resources are changed, send a notification associated with the Internet of Things device to the notified application entity.
  • Subscription notifications for action resources so that users can timely know the relevant action resources and whether they are valid, and can also independently decide whether some related action resources continue to be valid or invalid, which is more in line with the actual operation practice of users.
  • the new method for subscribing to applications is divided into a method for subscribing to notifications performed by a common service entity (Common Services Entity, CSE), a method for subscribing to notifications performed by a common service entity (CSE which resides in the Application Service Node, ASN) - Method of subscribing to notifications performed by AE) and method performed by a terminal for the Internet of Things.
  • CSE Common Services Entity
  • ASN Application Service Node
  • AE Application Service Node
  • FIG. 2 shows a flowchart of a method for subscribing to notifications performed by an application entity in an application service node according to an embodiment of the present disclosure.
  • the ASN-AE may send a request to create an action resource, wherein the action resource may be associated with a monitored application entity (eg, ADN-AE), the resource of the monitored application entity Properties are monitored for subscription notifications.
  • a monitored application entity eg, ADN-AE
  • the monitored application entities may include temperature sensors, air conditioning equipment, air purification equipment, desk lamp equipment, and door and window sensors.
  • the ASN-AE may be an application in a mobile phone.
  • the ASN-AE may send a request to the CSE to create an action resource "when the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room", wherein the resource attribute of the temperature sensor is monitored to subscribe to notifications.
  • the ASN-AE may receive a subscription notification corresponding to the action resource associated with the monitored application entity.
  • the above-mentioned ASN-AE can receive the subscription notification, but also the public service entity CSE can receive the subscription notification.
  • the above-mentioned ASN-AE can receive the subscription notification to carry out the related scheme. describe.
  • the monitored application entity may be a temperature sensor.
  • the ASN-AE may receive a subscription notification corresponding to the action resource associated with the temperature sensor. Specifically, assume that the following action resource is set up with respect to the temperature sensor:
  • Action resource 1 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room";
  • Action resource 2 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, open the window device in the living room";
  • Action resource 3 "When the temperature sensor detects that the ambient temperature in the living room is less than 15 degrees Celsius, close the windows in the living room";
  • the ASN-AE can receive the subscription resource corresponding to at least one of the above-mentioned action resources 1 to 3.
  • the subscription notification may include at least one of the following: a notification about the failure of a current action resource of the monitored application entity, a notification about a list of action resources associated with the monitored application entity , and a notification about the revalidation of the action resource of the monitored application entity.
  • the ASN-AE may receive a notification that the current action resource 1 of the temperature sensor is invalid.
  • the ASN-AE may be notified of the list of action resources 2 to 3 associated with the temperature sensor.
  • a button for allowing the user to select to determine whether the corresponding action resource continues to be valid or invalid may be set at a position corresponding to the action resource.
  • the ASN-AE can receive a notification that the action resource 3 of the temperature sensor is revalidated.
  • the method may further include: sending a request for creating a subscription resource, where the event notification standard condition of the subscription resource includes the identifier of the application entity to be monitored.
  • the ASN-AE may send a request for creating a subscription resource to the CSE, where the request specifies an application entity to be monitored, such as a temperature sensor.
  • an identifier eg, AE-ID-Stem
  • a monitored application entity eg, a temperature sensor
  • event notification criteria conditions eventNotificationCriteria conditions
  • the subscription notification may be triggered by the change of the properties of the application entity caused by the re-registration of the monitored application entity.
  • the registration process of the application entity will be introduced later with reference to FIG. 4 , and will not be repeated here. .
  • the monitored application entities may be air conditioning equipment and air purification equipment.
  • the subscription notification may be triggered by a property change corresponding to the air conditioner caused by the repowering of the air conditioner.
  • the subscription notification may be triggered by the air purification equipment being sold by the seller to the buyer after the buyer is powered on, and the subscription notification is sent to the seller's terminal device (eg, a mobile phone APP).
  • the seller's terminal device eg, a mobile phone APP
  • the method before receiving the subscription notification corresponding to the action resource associated with the monitored application entity, the method may further include: sending a request for changing the resource attribute of the monitored application entity; receiving the resource attribute of the monitored application entity Change response.
  • the monitored application entity may be a temperature sensor
  • the ASN-AE may send a request to the CSE to change the location information in the resource attribute of the temperature sensor, for example, cancel the location "living room” before the temperature sensor Check, uncheck "balcony", so as to complete the change of the location information in the resource attribute of the temperature sensor.
  • the CSE after the CSE has processed the above modification request, it will send a successful modification response to the ASN-AE (such as a mobile phone APP), and at this time, the ASN-AE will receive the ADN-AE ( Responses to resource attribute changes such as temperature sensors.
  • ASN-AE such as a mobile phone APP
  • the subscription notification may be triggered by a change of a resource attribute of the monitored application entity.
  • the subscription notification can be triggered by the change of the location information in the resource attribute of the temperature sensor.
  • the subscription notification is triggered after the location change is completed by the mobile phone APP.
  • the action resource is created after the monitored application entity completes the initial registration, and the registration process of the application entity will be introduced later with reference to FIG. 4 , and will not be repeated here.
  • the action resource may also be created after the monitored application entity completes the re-registration. That is, the action resource is created after the monitored application entity completes at least one registration.
  • the ASN-AE may send the CSE an action resource to create "when the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room" request.
  • the method for subscribing to notification performed by the application entity ASN-AE (eg, mobile phone APP) in the application service node is described in detail above with reference to FIG. 2 .
  • the ASN-AE can send a request to create an action resource to the CSE, and include the information associated with the monitored application entity in the request, so that the monitored application
  • the subscription notification can be triggered in time, so that the ASN-AE (such as the mobile APP) can receive the subscription notification corresponding to the action resources of the monitored application entity in time, so that the user can timely know the previously set and
  • the intelligent scenarios related to the monitored application entities are used to determine whether the relevant intelligent scenarios continue to be valid or invalid, which not only conforms to the user's actual operation practice, but also improves the user's IoT experience.
  • FIG. 3 shows a flowchart of a method for subscribing to notifications performed by a general service entity according to an embodiment of the present disclosure.
  • a subscription resource associated with the monitored application entity may be created based at least in part on the action resource associated with the monitored application entity.
  • multiple action resources associated with multiple application entities may be created on the common service entity CSE, and the monitored application entity is one of the multiple application entities.
  • Action resource 1 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room";
  • Action resource 2 "When the temperature sensor detects that the ambient temperature in the living room is less than 16 degrees Celsius, turn off the air conditioner in the living room";
  • Action resource 3 "When the humidity sensor detects that the humidity in the living room is less than 25%, turn on the humidification equipment in the living room";
  • the action resources 1 and 2 of the above-mentioned action resources 1 to 3 are related to the temperature sensor, therefore, the action resources 1 and/or 2 can be used to create an associated temperature sensor. Subscribe to resources.
  • the creation of the action resource associated with the monitored application entity may include: in response to receiving a request to create an action resource, creating the action resource, the action resource being associated with the monitored application entity Associated.
  • the creation of action resource 1 as described above may be in response to receiving a request from ASN-AE to create the following action resource: "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room", The action resource is created by the CSE and is associated with the monitored application entity, such as a temperature sensor.
  • the subscription resource may include an event notification standard attribute
  • the event notification standard of the subscription resource may include a registration monitoring attribute
  • the creating a subscription resource associated with the monitored application entity further It may include: adding the identifier of the monitored application entity to the subscription monitoring list corresponding to the registration monitoring attribute.
  • Table 1 shows the related attributes of subscription ( ⁇ subscription>) resources, including the attribute of event notification criteria (eventNotificationCriteria), the content shown in Table 1 is only It is exemplary, and it may also include other contents, which will not be repeated here.
  • Table 2 shows the relevant attributes included in the standard attributes of event notification included in the subscription resource (such as the registration monitor (regMonitor) attribute).
  • the content shown in Table 2 is only exemplary, and it may also include other content, here I won't go into details.
  • the identifier of the monitored application entity (eg, the AE-ID-stem of the temperature sensor) may be added to the corresponding subscription monitoring list of the regMonitor attribute.
  • the identifiers of all application entities that need to be monitored will be added to the above-mentioned subscription monitoring list (ie, the AE-ID-Stem list).
  • CSE will add the identifier of the application entity to be monitored under ⁇ CSEBase> or ⁇ remoteCSE> to monitor the re-registration status of the monitored application entity, and the above-mentioned re-registration status can be monitored It can be triggered by the re-registration of the application entity of the application entity, or it can be triggered by the change of the resource attribute of the monitored application entity.
  • the CSE creates a subscription resource associated with the resource of the temperature sensor and/or the air conditioner, it will put the identifier of the temperature sensor and/or the air conditioner under the ⁇ CSEBase> or ⁇ remoteCSE>, that is, add it to the Subscribe to the monitoring list to monitor its re-registration status.
  • the creating a subscription resource associated with the monitored application entity may include: in response to receiving a request to create a subscription resource for the monitored application entity, creating a subscription resource for the monitored application entity The subscription resource associated with the resource of the entity is added, and the identifier of the monitored application entity is added to the subscription monitoring list.
  • the ASN-AE may send a request to the CSE to create a subscription resource for a temperature sensor, and after receiving the above request, the CSE may create a subscription resource associated with the resource of the temperature sensor, and assign the identifier of the temperature sensor (such as AE-ID-stem) is added to the subscription monitoring list (that is, the identifier is added under ⁇ CSEBase> or ⁇ remoteCSE>) to enable monitoring of the resources of the temperature sensor.
  • the identifier of the temperature sensor such as AE-ID-stem
  • step S320 in the case that the resource attribute of the monitored application entity is changed, a notification message associated with the monitored application entity may be sent to the notified application entity.
  • the subscription notification corresponding to the action resource in the case that the resource attribute of the monitored application entity is changed.
  • the monitored application entity may be a temperature sensor, and when the resource attribute of the temperature sensor changes, the CSE may send an action associated with the temperature sensor to the application entity such as ASN-AE or an intermediate node (such as a gateway) The subscription notification corresponding to the resource.
  • the determination of the resource attribute change of the monitored application entity may include: receiving a re-registration request of the monitored application entity; comparing the resource attribute of the re-registered monitored application entity with the monitored application entity The resource attributes of the application entity before re-registration are compared to determine whether the resource attributes of the monitored application entity are changed.
  • the registration process of the application entity will be introduced later with reference to FIG. 4 and will not be repeated here.
  • the monitored application entity may be an air purifier with a Global Positioning System (Global Positioning System, GPS) function.
  • the air purifier is located in the living room before moving, and sends an initial registration request to the CSE, and the CSE registers the initial registration request after receiving the initial registration request.
  • the properties of the registered air purifier resource include location information (living room), identifier, etc.; after moving the air purifier to the bedroom, the air purifier sends a re-registration request to the CSE after being powered on, and the CSE re-registers it after receiving the re-registration request.
  • the resource attributes of the air purifier include location information (bedroom), identifiers, etc. Then CSE compares the resources of the air purifier before and after re-registration. At this time, the resource attributes of the air purifier have changed, and the air purifier can be determined. Purifier resource properties changed.
  • the entity being monitored may be a smart light bulb.
  • the smart light bulb sends an initial registration request to the CSE, and the CSE registers the initial registration request after receiving the initial registration request.
  • the properties of the smart light bulb's resources include location information (such as living room), identifiers, etc.; then After the living room is powered off and then powered on again, the smart light bulb sends a re-registration request to the CSE, and the CSE re-registers the re-registration request after receiving the re-registration request.
  • the attributes of the light bulb resource include location information (such as the living room) , identifier, etc.; then CSE compares the resources of the smart light bulbs before and after re-registration. At this time, if the resource attributes of the smart light bulbs are not changed, it can be determined that the resource properties of the smart light bulbs have not changed.
  • the determining of the resource attribute change of the monitored application entity may include: in response to receiving a request to change the resource attribute of the monitored application entity, determining the change of the resource attribute of the monitored application entity. Changes are made to the resource properties of the monitored application entity.
  • the monitored application entity may be a temperature sensor, in which case ASE-AE may send a request to CSE to change the resource properties of the temperature sensor, such as changing the location information in the resource properties of the temperature sensor from the "living room” Change to "bedroom", then, after the CSE receives the request to change the resource property of the temperature sensor, it can determine that the resource property of the temperature sensor has been changed.
  • ASE-AE may send a request to CSE to change the resource properties of the temperature sensor, such as changing the location information in the resource properties of the temperature sensor from the "living room” Change to "bedroom”, then, after the CSE receives the request to change the resource property of the temperature sensor, it can determine that the resource property of the temperature sensor has been changed.
  • the action resource associated with the monitored application entity may be created after the monitored application entity completes the initial registration.
  • an action resource associated with the temperature sensor or the air conditioner may be created.
  • Action resources associated with temperature sensors or air conditioning equipment that is, an IoT device (such as a temperature sensor or an air conditioner) cannot create an action resource associated with an IoT device (such as a temperature sensor or an air conditioner) until it has completed at least one registration with the CSE.
  • the subscription notification may include at least one of the following: a notification about the failure of a current action resource of the monitored application entity, a notification about a list of action resources associated with the monitored application entity , and notification about the revalidation of the action resource of the monitored application entity.
  • the monitored application entity may be a temperature sensor, assuming the following action resource is set up on the temperature sensor:
  • Action resource 1 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room";
  • Action resource 2 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, open the window in the living room";
  • Action Resource 3 "When the temperature sensor detects that the ambient temperature in the living room is less than 15 degrees Celsius, close the windows in the living room”.
  • the notified application entity (such as an application entity in ASN-AE or an intermediate node (such as a gateway)) can receive a notification about the failure of the current action resource 1 of the temperature sensor .
  • the notified application entity may receive action resources 2 to 3 associated with the temperature sensor List of notifications.
  • a key for the user to select to determine whether the corresponding action resource continues to be valid or invalid may be set at a position corresponding to the action resource.
  • the notified application entity (such as ASN-AE or the application entity in an intermediate node (such as a gateway)) can receive A notification about the revalidation of the temperature sensor's action resource 3.
  • the value of the activation state attribute of the action resource may be set to enable monitoring of the action resource.
  • Table 3 shows part of the content of the attribute of the action ( ⁇ action>) resource, which may also include other content, which will not be repeated here.
  • the value of the ActiveStatus attribute of an action resource may be set by the CSE after the above-described creation of the action resource to a value that enables monitoring of the action resource (ie, set to TRUE )
  • a value of "0..1" indicates that a sub-resource/attribute may exist; a value of "1" indicates that a sub-resource/attribute should exist; a fixed attribute multiplicity after (L) indicates that it is a list of values; RW Represents read and write; MA represents Mandatory Announced, that is, the attribute in the original resource is announced to the announced resource, the content of such an announced attribute is the same as the content of the original attribute; OA Optional Announced (Optional Announced) ), that is, the attribute in the original resource can be announced to the announced resource according to the content of the attribute announced at the original resource, such that the content of the announced attribute is the same as the content of the original attribute.
  • CSE can set the value of ActiveStatus to TRUE after creating an action resource such as "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room", so that the above action resource created in CSE It is monitored by the CSE and continues to verify the relevant dependencies after the main event is triggered to determine the trigger related action. For example, when the temperature monitoring detects that the ambient temperature in the living room is greater than 31 degrees Celsius, the CSE monitors that the trigger conditions in the above action resources have been satisfied, and executes the corresponding actions in the above action resources, that is, turns on the air conditioner in the living room, so that the above Action resources are implemented normally.
  • an action resource such as "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room", so that the above action resource created in CSE It is monitored by the CSE and continues to verify the relevant dependencies after the main event is triggered to determine the trigger related action. For example, when the
  • after the sending a subscription notification corresponding to the action resource associated with the monitored application entity to the notified application entity may further include: in response to receiving the monitored application entity's An indication of an action resource failure, setting the value of the activation state attribute of the action resource to disable monitoring of the action resource.
  • the CSE may set the value of ActiveStatus to FALSE in response to receiving an indication that the action resource "turn on the air conditioner in the living room when the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius", so that the above action resource is not executed. related monitoring.
  • the above-mentioned indication of the failure of the action resource may be obtained by the user selecting a relevant button in a relevant subscription notification interface, or may be obtained based on a rule predefined by the IoT management platform.
  • the action "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room” is provided with a button indicating that it can be selected to determine whether the above action continues to take effect or not.
  • the CSE will set the value of ActiveStatus to FALSE, so that after the main event is triggered, it will not continue to verify the related dependencies to determine the trigger related actions.
  • the temperature monitoring detects that the ambient temperature in the living room is greater than 31 degrees Celsius
  • the air conditioner in the living room will not be turned on, so that the above-mentioned action resources cannot be realized, that is, invalid.
  • the seller sets the action about the air purifier in his living room, then the seller sells the air purifier to the buyer, and the buyer sets the action about the air purifier in his bedroom, then the IoT management platform It can be determined according to the distance between the buyer and the seller, the access point and other information that the action resource about this air purifier in the action resource set by the seller is invalid at this time, then the seller passes the application in ASN-AE or intermediate node (such as gateway)
  • the entity can not only receive the subscription notification that the action resource of this air purifier has failed, but also the CSE will set the value of ActiveStatus to FALSE according to the above indication of the failure of the action resource, so that the air purifier will not be continued. monitoring.
  • the method of subscribing to notifications performed by the generic service entity is described in detail above with reference to FIG. 3 and Tables 1-3. It can be seen from the above content that the above-mentioned method for subscribing notifications provided by the present disclosure can closely combine subscription resources with action triggering.
  • the subscription notification corresponding to the action resource associated with the monitored application entity so that the notified application entity can be informed in time whether the related action resource of the monitored application entity is valid or invalid, and then the related actions continue to be triggered. , which better conforms to the user's actual operation practice and enhances the user's IoT experience.
  • the following describes a process for managing action triggering of IoT devices via action resources ⁇ action> and ⁇ dependency> resources.
  • the ⁇ action> resource is created when the user wishes to cause the IoT device to perform a specific action in response to the detection of a specific smart scene event.
  • An event has an object resource associated with it - a change to that object resource causes the managed CSE to conditionally trigger the object resource's target action.
  • Object resources are identified by the subjectResourceID attribute of the ⁇ action> resource, and the evalCriteria attribute of the ⁇ action> resource determines whether the action is conditionally triggered. Collectively, the combination is called an event expression, and the event is the primary event when it is fired.
  • one or more ⁇ dependency> resources can be created as child resources of the ⁇ action> resource.
  • the dependentResourceID attribute identifies the resource on which the event depends.
  • the evalCriteria attribute of the ⁇ dependency> resource determines whether the dependency condition is satisfied.
  • the logical property determines whether the dependent condition is sufficient (SUFFICIENT) or necessary (NECCESARY) for the action to trigger.
  • the evalPriority attribute of the ⁇ action> resource determines the priority of dependencies to apply when evaluating whether an action or action should be triggered based on the primary event. Managed CSEs will evaluate dependencies in order of evalPriority.
  • Step 1 The CSE creates the ⁇ action> resource as a sub-resource of the object resource or another location in the resource tree.
  • the object resource+resource can be any resource and is indicated by the subjectResourceID attribute.
  • CSE can create one or more ⁇ dependency> resources as sub-resources of ⁇ action> resources.
  • Changes to the object's resources may trigger the evaluation of evalCriteria.
  • Step 2 The CSE determines whether the attributes or sub-resources of the object resource are changed. If changed, the CSE updates the object.
  • Step 3 The managed CSE gets the updated result, and evaluates the primary event if the updated object resource matches the criteria defined in the evalCriteria attribute of the ⁇ action> resource.
  • Step 4 If the ActiveStatus property of the ⁇ action> resource is TRUE, the managed CSE will execute to Step 5; if the ActiveStatus property of the ⁇ action> resource is FALSE (for example, the action resource is invalid due to the property change of the object resource), then Subsequent triggering processes are no longer executed.
  • the ActiveStatus property of the ⁇ action> resource is TRUE, the managed CSE will execute to Step 5; if the ActiveStatus property of the ⁇ action> resource is FALSE (for example, the action resource is invalid due to the property change of the object resource), then Subsequent triggering processes are no longer executed.
  • FALSE for example, the action resource is invalid due to the property change of the object resource
  • Step 5 After the main event is triggered in Step 3, if there is at least one ⁇ dependency> subresource of the ⁇ action> resource, the managed CSEs are in the order provided in the evalPriority attribute or in the order based on local policy (if the attribute is missing) to handle each ⁇ dependency> subresource.
  • the method for subscribing notifications provided by the present disclosure adds a new step 4 in the above action triggering process, that is, the judgment of the active status (ActiveStatus), so that the subscription process and the action triggering process are closely combined, so that It better conforms to the user's actual operation practice and enhances the user's IoT experience.
  • ActiveStatus the active status
  • the above-mentioned method for subscribing to notifications provided by the present disclosure uses the registration of application entities. Next, the registration solution will be introduced with reference to FIG. 4 .
  • FIG. 4 shows a flow chart of registration of an application entity (AE) or an application program (APP) or a node (Node) with a common service entity (CSE).
  • AE application entity
  • APP application program
  • Node node
  • CSE common service entity
  • the registration of an application entity (AE) or an application program (APP) or a node (Node) with a common service entity (CSE) includes the following steps and situations.
  • Step 1 (optional): AE or APP or Node establishes a security association with the registrar CSE.
  • Step 2 AE or APP or Node sends a request to create an AE resource to the registrar CSE, and the request includes its identifier (such as App-ID, AE-ID-Stem), that is, sends a Request( CREATE ⁇ AE>).
  • identifier such as App-ID, AE-ID-Stem
  • Step 3 The Registrar CSE determines the allowed AE-ID-Stem values and App-IDs by looking in the Service Subscription Profile (Credential ID, Registrar CSE), or directly from the used certificate (if any) The combination.
  • Step 4 Check that the ⁇ AE> creation request is consistent with the allowed combination determined in Step 3.
  • the AE provides the CSE with the AE identifier AE-ID-Stem (that is, the identifier specified by the AE) starting with 'S', and then the following steps are performed:
  • Step 5 The registrar CSE sends a request for updating or creating an AE announcement to the IN-CSE, that is, sending Request(UPDATE or CREATE ⁇ AEannc>), wherein, creating an AE indicates the initial registration process, and updating the AE indicates a re-registration process.
  • Step 6 The IN-CSE verifies the "update” or “create” request (including credential identification, registered CSE), and updates or creates the ⁇ AEannc> resource.
  • Step 7 The IN-CSE sends the corresponding response to the registrar CSE, that is, Response(UPDATE or CREATE ⁇ AEannc>).
  • Step 8 The registrar CSE uses the AE-ID-Stem provided by the AE to create the ⁇ AE> resource.
  • Step 9 The registrar CSE sends a response to the creation to the AE or APP or Node, that is, sends Response(CREATE ⁇ AE>).
  • an AE eg, the above-mentioned temperature sensor
  • AE can complete the initial registration using the above-mentioned registration process.
  • the attributes of AE change for example, the temperature sensor is moved from the bedroom to the balcony
  • AE may notify CSE of its attribute change by re-registering, that is, the re-registration can be completed through the above registration process to report to CSE Notify it of property changes.
  • AE uses the AE-ID-Stem registered for the first time. Therefore, in the process of re-registration, even if the attributes of AE change, the AE-ID-Stem of AE does not change. Therefore, even if the attributes of the AE are changed due to re-registration, the CSE can still use the method of judging whether the AE-ID-Stem of the re-registered AE is in the subscription monitoring list of the subscription resource to further determine whether to send a message to the ASN-AE. Subscribe to notifications to inform the ASN-AE whether the action resource associated with this re-registered AE has expired.
  • the embodiments of the present disclosure also provide a method executed by a terminal for the Internet of Things, which will be described in detail below with reference to FIGS. 5A to 5C .
  • the terminal may be a handheld device (such as a mobile phone), a tablet computer, or the like.
  • an interface for setting the action of the IoT device may be displayed, and the interface may include a setting button for setting the action of the IoT device.
  • IoT devices can be temperature sensors and air conditioning devices.
  • the currently displayed interface is the interface for setting the actions of the temperature sensor and/or the air conditioner, wherein the setting button corresponding to the temperature sensor or the air conditioner can be clicked by the user, thereby Set the operation of the temperature sensor or air conditioner.
  • step S520 after the user clicks the above-mentioned setting button, the device for IoT may be triggered in response to the setting button, and then display an enable button for enabling monitoring of property changes of the IoT device.
  • an attribute change monitoring interface as shown in Figure 5C will pop up, in which the relevant attributes that can enable attribute change monitoring are listed, such as: location, Expiration time, label, etc., and an enable button is provided at the location corresponding to the shown related properties, which the user can select. Furthermore, when the last start button in Figure 5C is selected, it means that all attribute changes are monitored.
  • step S530 in response to the activation button being triggered, a subscription notification corresponding to a property change of the IoT device may be subscribed, wherein the property change of the IoT device causes an abnormal action of the IoT device.
  • the location property of the temperature sensor is monitored, that is, the subscription notification corresponding to the change of the location property of the temperature sensor is subscribed.
  • the action of the previously set temperature sensor will be abnormal, for example, the previously set action will not be executed.
  • the displaying the interface for setting the action resource of the IoT device may include: displaying an action creation interface for creating an action associated with the IoT device, the action creation interface comprising: At least one of the following items: a selection box for setting the content of the action, a selection box for setting an effective condition of the action, and a selection box for setting an attribute of an IoT device associated with the action.
  • an interface for creating an action may be displayed, and the interface may include a content selection box for setting the action, in the selection box, for example, you can select if a condition is met Turn on the relevant equipment when it is moved, turn on the relevant equipment if it is moved, etc.; the interface can also include a selection box for setting the effective conditions of the action, such as making the action take effect at 16:00 every day; the interface can also include an action association
  • the selection box of the properties of the IoT device such as the selection box of the properties of the temperature sensor associated with the selection action, in the property selection box, select the relevant properties of the temperature sensor, such as the location, etc.
  • the displaying an interface for creating an action associated with the IoT device may include: displaying a registration interface for registering the IoT device, the registering interface may include initiating a request for the IoT device. Button for registering IoT devices.
  • the registration of the temperature sensor may be initiated, such as registration to the home gateway.
  • the subscription notification may be triggered by a property change of the IoT device caused by re-registration of the IoT device.
  • the IoT device may be an air purifier, and the subscription notification is triggered in the case of a property change caused by the re-registration of the air purifier.
  • the subscription notification is used for at least one of the following: a notification about the failure of a current action resource of the IoT device, a notification about a list of action resources associated with the IoT device, and a notification about the revalidation of the action resource of the IoT device.
  • the IoT device may be a temperature sensor, on which the following actions are set:
  • Action resource 1 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, turn on the air conditioner in the living room";
  • Action resource 2 "When the temperature sensor detects that the ambient temperature in the living room is greater than 31 degrees Celsius, open the window device in the living room";
  • Action Resource 3 "When the temperature sensor detects that the ambient temperature in the living room is less than 15 degrees Celsius, close the windows in the living room”.
  • the subscription notification may be used for notification about the expiration of the current action resource 1 of the temperature sensor.
  • the subscription notification may be used for notification of the list of action resources 2 to 3 associated with the temperature sensor.
  • the subscription notification can be used for the notification about the re-validation of the action resource 3 of the temperature sensor.
  • the user can monitor the change of the relevant attributes of the Internet of Things device on the terminal used for the Internet of Things, and subscribe to the corresponding subscription notification, so as to monitor the attribute change of the Internet of Things device in time. , so that the relevant actions are abnormal, which conforms to the user's actual operation practice and enhances the user's Internet of Things experience.
  • FIG. 6 shows an interaction diagram between a general service entity and an application entity according to an embodiment of the present disclosure.
  • the participants in the entire interaction process include a first AE (eg, ASN-AE, an application in a mobile phone), a CSE (eg, a home gateway), and a second AE (eg, ADN-AE, thermometer).
  • a first AE eg, ASN-AE, an application in a mobile phone
  • a CSE eg, a home gateway
  • a second AE eg, ADN-AE, thermometer
  • step S610 the first AE sends a registration request to the CSE.
  • the CSE After receiving the registration request and creating a resource corresponding to the first AE, the CSE sends a registration creation response to the first AE in step S620, indicating registration Successful (see Figure 4 above for the specific registration process).
  • step S630 the second AE sends a registration request to the CSE.
  • the CSE After receiving the registration request and creating a resource corresponding to the second AE, the CSE sends a registration creation response to the second AE in step S640, indicating that the registration Successful (see Figure 4 above for the specific registration process).
  • step 650 the first AE sends a request for creating an action resource "when the temperature sensor detects that the ambient temperature is greater than 31 degrees Celsius, turn on the air conditioner" to the CSE.
  • step S660 sending an action resource creation response to the first AE, indicating that the action resource creation is successful.
  • step S670 the CSE creates a subscription resource associated with the monitored application entity (eg, temperature sensor), and adds the identifier of the temperature sensor to the subscription monitoring list.
  • the monitored application entity eg, temperature sensor
  • step S680 the first AE sends a request to the CSE to change the attributes of the resources of the second AE (eg, temperature sensor), such as changing the location of the temperature sensor from "living room” to "bedroom”; the CSE receives the above-mentioned change request and processes it Then, in step S690, an attribute change response is sent to the first AE, indicating that the change is successful.
  • the resources of the second AE eg, temperature sensor
  • step S6110 the CSE checks whether there is an identifier that is the same as the identifier of the temperature sensor in the subscription monitoring list. If there is, the CSE sends a notification of the subscription to the first AE in step S6120.
  • the notification please refer to the above The related introductions made in conjunction with FIG. 1A to FIG. 5C will not be repeated this time.
  • step S6130 the second AE (such as a temperature sensor) sends a re-registration request to the CSE.
  • the location of the second AE has changed, and the CSE receives the re-registration request and creates and re-registers the
  • step S6140 a re-registration creation response is sent to the second AE, indicating that the re-registration is successful (for the specific registration process, see FIG. 4 above).
  • step S6150 the CSE checks whether there is an identifier identical to the identifier of the temperature sensor in the subscription monitoring list. If there is, the CSE sends a notification of the subscription to the first AE in step S6160.
  • the notification please refer to the above The related introductions made in conjunction with FIG. 1A to FIG. 5C will not be repeated this time.
  • FIG. 7 shows a structural diagram of an electronic device 700 according to an embodiment of the present disclosure.
  • an electronic device 700 may include a processor 701 and a memory 702 . Both the processor 701 and the memory 702 may be connected by a bus 703 .
  • the virtual resource transfer device 700 may be a tower server, a rack server (Rack), a blade server (Blade Server), a rack server and the like.
  • the processor 701 can perform various actions and processes according to programs stored in the memory 702 .
  • the processor 701 may be an integrated circuit chip, which has signal processing capability.
  • the aforementioned processors may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs off-the-shelf programmable gate arrays
  • the methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc., and may be of an X86 architecture or an ARM architecture.
  • the memory 702 stores computer instructions, and when the computer instructions are executed by the processor 701 , the above-mentioned method 200 for sending a cross-resource event notification is implemented.
  • Memory 702 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory.
  • the nonvolatile memory may be read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Memory Bus Random Access Memory
  • Embodiments of the present disclosure also provide an apparatus for subscribing to notifications executed by a general service entity, comprising: a creation module configured to create a connection to the monitored application entity based at least in part on the action resource associated with the monitored application entity subscription resources associated with the application entity; and a notification module, configured to send a notification associated with the monitored application entity to the notified application entity when the resource attribute of the monitored application entity changes The subscription notification corresponding to the action resource.
  • An embodiment of the present disclosure provides an apparatus for performing subscription notification, including: a sending module configured to send a request for creating an action resource, where the action resource is associated with a monitored application entity, wherein the monitored application entity's A resource attribute is monitored for subscription notifications; and a receiving module is configured to receive subscription notifications corresponding to action resources associated with the monitored application entity.
  • An embodiment of the present disclosure provides a method executed by an Internet of Things system
  • the Internet of Things system includes: a general service entity, a monitored application entity, and a notified application entity
  • the method includes: the monitored application
  • the entity sends a registration request to the general service entity; the general service entity receives the registration request of the monitored application entity, and sends a registration success response to the monitored application entity; the notified application entity sends a registration request to the monitored application entity.
  • the general service entity sends a registration request; the general service entity receives the registration request of the notified application entity, and sends a registration success response to the notified application entity; the notified application entity sends a registration request to the notified application entity.
  • the general service entity sends an action resource creation request, and the action resource is associated with the monitored application entity; the general service entity receives the action resource creation request sent by the notified application entity, and sends the notified The application entity sends a creation success response; the general service entity, based at least in part on the action resource associated with the monitored application entity, creates a subscription resource associated with the monitored application entity; and in the monitored application entity When the resource attribute of the monitored application entity is changed, the general service entity sends a subscription notification corresponding to the action resource associated with the monitored application entity to the notified application entity.
  • the present disclosure also provides a computer-readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, the above-mentioned method can be implemented.
  • computer-readable storage media in embodiments of the present disclosure may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. It should be noted that computer-readable storage media described herein are intended to include, but not be limited to, these and any other suitable types of memory.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions.
  • the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.
  • the various example embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, firmware, logic, or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device. While aspects of the embodiments of the present disclosure are illustrated or described as block diagrams, flowcharts, or using some other graphical representation, it is to be understood that the blocks, apparatus, systems, techniques, or methods described herein may be taken as non-limiting Examples are implemented in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Accounting & Taxation (AREA)
  • General Business, Economics & Management (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Environmental & Geological Engineering (AREA)
  • General Health & Medical Sciences (AREA)
  • Toxicology (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种新型订阅应用的方法、设备和介质。所述方法可以由通用服务实体执行，所述方法包括：至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及在所述被监控的应用实体的资源属性变更的情况下，向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。该方法，可以响应于物联网设备的资源的属性变更，及时向被通知的应用实体发送与该物联网设备相关联的动作资源的订阅通知，以让用户及时获知相关的动作资源并自主或由物联网管理平台来决定相关动作资源是继续生效还是失效，从而更加符合用户的实际操作实践，增强用户的物联网体验。

Description

[根据细则37.2由ISA制定的发明名称]　一种订阅应用的方法、设备和介质
本申请要求于2021年01月26日递交的第202110103875.4号中国专利申请的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分。
技术领域
本公开涉及物联网领域，具体涉及一种新型订阅应用的方法、设备和介质。
背景技术
物联网技术是一种以机器智能交互为核心的、网络化的应用与服务。它通过在物联网设备内部嵌入无线或有线通信模块以及应用处理逻辑，实现用户对监控、指挥调度、数据采集和测量等方面的信息化需求。
随着物联网技术的发展，已经有越来越多的物联网设备(又称为实体)接入到物联网中。物联网通过搭建物联网管理平台来管理各个物联网设备。物联网管理平台生成与物联网设备相对应的资源来表示物联网设备，并通过操作资源来控制物联网设备。
智能家居平台是一种常见的物联网管理平台。其中，实体家用电器通过有线或无线方式接入到智能家居平台中，智能家居平台为实体的家用电器生成虚拟家用电器(也即资源)，应用终端通过智能家居平台对虚拟家用电器进行访问，进而实现对家用电器的远程监控和控制。
此外，应用终端可以通过物联网管理平台(如智能家居平台)来创建不同的智能场景并在智能场景中关联物联网设备，从而实现对物联网设备的进一步管控。
目前的物联网的动作资源和订阅资源之间的结合不够紧密，存在对物联网的流程控制进一步改进的必要。
发明内容
针对上述问题，本公开提供了一种新型订阅应用的方法、设备和介质。 利用本公开提供的新型订阅应用的方法，可对物联网设备的资源的属性的变更进行订阅，并在其资源的属性变更的情况下向被通知的应用实体发送与该物联网设备相关联的动作资源的订阅通知，从而使用户可以及时获知相关的动作资源及其是否有效，并且还可以自主决定部分相关的动作资源是继续生效还是失效，进而更加符合用户的实际操作实践。
根据本公开实施例提供了一种由通用服务实体执行的订阅通知的方法，包括：至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及在所述被监控的应用实体的资源属性变更的情况下，向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
根据本公开实施例，其中，所述通用服务实体上创建有与多个应用实体相关联的多个动作资源，所述被监控的应用实体为所述多个应用实体之一。
根据本公开实施例，其中，所述与被监控的应用实体相关联的动作资源的创建包括：响应于接收到创建动作资源的请求，创建所述动作资源，所述动作资源与被监控的应用实体相关联。
根据本公开实施例，其中，所述订阅资源包括事件通知标准属性，所述订阅资源的事件通知标准包括注册监控属性，其中，所述创建与所述被监控的应用实体相关联的订阅资源还包括：将所述被监控的应用实体的标识符添加到所述注册监控属性对应的订阅监控列表中。
根据本公开实施例，其中，所述创建与所述被监控的应用实体相关联的订阅资源包括：响应于接收到创建对被监控的应用实体的订阅资源的请求，创建对所述被监控的应用实体的资源相关联的订阅资源，并将所述被监控的应用实体的标识符添加到所述订阅监控列表中。
根据本公开实施例，其中，在创建所述动作资源之后，将所述动作资源的激活状态属性的值设置为启用对所述动作资源的监控。
根据本公开实施例，其中，在所述向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知之后还包括：响应于接收到所述被监控的应用实体的动作资源失效的指示，将所述动作资源的激活状态属性的值设置为禁用对所述动作资源的监控。
根据本公开实施例，其中，所述被监控的应用实体的资源属性变更的确定包括：接收被监控的应用实体的重新注册请求；将重新注册的被监控的应 用实体的资源属性与所述被监控的应用实体重新注册之前的资源属性进行比较，确定所述被监控的应用实体的资源属性是否变更。
根据本公开实施例，其中，所述被监控的应用实体的资源属性变更的确定还包括：响应于接收到更改所述被监控的应用实体的资源属性的请求，确定对所述被监控的应用实体的资源属性进行变更。
根据本公开实施例，其中，所述与被监控的应用实体相关联的动作资源是在所述被监控的应用实体完成初始注册之后创建的。
根据本公开实施例，其中，所述订阅通知用于以下各项中的至少一项：关于被监控的应用实体的当前动作资源失效的通知、关于与被监控的应用实体相关联的动作资源列表的通知、以及关于被监控的应用实体的动作资源重新生效的通知。
根据本公开实施例提供了一种由用于物联网的终端执行的方法，包括：显示对物联网设备的动作进行设置的界面，所述界面包括对所述物联网设备的动作进行设置的设置按钮；响应于所述设置按钮被触发，显示用于启用对所述物联网设备的属性变更进行监控的启用按钮；响应于所述启用按钮被触发，订阅与所述物联网设备的属性变更对应的订阅通知，其中，所述物联网设备的属性变更导致所述物联网设备的动作异常。
根据本公开实施例，其中，在所述显示对物联网设备的动作进行设置的界面之前包括：显示用于创建与所述物联网设备相关联的动作的动作创建界面，所述动作创建界面包括以下各项中的至少一项：设置所述动作的内容的选择框、设置所述动作的生效条件的选择框、设置所述动作关联的物联网设备的属性的选择框。
根据本公开实施例，其中，在所述显示创建与所述物联网设备相关联的动作的界面之前包括：显示用于注册所述物联网设备的注册界面，所述注册界面包括发起对所述物联网设备进行注册的按钮。
根据本公开实施例，其中，所述订阅通知是由所述物联网设备的重新注册导致的所述物联网设备的属性变更而触发的。
根据本公开实施例，其中，所述订阅通知用于以下项中的至少一项：关于所述物联网设备的当前动作资源失效的通知、关于与所述物联网设备相关联的动作资源列表的通知、以及关于所述物联网设备的动作资源重新生效的通知。
根据本公开实施例提供了一种由物联网系统执行的方法，所述物联网系统包括：通用服务实体、被监控的应用实体和被通知的应用实体，所述方法包括：所述被监控的应用实体向所述通用服务实体发送注册请求；所述通用服务实体接收所述被监控的应用实体的注册请求，并向所述被监控的应用实体发送注册成功响应；所述被通知的应用实体向所述通用服务实体发送注册请求；所述通用服务实体接收所述被通知的应用实体的注册请求，并向所述被通知的应用实体发送注册成功响应；所述被通知的应用实体向所述通用服务实体发送动作资源创建请求，所述动作资源与所述被监控的应用实体相关联；所述通用服务实体接收所述被通知的应用实体发送的动作资源创建请求，并向所述被通知的应用实体发送创建成功响应；所述通用服务实体，至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及在所述被监控的应用实体的资源属性变更的情况下，所述通用服务实体向所述被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
根据本公开实施例提供了一种执行订阅通知的装置，包括：订阅资源创建模块，被配置为至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；通知模块，被配置为在所述被监控的应用实体的资源属性变更的情况下，向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
根据本公开实施例，其中，所述通用服务实体上创建有与多个应用实体相关联的多个动作资源，所述被监控的应用实体为所述多个应用实体之一。
根据本公开实施例，其中，所述与被监控的应用实体相关联的动作资源的创建包括：响应于接收到创建动作资源的请求，创建所述动作资源，所述动作资源与被监控的应用实体相关联。
根据本公开实施例，其中，所述订阅资源包括事件通知标准属性，所述订阅资源的事件通知标准包括注册监控属性，其中，所述创建与所述被监控的应用实体相关联的订阅资源还包括：将所述被监控的应用实体的标识符添加到所述注册监控属性对应的订阅监控列表中。
根据本公开实施例，其中，所述订阅资源创建模块包括：响应于接收到创建对被监控的应用实体的订阅资源的请求，创建对所述被监控的应用实体的资源相关联的订阅资源，并将所述被监控的应用实体的标识符添加到所述 订阅监控列表中。
根据本公开实施例，其中，在创建所述动作资源之后，将所述动作资源的激活状态属性的值设置为启用对所述动作资源的监控。
根据本公开实施例，其中，在所述向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知之后还包括：响应于接收到所述被监控的应用实体的动作资源失效的指示，将所述动作资源的激活状态属性的值设置为禁用对所述动作资源的监控。
根据本公开实施例，其中，所述被监控的应用实体的资源属性变更的确定包括：接收被监控的应用实体的重新注册请求；将重新注册的被监控的应用实体的资源属性与所述被监控的应用实体重新注册之前的资源属性进行比较，确定所述被监控的应用实体的资源属性是否变更。
根据本公开实施例，其中，所述被监控的应用实体的资源属性变更的确定还包括：响应于接收到更改所述被监控的应用实体的资源属性的请求，确定对所述被监控的应用实体的资源属性进行变更。所述与被监控的应用实体相关联的动作资源是在所述被监控的应用实体完成初始注册之后创建的。
根据本公开实施例，其中，所述订阅通知用于以下各项中的至少一项：关于被监控的应用实体的当前动作资源失效的通知、关于与被监控的应用实体相关联的动作资源列表的通知、以及关于被监控的应用实体的动作资源重新生效的通知。
根据本公开实施例提供了一种用于物联网的终端，包括：显示动作设置模块，被配置为显示对物联网设备的动作进行设置的界面，所述界面包括对所述物联网设备的动作进行设置的设置按钮；显示属性变更模块，被配置为响应于所述设置按钮被触发，显示用于启用对所述物联网设备的属性变更进行监控的启用按钮；订阅通知模块，被配置为响应于所述启用按钮被触发，订阅与所述物联网设备的属性变更对应的订阅通知，其中，所述物联网设备的属性变更导致所述物联网设备的动作异常。
根据本公开实施例，其中，在所述显示对物联网设备的动作进行设置的界面之前包括：显示用于创建与所述物联网设备相关联的动作的动作创建界面，所述动作创建界面包括以下各项中的至少一项：设置所述动作的内容的选择框、设置所述动作的生效条件的选择框、设置所述动作关联的物联网设备的属性的选择框。
根据本公开实施例，其中，在所述显示创建与所述物联网设备相关联的动作的界面之前包括：显示用于注册所述物联网设备的注册界面，所述注册界面包括发起对所述物联网设备进行注册的按钮。
根据本公开实施例，其中，所述订阅通知是由所述物联网设备的重新注册导致的所述物联网设备的属性变更而触发的。
根据本公开实施例，其中，所述订阅通知用于以下项中的至少一项：关于所述物联网设备的当前动作资源失效的通知、关于与所述物联网设备相关联的动作资源列表的通知、以及关于所述物联网设备的动作资源重新生效的通知。
根据本公开实施例提供了一种执行订阅通知的电子设备，包括：处理器；存储器，存储器存储有计算机指令，该计算机指令被处理器执行时实现以上所述的方法。
根据本公开实施例提供了一种计算机可读存储介质，其上存储有计算机指令，所述计算机指令被处理器执行时实现以上所述的方法。
本公开实施例提供的一种新型订阅应用的方法、设备和介质。由于可以响应于物联网设备的资源的属性变更，可以及时向被通知的应用实体发送与该物联网设备相关联的动作资源的订阅通知，以让用户及时获知相关的动作资源并自主或由物联网管理平台来决定相关动作资源是继续生效还是失效，从而更加符合用户的实际操作实践，增强用户的物联网体验。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员而言，在没有做出创造性劳动的前提下，还可以根据这些附图获得其他的附图。以下附图并未刻意按实际尺寸等比例缩放绘制，重点在于示出本公开的主旨。
图1A示出了根据本公开的实施例的物联网示意性的架构图；
图1B示出根据本公开的实施例的各个设备之间的连接的示意图；
图1C示出了根据本公开的实施例的ASN-AE的界面图；
图1D示出了根据本公开的实施例的温度传感器移动前后的示意图；
图2示出了根据本公开实施例的一种由应用服务节点中的应用实体执行 的订阅通知的方法的流程图；
图3示出了根据本公开实施例的一种由通用服务实体执行的订阅通知的方法的流程图；
图4示出了应用实体(AE)或应用程序(APP)或节点(Node)向通用服务实体(CSE)注册的流程图。
图5A示出了根据本公开实施例的由用于物联网的终端执行的方法的流程图；
图5B示出了根据本公开实施例的动作设置的界面的示意图；
图5C示出了根据本公开实施例的属性变更监控界面的示意图；
图6示出了根据本公开实施例的通用服务实体和应用实体之间的交互图；
图7示出了根据本公开实施例的电子设备700的结构图。
具体实施方式
为了使得本公开的目的、技术方案和优点更为明显，下面将参照附图详细描述根据本公开的示例实施例。显然，所描述的实施例仅仅是本公开的一部分实施例，而不是本公开的全部实施例，应理解，本公开不受这里描述的示例实施例的限制。
在本说明书和附图中，具有基本上相同或相似步骤和元素用相同或相似的附图标记来表示，且对这些步骤和元素的重复描述将被省略。同时，在本公开的描述中，术语“第一”、“第二”等仅用于区分描述，而不能理解为指示或暗示相对重要性或排序。
随着信息技术尤其是互联网技术的发展，用于实现信息化、远程管理控制和智能化的网络的物联网技术正逐渐成熟。物联网利用局部网络或互联网等通信技术把传感器、控制器、机器、人员和物等通过新的方式联接在一起，形成人与物、物与物相联。物联网是互联网的延伸，它包括互联网及互联网上所有的资源，兼容互联网所有的应用。随着物联网技术在各个领域的应用，出现了诸如智能家居、智能交通、智慧健康等各种新的应用领域。
图1A示出了根据本公开的实施例的物联网示意性的架构图。图1B示出根据本公开的实施例的各个设备之间的连接的示意图。图1C示出了根据本公开的实施例的ASN-AE的界面图。图1D示出了根据本公开的实施例的温 度传感器移动前后的示意图。
图1A公开了本公开实施例的物联网示意性的架构图。如图1A所示，各种终端的客户端设备接入网络，并且通过网络接入到通用服务层，而通用服务层支持各种应用，从而形成了终端+网络+应用的架构。例如，在智能家居领域，各种家用设备可以利用局域网(LAN)接入通用服务平台，这样的局域网接入可以采用诸如无线或者有线方式。可选地，所述局域网可以是个域网(PAN)，例如以无线个域网(WPAN)为例，可以采用Bluetooth、IrDA、Home RF、ZigBee、或UWB(Ultra-Wideband Radio)等各种技术来实现接入。
如前所述，当物联网实体(例如，物联网终端设备或者节点设备中的软件模块)将数据或信息传输到通用服务实体后，该数据或信息可以作为单独的资源进行存储。此外，物联网实体可以向通用服务实体发送请求，从而更新通用服务实体上存储的与该物联网实体对应的资源，以便反映该物联网实体所运行的设备的状态。这种更新可以是实时的或者是周期性的，也可以由某一条件进行触发。由此，与该通用服务实体通信的其他物联网实体可以通过访问更新的资源，而获悉该物联网实体所对应的设备的状态；或者，与该通用服务实体通信的其他物联网实体可以对更新的资源进行操作。应注意，这里所称的资源，包括各种实体(例如，可以体现为物联网设备中的软件模块，诸如AE、CSE等实体)的资源。实体可以表示一通信设备的软件模块，而通用服务实体可以表示服务平台的软件模块，而服务平台可以是本地的或者是远程的。可选地，对更新的资源进行操作包括，例如，获取更新的资源的信息、删除更新的资源的信息、将更新的资源的信息通知给第三方，或者基于更新的资源的信息对其他资源进行操作。
在本公开中，所描述的实体，例如应用实体AE，通用服务实体CSE，以及数据等都可以通过资源进行表示。具体地，资源可以包括属性和子资源，其中属性用来存储资源相关的信息(例如，资源的标识符、资源对应的AE的物理位置、资源的状态信息等)，子资源是资源的下一级资源，资源包括指向下一级资源的索引。
应用实体AE可以包括应用服务节点中的应用实体ASN-AE和应用专用节点中的应用实体ADN-AE。应用实体ADN-AE可以是温度传感器、湿度传感器、空气进化器、智能灯泡等。应用实体ASN-AE可以为电视、智能家电 设备(例如，智能冰箱、智能微波炉等)、充电汽车、台式电脑、笔记本电脑、智能手机、平板电脑、音乐播放器(例如mp3播放器等)以及其他包括处理器和存储器的终端(例如，移动终端，智能终端)。应用实体ASN-AE上可以安装物联网相关应用，以通过通用服务实体CSE来对应用实体ADN-AE的操作进行设置。应用实体ASN-AE可以向通用服务实体CSE发送创建相关应用实体ADN-AE的订阅的请求。
参考图1B，通用服务实体CSE、应用服务节点中的应用实体ASN-AE(例如，手机终端)、应用专用节点中的第一应用实体和应用专用节点中的第二应用实体可以通过网络连接。上述各设备之间可以直接或间接地互相通信，例如，通过网络互相发送和接收数据和/或信号。
网络可以是基于互联网和/或电信网的物联网(Internet of Things)，其可以是有线网也可以是无线网，例如，其可以是局域网(LAN)、城域网(MAN)、广域网(WAN)、蜂窝数据通信网络等能实现信息交换功能的电子网络。
在一些实施例中，应用实体ADN-AE可以是温度计、空调、风扇、灯等小型物联网设备。当这些ADN-AE注册在CSE之后，CSE可在其上创建对应的资源。CSE通过对应资源的操作来控制这些ADN-AE。
在一些实施例中，操作者在ASN-AE进行操作(例如编辑智能场景)，向CSE发送创建智能场景的请求(例如，创建进程管理资源的请求、创建动作资源的请求、创建状态资源的请求等等)，进而使得各个ADN-AE可以联动。
例如，在图1C中涉及的智能家居场景中，各种物联网设备之间可以进行联动。ASN-AE可以设置如图1C所示的智能场景来控制物联网设备，这些物联网设备包括：温度传感器、空调设备、和风扇设备。温度传感器、空调设备和风扇设备均放置在客厅中。例如，可以设置这样的智能家居场景：当温度传感器检测到环境温度大于31摄氏度时，开启空调，并将风扇调节至自然风一档并开启摆头。那么当温度传感器监测到客厅内环境温度大于31摄氏度时，客厅内的空调就会开启，风扇调节至自然风一档并开启摆头，从而使客厅内的环境温度降低，以满足用户降温的目的。
然而，在这样的场景中，如图1D所示，用户将温度传感器移动到阳台，通过ASN-AE(如终端设备(例如手机APP))将温度传感器的位置“客厅”取消勾选，去勾选“阳台”，从而完成所述温度传感器的资源属性中位置信 息的变更，然而此时ASN-AE却不会收到任何订阅通知来告知用户之前设置的智能场景可能相应的变化，导致此时的智能场景实际变成了“阳台温度大于31摄氏度时开启客厅内的空调”，这与用户设置的智能家居场景的初衷不相符，不符合用户的实际操作实践，给用户带来不好的体验。
针对上述问题，本公开实施例提供了一种新型订阅应用的方法。利用本公开提供的新型订阅应用的方法，可对物联网设备的资源的属性的变更进行订阅，并在其资源的属性变更的情况下向被通知的应用实体发送与该物联网设备相关联的动作资源的订阅通知，从而使用户可以及时获知相关的动作资源及其是否有效，并且还可以自主决定部分相关的动作资源是继续生效还是失效，进而更加符合用户的实际操作实践。
具体而言，所述新型订阅应用的方法分为由通用服务实体(Common Services Entity，CSE)执行的订阅通知的方法、由应用服务节点中的应用实体(CSE which resides in the Application Service Node，ASN-AE)执行的订阅通知的方法以及由用于物联网的终端执行的方法。下面对上述方法进行详细地说明。
图2示出了根据本公开实施例的一种由应用服务节点中的应用实体执行的订阅通知的方法的流程图。
参照图2，在S210，所述ASN-AE可以发送创建动作资源的请求，其中，所述动作资源可以与被监控的应用实体(例如，ADN-AE)相关联，被监控的应用实体的资源属性被监控以用于订阅通知。
作为示例，所述被监控的应用实体可以包括温度传感器、空调设备、空气净化设备、台灯设备以及门窗传感器。
作为示例，所述ASN-AE可以是手机中的应用程序。
作为示例，所述ASN-AE可以向CSE发送创建“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调”动作资源的请求，其中，所述温度传感器的资源属性被监控以用于订阅通知。
在S220，所述ASN-AE可以接收与被监控的应用实体相关联的动作资源对应的订阅通知。
根据本公开实施例，不仅可以由上述ASN-AE来接收订阅通知，还可以有公共服务实体CSE来接收订阅通知，在此仅作为示例，由上述ASN-AE来接收订阅通知来进行相关方案的描述。
作为示例，被监控的应用实体可以是温度传感器。所述ASN-AE可以接收到与温度传感器相关联的动作资源对应的订阅通知。具体地，假设关于温度传感器设置了以下动作资源：
动作资源1：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调设备”；
动作资源2：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的窗户设备”；
动作资源3：“当温度传感器监测到客厅内环境温度小于15摄氏度时，关闭客厅内的窗户”；
则所述ASN-AE可以接收到与上述动作资源1至3中至少一个对应的订阅资源。
根据本公开实施例，所述订阅通知可以包括以下各项中的至少一项：关于被监控的应用实体的当前动作资源失效的通知、关于与被监控的应用实体相关联的动作资源列表的通知、以及关于所述被监控的应用实体的动作资源重新生效的通知。
作为示例，当温度传感器从客厅移到卧室时，则所述ASN-AE可以收到关于温度传感器的当前动作资源1失效的通知。
作为示例，当温度传感器从客厅移到卧室时，则所述ASN-AE可以收到与温度传感器相关联的动作资源2至3列表的通知。可选地，在所述通知中，可以在与动作资源对应的位置处设置让用户选择以确定相应的动作资源是继续生效还是失效的按钮。
作为示例，当温度传感器从客厅移到卧室后又重新将温度传感器从客卧室到客厅时，则所述ASN-AE可以收到关于温度传感器的动作资源3重新生效的通知。
根据本公开实施例，所述在发送创建动作资源的请求之后还可以包括：发送创建订阅资源的请求，所述订阅资源的事件通知标准条件中包括要被监控的应用实体的标识符。
作为示例，所述ASN-AE可以向CSE发送创建订阅资源的请求，在所述请求中指明需要被监控的应用实体如温度传感器。
作为示例，所述订阅资源的事件通知标准条件(eventNotificationCriteria conditions)中可以包括被监控的应用实体(如温度传感器)的标识符(如 AE-ID-Stem)。
根据本公开实施例，所述订阅通知可以由被监控的应用实体的重新注册导致的该应用实体的属性变更而触发的，关于应用实体的注册过程后续将结合图4进行介绍，这里不再赘述。
作为示例，被监控的应用实体可以是空调设备和空气净化设备。
作为示例，所述订阅通知可以是由空调设备的重新上电后导致与空调设备对应的属性变更而触发的。
作为示例，所述订阅通知可以是由空气净化设备被卖方卖给买方，由买方上电之后触发的，并且订阅通知发给的是卖方的终端设备(例如手机APP)。
根据本公开实施例，在接收与被监控的应用实体相关联的动作资源对应的订阅通知之前还可以包括：发送更改被监控的应用实体的资源属性的请求；接收被监控的应用实体的资源属性变更的响应。
作为示例，被监控的应用实体可以是温度传感器，在此情况下，所述ASN-AE可以向CSE发送更改温度传感器的资源属性中位置信息的请求，例如将温度传感器之前的位置“客厅”取消勾选，去勾选“阳台”，从而完成所述温度传感器的资源属性中位置信息的变更。
作为示例，在CSE端处理完毕上述更改请求后，就会向所述ASN-AE(如手机APP)发送变更成功响应，则此时，所述ASN-AE就会接收到所述ADN-AE(如温度传感器)的资源属性变更的响应。
根据本公开实施例，所述订阅通知可以是由被监控的应用实体的资源属性变更触发的。
作为示例，在被监控的应用实体为温度传感器的情况下，所述订阅通知可以由温度传感器的资源属性中的位置信息的变更来触发，例如，温度传感器从客厅移到了卧室并在终端设备(如手机APP)完成位置的更改之后触发了所述订阅通知。
根据本公开实施例，所述动作资源是在所述被监控的应用实体完成初始注册之后创建的，关于应用实体的注册过程后续将结合图4进行介绍，这里不再赘述。
作为示例，所述动作资源也可以由被监控的应用实体完成重新注册之后创建。也就是说，所述动作资源是在被监控的应用实体至少完成一次注册之后创建。
作为示例，在温度传感器和空调设备完成向CSE的注册之后，所述ASN-AE可以向CSE发送创建“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调”的动作资源的请求。
以上结合图2详细描述了由应用服务节点中的应用实体ASN-AE(如手机APP)执行的订阅通知的方法。由以上内容可知，在ADN-AE完成注册之后，ASN-AE可以向CSE发送创建动作资源的请求，并在所述请求中包括与被监控的应用实体相关联的信息，从而在被监控的应用实体的属性变更之后，能够及时触发订阅通知，从而使ASN-AE(如手机APP)及时接收到与被监控的应用实体的动作资源对应的订阅通知，进而使用户能够及时知道之前设置的与被监控的应用实体相关的智能场景，以便决定相关智能场景继续有效还是失效，这不仅符合用户的实际操作实践，也能够提高用户的物联网体验。
在以上结合图2详细描述了由ASN-AE执行的订阅通知的方法之后，接下来结合图3详细描述一种由通用服务实体执行的订阅通知的方法。
图3示出了根据本公开实施例的一种由通用服务实体执行的订阅通知的方法的流程图。
参照图3，在S310，可以至少部分地基于与被监控的应用实体相关联的动作资源，来创建与所述被监控的应用实体相关联的订阅资源。
根据本公开实施例，在所述通用服务实体CSE上可以创建有与多个应用实体相关联的多个动作资源，所述被监控的应用实体为所述多个应用实体之一。
作为示例，在CSE上可以创建有与温度传感器、湿度传感器、空调设备及加湿设备相关的以下动作资源：
动作资源1：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调设备”；
动作资源2：“当温度传感器监测到客厅内环境温度小于16摄氏度时，关闭客厅内的空调设备”；
动作资源3：“当湿度传感器检测到客厅内湿度小于25％时，开启客厅内的加湿设备”；
在被监控的应用实体是温度传感器的情况下，上述动作资源1至3中的动作资源1和2与温度传感器相关，因此，可以基于动作资源1和/或2来创建与温度传感器相关联的订阅资源。
根据本公开实施例，所述与被监控的应用实体相关联的动作资源的创建可以包括：响应于接收到创建动作资源的请求，创建所述动作资源，所述动作资源与被监控的应用实体相关联。
作为示例，如上述动作资源1的创建可以是响应于从ASN-AE接收到创建以下动作资源的请求：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调设备”，由CSE来创建所述动作资源，并且上述动作资源是与被监控的应用实体(如温度传感器)相关联的。
根据本公开实施例，所述订阅资源可以包括事件通知标准属性，所述订阅资源的事件通知标准可以包括注册监控属性，其中，所述创建与所述被监控的应用实体相关联的订阅资源还可以包括：将所述被监控的应用实体的标识符添加到所述注册监控属性对应的订阅监控列表中。
根据本公开实施例，如下表1和2所示，其中，表1示出了订阅(<subscription>)资源的相关的属性，包括事件通知标准(eventNotificationCriteria)属性，表1中所示的内容仅是示例性的，其还可以包括其他的内容，这里不在赘述。
表2示出了订阅资源包括的事件通知标准属性中包括的相关属性(如注册监控(regMonitor)属性)，表2中所示的内容仅是示例性的，其还可以包括其他的内容，这里不在赘述。
如表2所示，可以将被监控的应用实体的标识符(如温度传感器的AE-ID-stem)添加到所述regMonitor属性的对应的订阅监控列表中。
Figure PCTCN2022073217-appb-000001
Figure PCTCN2022073217-appb-000002
表1订阅资源的属性
Figure PCTCN2022073217-appb-000003
表2事件通知标准条件
在表1和表2中，值“0..1”表示子资源/属性可能存在；值“0..n”表示子资源/属性可能存在，如果存在，则支持多个实例；用(L)后固定的属性 多重性表示它是一个值列表；RW表示读写。
根据本公开实施例，如表2所示，所有需要被监控的应用实体的标识符都会被添加到上述订阅监控列表中(即AE-ID-Stem列表)。具体而言，CSE会将需要被监控的应用实体的标识符添加在<CSEBase>或<remoteCSE>下，以对被监控的应用实体的重新注册状态进行监控，而上述重新注册状态可以是被监控的应用实体的重新注册触发的，也可以是被监控的应用实体的资源属性变更触发的。
作为示例，上述CSE创建与温度传感器和/或空调设备的资源相关联的订阅资源之后，就会把温度传感器和/或空调设备的标识符放在<CSEBase>或<remoteCSE>下，即添加到订阅监控列表中，从而实现对其重新注册状态进行监控。
根据本公开实施例，所述创建与所述被监控的应用实体相关联的订阅资源可以包括：响应于接收到创建对被监控的应用实体的订阅资源的请求，创建对所述被监控的应用实体的资源相关联的订阅资源，并将所述被监控的应用实体的标识符添加到所述订阅监控列表中。
作为示例，ASN-AE可以向CSE发送创建对温度传感器的订阅资源的请求，而CSE接收到上述请求后，可以创建对温度传感器的资源相关联的订阅资源，并将温度传感器的标识符(如AE-ID-stem)添加到订阅监控列表中(即，将该标识符添加在<CSEBase>或<remoteCSE>下)，以实现对温度传感器的资源的监控。
返回参照图3，在创建订阅资源之后，在步骤S320，在所述被监控的应用实体的资源属性变更的情况下，可以向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
作为示例，被监控的应用实体可以是温度传感器，当温度传感器的资源属性变更的情况下，CSE可以向如ASN-AE或中间节点(如网关)中的应用实体发送与温度传感器相关联的动作资源对应的订阅通知。
根据本公开实施例，所述被监控的应用实体的资源属性变更的确定可以包括：接收被监控的应用实体的重新注册请求；将重新注册的被监控的应用实体的资源属性与所述被监控的应用实体重新注册之前的资源属性进行比较，确定所述被监控的应用实体的资源属性是否变更，其中，关于应用实体的注册过程后续将结合图4进行介绍，这里不再赘述。
作为示例，被监控的应用该实体可以是带有全球定位系统(Global Positioning System，GPS)功能的空气净化器。在这种情况下，空气净化器在移动前位于客厅，并向CSE发送初始注册请求，CSE接收所述初始注册请求后对其进行注册，此时注册的空气净化器的资源的属性包括位置信息(客厅)、标识符等；在将所述空气净化器移动到卧室后，空气净化器上电后向CSE发送重新注册请求，CSE接收到所述重新注册请求后对其进行重新注册，此时空气净化器的资源的属性包括位置信息(卧室)、标识符等，然后CSE将重新注册前后的空气净化器的资源进行比较，此时，空气净化器的资源属性发生了变更，即可以确定空气净化器的资源属性变更。
作为示例，被监控的应用该实体可以是智能灯泡。在这种情况下，智能灯泡向CSE发送初始注册请求，CSE接收所述初始注册请求后对其进行注册，此时，智能灯泡的资源的属性包括位置信息(如客厅)、标识符等；然后在客厅断电又重新上电之后，智能灯泡向CSE发送重新注册的请求，CSE接收到所述重新注册请求后对其进行重新注册，此时，灯泡的资源的属性包括位置信息(如客厅)、标识符等；然后CSE将重新注册前后的智能灯泡的资源进行比较，此时，智能灯泡的资源属性发未发送变更，即可以确定智能灯泡的资源属性未变更。
可选地，根据本公开实施例，所述被监控的应用实体的资源属性变更的确定可以包括：响应于接收到更改所述被监控的应用实体的资源属性的请求，来确定对所述被监控的应用实体的资源属性进行变更。
作为示例，被监控的应用实体可以是温度传感器，在这种情况下，ASE-AE可以向CSE发送更改温度传感器的资源属性的请求，如将温度传感器的资源属性中的位置信息从“客厅”更改为“卧室”，然后，CSE接收到更改温度传感器的资源属性的请求之后，就可以确定对温度传感器的资源属性进行了变更。
根据本公开实施例，所述与被监控的应用实体相关联的动作资源可以是在所述被监控的应用实体完成初始注册之后创建的。
作为示例，温度传感器或空调设备在向CSE完成初始注册之后，可以创建与温度传感器或空调设备相关联的动作资源，当然，也可以在温度传感器或空调设备在向CSE完成重新注册之后，创建与温度传感器或空调设备相关联的动作资源。也就是说，物联网设备(如温度传感器或空调设备)至少向 CSE完成一次注册之后，才可以创建与物联网设备(如温度传感器或空调设备)相关联的动作资源。
根据本公开实施例，所述订阅通知可以包括以下各项中的至少一项：关于被监控的应用实体的当前动作资源失效的通知、关于与被监控的应用实体相关联的动作资源列表的通知、以及关于被监控的应用实体的动作资源重新生效的通知。
作为示例，被监控的应用实体可以是温度传感器，假设关于温度传感器设置了以下动作资源：
动作资源1：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调”；
动作资源2：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的窗户”；
动作资源3：“当温度传感器监测到客厅内环境温度小于15摄氏度时，关闭客厅内的窗户”。
作为示例，当温度传感器从客厅移到卧室时，则被通知的应用实体(如ASN-AE或中间节点(如网关)中的应用实体)可以收到关于温度传感器的当前动作资源1失效的通知。
作为示例，当温度传感器从客厅移到卧室时，则被通知的应用实体(如ASN-AE或中间节点(如网关)中的应用实体)可以收到与温度传感器相关联的动作资源2至3列表的通知。可选地，在所述通知中，可以在与动作资源对应的位置处设置让用户选择以确定相应的动作资源是继续生效还是失效的键。
作为示例，当温度传感器从客厅移到卧室后又重新将温度传感器从客卧室到客厅时，则被通知的应用实体(如ASN-AE或中间节点(如网关)中的应用实体)可以收到关于温度传感器的动作资源3重新生效的通知。
根据本公开实施例，在上述创建动作资源之后，可以将所述动作资源的激活状态属性的值设置为启用对所述动作资源的监控。
根据本公开实施例，如下表3所示，表3示出了动作(<action>)资源的属性的部分内容，其还可以包括其他的内容，这里不在赘述。
在表3中，动作资源的激活状态属性(表3中示出为ActiveStatus)的值可以在上述创建动作资源之后被CSE设置为启用对所述动作资源的监控的 值(即，被设置为TRUE)
Figure PCTCN2022073217-appb-000004
Figure PCTCN2022073217-appb-000005
表3动作资源的属性
在表3中，值“0..1”表示子资源/属性可能存在；值“1”表示应该存 在子资源/属性；用(L)后固定的属性多重性表示它是一个值列表；RW表示读写；MA表示强制公告(Mandatory Announced)，即原始资源中的属性被公告到已公告的资源，这样一个公告的属性的内容和原来属性的内容是一样的；OA可选公告(Optional Announced)，即原始资源中的属性可以根据在原始资源处公告的属性的内容向公告的资源进行公告，这样一个公告属性的内容和原来属性的内容是一样的。
作为示例，CSE在创建如“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调”动作资源后，可以将ActiveStatus的值设置为TRUE，这样在CSE中创建的上述动作资源就会被CSE监控，并且在主要事件被触发之后继续核验相关的依赖关系，以确定触发相关动作。例如，当温度监测到客厅内环境温度大于31摄氏度时，则CSE监控到上述动作资源中的触发条件已被满足，则执行上述动作资源中的相应动作，即开启客厅内的空调，从而使得上述动作资源得以正常实现。
根据本公开实施例，在所述向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知之后还可以包括：响应于接收到所述被监控的应用实体的动作资源失效的指示，将所述动作资源的激活状态属性的值设置为禁用对所述动作资源的监控。
作为示例，CSE响应于接收到“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调”动作资源失效的指示，可以将ActiveStatus的值设置为FALSE，从而不对上述动作资源进行相关的监控。
作为示例，上述动作资源失效的指示可以是通过用户在相关的订阅通知的界面中选择相关的按键来获得，也可以基于物联网管理平台预定义的规则来获得。
作为示例，在相关的订阅通知的界面中动作“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调”后设置有表示可以选择以决定上述动作继续生效还是失效的按键。当用户选择了失效的按键后，CSE就会将ActiveStatus的值设置为FALSE，这样在主要事件被触发之后就不会继续核验相关的依赖关系，以确定触发相关动作。例如，温度监测到客厅内环境温度大于31摄氏度时，客厅内的空调就不会开启，使得上述动作资源得不能实现，即失效。
作为示例，卖方在自家客厅设置了关于空气净化器的动作，之后，卖方 把空气净化器卖给了买方，买方在自己的卧室里设置了关于空气净化器的动作，则此时物联网管理平台可以根据买卖双方的距离、接入点等信息来确定此时卖方设置的动作资源中关于这台空气净化器的动作资源失效，则卖方通过如ASN-AE或中间节点(如网关)中的应用实体不仅可以收到与这台空气净化器的动作资源失效的订阅通知，而且CSE会根据上述动作资源失效的指示，将ActiveStatus的值设置为FALSE，从而使得对对这台空气净化器不进行继续的监控。
以上结合图3和表1-3详细描述了由通用服务实体执行的订阅通知的方法。由以上内容可知，本公开提供的上述订阅通知的方法可以将订阅资源与动作触发进行紧密的结合，当被监控的应用实体的资源属性变更时，可以及时地向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知，从而可以使被通知的应用实体能够及时获知于所述被监控的应用实体的相关动作资源生效还是失效，进而使相关的动作继续触发，这更好地符合了用户的实际操作实践，增强了用户的物联网体验。
由此，订阅资源与动作资源之间进行了紧密的结合。以下描述了用于经由动作资源<action>和<dependency>资源来管理物联网设备的动作触发的过程。
当用户希望响应于检测到特定的智能场景的事件而使得物联网设备执行特定动作时，就创建<action>资源。事件具有与之相关联的对象资源–该对象资源的改变导致托管CSE有条件地触发对象资源的目标动作。对象资源由<action>资源的subjectResourceID属性来标识，并且<action>资源的evalCriteria属性确定动作是否被有条件地触发。总的来说，该组合被称为事件表达式，并且事件在被触发时是主要事件。
为了处理更复杂事件，可以创建一个或多个<dependency>资源作为<action>资源的子资源。在<dependency>资源内，dependentResourceID属性标识事件依赖的资源。<dependency>资源的evalCriteria属性确定是否满足依赖条件。逻辑属性确定依赖条件对于动作触发是足够的(SUFFICIENT)还是必要的(NECCESARY)。最后，<action>资源的evalPriority属性确定在评估是否应该基于主要事件触发动作或操作时要应用的依赖条件的优先级。托管CSE将按照evalPriority优先级顺序来评估依赖条件。
以下描述了托管CSE执行管理事件监控的过程，以及事件发生时，指定 的动作和操作的条件触发，具体步骤如下。
步骤一：CSE将<action>资源创建为对象资源的子资源或资源树中的其它位置。对象资+源可以是任何资源，并且由subjectResourceID属性指示。CSE可以创建一个或多个<dependency>资源作为<action>资源的子资源。
对象资源的改变可能触发evalCriteria的评估。
步骤二：CSE确定对象资源的属性或子资源是否变更。如果变更，则CSE对对象进行更新。
步骤三：托管CSE得到更新的结果，以及评估如果更新的对象资源并且如果更新的对象资源与<action>资源的evalCriteria属性中定义的标准相匹配，则认为触发了主要事件。
步骤四：如果<action>资源的ActiveStatus属性为TRUE，则托管CSE进行执行到步骤五；如果<action>资源的ActiveStatus属性为FALSE(例如，由于对象资源的属性变更导致该动作资源失效)，则后续的触发过程不再执行。
步骤五：在步骤三中触发了主要事件之后，如果至少存在一个<action>资源的<dependency>子资源，则托管CSE按照evalPriority属性中提供的顺序或按照基于本地策略(如果属性缺失)的顺序来处理每个<dependency>子资源。
由以上内容可知，本公开提供的订阅通知的方法，在上述动作触发过程中增加了新的步骤四，即激活状态(ActiveStatus)的判断，从而将订阅过程和动作触发过程进行紧密的结合，以更好地符合用户的实际操作实践，增强了用户的物联网体验。
上述在对本公开提供的订阅通知的方法中，用到了应用实体的注册，接下来将结合图4对注册解决方案进行介绍。
图4示出了应用实体(AE)或应用程序(APP)或节点(Node)向通用服务实体(CSE)注册的流程图。
参照图4，应用实体(AE)或应用程序(APP)或节点(Node)向通用服务实体(CSE)进行注册包括以下步骤和情况。
步骤1(可选)：AE或APP或Node与注册服务商CSE安全关联建立。
步骤2：AE或APP或Node向注册服务商CSE发送创建AE资源的请求，并且该请求中包括其标识符(如App-ID，AE-ID-Stem)，即向注册服务商CSE 发送Request(CREATE<AE>)。
步骤3：注册服务商CSE通过在服务订阅配置文件(凭证ID，注册服务商CSE)中查找，或者，直接从使用过的证书(如果有)确定允许的AE-ID-Stem值和App-ID的组合。
如果在注册服务商CSE上不可用，可能需要可选地从服务订阅配置文件中检索信息。
步骤4：检查<AE>创建请求是否与步骤3中确定的允许组合一致。
以下步骤可以适用于AE(例如上述的温度计)初始注册和重新注册过程，具体如下：
首先，AE向CSE提供以’S’开头的AE标识符AE-ID-Stem(即AE指定的标识符)，然后，进行如下步骤：
步骤5：注册服务商CSE向IN-CSE发送更新或创建AE公告的请求，即发送Request(UPDATE or CREATE<AEannc>)，其中，创建AE表示要初始注册过程，更新AE表示要重新注册过程。
步骤6：IN-CSE验证“更新”或“创建”请求(包括凭证标识、注册CSE),更新或创建<AEannc>资源。
步骤7：IN-CSE向注册服务商CSE发送相应的响应，即发送Response(UPDATE or CREATE<AEannc>)。
步骤8：注册服务商CSE使用由AE提供的AE-ID-Stem来创建<AE>资源。
步骤9：注册服务商CSE向AE或APP或Node发送对创建的响应，即发送Response(CREATE<AE>)。
由此，AE(例如上述的温度传感器)可以利用上述注册过程完成初始注册。但是当AE的属性变更(例如，温度传感器从卧室移至阳台)，此时AE可能会通过重新注册的方式来向CSE告知其的属性变更，即可以通过上述注册过程来完成重新注册来向CSE告知其的属性变更。
并且，由上述重新注册过程可知，AE沿用了第一次注册的AE-ID-Stem。因此，在重新注册的过程中，即使AE的属性变化了，AE的AE-ID-Stem也没有变化。因此，即使是由于重新注册导致的AE的属性变化，CSE仍然可以利用判断重新注册的AE的AE-ID-Stem是否在订阅资源的订阅监控列表中的方式，来进一步确定是否向ASN-AE发送订阅通知，以告知ASN-AE与该重新注册的AE相关联的动作资源是否失效。
本公开实施例除了提供上述订阅通知的方法之外，还提供了一种由用于物联网的终端执行的方法，接下来将结合附图5A至图5C对此进行详细说明。
图5A示出了根据本公开实施例的由用于物联网的终端执行的方法的流程图。所述终端可以是手持设备(如手机)、平板电脑等。
参照图5A，在步骤S510，可以显示对物联网设备的动作进行设置的界面，所述界面可以包括对所述物联网设备的动作进行设置的设置按钮。
作为示例，物联网设备可以是温度传感器和空调设备。
作为示例，如图5B所示，当前显示的界面就是对温度传感器和/或空调设备的动作进行设置的界面，其中，在与温度传感器或空调设备对应的设置按钮是可以被用户点击的，从而对温度传感器或空调设备的动作进行设置。
在步骤S520，在用户点击上述设置按钮后，用于物联网的设备可以响应于所述设置按钮被触发，然后显示用于启用对所述物联网设备的属性变更进行监控的启用按钮。
作为示例，当用户点击了与温度传感器对应的设置按钮时，会弹出如图5C所示的属性变更监控界面，在该界面中，列出了可以启用属性变更监控的相关属性，例如：位置、过期时间、标签等，并且在与所示相关属性对应的位置处设置有启用按钮，用户可以选择该启用按钮。此外，当选择图5C中的最后一个启动按钮时，表示对所有的属性变更均进行监控。
在步骤S530，响应于所述启用按钮被触发，可以订阅与所述物联网设备的属性变更对应的订阅通知，其中，所述物联网设备的属性变更导致所述物联网设备的动作异常。
作为示例，当用户选择了与位置属性相对应的启用按钮后，就会对温度传感器的位置属性就行监控，也就是说，订阅了与温度传感器的位置属性变更对应的订阅通知。当温度传感器的位置属性发生变化时，就会使之前设置的温度传感器的动作异常，比如之前设置的动作不执行。
根据本公开实施例，在所述显示对物联网设备的动作资源进行设置的界面之前可以包括：显示用于创建与所述物联网设备相关联的动作的动作创建界面，所述动作创建界面包括以下各项中的至少一项：设置所述动作的内容的选择框、设置所述动作的生效条件的选择框、设置所述动作关联的物联网设备的属性的选择框。
作为示例，在显示对物联网设备的动作资源进行设置的界面之前，可以 显示用于动作创建的界面，在该界面中可以包括设置动作的内容选择框，在选择框中例如可以选择如果满足条件时开启相关设备、如果被移动时开启相关设备等；在该界面中还可以包括设置所述动作的生效条件的选择框，如每天16:00使动作生效；在该界面中还可以包括动作关联的物联网设备的属性的选择框，如选择动作关联的温度传感器的属性的选择框，在所述属性选择框中，选择温度传感器的相关属性，如位置等。
根据本公开实施例，在所述显示创建与所述物联网设备相关联的动作的界面之前可以包括：显示用于注册所述物联网设备的注册界面，所述注册界面可以包括发起对所述物联网设备进行注册的按钮。
作为示例，在注册界面中，可以发起对温度传感器进行注册，比如注册到家庭网关。
根据本公开实施例，所述订阅通知可以是由所述物联网设备的重新注册导致的所述物联网设备的属性变更而触发的。
作为示例，所述物联网设备可以是空气净化器，在所述空气净化器的重新注册导致的其属性变更的情况下，触发了所述订阅通知。
根据本公开实施例，所述订阅通知用于以下项中的至少一项：关于所述物联网设备的当前动作资源失效的通知、关于与所述物联网设备相关联的动作资源列表的通知、以及关于所述物联网设备的动作资源重新生效的通知。
作为示例，所述物联网设备可以是温度传感器，关于温度传感器设置了以下动作：
动作资源1：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的空调设备”；
动作资源2：“当温度传感器监测到客厅内环境温度大于31摄氏度时，开启客厅内的窗户设备”；
动作资源3：“当温度传感器监测到客厅内环境温度小于15摄氏度时，关闭客厅内的窗户”。
作为示例，当温度传感器从客厅移到卧室时，则所述订阅通知可以用于关于温度传感器的当前动作资源1失效的通知。
作为示例，当温度传感器从客厅移到卧室时，则所述订阅通知可以用于与温度传感器相关联的动作资源2至3列表的通知。
作为示例，当温度传感器从客厅移到卧室后又重新将温度传感器从客卧 室到客厅时，则所述订阅通知可以用于关于温度传感器的动作资源3重新生效的通知。
以上结合图5A至图5C详细描述了由用于物联网的终端执行的方法。根据本公开提供的方法，用户可以在所述用于物联网的终端上对物联网设备的相关属性的变更进行监控，订阅对应的订阅通知，从而对所述物联网设备的属性变更进行及时监控，使相关的动作异常，符合了用户的实际操作实践，增强了用户的物联网体验。
接下来将结合图6以一个示例对上述介绍的内容进行示例性介绍。
图6示出了根据本公开实施例的通用服务实体和应用实体之间的交互图。
如图6所示，整个交互过程的参与方包括第一AE(例如，ASN-AE、手机里的应用程序)、CSE(如家庭网关)以及第二AE(例如，ADN-AE、温度计)。
在步骤S610，第一AE向CSE发送注册请求，CSE在接收所述注册请求并创建与所述第一AE对应的资源之后，在步骤S620，向所述第一AE发送注册创建响应，表示注册成功(具体注册流程可参见上述图4)。
在步骤S630，第二AE向CSE发送注册请求，CSE在接收所述注册请求并创建与所述第二AE对应的资源之后，在步骤S640，向所述第二AE发送注册创建响应，表示注册成功(具体注册流程可参见上述图4)。
在步骤650，第一AE向CSE发送创建动作资源“当温度传感器检测到环境温度大于31摄氏度时，开启空调”的请求，CSE在接收到所述请求并创建对应的动作资源之后，在步骤S660，向所述第一AE发送动作资源创建响应，表示动作资源创建成功。
在步骤S670，CSE创建对被监控的应用实体(如温度传感器)相关联的订阅资源，并把温度传感器的标识符添加到订阅监控列表中。
在步骤S680，第一AE向CSE发送更改第二AE(如温度传感器)的资源的属性的请求，如将温度传感器的位置从“客厅”更改为“卧室”；CSE接收到上述更改请求并处理后，在步骤S690，向第一AE发送属性变更响应，表示更改成功。
在步骤S6110，CSE在订阅监控列表中检查是否存在与温度传感器的标识符相同的标识符，若存在，则在步骤S6120，CSE向第一AE发送该订阅的通知，具体通知的内容可以参见上述结合图1A至图5C进行的相关介绍，此次 不再赘述。
在步骤S6130，第二AE(如温度传感器)向CSE发送了重新注册请求，在该请求中，所述第二AE的位置发生了变化，CSE在接收所述重新注册请求并创建与重新所述第二AE对应的资源之后，在步骤S6140，向所述第二AE发送重新注册创建响应，表示重新注册成功(具体注册流程可参见上述图4)。
在步骤S6150，CSE在订阅监控列表中检查是否存在与温度传感器的标识符相同的标识符，若存在，则在步骤S6160，CSE向第一AE发送该订阅的通知，具体通知的内容可以参见上述结合图1A至图5C进行的相关介绍，此次不再赘述。
图7示出了根据本公开实施例的电子设备700的结构图。
参见图7，电子设备700可以包括处理器701和存储器702。处理器701和存储器702都可以通过总线703相连。虚拟资源转移设备700可以是塔式服务器、机架服务器(Rack)、刀片服务器(Blade Server)、机柜式服务器等。
处理器701可以根据存储在存储器702中的程序执行各种动作和处理。具体地，处理器701可以是一种集成电路芯片，具有信号的处理能力。上述处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等，可以是X86架构或ARM架构的。
存储器702存储有计算机指令，在计算机指令被处理器701执行时实现上述发送跨资源事件通知的方法200。存储器702可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。非易失性存储器可以是只读存储器(ROM)、可编程只读存储器(PROM)、可擦除可编程只读存储器(EPROM)、电可擦除可编程只读存储器(EEPROM)或闪存。易失性存储器可以是随机存取存储器(RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(SDRAM)、双倍数据速率同步动态随机存取存储器DDRSDRAM)、增强型同步动态随机存取存储器(ESDRAM)、同步连接动态随机存取存储器(SLDRAM)和直接内存总线随机 存取存储器(DR RAM)。应注意，本文描述的方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本公开实施例还提供了一种由通用服务实体执行的订阅通知的装置，包括：创建模块，被配置为至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及通知模块，被配置为在所述被监控的应用实体的资源属性变更的情况下，向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
本公开实施例提供了一种执行订阅通知的装置，包括：发送模块，被配置为发送创建动作资源的请求，所述动作资源与被监控的应用实体相关联，其中，被监控的应用实体的资源属性被监控以用于订阅通知；以及接收模块，被配置为接收与被监控的应用实体相关联的动作资源对应的订阅通知。
本公开实施例提供了一种由物联网系统执行的方法，所述物联网系统包括：通用服务实体、被监控的应用实体和被通知的应用实体，所述方法包括：所述被监控的应用实体向所述通用服务实体发送注册请求；所述通用服务实体接收所述被监控的应用实体的注册请求，并向所述被监控的应用实体发送注册成功响应；所述被通知的应用实体向所述通用服务实体发送注册请求；所述通用服务实体接收所述被通知的应用实体的注册请求，并向所述被通知的应用实体发送注册成功响应；所述被通知的应用实体向所述通用服务实体发送动作资源创建请求，所述动作资源与所述被监控的应用实体相关联；所述通用服务实体接收所述被通知的应用实体发送的动作资源创建请求，并向所述被通知的应用实体发送创建成功响应；所述通用服务实体，至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及在所述被监控的应用实体的资源属性变更的情况下，所述通用服务实体向所述被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
本公开还提供了一种计算机可读存储介质，其上存储有计算机指令，该计算机指令被处理器执行时可以实现上述的方法。类似地，本公开实施例中的计算机可读存储介质可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。应注意，本文描述的计算机可读存储介质旨在包括但不限于这些和任意其它适合类型的存储器。
需要说明的是，附图中的流程图和框图，图示了按照本公开各种实施例 的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
一般而言，本公开的各种示例实施例可以在硬件或专用电路、软件、固件、逻辑，或其任何组合中实施。某些方面可以在硬件中实施，而其他方面可以在可以由控制器、微处理器或其他计算设备执行的固件或软件中实施。当本公开的实施例的各方面被图示或描述为框图、流程图或使用某些其他图形表示时，将理解此处描述的方框、装置、系统、技术或方法可以作为非限制性的示例在硬件、软件、固件、专用电路或逻辑、通用硬件或控制器或其他计算设备，或其某些组合中实施。
在上面详细描述的本发明的示例实施例仅仅是说明性的，而不是限制性的。本领域技术人员应该理解，在不脱离本发明的原理和精神的情况下，可对这些实施例或其特征进行各种修改和组合，这样的修改应落入本发明的范围内。

Claims (19)

  1. 一种由通用服务实体执行的订阅通知的方法，包括：
    至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及
    在所述被监控的应用实体的资源属性变更的情况下，向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
  2. 如权利要求1所述订阅通知的方法，其中，所述通用服务实体上创建有与多个应用实体相关联的多个动作资源，所述被监控的应用实体为所述多个应用实体之一。
  3. 如权利要求1所述订阅通知的方法，其中，所述与被监控的应用实体相关联的动作资源的创建包括：
    响应于接收到创建动作资源的请求，创建所述动作资源，所述动作资源与被监控的应用实体相关联。
  4. 如权利要求1所述订阅通知的方法，其中，所述订阅资源包括事件通知标准属性，所述订阅资源的事件通知标准包括注册监控属性，其中，所述创建与所述被监控的应用实体相关联的订阅资源还包括：
    将所述被监控的应用实体的标识符添加到所述注册监控属性对应的订阅监控列表中。
  5. 如权利要求4所述订阅通知的方法，其中，所述创建与所述被监控的应用实体相关联的订阅资源包括：
    响应于接收到创建对被监控的应用实体的订阅资源的请求，创建对所述被监控的应用实体的资源相关联的订阅资源，并将所述被监控的应用实体的标识符添加到所述订阅监控列表中。
  6. 如权利要求3所述订阅通知的方法，其中，在创建所述动作资源之后， 将所述动作资源的激活状态属性的值设置为启用对所述动作资源的监控。
  7. 如权利要求1所述订阅通知的方法，其中，在所述向被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知之后还包括：
    响应于接收到所述被监控的应用实体的动作资源失效的指示，将所述动作资源的激活状态属性的值设置为禁用对所述动作资源的监控。
  8. 如权利要求1所述订阅通知的方法，其中，所述被监控的应用实体的资源属性变更的确定包括：
    接收被监控的应用实体的重新注册请求；
    将重新注册的被监控的应用实体的资源属性与所述被监控的应用实体重新注册之前的资源属性进行比较，确定所述被监控的应用实体的资源属性是否变更。
  9. 如权利要求1所述订阅通知的方法，其中，所述被监控的应用实体的资源属性变更的确定还包括：
    响应于接收到更改所述被监控的应用实体的资源属性的请求，确定对所述被监控的应用实体的资源属性进行变更。
  10. 如权利要求1所述订阅通知的方法，其中，所述与被监控的应用实体相关联的动作资源是在所述被监控的应用实体完成初始注册之后创建的。
  11. 如权利要求1-10中任一项所述订阅通知的方法，其中，所述订阅通知用于以下各项中的至少一项：关于被监控的应用实体的当前动作资源失效的通知、关于与被监控的应用实体相关联的动作资源列表的通知、以及关于被监控的应用实体的动作资源重新生效的通知。
  12. 一种由用于物联网的终端执行的方法，包括：
    显示对物联网设备的动作进行设置的界面，所述界面包括对所述物联网 设备的动作进行设置的设置按钮；
    响应于所述设置按钮被触发，显示用于启用对所述物联网设备的属性变更进行监控的启用按钮；
    响应于所述启用按钮被触发，订阅与所述物联网设备的属性变更对应的订阅通知，其中，所述物联网设备的属性变更导致所述物联网设备的动作异常。
  13. 如权利要求12所述的方法，其中，在所述显示对物联网设备的动作进行设置的界面之前包括：
    显示用于创建与所述物联网设备相关联的动作的动作创建界面，所述动作创建界面包括以下各项中的至少一项：设置所述动作的内容的选择框、设置所述动作的生效条件的选择框、设置所述动作关联的物联网设备的属性的选择框。
  14. 如权利要求13所述的方法，其中，在所述显示创建与所述物联网设备相关联的动作的界面之前包括：
    显示用于注册所述物联网设备的注册界面，所述注册界面包括发起对所述物联网设备进行注册的按钮。
  15. 如权利要求13所述的方法，其中，所述订阅通知是由所述物联网设备的重新注册导致的所述物联网设备的属性变更而触发的。
  16. 如权利要求12-15中任一项所述的方法，其中，所述订阅通知用于以下项中的至少一项：关于所述物联网设备的当前动作资源失效的通知、关于与所述物联网设备相关联的动作资源列表的通知、以及关于所述物联网设备的动作资源重新生效的通知。
  17. 一种由物联网系统执行的方法，所述物联网系统包括：通用服务实体、被监控的应用实体和被通知的应用实体，所述方法包括：
    所述被监控的应用实体向所述通用服务实体发送注册请求；
    所述通用服务实体接收所述被监控的应用实体的注册请求，并向所述被监控的应用实体发送注册成功响应；
    所述被通知的应用实体向所述通用服务实体发送注册请求；
    所述通用服务实体接收所述被通知的应用实体的注册请求，并向所述被通知的应用实体发送注册成功响应；
    所述被通知的应用实体向所述通用服务实体发送动作资源创建请求，所述动作资源与所述被监控的应用实体相关联；
    所述通用服务实体接收所述被通知的应用实体发送的动作资源创建请求，并向所述被通知的应用实体发送创建成功响应；
    所述通用服务实体，至少部分地基于与被监控的应用实体相关联的动作资源，创建与所述被监控的应用实体相关联的订阅资源；以及
    在所述被监控的应用实体的资源属性变更的情况下，所述通用服务实体向所述被通知的应用实体发送与所述被监控的应用实体相关联的动作资源对应的订阅通知。
  18. 一种执行订阅通知的电子设备，包括：
    处理器；
    存储器，存储器存储有计算机指令，该计算机指令被处理器执行时实现如权利要求1-11中任一项所述的方法。
  19. 一种计算机可读存储介质，其上存储有计算机指令，所述计算机指令被处理器执行时实现权利要求1-11中任一项所述的方法。
PCT/CN2022/073217 2021-01-26 2022-01-21 一种订阅应用的方法、设备和介质 WO2022161284A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/273,294 US20240118947A1 (en) 2021-01-26 2022-01-21 Method, device and medium for subscribing applications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110103875.4 2021-01-26
CN202110103875.4A CN114791860A (zh) 2021-01-26 2021-01-26 一种新型订阅应用的方法、设备和介质

Publications (1)

Publication Number Publication Date
WO2022161284A1 true WO2022161284A1 (zh) 2022-08-04

Family

ID=82459619

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/073217 WO2022161284A1 (zh) 2021-01-26 2022-01-21 一种订阅应用的方法、设备和介质

Country Status (3)

Country Link
US (1) US20240118947A1 (zh)
CN (1) CN114791860A (zh)
WO (1) WO2022161284A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219118A (zh) * 2014-09-29 2014-12-17 珠海格力电器股份有限公司 家电设备控制装置和系统
US20180262941A1 (en) * 2017-03-13 2018-09-13 Verizon Patent And Licensing Inc. System and method for registration, monitoring, and notifications regarding groups of internet-of-things (iot) devices
CN108848159A (zh) * 2018-06-14 2018-11-20 电子科技大学 一种物联网设备互操作调度方法
CN110716439A (zh) * 2019-10-21 2020-01-21 合肥美的电冰箱有限公司 家电设备状态同步方法、家电设备及介质
US20200322884A1 (en) * 2018-01-02 2020-10-08 Convida Wireless, Llc Managing network enrollment and redirection for internet-of-things and like devices
CN111984895A (zh) * 2019-05-23 2020-11-24 京东方科技集团股份有限公司 用于订阅资源的方法、装置、设备和存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219118A (zh) * 2014-09-29 2014-12-17 珠海格力电器股份有限公司 家电设备控制装置和系统
US20180262941A1 (en) * 2017-03-13 2018-09-13 Verizon Patent And Licensing Inc. System and method for registration, monitoring, and notifications regarding groups of internet-of-things (iot) devices
US20200322884A1 (en) * 2018-01-02 2020-10-08 Convida Wireless, Llc Managing network enrollment and redirection for internet-of-things and like devices
CN108848159A (zh) * 2018-06-14 2018-11-20 电子科技大学 一种物联网设备互操作调度方法
CN111984895A (zh) * 2019-05-23 2020-11-24 京东方科技集团股份有限公司 用于订阅资源的方法、装置、设备和存储介质
CN110716439A (zh) * 2019-10-21 2020-01-21 合肥美的电冰箱有限公司 家电设备状态同步方法、家电设备及介质

Also Published As

Publication number Publication date
US20240118947A1 (en) 2024-04-11
CN114791860A (zh) 2022-07-26

Similar Documents

Publication Publication Date Title
US11991258B2 (en) Methods, systems, and media for managing notifications directed to multiple applications installed on a user device
US8588990B2 (en) Communicating through a server between appliances and applications
US11782590B2 (en) Scene-operation method, electronic device, and non-transitory computer readable medium
EP3905671A1 (en) Method and device for processing request
CN109407527B (zh) 实现智能设备推荐的方法及装置
CN113572799B (zh) 设备接入控制平台的方法、装置和服务器
WO2016065842A1 (zh) M2m群组及其通告资源创建、信息交互方法和存储介质
US11948009B2 (en) Method and device for operating instance resources based on instance arranging property
US11098914B2 (en) System and method for operating a HVAC system by determining occupied state of a structure via IP address
US11026045B2 (en) Mobile application and system for associating actions with independent geographic locations
WO2022161284A1 (zh) 一种订阅应用的方法、设备和介质
CN114967485A (zh) 设备控制方法、装置、电子设备及存储介质
WO2022161283A1 (zh) 由通用服务实体执行的进程控制的方法
WO2020078087A1 (zh) 音乐播放控制方法、装置、家电设备、终端及介质
US11871498B2 (en) Determining a reachability of an electronic device over multiple wireless communication protocols
WO2021052284A1 (zh) 动作资源的创建方法及执行方法、电子装置和存储介质
JP7236836B2 (ja) データ管理装置、機器制御システム、データ管理方法及びプログラム
JP7173086B2 (ja) 命令を生成するシステム、方法および非一時的な記録媒体
CN112583871B (zh) 发送跨资源事件通知的方法、电子设备和系统
TW202127268A (zh) 伺服器、資訊處理方法、及網路系統
CN114280951A (zh) 智能家居设备的控制方法、装置及存储介质
JP2021027561A (ja) 制御システム、及び、制御方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18273294

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 101123)

122 Ep: pct application non-entry in european phase

Ref document number: 22745159

Country of ref document: EP

Kind code of ref document: A1