JP7653371B2 - Method, apparatus, device and storage medium for subscribing to resources in the field of Internet of Things - Google Patents

Description

This application claims priority to Chinese Patent Application No. 201910433275.7, filed on May 23, 2019, the entire contents of which are incorporated herein by reference as part of this application.

This application relates to the field of resource subscription, and more particularly to a method, apparatus, device, and storage medium for subscribing to resources in the field of the Internet of Things.

With the development of information technology, especially Internet technology, Internet of Things technology is gradually maturing to realize informatization, remote management control and intelligence. The Internet of Things uses communication technologies such as local networks and the Internet to connect sensors, controllers, devices, people and things in new ways, forming connections between people and things, and between things and things. As Internet of Things technology develops rapidly in various application fields, more and more devices are accessing the Internet of Things, and various new application fields such as smart homes, smart transportation and smart health are emerging.

As the networking of things progresses, more and more application entities access the cloud, and the application entities are constantly digitized, forming corresponding virtual entities (called digital twins) for the application entities in the cloud. Applications can realize operations such as obtaining the status and sending commands to the application entities by controlling the virtual entities in the cloud. In order for an application entity to access the cloud, it needs to access the network of things platform by registering, and the network of things platform will generate corresponding resources for the application entity, and the application can obtain the state changes of the application entity by subscribing to the corresponding resources of the application entity.

The present application provides a method, an apparatus, a device, and a storage medium for subscribing to resources in the Internet of Things field.

According to one aspect of the present disclosure, a method for subscribing to a resource is provided, the method for subscribing to a resource including the steps of: a service entity receiving a subscription request for a first entity from a third entity; determining a second entity related to the first entity; generating a subscription for at least the second entity; and transmitting a subscription response indicating a result of the subscription.

According to one aspect of the present disclosure, a method for subscribing to another resource is provided, the method for subscribing to another resource includes sending a subscription request to a first entity and receiving a subscription response to the subscription request, the second entity and the first entity being associated, and the subscription response indicating at least a result of generating a subscription to the second entity.

According to another aspect of the present disclosure, an apparatus for subscribing to a resource is provided, the apparatus for subscribing to a resource including a receiving unit for a service entity to receive a subscription request for a first entity from a third entity, a determining unit for determining a second entity related to the first entity, a generating unit for generating a subscription for at least the second entity, and a transmitting unit for transmitting a subscription response indicating a result of the subscription.

According to yet another aspect of the present disclosure, a device for subscribing to a resource is provided, the device for subscribing to a resource including a memory configured to store computer-readable instructions and a processor configured to execute the computer-readable instructions stored in the memory, and when the processor executes the computer-readable instructions, the device performs the following steps: a service entity receives a subscription request for a first entity from a third entity; determines a second entity related to the first entity; generates a subscription for at least the second entity; and transmits a subscription response to indicate a result of the subscription.

According to yet another aspect of the present disclosure, a computer-readable storage medium having computer-readable instructions stored thereon, which, when executed by a computer, causes the computer to perform a method for subscribing to a resource, the method including the steps of: a service entity receiving a subscription request for a first entity from a third entity; determining a second entity related to the first entity; generating a subscription for at least the second entity; and transmitting a subscription response indicating a result of the subscription.

In the above aspect of the present disclosure, a subscription to a second entity related to a first entity can be realized by sending a subscription response to a third entity to indicate the result of generating a subscription to the second entity depending on the state of the second entity, thereby making the subscription resource more abundant. Also, different subscription modes are created depending on the state of the second entity, thereby realizing a diversity of modes for different cases.

The above and other objects, features and advantages of the present disclosure will become more apparent by describing the embodiments of the present disclosure in more detail with reference to the drawings. The drawings are used to provide a further understanding of the embodiments of the present disclosure, constitute a part of the specification, and are used to explain the present disclosure together with the embodiments of the present disclosure, and are not intended to limit the present disclosure. In the drawings, the same reference numerals generally represent the same parts or steps.
FIG. 1 is a schematic diagram of a system for subscribing to resources for implementing an embodiment of the present disclosure. FIG. 2 is a flowchart of a method for subscribing to a resource according to an embodiment of the present disclosure. FIG. 3 is a flowchart of a method for creating a subscription to a second entity according to an embodiment of the present disclosure. FIG. 4 is a flowchart of another method for creating a subscription to a second entity according to an embodiment of the present disclosure. FIG. 5 is a flowchart of another method for subscribing to a resource according to an embodiment of the present disclosure. FIG. 6 is a schematic diagram of a method for subscribing to a resource according to a first example of the present disclosure. FIG. 7 is a schematic diagram of a method for subscribing to a resource according to a second example of the present disclosure. FIG. 8 is a schematic diagram of a method for subscribing to a resource according to a third example of the present disclosure. FIG. 9 is a schematic diagram of an apparatus for subscribing to a resource according to an embodiment of the present disclosure. FIG. 10 is a schematic diagram of a device for subscribing to a resource according to an embodiment of the present disclosure. FIG. 11 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure.

The technical solutions in the embodiments of the present disclosure are described below clearly and completely with reference to the drawings in the embodiments of the present disclosure. It is clear that the described embodiments are only some of the embodiments of the present disclosure, and are not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present disclosure without requiring creative labor, all fall within the scope of protection of the present disclosure.

As used in this disclosure, the terms "first," "second," and similar terms do not denote any order, quantity, or importance, but merely distinguish between different elements. Similarly, similar terms such as "comprise" or "include" include the elements or components appearing before the term inclusive of the elements or items listed after the term and equivalents thereof, but do not exclude other elements or components. Similar terms such as "coupled" or "connected to each other" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect.

In some embodiments, typically, a sender (e.g., a subscriber) sends a request to a receiver (e.g., a service entity) to create a subscription resource, the receiver creates a subscription at the subscribed resource, and the receiver sends a subscription response to the notified party. Because the receiver subscribed only to the target resource specified in the sender's subscription request, the subscribed content cannot satisfy the application's requirements.

Flowcharts are used in this application to describe steps of methods according to embodiments of the application. It should be understood that previous or subsequent steps do not necessarily occur in precise order. Conversely, various steps may be reversed or processed simultaneously. Also, other operations may be added to these processes, and steps or steps may be removed from these processes.

As an extension of the Internet, the Internet of Things includes the Internet and all resources on the Internet and is compatible with all applications on the Internet. As Internet of Things technology is applied in various fields, various new smart Internet of Things application fields such as smart rooms, smart transportation and smart health are emerging.

With the development of Internet of Things technology, more and more terminal devices, such as smoke alarms, fire alarms, manhole cover movement sensors, etc., access the Internet of Things platform. The Internet of Things platform may be realized, for example, as a common service entity (CSE), and the terminal device may access the common service entity by sending registration information to the common service entity, and the common service entity manages the accessed terminal device. The terminal device may be represented as an application entity (AE), and the application entity that has accessed the common service entity can perform operations such as data transmission and information interaction with the common service entity. It should be noted that the application entity described in this specification may be an Internet of Things terminal device, or may be an application software module in the Internet of Things terminal device, or may be an application software module in the Internet of Things server.

An application entity (AE) and a common service entity (CSE) are logical entities, a physical device includes logical entities, a simple terminal device may include only an application entity, and a complex terminal device may include an application entity and a common service entity. For example, a server includes at least a common service entity and may include an application entity at the same time. The difference between a common service entity included in a terminal device and a common service entity included in a server lies in the difference in function. In general, the common service entity of a server includes more functions, such as device management. The common service entity described in this specification may be a service software module in an Internet of Things terminal device or a service software module in an Internet of Things server.

In the present disclosure, in response to a subscription request by a subscriber for a desired application entity, a subscription for an application entity associated with the desired application entity can be generated, and different subscription modes can be generated for the state of the application entity associated with the desired application entity, thereby realizing subscription diversification.

First, referring to FIG. 1, a system for subscribing to resources to realize an embodiment of the present disclosure will be described.

As shown in FIG. 1, in the Internet of Things system, the initiator of the subscription request may be an application entity or a generic service entity. Taking the application entity as an example, the application entity sends a subscription request 10 for an object 11 to the generic service entity. For example, when the generic service entity receives the subscription request for the object 11, it can directly create a subscription for the object 11 and send a subscription response 16 to the application entity indicating that the subscription for the object 11 has been created. In some embodiments, as shown in FIG. 1, when the generic service entity receives the subscription request for the object 11, it determines whether there is an associated object 13, and if there is an associated object 13, it creates a subscription for the associated object 13 or for the object 11 and the associated object 13 by determining the state (14) of the associated object, and then the generic service entity sends a subscription response 16 to the application entity indicating that the subscription for the associated object 13 or the object 11 and the associated object 13 has been created. As described above, subscriptions for associated objects related to an object can be realized, thereby making subscribing resources more abundant. For example, if the initiator of the subscription request does not know the related object or does not have the authority to know the related object, the initiator of the subscription request can realize the subscription to the related object through the system described in FIG. 1, enrich the subscribing resource, and improve the efficiency of the system. Note that the second entity may be one or more entities.

Hereinafter, with reference to FIG. 2, a method 100 for subscribing to a resource in an Internet of Things field according to an embodiment of the present disclosure will be described. The method may be performed by a general-purpose service entity (e.g., a retail server). The Internet of Things subscribing to a resource includes the following steps S101 to S104.

In step S101, the service entity receives a subscription request for the first entity from the third entity.

In step S102, a second entity related to the first entity is determined.

In step S103, a subscription is generated for at least the second entity.

In step S104, a subscription response is sent to indicate the results of the subscription.

As shown in FIG. 2, in step S101, the service entity receives a subscription request for the first entity from a third entity. For example, the service entity may receive a request from the third entity carrying correlation information that includes a subscription request for the first entity.

For example, the first entity (AE1) may be a virtual electronic tag for indicating corresponding product information managed by the service entity. This virtual electronic tag is a digital twin of a physical electronic tag, includes attributes such as an electronic tag identifier and a product identifier, and is associated with (or bound to) a corresponding product via the product identifier (ID). For example, the first entity may be a virtual shelf electronic tag, which is associated with a corresponding product on a shelf via the product identifier. The third entity (AE3) may be a shelf management application or a virtual shopping terminal. For example, in this step, the general-purpose service entity receives a subscription request for the shelf electronic tag AE1 by AE3 (shelf management application or shopping terminal).

Then, in step S102, a second entity related to the first entity is determined.

For example, the second entity (AE2) may be a virtual electronic tag managed by the service entity to indicate corresponding product information. For example, the second entity may be a virtual inventory electronic tag, which is associated with the corresponding product in the inventory via the product identifier. For example, in this step, it may be determined that the inventory electronic tag AE2 is associated with the shelf electronic tag AE1.

For example, the generic service entity may determine a second entity associated with a first entity by determining whether the first entity and the second entity are for the same object. For example, if the first entity and the second entity are for the same object, the generic service entity may determine that the second entity is associated with the first entity, and if the first entity and the second entity are for different objects, the generic service entity may determine that the second entity is not associated with the first entity.

For example, if a product associated with a first entity and a product associated with a second entity belong to the same category, the first entity and the second entity are considered to be for the same object. As one example, if the product associated with the first entity is a Fuji apple and the product associated with the second entity is a Huang Yuanshuai apple (a type of apple in the Chinese region), it is determined that these two products belong to the same category (both belong to apples), i.e., the first entity and the second entity can be considered to be for the same object. As another example, if the product associated with the first entity is a Fuji apple and the product associated with the second entity is a banana, it is determined that these two products do not belong to the same category, i.e., the first entity and the second entity can be considered to be for different objects.

For example, if a product associated with a first entity and a product associated with a second entity are exactly the same, the first entity and the second entity are considered to be for the same object. As one example, if the product associated with the first entity is a Fuji apple and the product associated with the second entity is a Fuji apple, it can be determined that these two products are exactly the same, i.e., the first entity and the second entity can be considered to be for the same object.

Also, for example, the general-purpose service entity can determine the second entity associated with the first entity by determining whether the first entity and the second entity belong to the same group, or by determining whether the related attributes of the first entity include the second entity, or by determining whether the related attributes of the second entity include the first entity. If it is determined that the condition is met, it is indicated that the first entity and the second entity are associated.

For example, different products are divided into different groups according to a predetermined rule, and the service entity can determine whether a first entity associated with (or bound to) a corresponding product and a second entity associated with (or bound to) a corresponding product belong to the same predetermined group, thereby determining a second entity associated with the first entity. As one example, if apples on a shelf and bananas in stock can be divided into the same group according to a predetermined rule, and a shelf electronic tag associated with an apple on a shelf is taken as a first entity, the service entity can determine an entity that belongs to the same group as the shelf electronic tag associated with an apple on a shelf, and determine a second entity (i.e., an inventory electronic tag) associated with this first entity.

In some embodiments, the generic service entity may determine the second entity associated with the first entity according to association rules included in the subscription request.

For example, the association rule may be included in a subscription request received by the general-purpose service entity and sent by the shopping terminal. For example, the association rule may indicate that an entity bound to a product in the same category as a product associated with the first entity is the second entity. The general-purpose service entity may then determine the second entity associated with the first entity according to the association rule.

In some embodiments, the strength of the association between the first entity and the second entity is calculated, and if the strength of the association is greater than a pre-defined threshold, it is determined that the first entity and the second entity are associated.

For example, the strength of the association between a first entity and a second entity is obtained by determining the difference in the categories of the products corresponding to the first entity and the second entity, and if the difference in the product categories is small, the strength of the association is indicated as high, whereas if the difference in categories is large, the strength of the association is indicated as low.

The second entity may be one or more entities.

After determining the second entity related to the first entity, a subscription to the second entity is generated in step S103. Here, generating the subscription to the second entity includes one of two methods: (1) creating a subscription resource for the second entity; and (2) creating subscription resources for the first entity and the second entity.

FIG. 3 is a flowchart of a method 200 for creating a subscription to a second entity according to an embodiment of the present disclosure, and FIG. 4 is a flowchart of another method 200 for creating a subscription to a second entity according to an embodiment of the present disclosure. Creating a subscription to the second entity is described below with reference to FIGS. 3-4.

As shown in FIG. 3, a flowchart of a method 200 for generating a subscription to a second entity according to an embodiment of the present disclosure. As shown in FIG. 3, a subscription to the second entity can be generated by a method including a step of determining a subscription mode for the second entity according to a state of the second entity (S201), and a step of generating a subscription to the second entity according to the determined subscription mode (S202).

For example, if the second entity is a virtual electronic tag in the retail field, the state of the second entity can be divided into two states: in stock and out of stock. Note that the state of the second entity is not limited to this, and the second entity may be classified into any appropriate state depending on the situation, but is not limited here.

For example, the subscription modes include long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high-priority subscription, low-priority subscription, high-frequency message subscription, low-frequency message subscription, etc. Different subscription modes differ in one or more of message priority, subscription resource expiration date, notification content, number of notification messages, etc. Different subscription modes can be selected according to different cases (e.g., state of the second entity), thereby improving the user experience. Then, each of the different subscription modes will be described in detail.

For example, depending on the length of the notification expiration period for which subscription resources are reserved, subscription modes can be divided into long-term subscriptions and short-term subscriptions, with the notification expiration period of long-term subscriptions being longer than that of short-term subscriptions. For example, in the case of long-term subscription mode, a long notification expiration period (e.g., one month) can be set, and if the event notification rules are met within that expiration period, a notification can be sent to the notified party. On the other hand, for example, in the case of short-term subscription mode, a short notification expiration period (e.g., real-time transmission) can be set, and if the event notification rules are met within that expiration period, a notification can be sent to the notified party.

For example, depending on the content of the notification for the subscribed resource, the subscription mode can be divided into additional information subscription and specified information subscription. For example, in the specified information subscription mode, when an event notification rule is satisfied for a certain product, detailed specified information such as the price, material, discount, etc. associated with this product in response to the specified information request can be sent to the notified party, and this specified information request can be included in the subscription request. For example, in the additional information subscription mode, when an event notification rule is satisfied for a certain product, detailed specified information such as the price, material, discount, etc. associated with this product in response to the specified information request can be sent to the notified party, and detailed additional information such as the price, material, discount, etc. associated with products similar to this product can also be sent to the notified party, and this detailed additional information is not included in the subscription request.

For example, depending on the priority of the notification for the subscribed resource, the subscription mode can be divided into high priority subscription and low priority subscription. For example, in the case of high priority subscription mode, the notification can be sent earlier in time or multiple times to ensure that the notified party can receive the notification, compared to the low priority subscription mode.

For example, depending on the number of notification information for the subscription resource, the subscription mode can be divided into high-frequency message subscription and low-frequency message subscription. For example, in the case of high-frequency information subscription mode, a short minimum notification time interval (e.g., 2 hours) can be set, and when the event notification rule is met, a notification is sent to the notified party, and the time between two consecutive notifications is not shorter than the minimum notification time interval. For example, in the case of low-frequency information subscription mode, a long minimum notification time interval (e.g., 24 hours) can be set, and when the event notification rule is met, a notification is sent to the notified party, and the time between two consecutive notifications is not shorter than the minimum notification time interval.

Still referring to FIG. 3, for example, in step S301, a subscription mode for the second entity can be determined according to the state of the second entity. The state of the second entity is determined by attributes of the second entity, and the attributes of the second entity include object attributes (e.g., the object of the second entity is a product, and the object attributes are product information, including the number and size of products), and environmental attributes (e.g., people, things, objects, sounds, lights, etc. around the second entity). By determining the object attributes, changes in the object can be adjusted in real time according to changes in the object attributes, which can realize diversification of subscription modes, contribute to rapid adjustment according to environmental changes, and improve efficiency. By determining changes in environmental attributes, the environment of the object can be adjusted in real time, which can realize diversification of subscription modes, contribute to rapid adjustment according to environmental changes, and improve efficiency.

In one example, if the first entity is a shelf electronic tag and the second entity associated with the first entity is an inventory electronic tag, and both the first entity and the second entity are for the same product A, and the first entity includes the number of shelves for product A and the second entity includes the inventory number for product A, and the second entity indicates that the inventory number for product A is zero, a long-term subscription can be selected (e.g., the notification expiration time can be set to one month and if an event notification rule is met within the expiration time, a notification can be sent to the notified party), whereas if the second entity indicates that the inventory number for product A is not zero, a short-term subscription can be selected (e.g., the notification expiration time can be set to one week and if an event notification rule is met, a notification message is sent to the notified party).

In another example, for a certain product, if it is in stock, a subscription to the specified information can be selected (e.g., when an event notification rule is satisfied, detailed specified information such as the price, material, discounts, etc. associated with this product in response to a specified information request can be sent to the notified party), whereas if it is out of stock, a subscription to additional information can be selected (e.g., in addition to sending detailed specified information such as the price, material, discounts, etc. associated with this product in response to a specified information request to the notified party, detailed additional information such as the price, material, discounts, etc. associated with products similar to this product can be sent to the notified party).

In one example, multiple subscription modes can be used simultaneously, and if the first entity is a shelf electronic tag, and the second entity related to the first entity is an inventory electronic tag, and both the first entity and the second entity are for the same product A, and the first entity includes the number of shelves for product A, and the second entity includes the inventory quantity for product A, and the second entity indicates that the inventory quantity for product A is zero, long-term subscription and low-frequency subscription can be selected (e.g., the notification expiration date can be set to one month, and if the event notification rule is met within the expiration date, processing such as caching and integrating the event is performed and a notification is sent to the processed event notified party), while simultaneously satisfying the requirements for long-term subscription and low-frequency subscription, short-term subscription and high-frequency subscription can be selected (e.g., the notification expiration date can be set to one week, and if the event notification rule is met, the event is not processed and a notification message is sent directly to the notified party).

Similarly, one or more of high priority subscription (when the event notification rule is satisfied, the notification is sent with priority), low priority subscription (when the event notification rule is satisfied and there is no high priority event to be sent, the notification is sent directly), high frequency message subscription (when the event is not processed and the time notification rule is satisfied, the notification is sent directly), and low frequency message subscription (when the event is processed and then the notification is sent, the processing includes event caching, event integration, etc.) can be selected. The above subscription modes are merely examples, and it should be understood that in different cases, one or more of long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc. may be selected, or other appropriate subscription modes may be selected, but will not be described again here.

After the subscription mode is determined, in step S302, a subscription to the second entity is generated according to the determined subscription mode.

Figure 4 shows a flowchart of another method 300 for generating a subscription to a second entity according to an embodiment of the present disclosure. As shown in Figure 4, a subscription to the second entity may be generated by a method including the steps of determining (S301) a subscription mode for the first entity and the second entity depending on the state of the second entity, and generating (S302) a subscription to the first entity and the second entity depending on the determined subscription mode. The selection of the subscription mode described in Figure 4 is similar to the selection of the subscription mode described in Figure 3 above, and will not be repeated here.

Returning to FIG. 1, after the subscription to the second entity is created, in step S104, a subscription response is sent to indicate the outcome of the subscription. For example, the subscription response may be sent to the third entity, or may be sent to another entity, the subscription response being for indicating the outcome of the created subscription.

For example, when creating a subscription resource for the second entity, the subscription response is for indicating the result of creating the subscription resource for the second entity. In some embodiments, when creating a subscription resource for the first entity and the second entity, the subscription response is for indicating the result of creating the subscription resource for the first entity and the second entity.

After creating a subscription, if the event notification rule is met, an event notification is sent to the recipient according to the determined subscription mode. The event notification rule is included in the subscription request.

Here, the subscription request may include multiple notifyes for receiving event notifications related to the subscription request. When the event notification rule of the subscriber is satisfied, the generic service entity sends the event notification to all notifyes included in the subscription request. For example, when a manhole cover is moved, the manhole cover movement sensor detects the change and sends update data to the generic service entity, and the generic service entity can determine whether the event notification rule is satisfied based on the update data of the manhole cover movement sensor. For example, when the subscription condition is manhole cover movement, the generic service entity determines that the event notification rule is satisfied and sends an event notification to all notifyes included in the subscription request requesting subscription to the event notification of manhole cover movement, i.e., all notifyes are notified of the event that the manhole cover has been moved.

Hereinafter, with reference to FIG. 5, another method 400 for subscribing to a resource according to an embodiment of the present disclosure will be described. The method may be performed by an application entity (e.g., the third entity AE3 described above).

As shown in FIG. 5, in step S401, a subscription request is sent to a first entity. In step S402, a subscription response to the subscription request is received, the second entity and the first entity are associated, and the subscription response is for indicating at least the result of generating a subscription to the second entity.

For example, the first entity (AE1) may be a virtual electronic tag for indicating corresponding product information managed by a service entity. The virtual electronic tag is associated with (or bound to) the corresponding product via a product identifier (ID). For example, the first entity may be a virtual shelf electronic tag, and the third entity (AE3) may be a shelf management application or a virtual shopping terminal. For example, in this step, AE3 (e.g., a shelf management application or a shopping terminal) sends a subscription request for the shelf electronic tag AE1 to a general-purpose service entity. Then, AE3 receives a subscription response to the subscription request, where the second entity and the first entity are associated, and the subscription response is for indicating at least the result of generating a subscription for the second entity.

Here, the subscription request may include an association rule that creates an association relationship between the first application entity and the second application entity. The generic service entity may then determine a second entity associated with the first entity according to the association rule included in the subscription request. For example, the association rule may indicate that the second entity is an entity bound to a product in the same category as a product associated with the first entity.

Here, the subscription response is generated based on a subscription mode for the subscription request that is determined according to the state of the second application entity.

For example, the subscription response is formed by determining a subscription mode for the second entity in response to a state of the second entity, and generating a subscription for the second entity in response to the determined subscription mode, the subscription response being for indicating at least a result of generating the subscription for the second entity.

In some embodiments, the subscription response may be formed by determining a subscription mode for the first entity and the second entity in response to the state of the second entity, and generating a subscription for the first entity and the second entity in response to the determined subscription mode, the subscription response being for indicating a result of generating the subscription for the first entity and the second entity. The method of generating the subscription response is similar to the method described in FIG. 2 and will not be repeated here.

When this event notification rule is met, you receive an event notification based on the determined subscription mode.

Hereinafter, examples for subscribing to resources according to embodiments of the present disclosure will be described in detail with reference to Figures 6 to 8. Figure 6 is a schematic diagram of a method for subscribing to resources according to a first embodiment of the present disclosure, Figure 7 is a schematic diagram of a method for subscribing to resources according to a second embodiment of the present disclosure, and Figure 8 is a schematic diagram of a method for subscribing to resources according to a third embodiment of the present disclosure.

The Internet of Things may be composed of a generic service entity and a set of application entities, where the generic service entity may be a retail server, etc., and the application entities may be various sensor devices, user terminals such as mobile phones, or software modules in devices, such as mobile phone application programs. The generic service entity manages the connected application entities and performs operations such as registration, data transfer, and task execution.

6 illustrates a first example of subscribing to resources according to the present disclosure. In this example, for example, a shelf management application entity of a market or supermarket initiates a subscription to adjust the cargo status of the market or supermarket in real time.

As shown in FIG. 6, for example, the retail server CSE 53 (service entity) receives registration requests from the shelf electronic tag AE1 51 (first entity), the inventory electronic tag AE2 52 (second entity), and the shelf management application AE3 54 (third entity) which is a subscriber, creates association relationships between the shelf electronic tag AE1 51, the inventory electronic tag AE2 52, and the shelf management application AE3 54, and updates their status according to changes in the status of the shelf electronic tag AE1 51, the inventory electronic tag AE2 52, and the shelf management application AE3 54 (55). Then, the retail server CSE 53 determines whether the product associated with the shelf electronic tag AE1 51 and the product associated with the inventory electronic tag AE2 52 are for products of the same category (56), and if the answer is "yes," creates an association between the shelf electronic tag AE1 51 and the inventory electronic tag AE2 52 (57).

When the shelf management application AE3 54 sends a subscription request 59 for the shelf electronic tag AE1 51 to the retail server CSE 53, the retail server CSE 53 first determines whether the shelf electronic tag AE1 51 has an inventory electronic tag AE2 52 of a related object (number 60 in FIG. 6). If the shelf electronic tag AE1 51 has an inventory electronic tag AE2 52 of a related object, the retail server CSE 53 may create a subscription resource for the inventory electronic tag AE2 52 and send a subscription response 62 to the retail server CSE 53 (or other entity) indicating the result of creating the subscription for the inventory electronic tag AE2 52. In some embodiments, the retail server CSE 53 may create subscription resources for the shelf tag AE1 51 and the inventory tag AE2 52 and send a subscription response 62 to the retail server CSE 53 (or another entity) indicating the results of creating the subscriptions for the shelf tag AE1 51 and the inventory tag AE2 52.

Furthermore, when creating a subscription resource for the inventory electronic tag AE2 52, the retail server CSE 53 can determine the subscription mode for the stock quantity electronic tag AE2 52 according to the status of the inventory electronic tag AE2 52 (61). For example, as described above, if the inventory electronic tag AE2 indicates that the item is in stock, a short-term subscription can be created, whereas if the inventory electronic tag AE2 indicates that the item is out of stock, a long-term subscription can be created.

In some embodiments, when the retail server CSE 53 creates subscription resources for the shelf tag AE1 51 and the inventory tag AE2 52, the retail server CSE 53 can determine the subscription mode for the shelf tag AE1 51 and the inventory tag AE2 52 depending on the status of the inventory tag AE2 52 (61). For example, as described above, if the inventory tag AE2 indicates that it is in stock, a short-term subscription can be created, and if the inventory tag AE2 indicates that it is out of stock, a long-term subscription can be created.

Then, the retail server CSE 53 updates the status of the shelf electronic tag AE1 51 (63). After that, if the event notification rule is satisfied (64), the retail server CSE 53 transmits an event notification 65 to the notified party (e.g., shelf management application AE3 54) according to the subscription mode determined above.

7 illustrates a second example of subscribing to a resource according to the present disclosure. In this example, for example, a shopping terminal (e.g., a user) initiates a subscription to obtain real-time information on the status of a product that the user wishes to purchase.

As shown in FIG. 7, for example, the retail server CSE 53 (service entity) receives registration requests from the shelf electronic tag AE1 51 (first entity), the inventory electronic tag AE2 52 (second entity), and the shopping terminal AE3 66 (third entity) which is a subscriber, and creates association relationships between the shelf electronic tag AE1 51, the inventory electronic tag AE2 52, and the shopping terminal AE3 66, and updates their status according to changes in the status of the shelf electronic tag AE1 51, the inventory electronic tag AE2 52, and the shopping terminal AE3 66. Then, as in FIG. 6, the retail server CSE 53 determines whether the product associated with the shelf electronic tag AE1 51 and the product associated with the inventory electronic tag AE2 52 are for products of the same category, and if the answer is "yes," creates an association between the shelf electronic tag AE1 51 and the inventory electronic tag AE2 52.

When the shopping terminal AE3 66 sends a subscription request for the shelf electronic tag AE1 51 to the retail server CSE 53, the retail server CSE 53 first determines whether the shelf electronic tag AE1 51 has an inventory electronic tag AE2 52 of a related object. If the shelf electronic tag AE1 51 has an inventory electronic tag AE2 52 of a related object, the retail server CSE 53 may create a subscription resource for the inventory electronic tag AE2 52 and send a subscription response to the shopping terminal AE3 66 (or other entity), which indicates the result of creating the subscription for the inventory electronic tag AE2 52. In some embodiments, the retail server CSE 53 may create subscription resources for the shelf tag AE1 51 and the inventory tag AE2 52 and send a subscription response to the shopping terminal AE3 66 (or other entity) indicating the results of creating the subscriptions for the shelf tag AE1 51 and the inventory tag AE2 52.

Furthermore, when the retail server CSE 53 creates a subscription resource for the inventory electronic tag AE2 52, it can determine the subscription mode for the inventory electronic tag AE2 52 depending on the status of the inventory electronic tag AE2 52. For example, if the inventory electronic tag AE2 indicates that the item is in stock, it can create a short-term subscription, and if the inventory electronic tag AE2 indicates that the item is out of stock, it can create a long-term subscription.

In some embodiments, when the retail server CSE 53 creates subscription resources for the shelf tag AE1 51 and the inventory tag AE2 52, it can determine the subscription mode for the shelf tag AE1 51 and the inventory tag AE2 52 depending on the status of the inventory tag AE2 52. For example, as described above, if the inventory tag AE2 indicates in stock, a short-term subscription can be created, and if the inventory tag AE2 indicates out of stock, a long-term subscription can be created.

Then, the retail server CSE 53 updates the status of the shelf electronic tag AE1 51 (63). After that, when the event notification rule is satisfied, the retail server CSE 53 transmits an event notification to the notified party (e.g., the shopping terminal AE3 66) according to the subscription mode determined above.

8 illustrates a third example of subscribing to resources according to the present disclosure. In this example, for example, the subscription request sent by the application entity includes an association rule, and the generic service entity creates associations between different objects according to the association rule.

As shown in FIG. 8, for example, the retail server CSE 53 (service entity) receives registration requests from the shelf electronic tag AE1 51 (first entity), the inventory electronic tag AE2 52 (second entity), and the subscriber shopping terminal AE3 66 (third entity), and thereby creates association relationships with the shelf electronic tag AE1 51, the inventory electronic tag AE2 52, and the shopping terminal AE3 66, and updates their status according to changes in the status of the shelf electronic tag AE1 51, the inventory electronic tag AE2 52, and the shopping terminal AE3 66.

When the shopping terminal AE3 66 sends a subscription request 71 for the shelf electronic tag AE1 51 to the retail server CSE 53, the retail server CSE 53 creates an association between the shelf electronic tag AE1 51 and the inventory electronic tag AE2 52 according to the association rule included in the subscription request. The retail server CSE 53 may then create a subscription resource for the inventory electronic tag AE2 52 and send a subscription response to the shopping terminal AE3 66 (or other entity) indicating the result of creating the subscription for the inventory electronic tag AE2 52. In some embodiments, the retail server CSE 53 may create subscription resources for the shelf electronic tag AE1 51 and the inventory electronic tag AE2 52 and send a subscription response to the shopping terminal AE3 66 (or other entity) indicating the result of creating the subscription for the shelf electronic tag AE1 51 and the inventory electronic tag AE2 52.

Furthermore, when the retail server CSE 53 creates a subscription resource for the inventory electronic tag AE2 52, it can determine the subscription mode for the stock quantity electronic tag AE2 52 depending on the status of the inventory electronic tag AE2 52. For example, as described above, if the inventory electronic tag AE2 indicates that the item is in stock, a short-term subscription can be created, and if the inventory electronic tag AE2 indicates that the item is out of stock, a long-term subscription can be created.

In some embodiments, when the retail server CSE 53 creates subscription resources for the shelf tag AE1 51 and the inventory tag AE2 52, it can determine the subscription mode for the shelf tag AE1 51 and the inventory tag AE2 52 depending on the status of the inventory tag AE2 52. For example, as described above, if the inventory tag AE2 indicates in stock, a short-term subscription can be created, and if the inventory tag AE2 indicates out of stock, a long-term subscription can be created.

Then, the retail server CSE 53 updates the status of the shelf electronic tag AE1 51. Then, when the event notification rule is satisfied, it sends an event notification to the notified party (e.g., the shopping terminal AE3 66) according to the subscription mode determined above.

As can be seen from the above, the above method for subscribing to resources can realize subscription to a second entity related to a first entity, thereby making the resources to be subscribed to more abundant. Also, different subscription modes can be created according to the state of the second entity, thereby realizing mode diversification in different cases.

Hereinafter, an apparatus 1000 for subscribing to resources according to an embodiment of the present disclosure will be described with reference to FIG. 9. FIG. 9 is a schematic diagram of an apparatus 1000 for subscribing to resources according to an embodiment of the present disclosure. The functionality of the apparatus for subscribing to resources in this embodiment is the same as the details of the method described above with reference to FIG. 1, and therefore, for simplicity, a detailed description of the same content will be omitted here.

As shown in FIG. 9, the device 1000 for subscribing to resources according to an embodiment of the present disclosure includes a receiving unit 1001, a determining unit 1002, a generating unit 1003, and a sending unit 1004. It should be noted that although the device 1000 for subscribing to resources in FIG. 9 is shown to include only four units, this is merely schematic, and the device 1000 for subscribing to resources may include one or more other units, which are omitted here because they are not related to the concept of the invention.

The receiving unit 1001 causes the service entity to receive a subscription request for the first entity from the third entity.

For example, the first entity (AE1) may be a shelf electronic tag, and the third entity (AE3) may be a shelf management application or a shopping terminal. For example, in this step, the general-purpose service entity receives a subscription request for the shelf electronic tag AE1 by AE3 (the shelf management application or the shopping terminal).

Then, the determination unit 1002 determines a second entity related to the first entity.

For example, the second entity (AE2) may be an inventory electronic tag. For example, in this step, the determination unit 1002 may determine an inventory electronic tag associated with the shelf electronic tag.

For example, the determination unit 1002 may determine a second entity associated with a first entity by determining whether the first entity and the second entity are for the same object. For example, if the first entity and the second entity are for the same object, it may determine that the second entity is associated with the first entity, and if the first entity and the second entity are for different objects, it may determine that the second entity is not associated with the first entity.

In some embodiments, the determination unit 1002 may determine a second entity associated with the first entity according to an association rule included in the subscription request.

For example, the association rule may be included in a subscription request sent by a shopping terminal received by the receiving unit 1001. For example, the association rule may indicate that an entity bound to a product in the same category as a product associated with the first entity is the second entity. The general-purpose service entity may then determine the second entity associated with the first entity according to the association rule.

After the determining unit 1002 determines a second entity related to the first entity, the generating unit 1003 then generates a subscription for at least the second entity. Here, generating a subscription for the second entity includes one of two methods: (1) creating a subscription resource for the second entity; and (2) creating subscription resources for the first entity and the second entity.

FIG. 3 is a flowchart of a method 200 for generating a subscription to a second entity according to an embodiment of the present disclosure, and FIG. 4 is a flowchart of another method 200 for generating a subscription to a second entity according to an embodiment of the present disclosure. Hereinafter, the generating unit 1003 will be described with reference to FIGS. 3-4 for generating a subscription to the second entity.

3, a flowchart of a method 200 for generating a subscription to a second entity according to an embodiment of the present disclosure. As shown in FIG. 3, the subscription to the second entity may be generated by a method including the steps of determining a subscription mode for the second entity (S301) in response to a state of the second entity, and generating a subscription to the second entity in response to the determined subscription mode (S302).

For example, if the second entity is a virtual electronic tag in the retail field, the state of the second entity can be divided into two states: in stock and out of stock. Note that the state of the second entity is not limited to this, and the second entity may be classified into any appropriate state according to the situation, but is not limited here. For example, the subscription modes include long-term subscription, short-term subscription, additional information subscription, specific information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc. Different subscription modes have different message priorities, subscription resource expiration dates, notification contents, number of notification messages, etc. Different subscription modes can be selected according to different cases (e.g., the state of the second entity), thereby improving the user experience. Then, each of the different subscription modes will be described in detail.

For example, depending on the length of the notification expiration period for which subscription resources are reserved, subscription modes can be divided into long-term subscriptions and short-term subscriptions, with the notification expiration period of long-term subscriptions being longer than that of short-term subscriptions. For example, in the case of long-term subscription mode, a long notification expiration period (e.g., one month) can be set, and if the event notification rules are met within that expiration period, a notification can be sent to the notified party. However, for example, in the case of short-term subscription mode, a short notification expiration period (e.g., real-time transmission) can be set, and if the event notification rules are met within that expiration period, a notification can be sent to the notified party.

For example, depending on the content of the notification for the subscribed resource, the subscription mode can be divided into additional information subscription and specified information subscription. For example, in the specified information subscription mode, when an event notification rule is satisfied for a certain product, detailed specified information such as the price, material, discount, etc. associated with this product in response to the specified information request is sent to the notified party, and this specified information request may be included in the subscription request. For example, in the additional information subscription mode, when an event notification rule is satisfied for a certain product, detailed specified information such as the price, material, discount, etc. associated with this product in response to the specified information request is sent to the notified party, and detailed additional information such as the price, material, discount, etc. associated with products similar to this product may also be sent to the notified party, and this detailed additional information is not included in the subscription request.

For example, depending on the priority of the notification for the subscribed resource, the subscription mode can be divided into high priority subscription and low priority subscription. For example, in the case of high priority subscription mode, the notification can be sent earlier in time or multiple times to ensure that the notified party can receive the notification, compared to the low priority subscription mode.

For example, depending on the number of notification information for the subscription resource, the subscription mode can be divided into high-frequency message subscription and low-frequency message subscription. For example, in the case of high-frequency information subscription mode, a short minimum notification time interval (e.g., 2 hours) can be set, and when the event notification rule is met, a notification is sent to the notified party, and the time between two consecutive notifications is not shorter than the minimum notification time interval. For example, in the case of low-frequency information subscription mode, a long minimum notification time interval (e.g., 24 hours) can be set, and when the event notification rule is met, a notification is sent to the notified party, and the time between two consecutive notifications is not shorter than the minimum notification time interval.

Continuing to refer to FIG. 3, for example, in step S301, a subscription mode for the second entity can be determined depending on the state of the second entity (e.g., in stock or out of stock).

In one example, for a product, if it is out of stock, a long-term subscription can be selected (e.g., the notification expiration time can be set to one month, and if the event notification rule is met within that expiration time, a notification can be sent to the notified party), whereas if it is in stock, a short-term subscription can be selected (e.g., if the event notification rule is met, a notification message is sent in real time).

In another example, for a certain product, if it is in stock, a subscription to the specified information can be selected (e.g., when an event notification rule is satisfied, detailed specified information such as the price, material, discounts, etc. associated with this product in response to a specified information request can be sent to the notified party), whereas if it is out of stock, a subscription to additional information can be selected (e.g., in addition to sending detailed specified information such as the price, material, discounts, etc. associated with this product in response to a specified information request to the notified party, detailed additional information such as the price, material, discounts, etc. associated with products similar to this product can be sent to the notified party).

Similarly, one or more of high priority subscription, low priority subscription, high frequency message subscription, and low frequency message subscription may be selected. It should be understood that the above subscription modes are merely examples, and that in different cases, one or more of long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc. may be selected, or other suitable subscription modes may be selected, but this will not be repeated here.

After the subscription mode is determined, then in step S302, the generating unit 1003 generates a subscription to the second entity in response to the determined subscription mode.

Figure 4 shows a flowchart of another method 300 for generating a subscription to a second entity according to an embodiment of the present disclosure. As shown in Figure 4, a subscription to the second entity may be generated by a method including the steps of determining (S301) a subscription mode for the first entity and the second entity depending on the state of the second entity, and generating (S302) a subscription to the first entity and the second entity depending on the determined subscription mode. The selection of the subscription mode described in Figure 4 is similar to the selection of the subscription mode described in Figure 3 above, and will not be repeated here.

After the generating unit 1003 generates the subscription to the second entity, the sending unit 1004 sends a subscription response to indicate the result of the subscription. For example, the subscription response may be sent to the third entity or may be sent to another entity, the subscription response being for indicating the result of the generated subscription.

For example, when creating a subscription resource for the second entity, the subscription response is for indicating the result of creating the subscription resource for the second entity. In some embodiments, when creating a subscription resource for the first entity and the second entity, the subscription response is for indicating the result of creating the subscription resource for the first entity and the second entity.

After creating a subscription, if this event notification rule is met, the event notification included in the subscription request will be sent to the notified party according to the determined subscription mode.

Here, the subscription request may include multiple notifyes for receiving event notifications related to the subscription request. When the event notification rule of the subscriber is satisfied, the generic service entity sends the event notification to all notifyes included in the subscription request. For example, when a manhole cover is moved, the manhole cover movement sensor detects the change and sends update data to the generic service entity, and the generic service entity can determine whether the event notification rule is satisfied based on the update data of the manhole cover movement sensor. For example, when the subscription condition is manhole cover movement, the generic service entity determines that the event notification rule is satisfied and sends an event notification to all notifyes included in the subscription request requesting the subscribed manhole cover movement event notification, i.e., all notifyes are notified of the event that the manhole cover has been moved.

Hereinafter, a device 1100 for subscribing to resources according to an embodiment of the present disclosure will be described with reference to FIG. 10. FIG. 10 is a schematic diagram of a device 1100 for subscribing to resources according to an embodiment of the present disclosure. The functionality of the device for subscribing to resources in this embodiment is the same as the details of the method described above with reference to FIG. 1, and therefore, for simplicity, a detailed description of the same content will be omitted here.

As shown in FIG. 10, the device 1100 for subscribing to resources includes a memory 1101 and a processor 1102. Note that although the device 1100 for subscribing to resources in FIG. 10 is shown as including only two devices, this is merely schematic and the device 1100 for subscribing to resources may include one or more other devices, which are omitted here as they are not relevant to the concept of the invention.

A device for subscribing to resources of the present disclosure includes a memory 1101 configured to store computer-readable instructions, a processor 1102 configured to execute the computer-readable instructions stored in the memory, and, when the processor executes the computer-readable instructions, performs the following steps: a service entity receives a subscription request for a first entity from a third entity; determines a second entity related to the first entity; generates a subscription for at least the second entity; and transmits a subscription response indicating a result of the subscription.

Figure 11 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure.

As shown in FIG. 11, the present disclosure further includes a computer-readable storage medium having computer-readable instructions stored thereon, which, when executed by a computer, causes the computer to perform a method for subscribing to a resource, the method including the steps of: a service entity receiving a subscription request for a first entity from a third entity; determining a second entity related to the first entity; generating a subscription for at least the second entity; and transmitting a subscription response to indicate a result of the generated subscription.

Those skilled in the art will appreciate that the various aspects of the present application can be described and described through a number of patentable categories or contexts, including new and useful processes, machines, articles of manufacture, or combinations of matter, or new and useful improvements thereto. Accordingly, the various aspects of the present application may be implemented entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. Any of the above hardware or software may be referred to as a "data block," "module," "engine," "unit," "assembly," or "system." Additionally, the various aspects of the present application may be embodied as a computer product provided on one or more computer-readable mediums, the product including computer-readable program code.

This application has used certain words to describe the embodiments of this application. For example, "one embodiment," "an embodiment," and/or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this application. It should be emphasized and noted that "one embodiment" or "one embodiment" or "an alternative embodiment" referenced two or more times in different locations in this specification do not necessarily refer to the same embodiment. Also, some features, structures, or characteristics in one or more embodiments of this application may be combined as appropriate.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It is also to be understood that terms as defined in ordinary dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art, and should not be interpreted in an idealized or overly formalized sense unless expressly stated herein.

The above is a description of the present disclosure and should not be considered as limiting thereof. Although several exemplary embodiments of the present disclosure have been described, those skilled in the art will readily appreciate that many modifications can be made to the exemplary embodiments without departing from the novel teachings and advantages of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the present disclosure as defined by the claims. It should be understood that the above is a description of the present disclosure and should not be considered as being limited to the specific embodiments disclosed, and that modifications to the disclosed embodiments and other embodiments are intended to be included within the scope of the appended claims. The present disclosure is defined by the claims and their equivalents.

51 Shelf electronic tag AE1
52 Inventory electronic tag AE2
53 Retail Server CSE
54 Shelf management application AE3
1000 Apparatus for subscribing to resources 1001 Receiving unit 1002 Determining unit 1003 Generating unit 1004 Sending unit 1100 Device for subscribing to resources

Claims (9)

A method for subscribing to a resource in the Internet of Things field, comprising:
receiving, by the service entity, a subscription request for a first object from a first entity;
a service entity determining a second object related to the first object;
creating a subscription by a service entity to at least the second object;
and a service entity sending a subscription response to indicate a result of the subscription;
The step of determining a second object related to the first object comprises:
determining whether the first object and the second object are for the same object; or
determining whether the first object and the second object belong to the same group; or
determining whether a related attribute of the first object includes a related attribute of a second object; or
determining whether a related attribute of the second object includes the first object; or
determining a second object related to the first object according to an association rule included in the subscription request ;
The step of generating a subscription to at least the second object further comprises:
creating a subscription resource for the second object;
determining a subscription mode for the second object in response to a state of the second object;
generating a subscription to the second object in response to the determined subscription mode;
The subscription mode includes one or more of: long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, frequent message subscription, and infrequent message subscription;
A method for subscribing to resources in the Internet of Things field. The subscription response indicating a result of the subscription,
The method of claim 1 , wherein the subscription response indicates a result of creating a subscription resource for the second object. The step of determining a second object related to the first object comprises:
determining that the second object and the first object are associated if the first object and the second object are for the same object. The method of claim 1, wherein the association rule directs that the second object is an entity bound to a product in the same category as a product associated with the first object. 1. A method for subscribing to a resource in the Internet of Things performed by a first entity, comprising:
sending a subscription request for a first object;
receiving a subscription response to the subscription request;
the first object is associated with a second object, and the subscription response is for indicating a result of creating a subscription to at least the second object;
The association between the first object and the second object is
whether the first object and the second object are for the same object, or
whether the first object and the second object belong to the same group, or
whether the related attribute of the first object includes a second object; or
whether the related attribute of the second object includes the first object; or
an association rule included in the subscription request;
It is decided by
A subscription resource for the second object is created, a subscription mode for the second object is determined according to a state of the second object, and is used to create a subscription for the second object;
The subscription mode includes one or more of: long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, frequent message subscription, and infrequent message subscription;
A method for subscribing to resources in the Internet of Things. The method of claim 5 , wherein the association rule dictates that the second object is an entity bound to a product in the same category as a product associated with the first object. An apparatus for subscribing to a resource in an internet of things, comprising:
a receiving unit for the service entity to receive a subscription request for the first object from the first entity;
a determination unit for determining a second object related to the first object;
a generating unit for generating a subscription to at least the second object;
a sending unit for sending a subscription response to indicate a result of the subscription;
Determining a second object related to the first object includes:
determining whether the first object and the second object are for the same object; or
determining whether the first object and the second object belong to the same group; or
determining whether a related attribute of the first object includes a second object; or
determining whether a related attribute of the second object includes the first object; or
determining a second object related to the first object according to an association rule included in the subscription request;
Creating a subscription to at least the second object includes:
creating a subscription resource for the second object;
determining a subscription mode for the second object in response to a state of the second object;
generating a subscription to the second object in response to the determined subscription mode;
The subscription mode includes one or more of: long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, frequent message subscription, and infrequent message subscription;
A device for subscribing to resources in the Internet of Things. A device for subscribing to resources in the Internet of Things, comprising:
a memory configured to store computer readable instructions;
a processor configured to execute the computer-readable instructions stored in the memory;
When the processor executes the computer-readable instructions,
receiving, by the service entity, a subscription request for a first object from a first entity;
determining a second object related to the first object;
creating a subscription to at least the second object;
sending a subscription response indicating a result of the subscription;
The step of determining a second object related to the first object comprises:
determining whether the first object and the second object are for the same object; or
determining whether the first object and the second object belong to the same group; or
determining whether a related attribute of the first object includes a related attribute of a second object; or
determining whether a related attribute of the second object includes the first object; or
determining a second object related to the first object according to an association rule included in the subscription request ;
The step of generating a subscription to at least the second object further comprises:
creating a subscription resource for the second object;
determining a subscription mode for the second object in response to a state of the second object;
generating a subscription to the second object in response to the determined subscription mode;
The subscription mode includes one or more of: long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, frequent message subscription, and infrequent message subscription;
A device for subscribing to resources in the Internet of Things. A computer-readable storage medium having computer-readable instructions stored thereon, the computer performing a method for subscribing to resources in the Internet of Things, when the computer-readable instructions are executed by a computer, the method comprising:
receiving, by the service entity, a subscription request for a first object from a first entity;
determining a second object related to the first object;
creating a subscription to at least the second object;
sending a subscription response indicating a result of the subscription;
The step of determining a second object related to the first object comprises:
determining whether the first object and the second object are for the same object; or
determining whether the first object and the second object belong to the same group; or
determining whether a related attribute of the first object includes a related attribute of a second object; or
determining whether a related attribute of the second object includes the first object; or
determining a second object related to the first object according to an association rule included in the subscription request ;
The step of generating a subscription to at least the second object further comprises:
creating a subscription resource for the second object;
determining a subscription mode for the second object in response to a state of the second object;
generating a subscription to the second object in response to the determined subscription mode;
The subscription mode includes one or more of: long-term subscription, short-term subscription, additional information subscription, predetermined information subscription, high priority subscription, low priority subscription, frequent message subscription, and infrequent message subscription;
A computer-readable storage medium.

Images