WO2021057762A1 - 发送跨资源事件通知的方法、电子设备、***以及计算机可读存储介质 - Google Patents
发送跨资源事件通知的方法、电子设备、***以及计算机可读存储介质 Download PDFInfo
- Publication number
- WO2021057762A1 WO2021057762A1 PCT/CN2020/116984 CN2020116984W WO2021057762A1 WO 2021057762 A1 WO2021057762 A1 WO 2021057762A1 CN 2020116984 W CN2020116984 W CN 2020116984W WO 2021057762 A1 WO2021057762 A1 WO 2021057762A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- cross
- event notification
- entity
- resources
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 238000012795 verification Methods 0.000 claims description 9
- 238000004458 analytical method Methods 0.000 claims description 4
- 238000012544 monitoring process Methods 0.000 description 38
- 238000012806 monitoring device Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 20
- 230000008569 process Effects 0.000 description 12
- 230000004044 response Effects 0.000 description 12
- 230000036961 partial effect Effects 0.000 description 11
- 238000012545 processing Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 8
- 230000008859 change Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 7
- 238000001514 detection method Methods 0.000 description 5
- 230000007613 environmental effect Effects 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012098 association analyses Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000010219 correlation analysis Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000670 limiting effect Effects 0.000 description 1
- 230000002829 reductive effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
- H04L41/0618—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on the physical or logical position
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1033—Signalling gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
Definitions
- the present disclosure relates to a method, electronic device, system, and computer-readable storage medium for sending cross-resource event notifications.
- the Internet of Things manages various Internet of Things devices by building an Internet of Things management platform.
- the Internet of Things management platform generates resources corresponding to the Internet of Things devices to represent the Internet of Things devices, and controls the Internet of Things devices by operating the resources.
- Application terminals can subscribe to notifications of changes in various resources through the Internet of Things management platform, so as to achieve further management and control of Internet of Things devices.
- the smart home platform is a common IoT management platform. Among them, 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.
- virtual household appliances that is, resources
- the embodiments of the present disclosure provide a method, apparatus, electronic device, computer-readable storage medium, and system for sending cross-resource event notifications, which can realize that any two or more resources among multiple resources meet the requirements of cross-resource event notifications.
- cross-resource event notifications are sent to the resource subscription entity, thereby meeting the differentiated needs of users and improving the processing efficiency of notifications.
- the embodiment of the present disclosure provides a method for sending a cross-resource event notification, including:
- a cross-resource subscription request is received from a resource subscription entity, the cross-resource subscription request is used to subscribe to multiple resources, and the cross-resource subscription request includes multiple single-resource event notification rules and cross-resource event notification rules; determining the m resources The n resources in s satisfy the single-resource event notification rule and the cross-resource event notification rule, and the cross-resource event notification is sent to the resource subscription entity, where m and n are positive integers greater than or equal to 2.
- the embodiments of the present disclosure provide a system for sending cross-resource event notifications, including:
- a device for sending cross-resource event notifications the device being a subscription service device; a resource subscription entity configured to send a cross-resource subscription request to the subscription service device; an application entity configured to send a resource operation to the subscription service device Request;
- the means for sending cross-resource event notifications includes: a cross-resource subscription unit configured to receive a cross-resource subscription request from a resource subscription entity, the cross-resource subscription request is used to subscribe to multiple resources, the cross-resource subscription The request includes multiple single-resource event notification rules and cross-resource event notification rules; the notification unit is configured to determine that n of the m resources satisfy the single-resource event notification rule and the cross-resource event notification rule, and report to the The resource subscription entity sends cross-resource event notifications, where m and n are positive integers greater than or equal to 2.
- An embodiment of the present disclosure provides an electronic device that sends a cross-resource event notification.
- the electronic device for sending cross-resource event notification includes a processor and a memory.
- the memory stores computer instructions, and when the computer instructions are executed by the processor, the foregoing method of sending cross-resource event notifications is realized.
- the embodiments of the present disclosure provide a computer-readable storage medium having computer instructions stored thereon, and when the computer instructions are executed by a processor, the foregoing method of sending cross-resource event notifications is implemented.
- Fig. 1A shows a schematic diagram of a scenario where a cross-resource event notification is sent.
- Fig. 1B shows a schematic diagram of an interaction process between devices participating in sending a cross-resource event notification.
- Fig. 2A shows a schematic diagram of a method for sending a cross-resource event notification according to an embodiment of the present disclosure.
- Fig. 2B shows a flowchart of a method for sending a cross-resource event notification according to an embodiment of the present disclosure.
- Fig. 3 shows an exemplary cross-resource subscription resource structure diagram according to an embodiment of the present disclosure.
- Fig. 4 shows a schematic diagram of an example according to an embodiment of the present disclosure.
- Fig. 5 shows a flowchart according to an example of an embodiment of the present disclosure.
- Fig. 6 shows a schematic diagram of an apparatus for sending a cross-resource event notification according to an embodiment of the present disclosure.
- Fig. 7 shows a structural diagram of an electronic device for sending a cross-resource event notification according to an embodiment of the present disclosure.
- entity may refer to hardware such as an Internet of Things device, an Internet of Things gateway, or an Internet of Things server, or the term “entity” may refer to a software component of the Internet of Things application layer or the Internet of Things (public) service layer.
- AE application entities
- CSE data
- resources can be represented as resources.
- a data structure that can be uniquely addressed with a unique address for example, a URI (Uniform Resource Identifier)
- URI Uniform Resource Identifier
- resources can be represented as specific data structures, and resources can be logically connected to each other. Therefore, the public service layer of IoT devices, IoT gateways, AE, CSE, or IoT servers can all include resources.
- resources are defined in the IoT system.
- the Internet of Things application may perform communication based on resources that are instantiated as resource types.
- resources can be used for IoT services such as application registration, reading sensor values, and so on.
- unique address information for example, URI
- the resource can have sub-resources and attributes.
- the attribute stores information about the resource itself, and may not include sub-resources.
- Sub-resources can include attributes and its own sub-resources.
- the sub-resources can be remote CSE resources, application entity resources, access control resources, container resources, group resources, subscription resources, and so on.
- FIG. 1A shows a schematic diagram of a scenario 100A of sending a cross-resource event notification.
- FIG. 1B shows a schematic diagram of an interaction process 100B between devices participating in sending cross-resource event notifications.
- the subscription service device 110, the first application entity 130, the second application entity 140, and the resource subscription entity 150 may be connected through the network 120.
- the above-mentioned devices may directly or indirectly communicate with each other, for example, send and receive data and/or signals to and from each other through the network 120.
- the network 120 may be the Internet of Things (Internet of Things) based on the Internet and/or a telecommunication network, and it may be a wired network or a wireless network.
- Internet of Things Internet of Things
- LAN local area network
- MAN metropolitan area network
- WAN wide area network
- cellular data communication network and other electronic networks that can realize the function of information exchange.
- the subscription service device 110 can centrally manage and control application entities (for example, the first application entity 130 and the second application entity 140).
- the subscription service device 110 may also send a cross-resource event notification to the resource subscription entity 150 via the network 120 to notify the application entity of the resource change status.
- the subscription service device 110 may be a server, and it may also be other electronic devices including a processor and a memory.
- the subscription service device 110 may also be a common service entity (CSE, Common Service Entity) in the Internet of Things.
- CSE Common Service Entity
- the resource subscription entity 150 and the application entity may be computing devices including a processor and a memory.
- the first application entity 130 and the second application entity 140 may be TVs, smart home appliances (for example, smart refrigerators, smart microwave ovens, etc.), charging cars, desktop computers, notebook computers, smart phones, tablet computers, music players ( Such as mp3 player, etc.) and other terminals including a processor and a memory (for example, mobile terminals, smart terminals).
- the first application entity 130 is a fixed monitoring device
- the second application entity 140 is a mobile monitoring device, which can be used to monitor the surrounding environment (for example, to monitor the temperature, humidity, and light conditions of the surrounding environment). monitor).
- the resource subscription entity 150 and the application entity may be the same entity or different entities.
- the resource subscription entity 150, the first application entity 130, and the second application entity 140 may be application entities (AE, Application Entity) in the Internet of Things.
- the resource subscription entity 150, the first application entity 130, and the second application entity 140 may also be general service entities.
- an AE can register with another CSE. After the registration is successful, a resource corresponding to the AE (or CSE) will be created on the CSE.
- AE can operate on the resources on the CSE through operations such as creation, update, acquisition, and deletion.
- a resource can include attributes and sub-resources. The attributes are used to store resource-related information (for example, the identifier of the resource, the physical location of the AE corresponding to the resource, the status information of the resource, etc.), and the sub-resource is the next level of the resource.
- Resources, resources include an index to the next level of resources.
- the operator performs an operation on the resource subscription entity 150 (for example, edits a resource subscription request), sends a resource subscription request to the subscription service device 110, and then receives a notification sent by the subscription service device 110 when the resource changes.
- the notification can indicate resource changes.
- FIG. 1B shows a typical resource subscription interaction process 100B.
- the resource subscription entity 150 sends a cross-resource subscription request to the subscription service device 110, which is used to subscribe to the application data of the first application entity 130 and the second application entity 140 at the same time, and set the cross-resource event notification rule "when When the time interval between the first application entity 130 and the second application entity 140 sending application data meets the time threshold, the application data of both are sent".
- the subscription service device 110 After receiving the cross-resource subscription request, the subscription service device 110 completes the operation of simultaneously subscribing to the application data of the first application entity 130 and the second application entity 140 in operation 102, and automatically informs the resource when the above-mentioned cross-resource event notification rule is satisfied.
- the subscribing entity 150 sends cross-resource event notifications.
- the subscription service device 110 will send a cross-resource subscription response to the resource subscription entity 150 in operation 103 to inform the resource subscription entity 150 that it has successfully set the cross-resource subscription.
- the subscription service device 110 may use relevant information of the first application entity 130 and the second application entity 140 to construct the first resource corresponding to the first monitoring device 130 and the second resource corresponding to the second monitoring device 140 within it. Two resources, and control the first monitoring device 130 and the second monitoring device 140 through the first resource and the second resource.
- the operator can also operate the application entity to send a resource operation request to the subscription service device 110.
- the application entity may also automatically send a resource operation request to the subscription service device 110 without manual intervention.
- the second application entity 130 may send a first resource operation request including the first application data to the subscription service device 110.
- the subscription service device 110 records the first application data according to the first resource operation request, and records the first moment when the first resource operation request is received.
- the subscription server 110 sends a first operation response to the second application entity 140.
- the first application entity 130 and the subscription service device 110 may also obtain the second application data and the second moment when the second application data is received through a second resource operation request.
- the subscription service device 110 determines whether the time difference between the first time and the second time meets a time threshold. If the time threshold is met, the subscription service device 110 sends the first application data and the second application data to the resource subscription entity 150 in operation 111. Then, in operation 112, the resource subscribing entity 150 may perform further processing on the first application data and the second application data. For example, the resource subscribing entity 150 may determine the first location to obtain the first application data and obtain the second application data. Whether the distance between the second positions meets the requirements of the position threshold.
- the resource subscription entity 150 may send a calibration request in operation 113 to notify the second application entity 140 that it should perform calibration based on the first application data and the second application data .
- the second application entity 140 may return a calibration response to the resource subscription entity 150 in operation 114 after completing the calibration.
- the subscription service device 110 cannot determine the location relationship between the first application entity 130 and the second application entity 140. Therefore, the events generated by the first resource and the second resource cannot be processed further.
- the second application entity 140 is a mobile monitoring device, and the first application data needs to be calibrated.
- the resource subscription entity 150 not only needs the generation time of the first application data (that is, the first time) to be close to the generation time of the second application data (that is, the second time), but also requires the difference between the first location and the second location. The distance is closer. Since the subscription service device cannot determine the distance between the first location and the second location, the resource subscription entity 150 is required to further process the first application data and the second application data, thereby increasing the calculation of the resource subscription entity 150 burden. Since the resource subscription entity 150 is usually a mobile terminal, an operator is required to manually determine whether the first application data and the second application data can be used for calibration, which increases the operating burden of the operator and brings inconvenience to the operator.
- the subscription service device 110 can only pay attention to the situation where the first resource corresponding to the first application entity 130 and the second resource corresponding to the second application entity 140 generate events within the time threshold.
- the resource subscribing entity 150 may prefer to obtain resource occurrence events corresponding to any number of application entities among multiple application entities. For example, suppose there is a third application entity near the second application entity, and when the second application entity 140 obtains the first application data, the third application entity also obtains the third application data. At this time, the resource subscription entity 150 may wish to calibrate the second application entity 140 based on the third application data and/or the first application data.
- the resource subscription entity 150 needs to send another cross-resource subscription request to the subscription service device 110 to subscribe to the cross-resource event of the second application entity and the third application entity. This is not only complicated in the process, but also occupies excessive computing resources and storage space of the subscription service device 110 and the resource subscription entity 150, thereby reducing the processing efficiency of notifications.
- the present disclosure proposes an improved method, device, electronic device, computer-readable storage medium, and system for sending cross-resource event notifications, which can realize that any two or more resources among multiple resources can satisfy
- the cross-resource event notification rule the cross-resource event notification is sent to the resource subscription entity, thereby meeting the differentiated needs of users and improving the efficiency of system message processing.
- FIG. 2A shows a schematic diagram of a method 200 for sending a cross-resource event notification according to an embodiment of the present disclosure.
- FIG. 2B shows a flowchart of a method 200 for sending a cross-resource event notification according to an embodiment of the present disclosure.
- the method 200 may include some or all of the operations shown in FIGS. 2A and 2B (for example, some or all of operations 2010 and 2020). Of course, the method 200 may also include other operations not shown in FIGS. 2A and 2B.
- the method 200 may be executed by the subscription service device 110.
- the method 200 may also be executed by any other electronic device having a communication function and a computing function.
- the subscription service device 110 is taken as an example for description.
- a cross-resource subscription request is received from the resource subscription entity 150.
- Cross-resource subscription requests are used to subscribe to multiple resources.
- the cross-resource subscription request includes multiple single-resource event notification rules and cross-resource event notification rules.
- the first resource corresponds to the first application entity 130
- the second resource corresponds to the second application entity 140.
- the aforementioned cross-resource subscription request can be used to subscribe to multiple resources, including the aforementioned first resource and second resource, and any number of other resources.
- the single-resource event notification rule indicates a rule for a certain resource to generate an event.
- any resource in the subscription service device 110 has a single-resource event notification rule corresponding to the resource.
- Any two single-resource event notification rules in the aforementioned multiple single-resource event notification rules may be the same or different.
- a single-resource event notification rule may indicate that when a single resource generates an event, the resource subscription entity is notified.
- the single-resource event notification rule may also indicate that when a single resource generates a specific event, one or more operations are performed on the resource or the physical device corresponding to the resource.
- the 2A may include the event notification rule of the first resource and the event notification rule of the second resource.
- the event notification rule of the first resource and the event notification rule of the second resource may be the same or different, which is not limited in the present disclosure.
- the aforementioned multiple single-resource event notification rules may also include event notification rules for other resources.
- multiple events may be generated for the same resource operation request.
- a certain operation request may indicate that the temperature data stored in the first resource and the second resource are increased by 5%, and event 1-increase the temperature data of the first resource by 5%, and event 2-increase the temperature data of the second resource The temperature data increased by 5%.
- two single-resource event notification rules are different, multiple resource operation requests may be required to generate multiple events.
- the event notification rule of the first resource may indicate that when any change occurs in the first resource, a notification indicating the change of the first resource is sent to the resource subscription entity 150.
- the first application entity 130 sends a second resource operation request to the subscription service device 110, and the second resource operation request indicates that the location of the first resource has changed.
- a resource operation request is received before sending the cross-resource event notification.
- the resource operation request may include one or more of location information, application data, and operation time.
- n of the m resources satisfy the single-resource event notification rule and the cross-resource event notification rule.
- the application data may be monitoring data.
- the subscription service device 110 may update these resources according to the resource operation request. The location information, application data, and operation time in the resource corresponding to the application entity, thereby realizing the resource to accurately represent the state of the application entity.
- the subscription service device 110 will send a notification of the location information change of the first resource to the resource subscription entity 150.
- the event notification rule of the first resource may also indicate other operations, for example, it may indicate to change at least one of the resource level, location information, and status information of the first resource. This disclosure does not limit the content of the single-resource event notification rule.
- the cross-resource subscription event notification rule may indicate a rule for generating events for n resources among multiple resources.
- the cross-resource subscription event notification rule may indicate that when n resources among multiple resources generate an event, a cross-resource event notification is sent to the resource subscription entity 150, or an operation is performed on n resources.
- the cross-resource subscription event notification rule may indicate that the cross-resource event notification is sent when the value of the application data of any two resources in the multiple resources has increased to a specific threshold.
- the cross-resource subscription event notification rule may also indicate that when the location information of any two resources in the multiple resources changes, the distance between the locations of the two resources is calculated.
- a change in the location information of the resource may indicate that the physical location of the application entity corresponding to the resource has changed.
- the application entity is a mobile device, it may be useful for the subscription service device to know the physical location of the application entity.
- This disclosure does not limit the content of the cross-resource subscription event notification rule.
- the subscription service device 110 may also return a cross-resource subscription response to the resource subscription entity in operation 2011.
- n of the m resources satisfy the single-resource event notification rule and the cross-resource event notification rule, and the cross-resource event notification is sent to the resource subscription entity, where m and n are greater than or equal to A positive integer of 2.
- the foregoing n resources satisfying the cross-resource event notification rule may include, but are not limited to, a combination of one or more of the following items: the location information of the n resources satisfies the cross-resource event notification rule, and the value of n satisfies the cross-resource event notification rule.
- the event notification rule, the application data of n resources satisfy the cross-resource event notification rule, and the operation of the n resources satisfy the cross-resource event notification rule at all times.
- the cross-resource event notification rule can correspondingly indicate but is not limited to one or a combination of the following items: the distance threshold between the positions of n resources, the threshold of n, and the application data of n resources.
- the similarity threshold between the two and the time threshold of the operation time of n resources can be used.
- the distance threshold may be one or more of the following items: the maximum distance, the minimum distance, and the distance range between the locations of n resources.
- the threshold of n may be one or more of the following: the maximum value MAX, the minimum value MIN, and both the maximum value MAX and the minimum value MIN of n.
- the similarity threshold may be one or more of the following: the lowest similarity, the highest similarity, and the similarity range of the application data of n resources.
- the time threshold may be one or more of the following items: the maximum value, the minimum value, or the time difference range of the difference between the operation moments of the n resources.
- the cross-resource event notification rule may indicate the distance threshold between the locations of n resources and the similarity threshold between the application data of the n resources.
- the cross-resource event notification rule may also indicate a threshold of n, a threshold of similarity between application data of n resources, and a threshold of time between operation moments of n resources.
- the foregoing n resources satisfying the cross-resource event notification rule may also include n resources satisfying other unmentioned cross-resource event notification rules, which is not limited in this disclosure.
- the event notification rule of the first resource is to update the application data of the first resource when the application data of the first resource changes
- the event notification rule of the second resource is to increase the value of the application data of the second resource Notify the resource subscribing entity when
- the cross-resource subscription event notification rule instructs to send a cross-resource event notification when the value of the application data of any two of the multiple resources increases.
- the second application entity 140 sends a first resource operation request to the subscription service device 110 in operation 2100
- the first application entity 130 sends a second resource operation request to the subscription service device 110 in operation 2200.
- the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150 based on the event notification rule of the second resource.
- the subscription service device 110 may send a first operation response to the second application entity 140.
- the subscription service device 110 updates the application data of the first resource based on the event notification rule of the first resource.
- the subscription service device may return a second operation response to the first application entity 130.
- the first resource and the second resource also satisfy the cross-resource event notification rule, and the subscription service device 110 may send a cross-resource event notification to the resource subscription entity 150 in operation 2020.
- the method 200 for sending a cross-resource event notification can implement a cross-resource event notification to a resource subscription entity when any two or more resources in a plurality of resources satisfy the cross-resource event notification rule. This simplifies the complexity of operations, satisfies the needs of users for differentiation, and improves the efficiency of system message processing.
- the method 200 for sending a cross-resource event notification is further exemplified below.
- the resource operation request includes location information.
- the n resources satisfying the cross-resource event notification rule further includes: the location information of the n resources satisfy the cross-resource event notification rule, where the cross-resource event notification rule indicates a distance threshold between the locations of the n resources.
- the subscription service device 110 receives a resource operation request including the location information of the first application entity 130 (for example, the second resource operation request in FIG. 2A).
- the resource subscription entity 105 also receives a resource operation request including the location information of the second application entity 140 (for example, the first resource operation request in FIG. 2A).
- the subscription service device 110 determines whether the event notification rule of the first resource is satisfied, and if it is satisfied, an event of the first resource is generated. It is assumed that the event notification rule of the first resource (that is, the single-resource event notification rule) stipulates that if the location information of the first application entity 130 is received, an event for updating the location information of the first resource is generated.
- the subscription service device 110 updates the first location of the first resource based on the location information of the first application entity 130 (for example, operation 2201 in FIG. 2A). ). Similarly, the subscription service device 110 updates the second location of the second resource based on the location information of the second application entity 140. Since the cross-resource event notification rule indicates the distance threshold between the locations of n resources, the subscription service device 110 calculates the distance between the first location and the second location, and determines whether the cross-resource event notification rule is controlled based on the distance. Satisfy.
- the subscription service device 110 determines that the distance between the first location and the second location is less than the maximum distance
- the subscription service The device 110 sends a cross-resource event notification to the resource subscription entity 150.
- the subscription service device 110 reports to the resource subscription entity 150 Send cross-resource event notifications.
- the distance threshold indicates the distance range in the distance between the positions of any two resources (the maximum and minimum of the distance between the positions of any two resources) and the distance between the first position and the second position is in the distance If it is within the range (greater than the minimum value in the distance range and less than the maximum value in the distance range), a cross-resource event notification is sent to the resource subscription entity 150. Specifically, the notification is determined according to the cross-resource event notification rule. For example, in the case where the first application entity 130 and the second application entity 140 are both mobile environmental monitoring devices (such as temperature detection devices), the cross-resource event notification rule may be set between the first application entity 130 and the second application entity 140.
- a cross-resource event notification is sent to the resource subscription entity 150-at this time, the temperature detected by the first application entity 130 and the second application entity 140 can be calibrated. In this way, it can be ensured that the data to be calibrated are generated within a certain physical range, thereby ensuring the accuracy of the calibration.
- n resources satisfying the cross-resource event notification rule further includes: the value of n satisfies the cross-resource event notification rule, wherein the cross-resource event notification rule further indicates a threshold value of n.
- the subscription service device 110 receives multiple resource operation requests (for example, in FIG. 2A, the subscription service device 110 has received a total of two resource operation requests).
- the subscription service device 110 determines that there are n resources satisfying the single-resource event notification rule based on multiple resource operation requests.
- the subscription service device 110 may determine that there are two resources that satisfy the single-resource event notification rule, that is, n is 2. . Based on this, the subscription service device 110 can determine whether the total number of resources meets the cross-resource event notification rule.
- the subscription service device 110 determines that the cross-resource event notification rule has been satisfied, and sends a cross-resource event notification to the resource subscription entity 150.
- the threshold value indicating the total number of resources indicating n indicates the minimum value MIN of n and n is greater than MIN
- the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150.
- the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150.
- the notification is determined according to the cross-resource event notification rule.
- the cross-resource event notification rule may be that at least M application entities in the N application entities have monitored the humidity change
- a cross-resource event notification is sent to the resource subscription entity 150: at this time, the humidity detected by the M application entities can be calibrated, or the average value of the M humidity values can be calculated at this time.
- the foregoing embodiment can simplify the operation process and reduce the storage space of the subscription service device.
- the resource operation request includes application data.
- the n resources satisfying the cross-resource event notification rule further includes: the application data of the n resources satisfy the cross-resource event notification rule, where the cross-resource event notification rule also indicates a similarity threshold between the application data of the n resources.
- the subscription service device 110 receives a resource operation request including application data of the first application entity (for example, the second resource operation request of operation 2200) and a resource operation including application data of the second application entity Request (for example, the first resource operation request of operation 2100).
- the event notification rule of the first resource stipulates that if the application data of the first application entity 130 is received, an event of updating the application data of the first resource is generated.
- the subscription service device 110 updates the first application data of the first resource based on the application data of the first application entity.
- the subscription service device 110 also updates the second application data of the second resource based on the application data of the second application entity. Since the cross-resource event notification rule indicates the similarity threshold between the application data of n resources, the subscription service device 110 calculates the similarity between the first application data and the second application data, and determines the cross-resource based on the similarity. Whether the resource event notification rules are met. For example, in a case where the similarity threshold indicates the maximum similarity of the application data of any two resources, and the similarity between the first application data and the second application data is less than the maximum similarity, the subscription service device 110 may report The resource subscription entity sends cross-resource event notifications.
- the subscription service device 110 sends a cross-reference to the resource subscription entity.
- Resource event notification In the case that the similarity threshold indicates the similarity range of the application data of any two resources and the similarity between the first application data and the second application data is within the similarity range, the subscription service device 110 sends to the resource subscription entity Cross-resource event notification. Specifically, the notification is determined according to the cross-resource event notification rule.
- the cross-resource event notification rule may be set between the first application entity 130 and the second application entity 140.
- the similarity between the detected temperature data is less than the maximum similarity, a notification is sent to the resource subscription entity 150 that the temperature detected by the first application entity 130 and the second application entity 140 can be calibrated. In this way, the similarity of the calibration data can be ensured, thereby ensuring the accuracy of the calibration.
- the resource operation request includes the operation time.
- the n resources satisfying the cross-resource event notification rule further includes: the operation time of the n resources satisfy the cross-resource event notification rule, where the cross-resource event notification rule also indicates the time threshold of the operation time of the n resources.
- the subscription service device 110 receives a resource operation request including the operation moment of the first application entity (for example, the second resource operation request of operation 2200) and a resource operation including the operation moment of the second application entity Request (for example, the first resource operation request of operation 2100).
- the event notification rule of the first resource stipulates that if the operation time of the first application entity 130 is received, an event of updating the operation time of the first resource is generated.
- the subscription service device 110 updates the first operation moment of the first resource based on the application data of the first application entity.
- the subscription service device 110 also updates the second operation moment of the second resource based on the operation moment of the second application entity. Since the cross-resource event notification rule indicates the time threshold between the operation moments of n resources, the subscription service device 110 calculates the time difference between the first operation moment and the second operation moment, and determines the cross-resource event notification based on the time difference Whether the rules are met. For example, in the case where the time threshold indicates the maximum time difference between the operation moments of any two resources, and the time difference between the first operation moment and the second operation moment is less than the maximum time difference, the subscription service device 110 may subscribe to the resource The entity sends cross-resource event notifications.
- the subscription service device 110 sends a cross-check to the resource subscription entity.
- Resource event notification In the case that the time threshold indicates the time difference range between the operation moments of any two resources, and the time difference between the first operation moment and the second operation moment is within the time difference range, the subscription service device 110 sends a cross-reference to the resource subscription entity. Resource event notification. Specifically, the notification is determined according to the cross-resource event notification rule.
- the cross-resource event notification rule may be set between the first application entity 130 and the second application entity 140.
- the difference between the time of the detected temperature data is less than the maximum time difference, a notification is sent to the resource subscription entity 150 that the temperature detected by the first application entity 130 and the second application entity 140 can be calibrated. In this way, it can be ensured that the calibration data are all generated within a certain time range, thereby ensuring the accuracy of the calibration.
- n resources satisfy the cross-resource event notification rule further includes: the notification content types of the n resources satisfy the cross-resource event notification rule.
- the cross-resource event notification rule also indicates: when the notification content types of any two of the n resources are the same, the resource subscription entity is notified of the verification application data; In the case of different notification content types, the resource subscription entity is notified of the associated analysis application data.
- the subscription service device 110 receives the resource operation request of the first application entity (operation 2200) and the resource operation request of the second application entity (operation 2100).
- the subscription service device 110 determines whether there are n resources satisfying the single-resource event notification rule based on multiple resource operation requests.
- the event notification rule of the first resource is to update the location information of the first resource when the resource operation request of the first application entity 130 includes location information.
- the event notification rule of the second resource is to update the application data of the second resource when the resource operation request of the second application entity 140 includes application data. It is assumed that the event notification rules of the first resource and the second resource are both satisfied at this time.
- the subscription service device 110 can determine that the notification content of the first resource and the second resource are different. Therefore, the subscription service device 110 notifies the resource subscription entity 150 of the association analysis application data. Specifically, for example, in the case where the first application entity 130 and the second application entity 140 are both mobile environmental monitoring devices (such as temperature detection devices), the subscription service device 110 sends the resource subscription entity 150 to the first application entity 130 and The position relationship between the second application entity 140 is used to analyze the rationality of the temperature data detected by the second application entity. In another aspect, it is assumed that the event notification rule of the first resource is to update the application data of the first resource when the resource operation request of the first application entity 130 includes application data.
- the event notification rule of the second resource is also to update the application data of the second resource when the resource operation request of the second application entity 140 includes application data. It is assumed that the event notification rules of the first resource and the second resource are both satisfied at this time. Based on this, the subscription service device 110 can determine that the notification content of the first resource and the second resource are the same. Therefore, the subscription service device 110 notifies the resource subscription entity 150 of the verification application data. Specifically, for example, in the case where the first application entity 130 is a fixed temperature monitoring device and the second application entity 140 is a mobile environment monitoring device (such as a temperature detection device), the subscription service device 110 checks with the resource subscription entity 150 Temperature data detected by the first application entity 130 and the second application entity 140.
- FIG. 3 shows a schematic structural diagram of an exemplary cross-resource subscription resource 300 according to an embodiment of the present disclosure.
- the subscription service device 110 After the subscription service device 110 receives the cross-resource subscription request, the subscription service device 110 creates a cross-resource subscription resource 300 (ie, the ⁇ crossResourcesSubscription> resource in FIG. 3).
- the cross-resource subscription resource 300 optionally includes one or more of the following content items shown in FIG.
- the cross-resource subscription resource 300 may also include other content items not shown in FIG. 3, and the present disclosure is not limited herein.
- the content items in the cross-resource subscription resource 300 are further described below.
- the n resources in the foregoing operation 2020 satisfying the cross-resource event notification rule may include: location information of the n resources satisfy the cross-resource event notification rule.
- the cross-resource event notification rule indicates the maximum distance between the positions of any two resources among the n resources.
- the cross-resource subscription resource 300 may include target resource location reference and location verification.
- the location verification can specify a certain location range or location distance.
- the subscription service device 110 judges that the location information of any two of the n resources meets the cross-resource event notification rule by comparing the distances between multiple application entities.
- the specific location information can be obtained by referring to the location of the target resource.
- the target resource location reference indicates the location index corresponding to the AE or CSE where the target resource is located.
- the target resource location reference may include ⁇ AE>/ ⁇ locationPolicy>/locationContainer ID, or ⁇ CSE>/ ⁇ locationPolicy>/locationContainer ID.
- ⁇ AE> and ⁇ CSE> resources can be used to identify the application logic of the entity.
- the sub-resource of the ⁇ AE> or ⁇ CSE> resource-the ⁇ LocationPolicy> resource can be used to store the logic for obtaining the location information of the target entity.
- the locationContainer ID is the URI of the ⁇ container> that stores the actual physical location information of a specific entity, where the ⁇ container> can be used as a container and store specific content information.
- FIG. 4 shows a schematic diagram of an example 400 according to an embodiment of the present disclosure, which is used to further illustrate the cross-resource event notification rule.
- Figure 4 shows 8 application entities, including: a first application entity AE1, a second application entity AE2, and a third application entity AE3.
- AE1 is a fixed monitoring device
- the 7 application entities (for example, AE2 and AE3) in the dotted line are mobile monitoring devices.
- the monitoring data of fixed monitoring equipment is more accurate than the monitoring data of mobile monitoring equipment. Therefore, the monitoring data of fixed monitoring equipment can be used to calibrate the monitoring data of mobile monitoring equipment.
- the aforementioned cross-resource event notification rule may indicate that among the resources corresponding to the aforementioned eight application entities, if the locations of two resources meet the location threshold (assuming that the location threshold indicates the maximum distance between the two resources), then the cross-resource event notification is sent .
- the subscription service device 110 may obtain the specific physical locations of AE1 to AE3 based on the target resource location reference in the cross-resource subscription resource, and calculate the distance between the three monitoring devices. By comparing these distances with the location check, the subscription service device 110 can determine that the distance between AE1 and AE2 is less than the maximum distance between the locations of the two resources, and then can send a cross-resource event notification to the resource subscription entity 150 to Inform that the monitoring data of AE2 can be verified through the monitoring data of AE1.
- the method 200 can directly determine the positional relationship between multiple application entities, and then determine the location relationship between multiple application entities. Resources for further processing. As a result, the computational burden of the resource subscription entity 150 is reduced, and it is more convenient for the operator to operate the resource subscription entity 150.
- the foregoing n resources satisfying the cross-resource notification event rule also includes: the value of n satisfies the cross-resource event notification rule.
- the cross-resource event notification rule indicates the threshold of n.
- the cross-resource subscription resource 300 may include a partial subscription enable switch (partResourceNotificationEnable) and a partial subscription generation number (partResourceNotificationNr).
- the partial subscription enable switch indicates whether to enable partial cross-resource subscription notifications. It can be a binary number. When its value is 0, it means that partial cross-resource subscription notifications are not turned on. When its value is 1, it means that partial cross-resource subscriptions are turned on. Notice.
- the number of generated partial subscriptions indicates the minimum number of resources that generate events for cross-resource subscription notifications.
- the cross-resource event notification rule may indicate that the cross-resource event notification is sent when the monitoring data of resources corresponding to more than or equal to 3 application entities in the 8 application entities in FIG. 4 is updated.
- AE1 to AE3 all send resource operation requests to the subscription service device 110 to request to update the monitoring data in their corresponding resources.
- the subscription server 110 determines that the number of resources is equal to 3 before sending a cross-resource event notification to the resource subscription entity 150.
- the method 200 Compared with the interaction process between the devices participating in sending cross-resource event notifications shown in FIG. 1B, the method 200 only needs to create a cross-resource subscription resource 300, and does not need to be created for every two of the eight application entities. Each application entity creates a cross-resource subscription resource (a total of 28 cross-resource subscription resources). The method 200 can obtain events generated by resources corresponding to any number of application entities in multiple application entities by creating a cross-resource subscription resource 300. This greatly saves computing resources and storage space, and improves notification processing efficiency.
- the foregoing n resources satisfying the cross-resource event notification rule also includes: the application data of the n resources satisfy the cross-resource event notification rule.
- the cross-resource event notification rule indicates the similarity threshold between the application data of any two of the n resources.
- the cross-resource event notification rule can indicate when the similarity of the monitoring data measured by any number of monitoring devices in the multiple monitoring devices is greater than the minimum similarity
- the multiple monitoring devices are calibrated. For example, assume that AE1 to AE3 have acquired the first monitoring data, the second monitoring data, and the third monitoring data, respectively. Assuming that the similarity between the first monitoring data and the second monitoring number is higher than the minimum similarity, the AE2 monitoring data can be calibrated based on the first monitoring data.
- the foregoing n resources satisfying the cross-resource event notification rule also includes: the operation moments of the n resources satisfy the cross-resource event notification rule.
- the cross-resource event notification rule also indicates the time threshold between the operation moments of any two of the n resources.
- the cross-resource subscription resource 300 may include a time window type and a time window size.
- the size of the time window may indicate the maximum value w of the difference between the operating moments of the two resources.
- the monitoring data of AE3 can be calibrated based on the first monitoring data.
- the foregoing n resources satisfying the cross-resource event notification rule also includes: the notification content types of the n resources satisfy the cross-resource event notification rule.
- the cross-resource event notification rule also indicates: when the notification content types of any two of the n resources are the same, notify the resource subscription entity of the verification application data; and in the n resources When the notification content types of any two resources are different, the resource subscription entity is notified of the associated analysis application data.
- the cross-resource subscription to the resource 300 may include cross-resource subscription notification content type.
- the subscription service device 110 may use the monitoring data for calibration.
- the monitoring data and location data can be used for correlation analysis. For example, you can analyze the changes in the monitoring data at a certain location.
- FIG. 5 shows a flowchart of an example 500 according to an embodiment of the present disclosure.
- the resource subscription entity 150 and the application entities AE1 to AEn register with the subscription service device 110.
- the resource subscription entity 150 sends a cross-resource subscription request to the subscription service device 110.
- the subscription request includes a cross-resource event notification rule and an event notification rule for subscribing to events generated from AE1 to AEn.
- the cross-resource event notification rule indicates when the location interval from AE2 to AEn is less than a certain location threshold and the difference in event generation time from AE2 to AEn is less than the time threshold.
- the subscription service device 110 creates subscription resources (including event notification rules) for AE1 to AEn.
- the subscription service device 110 creates a cross-resource subscription resource, and returns a cross-resource subscription response.
- the application entity AE2 sends the first resource operation request, which includes monitoring data and location information.
- the subscription service device 110 determines whether the monitoring data of AE2 meets the event notification rule of AE2, and if so, generates a first event, and returns a first operation response.
- the application entity AE1 sends a second resource operation request.
- the subscription service device 110 determines whether the monitoring data of the application entity AE1 meets the event notification rule of AE1, and if so, generates a second event, and returns a second operation response.
- the subscription service device 110 determines whether the first event and the second event meet the cross-resource notification rule, that is, whether the first event and the second event meet the following four conditions: 1 Whether the location information corresponding to the first event and the second event is less than A certain location threshold; 2Whether the time information corresponding to the first event and the second event is less than a certain time threshold; 3Whether the similarity between the application data corresponding to the first event and the second event is greater than a certain similarity threshold; and 4Whether the sum of the number of events corresponding to the first event and the second event is greater than a threshold of the total number of resources, if the first event and the second event correspond to the above four conditions, a cross-resource event notification is sent to the resource subscription entity 150.
- the resource subscription entity 150 may return a notification response to the subscription service device 110.
- the resource subscription entity 150 may also send a verification request to the application entity AE2 and receive a verification response sent by the application entity AE2.
- the subscription service device 110 also receives the third resource operation request and the fourth resource operation request sent by the application entities AE4 and AE5, which include monitoring data and location information.
- the subscription service device 110 determines whether the monitoring data of the application entities AE4 and AE5 meet the event notification rule, and if so, generates a third event and a fourth event, and returns an operation response.
- the subscription service device 110 determines whether the third event and the fourth event meet the cross-resource notification rule, and if they do, sends a cross-resource event notification to the resource subscription entity 150.
- Fig. 6 shows a schematic diagram of an apparatus 600 for sending a cross-resource event notification according to an embodiment of the present disclosure.
- the system for sending a cross-resource event notification may include: a device for sending a cross-resource event notification, and the device is a subscription service device.
- the resource subscription entity is configured to send a cross-resource subscription request to the subscription service device.
- the application entity is configured to send a resource operation request to the subscription service device.
- the apparatus 600 for sending cross-resource event notifications includes a cross-resource subscription unit 601 and a notification unit 602.
- the cross-resource subscription unit 601 is configured to receive a cross-resource subscription request from the resource subscription entity.
- the cross-resource subscription request is used to subscribe to multiple resources, which includes the event notification rule and the cross-resource event notification rule of each of the multiple resources.
- the notification unit 602 is configured to send a cross-resource event notification to the resource subscription entity when n resources among the multiple resources satisfy the single-resource event notification rule, and when the n resources satisfy the cross-resource event notification rule.
- FIG. 7 shows a structural diagram of an electronic device 700 for sending a cross-resource event notification according to an embodiment of the present disclosure.
- the electronic device 700 that sends a cross-resource event notification may include a processor 701 and a memory 702. Both the processor 701 and the memory 702 may be connected through the bus 703.
- the electronic device 700 may be a tower server, a rack server (Rack), a blade server (Blade Server), a cabinet server, or the like.
- the processor 701 can perform various actions and processing according to a program stored in the memory 702.
- the processor 701 may be an integrated circuit chip with signal processing capability.
- the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, or discrete hardware components.
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA off-the-shelf programmable gate array
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general-purpose processor may be a microprocessor or the processor may also 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 foregoing method 200 for sending cross-resource event notifications is implemented.
- the memory 702 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile 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
- 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 connection dynamic random access memory
- DRRAM direct memory bus random access memory
- the present disclosure also provides a system for sending cross-resource event notifications.
- the system for sending cross-resource event notifications may include a subscription service device 110, a resource subscription entity 150, and an application entity (for example, a first application entity 130 and a second application entity 140) as shown in FIG. 1A and FIG. 1B.
- the resource subscription entity 150 is configured to send a cross-resource subscription request to the subscription service device.
- the application entity is configured to send a resource operation request to the subscription service device.
- the present disclosure also provides a computer-readable storage medium on which computer instructions are stored.
- the computer instructions are executed by a processor, the above-mentioned method 200 for sending cross-resource event notifications can be implemented.
- the computer-readable storage medium in the 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 the computer-readable storage media described herein are intended to include, but are not limited to, these and any other suitable types of memory.
- the present disclosure proposes an improved method, device, electronic device, computer-readable storage medium, and system for sending cross-resource event notifications.
- the method, apparatus, electronic device, computer-readable storage medium, and system for sending cross-resource event notifications can process complex event information generated by some resources among multiple resources, and then process information notifications efficiently.
- each block in the flowchart or block diagram may represent a module, program segment, or part of code, and the module, program segment, or part of code contains one or more for realizing the specified logical function Executable instructions.
- the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown in succession can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved.
- each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.
- 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.
- firmware or software that may be executed by a controller, microprocessor, or other computing device.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (20)
- 一种发送跨资源事件通知的方法,包括:从资源订阅实体接收跨资源订阅请求,所述跨资源订阅请求用于订阅多个资源,所述跨资源订阅请求包括多个单资源事件通知规则和跨资源事件通知规则;确定所述m个资源中的n个资源满足单资源事件通知规则且满足跨资源事件通知规则,向所述资源订阅实体发送跨资源事件通知,其中m和n为大于或等于2的正整数。
- 如权利要求1所述的发送跨资源事件通知的方法,还包括,在发送所述跨资源事件通知之前,接收资源操作请求,所述资源操作请求包括位置信息、应用数据、操作时刻中的一个或多个;基于所述资源操作请求确定所述m个资源中的n个资源满足单资源事件通知规则且满足跨资源事件通知规则。
- 如权利要求2所述的发送跨资源事件通知的方法,其中,所述资源操作请求包括位置信息;所述n个资源满足跨资源事件通知规则还包括:所述n个资源的位置信息满足跨资源事件通知规则。
- 如权利要求3所述的发送跨资源事件通知的方法,其中,所述跨资源事件通知规则指示n个资源的位置之间的距离阈值。
- 如权利要求4所述的发送跨资源事件通知的方法,还包括:接收包括第一应用实体的位置信息的资源操作请求和包括第二应用实体的位置信息的资源操作请求,基于所述第一应用实体的位置信息更新第一资源的第一位置;基于所述第二应用实体的位置信息更新第二资源的第二位置;所述距离阈值为任意两个资源的位置之间的距离中的最大距离;所述第一位置和第二位置之间的距离小于所述最大距离的情况下,向资源订阅实体发送跨资源事件通知;或所述距离阈值为任意两个资源的位置之间的距离中的最小距离;在当所述第一位置和第二位置之间的距离大于所述最小距离的情况下,向资源订阅实体发送跨资源事件通知;或所述距离阈值为任意两个资源的位置之间的距离中的距离范围;在当所述第一位置和第二位置之间的距离在所述距离范围内时,向资源订阅实体发送跨资源事件通知。
- 如权利要求1-5中的任一项所述的发送跨资源事件通知的方法,其中,所述n个资源满足跨资源事件通知规则还包括:所述n满足跨资源事件通知规则。
- 如权利要求6所述的发送跨资源事件通知的方法,其中,所述跨资源事件通知规则还指示n的阈值,n<m。
- 如权利要求7所述的发送跨资源事件通知的方法,还包括:所述n的阈值指示n的最大值MAX;在n小于MAX的情况下,向资源订阅实体发送跨资源事件通知;或所述n的阈值指示n的最小值MIN;在n大于MIN的情况下,向资源订阅实体发送跨资源事件通知;或所述n的阈值指示n的最大值MAX和最小值MIN;在n小于MAX并且n大于MIN的情况下,向资源订阅实体发送跨资源事件通知。
- 如权利要求2-8中的任一项所述的发送跨资源事件通知的方法,其中,所述资源操作请求包括应用数据;所述n个资源满足跨资源事件通知规则还包括:所述n个资源的应用数据满足跨资源事件通知规则。
- 如权利要求9所述的发送跨资源事件通知的方法,还包括,所述跨资源事件通知规则还指示n个资源的应用数据之间的相似度阈值。
- 如权利要求10所述的发送跨资源事件通知的方法,还包括:接收包括第一应用实体的应用数据的资源操作请求和包括第二应用实体的应用数据的资源操作请求,基于所述第一应用实体的应用数据更新第一资源的第一应用数据;基于所述第二应用实体的应用数据更新第二资源的第二应用数据;所述相似度阈值为任意两个资源的应用数据的最大相似度;在第一应用数据和第二应用数据的相似度小于所述最大相似度的情况下,向资源订阅实体发送跨资源事件通知;或所述相似度阈值为任意两个资源的应用数据的最小相似度;在第一应用数据和第二应用数据的相似度大于所述最小相似度的情况下,向资源订阅实体发送跨资源事件通知;或所述相似度阈值为任意两个资源的应用数据的相似度范围;在第一应用数据和第二应用数据的相似度在所述相似度范围内时,向资源订阅实体发送跨资源事件通知。
- 如权利要求2-11中的任一项所述的发送跨资源事件通知的方法,其中,所述资源操作请求包括操作时刻;所述n个资源满足跨资源事件通知规则还包括:所述n个资源的操作时刻满足跨资源事件通知规则。
- 如权利要求12所述的发送跨资源事件通知的方法,其中,所述跨资源事件通知规则还指示n个资源的操作时刻的时间阈值。
- 如权利要求13所述的发送跨资源事件通知的方法,还包括:接收包括第一应用实体的操作时刻的资源操作请求和包括第二应用实体的操作时刻的资源操作请求,基于所述第一应用实体的操作时刻更新第一资源的第一操作时刻;基于所述第二应用实体的操作时刻更新第二资源的第二操作时刻;所述时间阈值为任意两个资源的操作时刻之间的最大时间差;在第一操作时刻和第二操作时刻之间的时间差小于所述最大时间差的情况下,向资源订阅实体发送跨资源事件通知;或所述时间阈值为任意两个资源的操作时刻之间的最小时间差;在第一操作时刻和第二操作时刻大于所述最小时间差的情况下,向资源订阅实体发送跨资源事件通知;或所述时间阈值为任意两个资源的操作时刻之间的时间差范围;在所述第一操作时刻和第二操作时刻的时间差在所述时间差范围内时,向资源订阅实体发送跨资源事件通知。
- 如权利要求1-14中的任一项所述的发送跨资源事件通知的方法,其中,所述n个资源满足跨资源事件通知规则还包括:所述n个资源的通知内容类型满足跨资源事件通知规则。
- 如权利要求15所述的发送跨资源事件通知的方法,其中,所述跨资源事件通知规则还指示:在所述n个资源中的任意两个资源的通知内容类型相同的情况下,向资源订阅实体通知校验应用数据;在所述n个资源中的任意两个资源的通知内容类型不同的情况下,向资源订阅实体通知关联分析应用数据。
- 如权利要求16所述的发送跨资源事件通知的方法,还包括:接收第一应用实体的资源操作请求和第二应用实体的资源操作请求,基于所述第一应用实体的资源操作请求和事件通知规则确定第一资源的第一通知内容类型;或基于所述第二应用实体的资源操作请求和事件通知规则确定第二资源的第二通知内容类型;或在所述第一通知内容类型和所述第二通知内容类型相同的情况下,向资源订阅实体通知校验应用数据;或在所述第一通知内容类型和所述第二通知内容类型不同的情况下,向资源订阅实体通知关联分析应用数据。
- 一种发送跨资源事件通知的***,包括:发送跨资源事件通知的装置,所述装置为订阅服务设备;资源订阅实体,被配置为向所述订阅服务设备发送跨资源订阅请求;应用实体,被配置为向所述订阅服务设备发送资源操作请求;所述发送跨资源事件通知的装置,包括:跨资源订阅单元,被配置为从资源订阅实体接收跨资源订阅请求,所述跨资源订阅请求用于订阅多个资源,所述跨资源订阅请求包括多个单资源事件通知规则和跨资源事件通知规则;通知单元,被配置为确定m个资源中的n个资源满足单资源事件通知规则且满足跨资源事件通知规则,向所述资源订阅实体发送跨资源事件通知,其中m和n为大于或等于2的正整数。
- 一种发送跨资源事件通知的电子设备,包括:处理器;存储器,存储器存储有计算机指令,该计算机指令被处理器执行时实现如权利要求1-17中任一项所述的发送跨资源事件通知的方法。
- 一种计算机可读存储介质,其上存储有计算机指令,所述计算机指令被处理器执行时实现权利要求1-17中任一项所述的发送跨资源事件通知的方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020227014099A KR20220073788A (ko) | 2019-09-29 | 2020-09-23 | 교차 리소스 이벤트 통지를 송신하기 위한 방법, 전자 디바이스, 시스템 및 컴퓨터 판독가능 저장 매체 |
EP20867910.0A EP4044555A4 (en) | 2019-09-29 | 2020-09-23 | MULTI-RESOURCE EVENT NOTIFICATION TRANSMISSION METHOD, ELECTRONIC DEVICE, SYSTEM AND COMPUTER-READABLE STORAGE MEDIUM |
JP2022519536A JP2022549924A (ja) | 2019-09-29 | 2020-09-23 | クロスリソースイベント通知を送信する方法、電子機器、システム及びコンピュータ読み取り可能な記憶媒体 |
US17/763,691 US12010179B2 (en) | 2019-09-29 | 2020-09-23 | Method, electronic device, system, and computer-readable storage medium for transmitting cross-resource event notifications |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910936059.4A CN112583871B (zh) | 2019-09-29 | 2019-09-29 | 发送跨资源事件通知的方法、电子设备和*** |
CN201910936059.4 | 2019-09-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021057762A1 true WO2021057762A1 (zh) | 2021-04-01 |
Family
ID=75111142
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/116984 WO2021057762A1 (zh) | 2019-09-29 | 2020-09-23 | 发送跨资源事件通知的方法、电子设备、***以及计算机可读存储介质 |
Country Status (6)
Country | Link |
---|---|
US (1) | US12010179B2 (zh) |
EP (1) | EP4044555A4 (zh) |
JP (1) | JP2022549924A (zh) |
KR (1) | KR20220073788A (zh) |
CN (1) | CN112583871B (zh) |
WO (1) | WO2021057762A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140340219A1 (en) * | 2013-05-15 | 2014-11-20 | Zephyr Technology Corporation | Physiological monitoring and alerting |
US9064389B1 (en) * | 2012-11-13 | 2015-06-23 | e-Control Systems, Inc. | Intelligent sensor for an automated inspection system |
US20150295785A1 (en) * | 2012-10-29 | 2015-10-15 | Zte Corporation | Resource Subscription Method and Device |
CN105659633A (zh) * | 2013-08-29 | 2016-06-08 | 康维达无线有限责任公司 | 物联网事件管理***以及方法 |
CN108353094A (zh) * | 2015-11-16 | 2018-07-31 | 康维达无线有限责任公司 | 用于m2m服务层的跨资源订阅 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106973118B (zh) * | 2017-05-12 | 2021-04-27 | 京东方科技集团股份有限公司 | 生成和订阅通知的方法和装置 |
-
2019
- 2019-09-29 CN CN201910936059.4A patent/CN112583871B/zh active Active
-
2020
- 2020-09-23 KR KR1020227014099A patent/KR20220073788A/ko unknown
- 2020-09-23 US US17/763,691 patent/US12010179B2/en active Active
- 2020-09-23 WO PCT/CN2020/116984 patent/WO2021057762A1/zh unknown
- 2020-09-23 JP JP2022519536A patent/JP2022549924A/ja active Pending
- 2020-09-23 EP EP20867910.0A patent/EP4044555A4/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150295785A1 (en) * | 2012-10-29 | 2015-10-15 | Zte Corporation | Resource Subscription Method and Device |
US9064389B1 (en) * | 2012-11-13 | 2015-06-23 | e-Control Systems, Inc. | Intelligent sensor for an automated inspection system |
US20140340219A1 (en) * | 2013-05-15 | 2014-11-20 | Zephyr Technology Corporation | Physiological monitoring and alerting |
CN105659633A (zh) * | 2013-08-29 | 2016-06-08 | 康维达无线有限责任公司 | 物联网事件管理***以及方法 |
CN108353094A (zh) * | 2015-11-16 | 2018-07-31 | 康维达无线有限责任公司 | 用于m2m服务层的跨资源订阅 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4044555A4 |
Also Published As
Publication number | Publication date |
---|---|
KR20220073788A (ko) | 2022-06-03 |
CN112583871B (zh) | 2024-07-16 |
US12010179B2 (en) | 2024-06-11 |
EP4044555A1 (en) | 2022-08-17 |
EP4044555A4 (en) | 2023-09-27 |
US20220345529A1 (en) | 2022-10-27 |
CN112583871A (zh) | 2021-03-30 |
JP2022549924A (ja) | 2022-11-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11469949B2 (en) | Hierarchical configuration of networked communication devices | |
WO2020221267A1 (zh) | 终端设备的位置确定方法和设备 | |
CN106937362B (zh) | 网络切片管理装置和网络切片管理方法 | |
US11824787B2 (en) | Method and apparatus for node speed limiting, electronic device and storage medium | |
WO2018176952A1 (zh) | 一种室内定位方法及服务器 | |
CN111597002A (zh) | 一种页面渲染方法、装置、电子设备及存储介质 | |
US11924640B1 (en) | Confidence based network provisioning of devices | |
CN112671897A (zh) | 分布式***的访问方法、装置、存储介质、设备和产品 | |
US11080107B2 (en) | Event notification method, server device, event notification apparatus, and medium | |
KR102678671B1 (ko) | 보안 인증을 위한 데이터 처리 방법, 서버, 클라이언트 디바이스 및 매체 | |
CN112039934A (zh) | 一种信息反馈、反馈信息处理方法及装置 | |
WO2021057762A1 (zh) | 发送跨资源事件通知的方法、电子设备、***以及计算机可读存储介质 | |
CN113872995B (zh) | 选择边缘使能客户端的方法和装置 | |
WO2021169585A1 (zh) | 局域网环境下设备间的仲裁方法、电子设备、局域网*** | |
WO2021143287A1 (zh) | 服务调度方法、装置、电子设备及存储介质 | |
CN111092791A (zh) | 一种确定从应用至服务器的可用网络带宽的方法与设备 | |
WO2022194008A1 (zh) | 地图数据处理方法及装置 | |
EP3887949A1 (en) | Automatic and dynamic adaptation of grouping in a data processing system | |
CN111629054B (zh) | 消息处理方法、装置、***、电子设备及可读存储介质 | |
CN111400327B (zh) | 一种数据同步方法、装置、电子设备及存储介质 | |
WO2021134252A1 (zh) | 设备间通信方法、装置、和存储介质 | |
CN111371675A (zh) | 智能寻址方法、装置、设备及其存储介质 | |
US11652877B2 (en) | Method and system for establishing trust between nodes in a network based on recommendations | |
WO2023216856A1 (zh) | 业务管理方法和装置 | |
US20180270190A1 (en) | Method and device for creating application announcement resource |
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: 20867910 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022519536 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20227014099 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2020867910 Country of ref document: EP Effective date: 20220429 |