Method, electronic device, system and computer-readable storage medium for transmitting cross-resource event notifications

Abstract

A method, an electronic device, and a system for sending a cross-resource event notification are disclosed, which include the steps of receiving a cross-resource subscription request from a resource subscription entity for subscribing to a plurality of resources, the cross-resource subscription request including a plurality of single-resource event notification rules and cross-resource event notification rules, and determining that n (a positive integer greater than or equal to 2) resources among the m (a positive integer greater than or equal to 2) resources satisfy both the single-resource event notification rules and the cross-resource event notification rules, and sending a cross-resource event notification to the resource subscription entity.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to Chinese patent application No. 201910936059.4, filed on September 29, 2019, and the entire contents of the above Chinese patent application are incorporated herein by reference.

[0002] The present disclosure relates to a method, an electronic device, a system, and a computer-readable storage medium for transmitting a cross-resource event notification. [Background technology]

[0003] With the development of Internet of Things technology, more and more Internet of Things devices (also called entities) are accessing the Internet of Things. The Internet of Things manages each Internet of Things device 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. An application terminal can subscribe to notification of each change of resources through the Internet of Things management platform, and can further control the Internet of Things devices.

[0004] The smart home platform is a general Internet of Things management platform. An entity home appliance accesses the smart home platform via wired or wireless communication, the smart home platform generates a virtual home appliance (i.e., resource) for the entity home appliance, and an application terminal accesses the virtual home appliance through the smart home platform, and further realizes remote monitoring and control of the home appliance.

[0005] Currently, the Internet of Things requires complicated processing of multiple data, and the processing efficiency is not very high, which causes inconvenience to users. Summary of the Invention [Problem to be solved by the invention]

[0006] Embodiments of the present disclosure provide a method, device, electronic device, computer-readable storage medium, and system for sending cross-resource event notification, which can send a cross-resource event notification to a resource subscription entity when any two or more resources among a plurality of resources satisfy a cross-resource event notification rule, thereby meeting the personalized needs of users and improving notification processing efficiency. [Means for solving the problem]

[0007] An embodiment of the present disclosure provides a method for sending a cross-resource event notification, the method including: The method includes receiving a cross-resource subscription request from a resource subscription entity to subscribe to multiple resources, the cross-resource subscription request including multiple single-resource event notification rules and cross-resource event notification rules; determining that n (a positive integer greater than or equal to 2) resources out of the m (a positive integer greater than or equal to 2) resources satisfy the single-resource event notification rules and the cross-resource event notification rules, and sending a cross-resource event notification to the resource subscription entity.

[0008] An embodiment of the present disclosure provides a system for sending cross-resource event notifications, the system comprising: a resource subscription entity configured to send a cross-resource subscription request to the subscription service device; and an application entity configured to send a resource operation request to the subscription service device, wherein the cross-resource event notification sending device includes a cross-resource subscription request from the resource subscription entity to subscribe to a plurality of resources, the cross-resource subscription request including a plurality of single-resource event notification rules and cross-resource event notification rules; and a notification unit configured to determine that n (a positive integer equal to or greater than 2) resources out of the m (a positive integer equal to or greater than 2) resources satisfy the single-resource event notification rule and the cross-resource event notification rule, and to send a cross-resource event notification to the resource subscription entity.

[0009] An embodiment of the present disclosure provides an electronic device for transmitting a cross-resource event notification, the electronic device for transmitting a cross-resource event notification includes a processor and a memory, the memory storing computer instructions, which, when executed by the processor, realizes the method for transmitting a cross-resource event notification.

[0010] An embodiment of the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, results in the method for sending cross-resource event notifications.

[0011] In order to more clearly describe the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments are briefly described below. It is apparent that the drawings described below are not limitations on the present disclosure, but are only related to some embodiments of the present disclosure.

[0012] In order to more clearly describe the technical solutions of the embodiments of the present disclosure, the following will briefly describe the drawings required in the description of the embodiments. The drawings described below are only exemplary embodiments of the present disclosure. [Brief description of the drawings]

[0013] [Figure 1A] 1 shows a schematic diagram of a scene for sending a cross-resource event notification. [Figure 1B] 1 shows a schematic diagram of the interaction process between devices participating in sending cross-resource event notifications. [Figure 2A] 1 illustrates a schematic diagram of a method for sending a cross-resource event notification according to an embodiment of the present disclosure; [Figure 2B] 1 illustrates a flowchart of a method for sending a cross-resource event notification according to an embodiment of the present disclosure. [Diagram 3] 1 illustrates a structural diagram of an exemplary cross-resource subscription resource according to an embodiment of the present disclosure; [Figure 4] 1 shows a schematic diagram of an example according to an embodiment of the present disclosure. [Diagram 5] 1 shows an example flowchart according to an embodiment of the present disclosure. [Figure 6] 1 illustrates a schematic diagram of an apparatus for sending cross-resource event notifications according to an embodiment of the present disclosure; [Figure 7] 1 illustrates a structural diagram of an electronic device that sends a cross-resource event notification according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] In order to more clearly describe the objectives, technical solutions and advantages of the present disclosure, exemplary embodiments of the present disclosure are described in detail below with reference to the drawings. It should be understood that the described embodiments are only some embodiments of the present disclosure, but are not all embodiments of the present disclosure, and the present disclosure is not limited to the exemplary embodiments described herein.

[0015] In the present specification and drawings, steps and elements that are basically the same or similar are represented by the same or similar reference numerals, and redundant descriptions of these steps and elements are omitted. Meanwhile, in the description of the present disclosure, the terms "first", "second", etc. are used only to distinguish the description, and should not be understood as indicating relative importance or order.

[0016] In this specification, the term "entity" may refer to the hardware of an Internet of Things device, an Internet of Things gateway, or an Internet of Things server, or may refer to a software unit of the Internet of Things application layer or the Internet of Things (common) service layer.

[0017] In this specification, an Application Entity (AE), a CSE, data, etc. may be represented as a resource. In the Internet of Things, a data structure that can be uniquely addressed using a unique address (e.g., a URI (Uniform Resource Identifier)) is called a resource. In an Internet of Things system, resources are represented as predefined data structures and can be logically interconnected. Thus, the common service layer of an Internet of Things device, an Internet of Things gateway, an AE, a CSE, or an Internet of Things server may all include resources.

[0018] Various resources are defined in an Internet of Things system. Internet of Things applications can communicate based on resources implemented as resource types. For example, resources can be used for Internet of Things services such as registering applications, reading sensor values, etc. Each resource can be given a unique address information (e.g., URI) when creating an instance of the corresponding resource type.

[0019] Optionally, a resource can have sub-resources and attributes. An attribute stores information about the resource itself and may not contain sub-resources. A sub-resource can contain attributes and its own sub-resources. For example, a sub-resource can be a remote CSE resource, an application entity resource, an access control resource, a container resource, a group resource, a subscription resource, etc.

[0020] Fig. 1A shows a schematic diagram of a scene 100A for transmitting a cross-resource event notification, and Fig. 1B shows a schematic diagram of an interaction process 100B between devices participating in transmitting a cross-resource event notification.

[0021] 1A, in scene 100A, subscription service device 110, first application entity 130, second application entity 140, and resource subscription entity 150 may be connected via network 120. Each of the above devices may directly or indirectly communicate with each other, for example, by transmitting and receiving data and / or signals via network 120.

[0022] Network 120 may be the Internet and / or the Internet of Things based on a telecommunications network, may be a wired network, may be a wireless network, and may be any electronic network capable of implementing message exchange functions, such as a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a cellular data communication network, etc.

[0023] The subscription service device 110 can perform centralized management and control over entities (e.g., the first application entity 130, the second application entity 140) via the network 120. The subscription service device 110 can also send cross-resource event notifications to the resource subscription entity 150 via the network 120 to notify the resource subscription entity 150 of the changing state of the resource of the application entity. Specifically, the subscription service device 110 can be a server or other electronic device including a processor and a memory. The subscription service device 110 can also be a Common Service Entity (CSE) in the Internet of Things.

[0024] The resource subscription entity 150 and the application entity may be computing devices including a processor and a memory. For example, the first application entity 130 and the second application entity 140 may be a television, a smart home appliance (e.g., a smart refrigerator, a smart microwave, etc.), a charging car, a desktop computer, a laptop, a smartphone, a tablet computer, a music player (e.g., an mp3 player, etc.), and other terminals including a processor and a memory (e.g., a mobile terminal, a smart terminal). In some embodiments, the first application entity 130 is a fixed monitoring device and the second application entity 140 is a mobile monitoring device that can be used to monitor the surrounding environment (e.g., monitor the temperature, humidity, light conditions, etc. of the surrounding environment). In some embodiments, the resource subscription entity 150 and the application entity may be the same entity or different entities. For example, the resource subscription entity 150, the first application entity 130, and the second application entity 140 may be Application Entities (AEs) in the Internet of Things. Of course, the resource subscription entity 150, the first application entity 130 and the second application entity 140 may be a common service entity.

[0025] For example, in the Internet of Things, an AE (or CSE) registers with another CSE, and after registration, the CSE creates a resource corresponding to the AE (or CSE). The AE can operate the resource on the CSE by creating, updating, retrieving, deleting, etc. Specifically, a resource may include attributes and sub-resources, among which the attributes are for storing resource-related information (e.g., an identifier of the resource, a physical location of the AE corresponding to the resource, status information of the resource, etc.), the sub-resources are the next-level resources of the resource, and the resource includes an index to the next-level resources.

[0026] In some embodiments, an operator operates at the resource subscription entity 150 (e.g., edits a resource subscription request), sends a resource subscription request to the subscription service device 110, and receives notifications sent by the subscription service device 110 when the resource changes. The notifications may indicate the change status of the resource.

[0027] For example, FIG. 1B illustrates a conventional resource subscription interaction process 100B.

[0028] In operation 101, the resource subscription entity 150 sends a cross-resource subscription request to the subscription service device 110 to simultaneously subscribe to application data of the first application entity 130 and the second application entity 140, and sets a cross-resource event notification rule of "send the application data of both the first application entity 130 and the second application entity 140 when the interval between sending application data meets a time threshold."

[0029] In operation 102, when the subscription service device 110 receives the cross-resource subscription request, it subscribes to the application data of the first application entity 130 and the second application entity 140 simultaneously, and automatically sends a cross-resource event notification to the resource subscription entity 150 when the above-mentioned cross-resource event notification rule is satisfied. Then, in operation 103, the subscription service device 110 sends a cross-resource subscription response to the resource subscription entity 150, and informs the resource subscription entity 150 that the cross-resource subscription has been set. Specifically, the subscription service device 110 can internally construct a first resource corresponding to the first monitoring device 130 and a second resource corresponding to the second monitoring device 140 using the correlation information of the first application entity 130 and the second application entity 140, and operate the first monitoring device 130 and the second monitoring device 140 by the first resource and the second resource.

[0030] An operator may operate the application entity to send a resource operation request to the subscription service device 110. Of course, the application entity may automatically send the resource operation request to the subscription service device 110 without manual intervention. For example, in operation 104, the second application entity 130 may send a first resource operation request including first application data to the subscription service device 110. In operation 105, the subscription service device 110 records the first application data based on the first resource operation request and records the first time when the first resource operation request is received. In operation 106, the subscription server 110 sends a first operation response to the second application entity 140.

[0031] Similarly, in operations 107-109, the first application entity 130 and the subscription service device 110 can obtain second application data and a second time point at which the second application data is received through a second resource operation request.

[0032] In operation 110, the subscription service device 110 determines whether the time difference between the first time point and the second time point meets the time threshold. If the time threshold is met, the subscription service device 110 transmits the first application data and the second application data to the resource subscription entity 150 in operation 111. Then, in operation 112, the resource subscription entity 150 can perform further processing on the first application data and the second application data. For example, the resource subscription entity 150 can determine whether the distance between the first location where the first application data is obtained and the second location where the second application data is obtained meets the requirements of the location threshold. If the first location and the second location meet the location threshold, the resource subscription entity 150 can send a calibration request in operation 113 to notify the second application entity 140 that it should calibrate based on the first application data and the second application data. After calibrating, the second application entity 140 can send a calibration response back to the resource subscription entity 150 in operation 114.

[0033] In the interaction process 100B, since the locations of the first application entity 130 and the second application entity 140 may be constantly changing, the subscription service device 110 cannot determine the location relationship between the first application entity 130 and the second application entity 140 and cannot perform further processing on the events generated by the first resource and the second resource.

[0034] Specifically, the second application entity 140 is a mobile monitoring device and needs to calibrate the first application data. The resource subscription entity 150 not only requires that the time of generation of the first application data (i.e., the first time point) and the time of generation of the second application data (i.e., the second time point) are close to each other, but also requires that the distance between the first location and the second location is close to each other. The subscription service device cannot determine the distance between the first location and the second location, so the resource subscription entity 150 needs to perform further processing on the first application data and the second application data, which increases the computation burden of the resource subscription entity 150. The resource subscription entity 150 is usually a mobile terminal, so the operator needs to manually determine whether the first application data and the second application data can be used for calibration, which increases the operation burden of the operator and causes inconvenience to the operator.

[0035] Also, in the interaction process 100B, 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 an event within a time threshold. However, in more scenarios, the resource subscription entity 150 may be more willing to obtain the situation where the resources corresponding to any number of application entities among the multiple application entities generate an event. For example, there is a third application entity near the second application entity, and the second application entity 140 obtains the first application data, and the third application entity also obtains the third application data. At this time, the resource subscription entity 150 may be more willing to calibrate the second application entity 140 based on the third application data and / or the first application data. In a conventional Internet of Things system, 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 events of the second application entity and the third application entity. Doing so complicates the process and occupies too much computing resources and storage space of the subscription service device 110 and the resource subscription entity 150, reducing the processing efficiency of notifications.

[0036] Therefore, the present disclosure provides an improved method, apparatus, electronic device, computer-readable storage medium, and system for sending cross-resource event notification, which can send a cross-resource event notification to a resource subscription entity when any two or more resources among a plurality of resources satisfy a cross-resource event notification rule, thereby meeting the personalized needs of users and improving the message processing efficiency of the system.

[0037] 2A and 2B show a schematic diagram and a flow chart of a method 200 for sending a cross-resource event notification according to an embodiment of the present disclosure.

[0038] Method 200 may include some or all of the operations shown in Figures 2A and 2B (e.g., some or all of operations 2010 and 2020). Of course, method 200 may include other operations not shown in Figures 2A and 2B. Optionally, method 200 may be performed by subscription service device 110. Of course, method 200 may be performed by other electronic devices having communication and computing capabilities. The following description takes subscription service device 110 as an example.

[0039] 2B, in operation 2010, a cross-resource subscription request is received from resource subscription entity 150. The cross-resource subscription request is used to subscribe to multiple resources. The cross-resource subscription request includes multiple single-resource event notification rules and cross-resource event notification rules.

[0040] 2A, in the subscription service device 110, a first resource corresponds to a first application entity 130, and a second resource corresponds to a second application entity 140. The above cross-resource subscription request is used to subscribe to multiple resources, including the above first resource, the second resource, and any other number of resources.

[0041] Optionally, the single-resource event notification rule indicates a rule for a resource to generate an event. Also, 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 among the above multiple single-resource event notification rules may be the same or different. For example, the single-resource event notification rule may indicate that when the single resource generates an event, a resource subscription entity is notified. Or, the single-resource event notification rule may indicate that when the single resource generates a certain event, one or more operations are performed on the resource or a physical device corresponding to the resource. For example, the multiple single-resource event notification rules in FIG. 2A may include a first resource event notification rule and a second resource event notification rule. The first resource event notification rule and the second resource event notification rule may be the same or different, but the present disclosure is not limited thereto. Of course, the above multiple single-resource event notification rules may include event notification rules of other resources. If the event notification rules of any single resources are the same, the same resource operation request may generate multiple events. For example, if an operation request instructs to increase the temperature data stored in both the first resource and the second resource by 5%, an event (1) that increases the temperature data of the first resource by 5% and an event (2) that increases the temperature data of the second resource by 5% are generated. If the event notification rules of the two single resources are different, multiple resource operation requests may be required to generate multiple events.

[0042] 2B, the event notification rule for the first resource may indicate that when any change occurs in the first resource, a notification indicating the change in the first resource is sent to the resource subscription entity 150. The first application entity 130 shall send a second resource operation request to the subscription service device 110 indicating that the location of the first resource has changed.

[0043] Optionally, before sending the cross-resource event notification, a resource operation request is received. The resource operation request may include one or more of location information, application data, and operation time. Also, based on the resource operation request, it can be determined that n resources among the m resources satisfy the single-resource event notification rule and satisfy the cross-resource event notification rule. If the application entity is a monitoring device, the application data may be monitoring data. For example, when each of the application entities sends a resource operation request to the subscription service device 110, the resource operation request includes one or more of the location information, application data, and operation time of the application entity, the subscription service device 110 can update the location information, application data, and operation time of the resources corresponding to these application entities based on the resource operation request, and further realize that the resources accurately represent the state of the application entities.

[0044] At this time, the subscription service device 110 can send a notification to the resource subscription entity 150 to change the location information of the first resource according to the event notification rule of the first resource. Of course, the event notification rule of the first resource may further instruct other operations, such as changing at least one of the resource level, location information, and status information of the first resource, etc. The present disclosure does not limit the content of the event notification rule of a single resource.

[0045] Optionally, the cross-resource subscription event notification rule may indicate a rule that n resources among the multiple resources generate an event. For example, the cross-resource subscription event notification rule may indicate that when n resources among the multiple resources generate an event, the resource subscription entity 150 is to send a cross-resource event notification or to operate the n resources. For example, the cross-resource subscription event notification rule may indicate that when the values ​​of the application data of any two resources among the multiple resources both increase to a predetermined threshold, a cross-resource event notification is to be sent. The cross-resource subscription event notification rule may further indicate that when the location information of any two resources among the multiple resources changes, a distance between the locations of the two resources is to be calculated. Specifically, a change in the location information of a resource may indicate that a physical location of an application entity corresponding to the resource changes. Especially when the application entity is a mobile device, it may be useful for a subscription service device to obtain the physical location of the application entity. The present disclosure does not limit the content of the cross-resource subscription event notification rule.

[0046] Optionally, upon receiving the cross-resource subscription request, the subscription service device 110 may return a cross-resource subscription response to the resource subscription entity in operation 2011 .

[0047] In operation 2020, it is determined that n (a positive integer greater than or equal to 2) resources among the m (a positive integer greater than or equal to 2) resources satisfy a single-resource event notification rule and a cross-resource event notification rule, and a cross-resource event notification is sent to the resource subscription entity.

[0048] Specifically, the above n resources satisfying the cross-resource event notification rule may include, but is not limited to, one or more combinations of: the location information of the n resources satisfies the cross-resource event notification rule, the value of n satisfies the cross-resource event notification rule, the application data of the n resources satisfies the cross-resource event notification rule, and the operation time of the n resources satisfies the cross-resource event notification rule. Accordingly, the cross-resource event notification rule may indicate, but is not limited to, one or more combinations of a distance threshold between the locations of the n resources, a threshold of n, a similarity threshold between the application data of the n resources, and a time threshold of the operation time of the n resources.

[0049] Specifically, the distance threshold may be one or more of the maximum distance, the minimum distance, and the distance range between the positions of the n resources. Similarly, the threshold of n may be one or more of 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 minimum similarity, the maximum similarity, and the similarity range of the application data of the n resources. The time threshold may be one or more of the maximum value, the minimum value, and the time difference range of the difference of the operation time points of the n resources.

[0050] For example, the cross-resource event notification rule may indicate a distance threshold between the locations of the n resources and a similarity threshold between the application data of the n resources. Or, the cross-resource event notification rule may further indicate a threshold of n, a similarity threshold between the application data of the n resources, and a time threshold between the operation time points of the n resources. Of course, the above-mentioned n resources satisfying the cross-resource event notification rule may further include the n resources satisfying other cross-resource event notification rules not mentioned, but the present disclosure is not limited thereto.

[0051] Optionally, 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, and the event notification rule of the second resource is to notify the resource subscription entity when the value of the application data of the second resource increases. The cross-resource subscription event notification rule is to instruct to send a cross-resource event notification when the values ​​of the application data of any two resources among the multiple resources both increase. Referring to FIG. 2A , the second application entity 140 sends a first resource operation request to the subscription service device 110 in operation 2100, and the first application entity 130 sends a second resource operation request to the subscription service device 110 in operation 2200. The first resource operation request is to indicate that the value of the application data of the second application entity 140 has increased by 5%, and the second resource operation request is to indicate that the value of the application data of the first application entity 130 has increased from 60 to 75. In operation 2101, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150 according to the event notification rule of the second resource based on the first resource operation request. In operation 2102, the subscription service device 110 can send a first operation response to the second application entity 140. In operation 2201, the subscription service device 110 updates the application data of the first resource according to the event notification rule of the first resource based on the second resource operation request. In operation 2202, the subscription service device can return a second operation response to the first application entity 130. At this time, the first resource and the second resource satisfy the cross-resource event notification rule, and the subscription service device 110 can send a cross-resource event notification to the resource subscription entity 150 in operation 2020.

[0052] The method 200 for sending a cross-resource event notification according to an embodiment of the present disclosure can send a cross-resource event notification to a resource subscription entity when any two or more resources among a plurality of resources satisfy a cross-resource event notification rule, thereby simplifying operation complexity, meeting user personalized needs, and improving the message processing efficiency of the system.

[0053] The method 200 for sending a cross-resource event notification according to an embodiment of the present disclosure is further exemplarily described below.

[0054] In some embodiments, 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 satisfying the cross-resource event notification rule indicating a distance threshold between the locations of the n resources.

[0055] Referring to FIG. 2A, in the above case, the subscription service device 110 receives a resource operation request (for example, the second resource operation request in FIG. 2A) including the location information of the first application entity 130. The resource subscription entity 105 further receives a resource operation request (for example, the first resource operation request in FIG. 2A) including the location information of the second application entity 140. The subscription service device 110 judges whether the event notification rule of the first resource is satisfied, and if satisfied, generates an event of the first resource. The event notification rule of the first resource (i.e., the event notification rule of the single resource) specifies that, upon receiving the location information of the first application entity 130, an event for updating the location information of the first resource is generated. At this time, since the second operation request includes the location information of the first application entity 130, 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. The cross-resource event notification rule indicates a distance threshold between the locations of the n resources, and thus 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 satisfied based on the distance. For example, if the distance threshold indicates the maximum distance between the locations of any two resources, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150 when it determines that the distance between the first location and the second location is less than the maximum distance. For example, if the distance threshold indicates the minimum distance between the locations of any two resources, and the distance between the first location and the second location is greater than the minimum distance, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150.If the distance threshold indicates a distance range (the maximum and minimum values ​​of the distance between the locations of any two resources) of the distance between the locations of any two resources, and the distance between the first location and the second location is within the distance range (greater than the minimum value in the distance range and smaller than the maximum value in the distance range), send a cross-resource event notification to the resource subscription entity 150. Specifically, the notification is determined according to a cross-resource event notification rule. For example, if the first application entity 130 and the second application entity 140 are both mobile environment monitoring devices (e.g., temperature detection devices), the cross-resource event notification rule may be to send a cross-resource event notification to the resource subscription entity 150 when the distance between the physical location of the first application entity 130 and the physical location of the second application entity 140 is smaller than the maximum distance. At this time, the temperatures detected by the first application entity 130 and the second application entity 140 can be calibrated. In this way, the calibration data are all generated within a predetermined physical range, and the accuracy of the calibration can be further guaranteed.

[0056] In some embodiments, the n resources satisfying a cross-resource event notification rule further includes the value of n satisfying a cross-resource event notification rule that further indicates a threshold value for n.

[0057] Continuing to refer to FIG. 2A, in the above case, the subscription service device 110 receives multiple resource operation requests (for example, in FIG. 2A, the subscription service device 110 receives a total of two resource operation requests). The subscription service device 110 determines that n resources satisfy the single-resource event notification rule according to the multiple resource operation requests. At this time, if the event rules of the first resource and the fifth resource are satisfied and the event rule of the second resource is not satisfied, the subscription service device 110 can determine that two resources satisfy the single-resource event notification rule, where n is 2. Based on this, the subscription service device 110 can determine whether the resource total satisfies the cross-resource event notification rule. For example, if the threshold value of n indicates the maximum value MAX of n, and n is less than MAX, the subscription service device 110 determines that the cross-resource event notification rule is satisfied, and sends a cross-resource event notification to the resource subscription entity 150. When the threshold value of n indicates a 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. When the threshold value of n indicates a maximum value MAX and a minimum value MIN of n, and n is less than MAX and greater than MIN, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity 150. Specifically, the notification is determined according to a cross-resource event notification rule. For example, if there are N application entities, and the N application entities are all sensors for monitoring environmental humidity, the cross-resource event notification rule may be that when at least M application entities of the N application entities monitor humidity changes, a cross-resource event notification is sent to the resource subscription entity 150. At this time, the humidity detected by the M application entities may be calibrated, or the average value of the M humidity values ​​may be calculated at this time.In this way, it is possible to ensure that there are sufficient calibration data samples, and further ensure the accuracy of the calibration. This realizes the creation of only one new cross resource request when N is smaller than M. Compared with the need to create multiple new cross resource requests in Fig. 1B, the above embodiment can simplify the operation process and reduce the storage space of the subscription service device.

[0058] In some embodiments, 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 satisfying the cross resource event notification rule further indicating a similarity threshold between the application data of the n resources.

[0059] 2A , in the above case, the subscription service device 110 receives a resource operation request (e.g., the second resource operation request of operation 2200) including application data of a first application entity and a resource operation request (e.g., the first resource operation request of operation 2100) including application data of a second application entity. Assume that the event notification rule of the first resource (i.e., the event notification rule of a single resource) specifies that, upon receiving the application data of the first application entity 130, an event is generated to update the application data of the first resource. In operation 2201, the subscription service device 110 updates the first application data of the first resource based on the application data of the first application entity. Similarly, in operation 2101, the subscription service device 110 further updates the second application data of the second resource based on the application data of the second application entity. The cross-resource event notification rule indicates a similarity threshold between the application data of the n resources, and the subscription service device 110 calculates the similarity between the first application data and the second application data, and determines whether the cross-resource event notification rule is satisfied based on the similarity. For example, if the similarity threshold indicates the maximum similarity between 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 can send a cross-resource event notification to the resource subscription entity. If the similarity threshold indicates the minimum similarity between the application data of any two resources, and the similarity between the first application data and the second application data is greater than the minimum similarity, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity.When 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 a cross-resource event notification to the resource subscription entity. Specifically, the notification is determined according to a cross-resource event notification rule. For example, when the first application entity 130 and the second application entity 140 are both mobile environment monitoring devices (e.g., temperature detection devices), the cross-resource event notification rule may be that, when the similarity between the temperature data detected by the first application entity 130 and the second application entity 140 is less than the maximum similarity, a notification is sent to the resource subscription entity 150, which can calibrate the temperatures detected by the first application entity 130 and the second application entity 140. In this way, the similarity of the calibration data can be guaranteed, and the accuracy of the calibration can be further guaranteed.

[0060] In some embodiments, the resource operation request includes an operation time point. The n resources satisfying the cross-resource event notification rule further includes the operation time points of the n resources satisfying a cross-resource event notification rule further indicating a time threshold of the operation time points of the n resources.

[0061] 2A, in the above case, the subscription service device 110 receives a resource operation request (e.g., the second resource operation request of the operation 2200) including an operation time of a first application entity and a resource operation request (e.g., the first resource operation request of the operation 2100) including an operation time of a second application entity. Assume that the event notification rule of the first resource (i.e., the event notification rule of a single resource) specifies that, upon receiving the operation time of the first application entity 130, an event is generated to update the operation time of the first resource. In the operation 2201, the subscription service device 110 updates the first operation time of the first resource based on the application data of the first application entity. Similarly, in the operation 2101, the subscription service device 110 further updates the second operation time of the second resource based on the operation time of the second application entity. The cross-resource event notification rule indicates a time threshold between the operation times of the n resources, so that the subscription service device 110 calculates a time difference between the first operation time and the second operation time, and judges whether the cross-resource event notification rule is satisfied based on the time difference. For example, if the time threshold indicates a maximum time difference between the operation times of any two resources, and the time difference between the first operation time and the second operation time is smaller than the maximum time difference, the subscription service device 110 can send a cross-resource event notification to the resource subscription entity. If the time threshold indicates a minimum time difference between the operation times of any two resources, and the time difference between the first operation time and the second operation time is larger than the minimum time difference, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity. If the time threshold indicates a time difference range between the operation times of any two resources, and the time difference between the first operation time and the second operation time is within the time difference range, the subscription service device 110 sends a cross-resource event notification to the resource subscription entity. Specifically, the notification is determined according to cross-resource event notification rules.For example, if the first application entity 130 and the second application entity 140 are both mobile environment monitoring devices (e.g., temperature detection devices), the cross-resource event notification rule may be that when the difference value between the time points of the temperature data detected by the first application entity 130 and the second application entity 140 is smaller than the maximum time difference, a notification is sent to the resource subscription entity 150 to calibrate the temperatures detected by the first application entity 130 and the second application entity 140. In this way, the calibration data are all generated within a predetermined time range, and the accuracy of the calibration can be further guaranteed.

[0062] In some embodiments, the n resources satisfying a cross-resource event notification rule further includes a notification content type of the n resources satisfying the cross-resource event notification rule, the cross-resource event notification rule further instructing: notifying the resource subscribing entity to calibrate application data if the notification content type of any two resources of the n resources is identical; and notifying the resource subscribing entity to correlate application data if the notification content type of any two resources of the n resources is different.

[0063] Continuing to refer to FIG. 2A, in the above case, the subscription service device 110 receives a resource operation request of a first application entity (operation 2200) and a resource operation request of a second application entity (operation 2100). The subscription service device 110 determines whether the n resources satisfy the event notification rule of a single resource according to the 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. At this time, when the event notification rules of the first resource and the second resource are both satisfied, the subscription service device 110 can determine that the notification contents of the first resource and the second resource are different, and therefore the subscription service device 110 notifies the resource subscription entity 150 to perform correlation analysis on the application data. Specifically, for example, when the first application entity 130 and the second application entity 140 are both mobile environment monitoring devices (e.g., temperature detection devices), the subscription service device 110 makes the resource subscription entity 150 analyze the reasonableness of the temperature data detected by the second application entity based on the positional relationship between the first application entity 130 and the second application entity 140. Meanwhile, 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, and 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.At this time, if the event notification rules of the first resource and the second resource are both satisfied, the subscription service device 110 can determine that the notification contents of the first resource and the second resource are identical, and therefore the subscription service device 110 notifies the resource subscription entity 150 to calibrate the application data. Specifically, for example, when the first application entity 130 is a fixed temperature monitoring device and the second application entity 140 is a mobile environment monitoring device (e.g., a temperature detection device), the subscription service device 110 makes the resource subscription entity 150 calibrate the temperature data detected by the first application entity 130 and the second application entity 140.

[0064] FIG. 3 illustrates a structural diagram of an exemplary cross-resource subscription resource 300 according to an embodiment of the present disclosure.

[0065] When the subscription service device 110 receives the cross-resource subscription request, the subscription service device 110 generates a cross-resource subscription resource 300 (i.e., <crossresourcessubscription>For example, the cross-resource subscription resource 300 optionally includes one or more of the following: an address of a resource subscription entity (notificationURI), a type of notification event (notificationEventCat), an address of a subscriber (subscriberURI) (e.g., an address of an application entity), regular resources as targets (regularResourcesAsTarget), subscription resources as targets (subscriptionResourcesAsTarget), a time window type (timeWindowType), a size of the time window (timeWindowSize), a set of event notification rules for a single resource (eventNotificationCriteriaSet), a location reference of the target resource (targetResourceLocationRef), a location criterion (LocationRef), a content type of the cross-resource subscription notification (crossResourceContentType), an enable switch of some subscriptions (partResourceNotificationEnable), and a generation number of some subscriptions (partResourceNotificationNr), etc., as shown in FIG. Cross-resource subscription resources 300 may include other content items not shown in FIG. 3, although this disclosure is not limited in this regard.

[0066] The content items in the cross-resource subscription resource 300 are further described below.

[0067] For example, the n resources satisfying the cross-resource event notification rule in the above operation 2020 may include that the location information of the n resources satisfies the cross-resource event notification rule, in which the cross-resource event notification rule indicates the maximum distance between the locations of any two resources among the n resources.

[0068] To this end, the cross-resource subscription resource 300 may include a location reference and a location criterion (or location check) of the target resource. Specifically, the location criterion may be specified as a predetermined location range or location distance. The subscription service device 110 determines that the location information of any two resources among the n resources satisfies the cross-resource event notification rule by comparing the distances between multiple application entities. The specific location information can be obtained by the location reference of the target resource. The location reference of the target resource indicates a location index corresponding to a certain AE or CSE of the target resource. For example, the location reference of the target resource may be: <ae> / <locationpolicy> / locationContainerID, or <cse> / <locationpolicy>Can contain / locationContainerID. <ae>and <cse>A resource is used to identify the application logic of an entity. <ae>or <cse>Sub-resources of a resource - <locationpolicy>The resource is used to store the location logic of the target entity. The locationContainerID is the actual physical location of a given entity. <container>is a URI that stores <container>may act as a container for storing specific content information.

[0069] Specifically, FIG. 4 shows a schematic diagram of an example 400 according to an embodiment of the present disclosure to further illustrate cross-resource event notification rules.

[0070] FIG. 4 shows eight 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, and the seven application entities within the dashed line (e.g., AE2 and AE3) are mobile monitoring devices. Usually, the monitoring data of the fixed monitoring device is more accurate than that of the mobile monitoring device, so the monitoring data of the mobile monitoring device can be calibrated with the monitoring data of the fixed monitoring device. The above cross-resource event notification rule may instruct to send a cross-resource event notification when the locations of two resources among the resources corresponding to the above eight application entities meet a location threshold (when the location threshold indicates the maximum distance between the two resources). Assume that each of AE1 to AE3 sends a resource operation request including the monitoring data to the subscription service device 110. The subscription service device 110 can obtain the specific physical locations of AE1 to AE3 based on the location reference of the target resource in the cross-resource subscription resource, and calculate the distance between each two of the three monitoring devices. By comparing these distances with the location criteria, 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 can further send a cross-resource event notification to the resource subscription entity 150, informing it that the monitoring data of AE2 can be calibrated with the monitoring data of AE1.

[0071] Compared with the interaction process between devices participating in the transmission of cross-resource event notification shown in Fig. 1B, the method 200 according to the embodiment of the present disclosure can directly determine the location relationship of multiple application entities, and further process multiple resources, thereby reducing the computation burden of the resource subscription entity 150 and making it easier for an operator to operate the resource subscription entity 150.

[0072] For example, the n resources satisfying the cross-resource notification event rule further includes that the value of n satisfies the cross-resource notification event rule, where the cross-resource event notification rule indicates a threshold value of n.

[0073] For this purpose, the cross-resource subscription resource 300 may include a part subscription enable switch (partResourceNotificationEnable) and a part subscription generation number (partResourceNotificationNr). The part subscription enable switch indicates whether to turn on the part cross-resource subscription notification, and may be a binary number, where a value of 0 indicates that the part cross-resource subscription notification is not turned on, and a value of 1 indicates that the part cross-resource subscription notification is turned on. The part subscription generation number indicates the minimum number of resources for which the cross-resource subscription notification generates an event.

[0074] Referring to FIG. 4, the cross-resource subscription request is used to subscribe to eight application entities shown in FIG. 4. In addition, the cross-resource subscription request sets the enable switches of some subscriptions in the cross-resource subscription resource 300 to 1, and sets the generation number of some subscriptions to 3. Thus, the cross-resource event notification rule may instruct to send a cross-resource event notification when the monitoring data of the resources corresponding to three or more application entities among the eight application entities in FIG. 4 is updated. For example, AE1 to AE3 each send a resource operation request to the subscription service device 110 to request to update the monitoring data in the resources corresponding thereto. At this time, if the subscription server 110 determines that the number of resources is equal to three, it sends a cross-resource event notification to the resource subscription entity 150.

[0075] Compared with the interaction process between devices participating in the transmission of cross-resource event notification shown in Fig. 1B, the method 200 only needs to create one new cross-resource subscription resource 300, instead of creating one new cross-resource subscription resource for every two of the eight application entities (a total of 28 cross-resource subscription resources). By creating one new cross-resource subscription resource 300, the method 200 can obtain events generated by resources corresponding to any number of application entities among the multiple application entities, thereby greatly saving computation resources and storage space and improving the processing efficiency of notifications.

[0076] For example, the n resources satisfying the cross-resource event notification rule further includes that the application data of the n resources satisfy the cross-resource event notification rule. In this case, the cross-resource event notification rule indicates a similarity threshold between the application data of any two resources among the n resources. For example, in the application scene of calibrating multiple monitoring devices in FIG. 4, the cross-resource event notification rule may indicate that the multiple monitoring devices are calibrated when the similarity of the monitoring data measured by any number of the multiple monitoring devices is greater than the minimum similarity. For example, each of AE1 to AE3 acquires first monitoring data, second monitoring data, and third monitoring data. When the similarity between the first monitoring data and the second monitoring data is higher than the minimum similarity, the monitoring data of AE2 can be calibrated based on the first monitoring data.

[0077] For example, the above n resources satisfying the cross-resource event notification rule further includes that the operation time points of the n resources satisfy the cross-resource event notification rule, in which the cross-resource event notification rule further indicates a time threshold between the operation time points of any two resources among the n resources.

[0078] Therefore, the cross-resource subscription resource 300 may include a time window type and a time window size. Specifically, the time window size may indicate the maximum value w of the difference between the operation time points of two resources. For example, in the scene of Fig. 4, AE1 to AE3 respectively obtain the first monitoring data at time T1, the second monitoring data at time T2, and the third monitoring data at time T3. If the difference value between T1 and T3 is smaller than w, the monitoring data of AE3 can be calibrated based on the first monitoring data.

[0079] For example, the n resources satisfying the cross-resource event notification rule further includes that the notification content types of the n resources satisfy the cross-resource event notification rule, in which the cross-resource event notification rule further instructs: when the notification content types of any two resources among the n resources are identical, notify the resource subscribing entity to calibrate application data, and when the notification content types of any two resources among the n resources are different, notify the resource subscribing entity to correlate application data.

[0080] Thus, the cross-resource subscription resource 300 may include a content type of cross-resource subscription notification. For example, if the notification content type of two resources is both monitoring data, the subscription service device 110 may be calibrated using the monitoring data. If one of the notification content types of two resources is monitoring data and the other is location data, correlation analysis may be performed using the monitoring data and the location data. For example, changes in the monitoring data may be analyzed at a certain location.

[0081] FIG. 5 illustrates a flow chart of an example 500 according to an embodiment of the present disclosure.

[0082] In the example 500, the resource subscription entity 150, application entities AE1-AEn register with the subscription service device 110.

[0083] The resource subscription entity 150 sends a cross-resource subscription request to the subscription service device 110, including a cross-resource event notification rule and an event notification rule for subscribing to events generated by AE1-AEn. The cross-resource event notification rule indicates that the location interval of AE2-AEn is less than a location threshold and the difference in event generation time of AE2-AEn is less than a time threshold. The subscription service device 110 creates new subscription resources (including the event notification rule) for AE1-AEn.

[0084] The subscription service device 110 creates a new cross-resource subscription resource and returns a cross-resource subscription response.

[0085] The application entity AE2 sends a first resource operation request that includes the monitoring data and the location information.

[0086] The subscription service device 110 determines whether the monitoring data of AE2 satisfies the event notification rule of AE2, and if so, generates a first event and returns a first operation response.

[0087] The application entity AE1 sends a second resource operation request.

[0088] The subscription service device 110 determines whether the monitoring data of application entity AE1 satisfies the event notification rule of AE1, and if so, generates a second event and returns a second operation response.

[0089] The subscription service device 110 determines whether the first event and the second event satisfy the cross-resource notification rule, i.e., whether the first event and the second event satisfy the following four conditions: (1) whether the location information corresponding to the first event and the second event is less than a location threshold, (2) whether the time information corresponding to the first event and the second event is less than a time threshold, (3) whether the similarity between the application data corresponding to the first event and the second event is greater than a similarity threshold, and (4) whether the total number of events corresponding to the first event and the second event is greater than a resource total threshold. If the first event and the second event satisfy the above four conditions, send a cross-resource event notification to the resource subscription entity 150.

[0090] Upon receiving the notification, the resource subscribing entity 150 may send a notification response back to the subscription service device 110. The resource subscribing entity 150 may further send a calibration request to the application entity AE2 and receive a calibration response sent by the application entity AE2.

[0091] The subscription service device 110 further receives a third resource operation request and a fourth resource operation request sent by application entities AE4 and AE5, the third resource operation request including the monitoring data and the location information.

[0092] The subscription service device 110 determines whether the monitoring data of the application entities AE4 and AE5 satisfy the event notification rules, and if so, generates a third event and a fourth event, and returns an operation response.

[0093] The subscription service device 110 determines whether the third and fourth events satisfy a cross-resource notification rule, and if so, sends a cross-resource event notification to the resource subscription entity 150 .

[0094] FIG. 6 illustrates a schematic diagram of an apparatus 600 for sending cross-resource event notifications according to an embodiment of the present disclosure.

[0095] The system for sending cross-resource event notification may include: a device for sending cross-resource event notification, which is a subscription service device; a resource subscription entity configured to send a cross-resource subscription request to the subscription service device; and an application entity configured to send a resource operation request to the subscription service device. The device 600 for sending cross-resource event notification includes a cross-resource subscription unit 601 and a notification unit 602.

[0096] The cross-resource subscription unit 601 is 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, and includes an event notification rule and a cross-resource event notification rule of each resource of the multiple resources.

[0097] The notification unit 602 is configured to send a cross-resource event notification to a resource subscription entity when n resources among the multiple resources satisfy a single-resource event notification rule and the n resources satisfy a cross-resource event notification rule.

[0098] FIG. 7 illustrates a structural diagram of an electronic device 700 for sending cross-resource event notifications according to an embodiment of the present disclosure.

[0099] 7, an electronic device 700 that transmits a cross-resource event notification may include a processor 701 and a memory 702. The processor 701 and the memory 702 may be connected via a bus 703. The electronic device 700 may be a tower server, a rack server, a blade server, a cabinet server, or the like.

[0100] The processor 701 can execute various operations and processes according to the programs stored in the memory 702. Specifically, the processor 701 may be an integrated circuit chip having a signal processing capability. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware unit. Each method, step, and logic block diagram disclosed in the embodiments of the present application can be realized or executed. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc., and may be an X86 architecture or an ARM architecture.

[0101] The memory 702 stores computer instructions that, when executed by the processor 701, implement the method 200 for transmitting a cross-resource event notification. The memory 702 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM) that functions as an external high speed cache. Many forms of RAM may be used, such as, by way of example and not limitation, static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronously attached dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory of the methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

[0102] The present disclosure further provides a system for transmitting a cross-resource event notification. The system for transmitting a cross-resource event notification may include a subscription service device 110, a resource subscription entity 150, and an application entity (e.g., a first application entity 130 and a second application entity 140) as shown in Figures 1A and 1B. The resource subscription entity 150 is configured to transmit a cross-resource subscription request to the subscription service device. The application entity is configured to transmit a resource operation request to the subscription service device.

[0103] The present disclosure further provides a computer-readable storage medium having computer instructions stored thereon that, when executed by a processor, implements the method 200 for sending cross-resource event notifications described above. Similarly, the computer-readable storage medium in embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The computer-readable storage media described herein are intended to include, without being limited to, these and any other suitable types of memory.

[0104] The present disclosure provides an improved method, device, electronic device, computer-readable storage medium and system for sending cross-resource event notification, which can process complex event information generated by some resources among multiple resources and can efficiently process information notifications.

[0105] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, program segment, or part of code that includes executable instructions for implementing a certain logical function. It should also be noted that in alternative implementations, the functions shown in the blocks may occur in a different order than that shown in the drawings. For example, two successively illustrated blocks may in fact be essentially executed in parallel, or may be executed in a reverse order depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented in a dedicated hardware-based system for implementing a certain function or operation, or in a combination of dedicated hardware and computer instructions.

[0106] In general, various exemplary embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, firmware, logic, or any combination thereof. Some 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. Where various aspects of the embodiments of the present disclosure have been illustrated or described using block diagrams, flowcharts, or some other graphical representations, it will be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in, by way of non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof.

[0107] The exemplary embodiments of the present invention described in detail above are merely illustrative and not limiting. Those skilled in the art will appreciate that various modifications and combinations of these embodiments or features thereof can be made without departing from the principles and spirit of the present invention, and such modifications should fall within the scope of the present invention.

[0108] The above are only exemplary embodiments of the present disclosure, and do not limit the protection scope of the present disclosure, which is determined by the appended claims. [Explanation of symbols]

[0109] 110 Subscription Service Equipment 120 Network 130 First Application Entity 140 Secondary Application Entity 150 Resource Subscription Entities< / container> < / container> < / locationpolicy> < / cse> < / ae> < / cse> < / ae> < / locationpolicy> < / cse> < / locationpolicy> < / ae> < / crossresourcessubscription>

Claims

1. 1. A method for sending a cross-resource event notification, comprising: receiving a cross-resource subscription request from a resource subscription entity for subscribing to a plurality of resources, the cross-resource subscription request including a plurality of single-resource event notification rules and cross-resource event notification rules corresponding to the plurality of resources including m resources, the m resources being a positive integer equal to or greater than 2; determining that n resources (n being a positive integer equal to or greater than 1) among the m resources each satisfy a corresponding single-resource event notification rule and a cross-resource event notification rule, and sending a cross-resource event notification to the resource subscription entity; receiving a resource operation request prior to sending the cross-resource event notification; determining, based on the resource operation request, that the n resources among the m resources satisfy a corresponding single-resource event notification rule and satisfy the cross-resource event notification rule.

2. The method for sending a cross-resource event notification described in claim 1, wherein the resource operation request includes one or more of location information, application data, and operation time.

3. the resource operation request includes location information; The method for sending a cross-resource event notification according to claim 2 , wherein the step of the n resources satisfying a cross-resource event notification rule further comprises: location information of the n resources satisfying a cross-resource event notification rule.

4. The method of claim 3 , wherein the cross-resource event notification rule indicates a distance threshold between the locations of n resources.

5. receiving a resource operation request including location information of a first application entity and a resource operation request including location information of a second application entity; updating a first location of a first resource based on location information of the first application entity; updating a second location of a second resource based on location information of the second application entity; sending a cross-resource event notification to a resource subscription entity if the distance threshold is a maximum distance between the locations of any two resources and the distance between the first location and the second location is less than the maximum distance; or sending a cross-resource event notification to a resource subscription entity if the distance threshold is a minimum distance between the locations of any two resources and the distance between the first location and the second location is greater than the minimum distance; or 5. The method of claim 4, further comprising the step of: sending a cross-resource event notification to a resource subscription entity when the distance threshold is a distance range between the locations of any two resources and the distance between the first location and the second location is within the distance range.

6. The method for sending a cross-resource event notification according to any one of claims 1 to 5, wherein the step of the n resources satisfying a cross-resource event notification rule further comprises: the n resources satisfying a cross-resource event notification rule.

7. The method of claim 6 , wherein the cross-resource event notification rule further indicates a threshold value of n, where n<m.

8. the threshold value of n indicates a maximum value MAX of n, and if n is less than MAX, sending a cross-resource event notification to a resource subscription entity; or the threshold value of n indicates a minimum value MIN of n, and if n is greater than MIN, sending a cross-resource event notification to a resource subscription entity; or 8. The method of claim 7, further comprising the step of: sending a cross-resource event notification to a resource subscription entity when the threshold value of n indicates a maximum value MAX and a minimum value MIN of n, and when n is less than MAX and n is greater than MIN.

9. the resource operation request includes application data; The method for sending a cross-resource event notification according to any one of claims 2 to 5, wherein the step of the n resources satisfying a cross-resource event notification rule further includes: application data of the n resources satisfying a cross-resource event notification rule.

10. The method for sending a cross-resource event notification according to claim 9 , wherein the cross-resource event notification rule further indicates a similarity threshold between application data of the n resources.

11. receiving a resource operation request including application data of a first application entity and a resource operation request including application data of a second application entity; updating first application data of a first resource based on application data of the first application entity; updating second application data of a second resource based on application data of the second application entity; sending a cross-resource event notification to a resource subscription entity if the similarity threshold is a maximum similarity of 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; or sending a cross-resource event notification to a resource subscription entity if the similarity threshold is a minimum similarity of application data of any two resources, and the similarity between the first application data and the second application data is greater than the minimum similarity; or 11. The method of claim 10, further comprising the step of: sending a cross-resource event notification to a resource subscription entity if the similarity threshold is a similarity range of application data of any two resources, and the similarity between the first application data and the second application data is within the similarity range.

12. The resource operation request includes an operation time point; The method for sending a cross-resource event notification according to any one of claims 2 to 5, wherein the step of the n resources satisfying a cross-resource event notification rule further includes the step of the operation time of the n resources satisfying the cross-resource event notification rule.

13. The method for sending a cross-resource event notification according to claim 12 , wherein the cross-resource event notification rule further indicates a time threshold of an operation point of the n resources.

14. receiving a resource operation request including an operation time of a first application entity and a resource operation request including an operation time of a second application entity; updating a first operation time of a first resource according to an operation time of the first application entity; updating a second operation time of a second resource according to an operation time of the second application entity; sending a cross-resource event notification to a resource subscription entity when the time threshold is a maximum time difference between operation times of any two resources, and the time difference between the first operation time and the second operation time is less than the maximum time difference; or sending a cross-resource event notification to a resource subscription entity when the time threshold is a minimum time difference between operation times of any two resources, and the time difference between the first operation time and the second operation time is greater than the minimum time difference; or The method for sending a cross-resource event notification of claim 13, further comprising: sending a cross-resource event notification to a resource subscription entity when the time threshold is a time difference range between operation times of any two resources, and the time difference between the first operation time and the second operation time is within the time difference range.

15. The method for sending a cross-resource event notification according to any one of claims 1 to 14, wherein the step of the n resources satisfying a cross-resource event notification rule further includes the step of the notification content type of the n resources satisfying the cross-resource event notification rule.

16. The cross-resource event notification rule comprises: notifying a resource subscription entity to update application data when the notification content types of any two of the n resources are the same; 16. The method for sending cross-resource event notifications of claim 15, further instructing: notifying a resource subscribing entity to correlate application data if the notification content types of any two of the n resources are different.

17. receiving a resource operation request of a first application entity and a resource operation request of a second application entity; determining a first notification content type of a first resource according to a resource operation request and an event notification rule of the first application entity; or determining a second notification content type of a second resource according to a resource operation request and an event notification rule of the second application entity; or notifying a resource subscribing entity to update application data if the first notification content type and the second notification content type are identical; or 20. The method of claim 16, further comprising: notifying a resource subscribing entity to correlate application data if the first notification content type and the second notification content type are different.

18. 1. A system for transmitting cross-resource event notifications, comprising: a subscription service device, the device for sending cross-resource event notifications; a resource subscription entity that sends a cross-resource subscription request to the subscription service device; an application entity that sends a resource operation request to the subscription service device; The device for transmitting the cross resource event notification comprises: A cross-resource subscription unit for receiving a cross-resource subscription request for subscribing to a plurality of resources from a resource subscription entity, the cross-resource subscription request including a plurality of single-resource event notification rules and cross-resource event notification rules respectively corresponding to the plurality of resources including m resources (a positive integer of 2 or more); a notification unit for determining that n (a positive integer equal to or greater than 2) resources among the m resources respectively satisfy a corresponding single-resource event notification rule and a cross-resource event notification rule, and sending a cross-resource event notification to the resource subscription entity; The device for transmitting the cross resource event notification further comprises: receiving a resource operation request prior to sending the cross-resource event notification; A system for sending a cross-resource event notification, determining, based on the resource operation request, that the n resources of the m resources satisfy a corresponding single-resource event notification rule and satisfy the cross-resource event notification rule.

19. An electronic device for transmitting a cross resource event notification, comprising: A processor; and a memory having computer instructions stored therein; An electronic device, wherein the computer instructions, when executed by a processor, result in the method for sending a cross-resource event notification according to any of claims 1 to 17 being implemented.

20. A computer-readable storage medium having computer instructions stored thereon, A storage medium, wherein the computer instructions, when executed by a processor, result in a method for sending cross-resource event notifications according to any one of claims 1 to 17.

Images