WO2020233658A1 - 物联网领域的订阅资源的方法、装置、设备和存储介质 - Google Patents

物联网领域的订阅资源的方法、装置、设备和存储介质 Download PDF

Info

Publication number
WO2020233658A1
WO2020233658A1 PCT/CN2020/091525 CN2020091525W WO2020233658A1 WO 2020233658 A1 WO2020233658 A1 WO 2020233658A1 CN 2020091525 W CN2020091525 W CN 2020091525W WO 2020233658 A1 WO2020233658 A1 WO 2020233658A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
subscription
response
resources
indicate
Prior art date
Application number
PCT/CN2020/091525
Other languages
English (en)
French (fr)
Inventor
赵君杰
苏京
赵砚秋
Original Assignee
京东方科技集团股份有限公司
北京京东方技术开发有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司, 北京京东方技术开发有限公司 filed Critical 京东方科技集团股份有限公司
Priority to EP20810267.3A priority Critical patent/EP3975598A4/en
Priority to KR1020217041695A priority patent/KR20220011687A/ko
Priority to JP2021569527A priority patent/JP2022534064A/ja
Priority to US17/611,923 priority patent/US20220256007A1/en
Publication of WO2020233658A1 publication Critical patent/WO2020233658A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9532—Query formulation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9535—Search customisation based on user profiles and personalisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/567—Integrating service provisioning from a plurality of service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • This application relates to the field of resource subscriptions, and in particular to a method, device, equipment, and storage medium for subscribing to resources in the field of Internet of Things.
  • the Internet of Things uses communication technologies such as local networks or the Internet to connect sensors, controllers, machines, people, and objects in new ways to form a connection between people and things, and things and things.
  • communication technologies such as local networks or the Internet to connect sensors, controllers, machines, people, and objects in new ways to form a connection between people and things, and things and things.
  • the application can implement operations such as obtaining the status of the application entity and issuing commands.
  • the Internet of Things platform generates corresponding resources for the application entity.
  • the application can obtain the status change of the application entity by subscribing to the resource corresponding to the application entity.
  • This application provides a method, device, equipment and storage medium for subscribing to resources in the field of Internet of Things.
  • a service entity receives a subscription request from a third entity to a first entity; determining a second entity associated with the first entity; The subscription of the second entity; sending a subscription response, the subscription response being used to indicate the result of the subscription.
  • another method for subscribing to resources including: sending a subscription request to a first entity; receiving a subscription response to the subscription request, wherein the second entity and the The first entity is associated, and the subscription response is used to indicate that a result of at least a subscription to the second entity is generated.
  • an apparatus for subscribing to resources including: a receiving unit, configured to enable a service entity to receive a subscription request from a third entity to a first entity; and a determining unit, configured to determine A second entity associated with the first entity; a generating unit, configured to generate at least a subscription to the second entity; a sending unit, configured to send a subscription response, the subscription response being used to indicate the result of the subscription.
  • a device for subscribing to resources including: a memory configured to store computer-readable instructions; and a processor configured to run the computer-readable instructions stored in the memory Instructions, wherein the processor executes the following steps when running the computer-readable instructions: a service entity receives a subscription request from a third entity to a first entity; determines a second entity associated with the first entity; generates at least a pair The subscription of the second entity; sending a subscription response, the subscription response being used to indicate the result of the subscription.
  • a computer-readable storage medium having computer-readable instructions stored thereon, and when the computer-readable instructions are executed by a computer, the computer executes a method for subscribing to resources, and The method includes: a service entity receiving a subscription request from a third entity to a first entity; determining a second entity associated with the first entity; generating at least a subscription to the second entity; sending a subscription response, the subscription response Used to indicate the result of the subscription.
  • the subscription response is used to indicate the generation of the result of the subscription to the second entity, and the The subscription of the second entity makes the subscription resources more abundant.
  • different subscription modes can be created for the state of the second entity, so as to achieve diversification of modes in different situations.
  • FIG. 1 is a schematic diagram of a system for subscribing to resources in an embodiment of the present disclosure
  • Fig. 2 is a flowchart of a method for subscribing to resources according to an embodiment of the present disclosure
  • Fig. 3 is a flowchart of a method for generating a subscription to a second entity according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of another method for generating 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 resources according to an embodiment of the present disclosure
  • Fig. 6 is a schematic diagram of a method for subscribing to resources according to the first example of the present disclosure
  • Fig. 7 is a schematic diagram of a method for subscribing to resources according to a second example of the present disclosure.
  • Fig. 8 is a schematic diagram of a method for subscribing to resources according to a third example of the present disclosure.
  • Fig. 9 is a schematic diagram of an apparatus for subscribing to resources according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a device for subscribing to resources 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 sender (for example, as a subscriber) usually sends a request to create a subscription resource to the receiver (for example, a service entity), and then the receiver creates a subscription under the subscribed resource, and then the receiver is notified
  • the party sends the subscribed response.
  • the receiver only subscribes to the target resource specified in the sender's subscription request, so that the content of the subscription cannot meet the needs of the application.
  • a flowchart is used in this application to illustrate the steps of the method according to the embodiment of the application. It should be understood that the preceding or following steps are not necessarily performed in precise order. Instead, the various steps can be processed in reverse order or simultaneously. At the same time, other operations can be added to these processes, or a certain step or steps can be removed from these processes.
  • the Internet of Things can be used as an extension of the Internet. It includes the Internet and all resources on the Internet, and is compatible with all Internet applications. With the application of the Internet of Things technology in various fields, a variety of new applications of smart IoT such as smart home, smart transportation, and smart health have emerged.
  • the Internet of Things platform may be implemented as a Common Service Entity (CSE), for example, and a terminal device may connect to the Common Service Entity by sending registration information to the Common Service Entity, and the Common Service Entity may access To its terminal equipment for management.
  • CSE Common Service Entity
  • the terminal device may be represented as an application entity (Application Entity, AE), and the application entity that is connected to the general service entity can perform operations such as data transmission and information interaction with the general service entity.
  • Application Entity Application Entity
  • the application entity described in this article can be an IoT terminal device, or can also be an application software module in an IoT terminal device, etc., or can also be an application software module in an IoT server.
  • Application Entity (AE) and Common Service Entity (CSE) are logical entities.
  • Physical devices include logical entities.
  • Relatively simple terminal devices may only include application entities, and relatively complex terminal devices may include application entities and General service entity.
  • the server includes at least a general service entity, and may also include an application entity at the same time.
  • the difference between the general service entity included in the terminal device and the general service entity included in the server lies in the difference in functions.
  • the general service entity of the server includes more functions, such as device management and other functions.
  • the general service entity described in this article may be a service software module in an IoT terminal device, or may also be a service software module in an IoT server.
  • the subscription of the application entity associated with the desired application entity can be generated for the subscriber's subscription request to the desired application entity, and different subscription modes can be generated for the state of the application entity associated with the desired application entity , Which can realize the diversification of subscriptions.
  • the initiator of the subscription request can be an application entity or a general service entity.
  • the application entity sends a subscription request 10 for the object 11 to the general service entity.
  • the general service entity may directly create a subscription for the object 11, and send a subscription response 16 indicating the generation of the subscription for the object 11 to the application entity.
  • the general service entity can determine whether there is an associated object 13 after receiving a subscription request for an object 11.
  • the general service entity sends to the application entity a subscription response 16 indicating the generation of the subscription to the associated object 13 or the object 11 and the associated object 13.
  • the subscription to the associated object associated with the object can be realized, thereby making the subscription resources more abundant.
  • the initiator of the subscription request does not know the associated object or does not have the authority to know the associated object
  • the initiator of the subscription request can subscribe to the associated object through the system described in Figure 1, which enriches the subscription resources and improves the system s efficiency.
  • the second entity may be one or more entities.
  • the following describes a method 100 for subscribing to resources in the Internet of Things field according to an embodiment of the present disclosure with reference to FIG. 2.
  • the method can be performed by a general service entity (for example, a retail server).
  • the Internet of Things subscription resource includes the following steps S101 to S104.
  • step S101 the serving entity receives a subscription request from a third entity to the first entity.
  • step S102 a second entity associated with the first entity is determined.
  • step S103 a subscription to at least the second entity is generated.
  • step S104 a subscription response is sent, and the subscription response is used to indicate the result of the subscription.
  • the service entity receives a subscription request from a third entity to the first entity.
  • the service entity may receive a request from a third entity, the request carries related information, and the related information contains a subscription request to the first entity.
  • the first entity (AE1) may be a virtual electronic tag managed by the service entity and used to indicate corresponding product information.
  • the virtual electronic tag is a digital twin of a physical electronic tag, including attributes such as an electronic tag identifier and a product identifier, and is associated with (or bound to the corresponding product) through the product identifier (ID).
  • the first entity may be a virtual shelf electronic label, which is associated with the corresponding commodity on the shelf through the identification of the commodity;
  • the third entity (AE3) may be a shelf management application or a virtual shopping terminal.
  • the general service entity receives a subscription request from AE3 (shelf management application or shopping terminal) to the shelf electronic label AE1.
  • step S102 a second entity associated with the first entity is determined.
  • the second entity may serve a virtual electronic tag managed by the entity and used to indicate corresponding product information.
  • the second entity may be a virtual inventory electronic tag, which is associated with a corresponding product in the inventory through a product identifier.
  • the general service entity can determine the second entity associated with the first entity by judging 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 is determined that the second entity is associated with the first entity; if the first entity and the second entity are for different objects, it is determined that the second entity is not associated with the first entity .
  • the first entity and the second entity are considered to be for the same object.
  • the product associated with the first entity is Fuji apples
  • the product associated with the second entity is Huang Marshal apples
  • the product associated with the first entity is Fuji apples and the product associated with the second entity is bananas
  • the first entity and the second entity are considered to be for the same object.
  • the product associated with the first entity is Fuji Apple
  • the product associated with the second entity is Fuji Apple
  • the general service entity may determine whether the first entity and the second entity belong to the same group, or determine whether the associated attribute of the first entity includes the second entity, or determine whether the second entity Whether the association attribute includes the first entity determines the second entity associated with the first entity. When it is determined that the condition is met, it indicates that the first entity and the second entity are associated.
  • different commodities can be divided into different groups according to predetermined rules, and the service entity can determine the first entity associated with the corresponding commodity (or bound to the corresponding commodity) and the first entity associated with the corresponding commodity (or bound to the corresponding commodity). Whether the second entity of the commodity belongs to the same predetermined group to determine the second entity associated with the first entity.
  • the apples in the shelf and the bananas in the inventory can be divided into the same group according to predetermined rules. Then, in the case that the shelf electronic label associated with the apples on the shelf is the first entity, the service entity can determine and The shelf electronic tags associated with the apples on the shelf belong to the same group of entities to determine the second entity (ie, the inventory electronic tag) associated with the first entity.
  • the general service entity may also determine the second entity associated with the first entity based on the association rule included in the subscription request.
  • the association rule may be included in the subscription request sent by the shopping terminal received by the general service entity.
  • the association rule may indicate that an entity bound to a commodity of the same category as the commodity associated with the first entity is used as the second entity.
  • the general service entity can then determine the second entity associated with the first entity according to the association rule.
  • the strength of the association between the first entity and the second entity is determined by judging the difference in the categories of the products corresponding to the first entity and the second entity.
  • the difference in the category of the product is small, it means that the strength of the association is high, and the difference in the category is large.
  • the correlation strength is low.
  • the second entity may be one or more entities.
  • a subscription to the second entity is generated.
  • generating a subscription to the second entity includes one of two methods: (1) creating a subscription resource to the second entity; (2) creating a subscription to the first entity and the second entity Subscribe to resources.
  • 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
  • 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. The following describes generating a subscription to the second entity with reference to FIGS. 3-4.
  • Fig. 3 shows a flowchart of a method 200 for generating a subscription to a second entity according to an embodiment of the present disclosure.
  • the subscription to the second entity may be generated in the following manner including: determining a subscription mode for the second entity based on the state of the second entity (S301); and according to the determined subscription mode , Generating a subscription to the second entity (S302).
  • the status of the second entity can be classified into two states: in stock and out of stock. It should be realized that the state of the second entity is not limited to this, and the second entity can be classified into any appropriate state according to the situation, and there is no limitation here.
  • the subscription mode includes long-term subscription, short-term subscription, additional information subscription, scheduled information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc.
  • One or more of the message priority, the validity period of the subscription resource, the notification content, and the number of notification messages under different subscription modes are different. Different subscription modes can be selected for different situations (for example, the state of the second entity), thereby improving user experience.
  • the subscription mode can be divided into long-term subscription and short-term subscription according to the length of the notification validity period reserved for subscription resources.
  • the notification validity period of the long-term subscription is longer than that of the short-term subscription.
  • a longer notification validity period for example, 1 month
  • a shorter notification validity period for example, real-time delivery
  • a notification can be sent to the notified party when the event notification rule is met within the validity period.
  • the subscription mode can be divided into additional information subscription and scheduled information subscription.
  • additional information subscription For example, in the case of a reservation information subscription model, for a certain product, when the event notification rules are met, detailed reservation information such as price, material, discount and other related products related to the reservation information request can be sent to the notified party. , The reservation information request can be included in the subscription request.
  • the notified party can also send additional detailed information such as price, material, discount and other related products that are similar to the product, and the additional detailed information is not included in the subscription request.
  • the subscription mode can be divided into a high priority subscription and a low priority subscription.
  • the notification can be sent first in time, or multiple notifications can be sent to ensure that the notified party can receive the notification.
  • the subscription mode can be divided into high-frequency message subscription and low-frequency message subscription according to the amount of notification information for subscription resources. For example, in the case of high-frequency information subscription mode, you can set a short minimum notification time interval (for example, 2 hours). When the event notification rule is met, a notification is sent to the notified party. The time between two consecutive notifications Not shorter than the minimum notification time interval. For example, in the case of low-frequency information subscription mode, you can set a longer minimum notification time interval (for example, 24 hours). When the event notification rule is met, a notification is sent to the notified party. The time between two consecutive notifications is not Shorter than the minimum notification interval.
  • a subscription mode for the second entity may be determined for the state of the second entity.
  • the status of the second entity is judged by the attributes of the second entity.
  • the attributes of the second entity include object attributes (for example, the second entity object is a commodity, and the object attribute is information about the commodity, including the quantity and size of the commodity), environmental attributes ( For example, people, things, things, sounds, light, etc. around the second entity).
  • the first entity is a shelf electronic label
  • the second entity associated with the first entity is an inventory electronic label. Both the first entity and the second entity are for the same commodity A.
  • the first entity includes the shelf quantity of commodity A.
  • the second entity includes the inventory quantity of commodity A.
  • the first entity is a shelf electronic label
  • the second entity associated with the first entity is an inventory electronic label. Both the first entity and the second entity are for the same commodity A, and the first entity is The entity includes the shelf quantity of commodity A, and the second entity includes the inventory quantity of commodity A.
  • the second entity shows that the inventory quantity of commodity A is zero
  • you can choose between long-term subscription and low-frequency subscription for example, you can set the notification validity period to For 1 month, when the event notification rules are met within the validity period, the event will be cached and integrated, and the processed event will be sent to the notified party (notification), while meeting the requirements of long-term subscription and low-frequency subscription
  • high-priority subscription send notifications first when the event notification rules are met
  • low-priority subscriptions send notifications when the event notification rules are met and no high-priority events are to be sent
  • high-frequency message subscriptions not process events
  • the time notification rule is met, the notification is sent directly
  • the low-frequency message subscription notification is sent after the event is processed, including event caching, event integration, etc.
  • the above subscription mode is just an example. For different situations, you can choose one of long-term subscription, short-term subscription, additional information subscription, scheduled information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc. Or more, you can also choose other suitable subscription modes, which will not be repeated here.
  • step S302 a subscription to the second entity is generated according to the determined subscription mode.
  • FIG. 4 shows a flowchart of another method 300 for generating a subscription to a second entity according to an embodiment of the present disclosure.
  • generating a subscription to the second entity in the following manner includes: determining a subscription mode for the first entity and the second entity based on the state of the second entity (S301); The determined subscription mode generates subscriptions to the first entity and the second entity (S302).
  • the selection of the subscription mode described in FIG. 4 is similar to the selection of the subscription mode described in FIG. 3 above, and will not be repeated here.
  • a subscription response is sent, and the subscription response is used to indicate the result of the subscription.
  • a subscription response may be sent to a third entity, or a subscription response may be sent to other entities, where the subscription response is used to indicate the result of the generated subscription.
  • the subscription response is used to indicate the result of creating a subscription resource to the second entity; in some embodiments, when creating a subscription resource to the second entity, the subscription response is used to indicate a result of the creation of the subscription resource for the first entity and the second entity.
  • the subscription request may include multiple notified parties for receiving event notifications related to the subscription request.
  • the general service entity When the event notification rule of the subscriber is satisfied, the general service entity will send an event notification to all notified parties included in the subscription request. For example, when the manhole cover is moved, the manhole cover movement sensor will sense this change and send update data to the general service entity.
  • the general 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 the movement of the manhole cover, at this time, the general service entity determines that the event notification rule is satisfied, and sends an event notification to all notified parties included in the subscription request for subscribing to the event notification of the manhole cover movement, that is, notify all The notified party's manhole cover was moved.
  • the following describes another method 400 for subscribing to resources according to an embodiment of the present disclosure with reference to FIG. 5.
  • This method may be executed by an application entity (for example, the aforementioned third entity AE3).
  • step S401 a subscription request for the first entity is sent.
  • step S402 a subscription response to the subscription request is received, wherein the second entity is associated with the first entity, and the subscription response is used to indicate that a result of at least a subscription to the second entity is generated .
  • the first entity (AE1) may be a virtual electronic tag managed by the service entity and used to indicate corresponding product information.
  • the virtual electronic tag is associated with the corresponding product (or bound to the corresponding product) through the product identifier (ID).
  • the first entity may be a virtual shelf electronic label;
  • the third entity (AE3) may be a shelf management application or a virtual shopping terminal.
  • AE3 (for example, a shelf management application or a shopping terminal) sends a subscription request for the shelf electronic tag AE1 to the general service entity.
  • AE3 receives a subscription response to the subscription request, wherein the second entity is associated with the first entity, and the subscription response is used to indicate that a result of at least a subscription to the second entity is generated.
  • the subscription request may include an association rule for establishing an association relationship between the first application entity and the second application entity.
  • the universal service entity can also determine the second entity associated with the first entity based on the association rule included in the subscription request.
  • the association rule may indicate that an entity bound to a commodity of the same category as the commodity associated with the first entity is used as the second entity.
  • the subscription response is generated based on the subscription mode for the subscription request determined based on the state of the second application entity.
  • the subscription response is formed by: determining a subscription mode for the second entity based on the status of the second entity; generating a subscription for the second entity according to the determined subscription mode, and The subscription response is used to indicate that at least the result of the subscription to the second entity is generated.
  • the subscription response may also be formed in the following manner: based on the state of the second entity, determine the subscription mode for the first entity and the second entity; and generate a response to the subscription mode according to the determined subscription mode.
  • the subscription of the first entity and the second entity, and the subscription response is used to indicate the result of generating the subscription to the first entity and the second entity.
  • the method of generating the subscription response is the same as the method described in Figure 2, and will not be repeated here.
  • FIGS. 6-8 is a schematic diagram of a method for subscribing to resources according to a first example of the present disclosure
  • FIG. 7 is a schematic diagram of a method for subscribing to resources according to a second example of the present disclosure
  • FIG. 8 is a schematic diagram of a method for subscribing to resources according to a third example of the present disclosure Schematic diagram of the method.
  • the Internet of Things can be composed of a general service entity and a series of application entities.
  • the general service entity can be a retail server, etc.
  • the application entity can be various sensor devices, or a user terminal such as a mobile phone, or a device.
  • Software modules such as mobile phone applications.
  • the general service entity manages its connected application entities and performs operations such as registration, data transmission, task execution, and so on.
  • Fig. 6 shows a first example for subscribing to resources according to the present disclosure.
  • the shelf management application entity of a shopping mall or supermarket initiates a subscription to adjust the goods status of the shopping mall or supermarket in time.
  • the retail server CSE53 receives electronic tags from the shelf AE1 51 (first entity), inventory electronic tags AE2 52 (second entity), and the shelf management application AE3 54 ( The third entity)’s registration request to establish an association with the shelf electronic label AE1 51, inventory electronic label AE2 52, and shelf management application AE3 54, and follow the shelf electronic label AE1 51, inventory electronic label AE2 52, and shelf management Update their status 55 with the status change of AE3 54.
  • the retail server CSE53 determines whether the goods associated with the shelf electronic label AE1 51 and the goods associated with the inventory electronic label AE2 52 are for the same category of goods 56. If so, the shelf electronic label AE1 51 is established with the inventory electronic label AE2 52. Association between tags AE252 57.
  • the retail server CSE 53 first determines whether the shelf electronic label AE151 has an associated object inventory electronic label AE2 52 (the label in Figure 6 is 60).
  • the retail server CSE 53 can create a subscription resource for the inventory electronic label AE2 52, and send a subscription response 62 to the retail server CSE 53 (or other entity) to subscribe In response to the instruction, the result of subscribing to the inventory electronic label AE2 52 is generated; in some embodiments, the retail server CSE 53 can also create subscription resources for the shelf electronic label AE1 51 and the inventory electronic label AE2 52, and send it to the retail server CSE 53 (or The other entity) sends a subscription response 62, which indicates that the result of subscribing to the shelf electronic tag AE1 51 and the inventory electronic tag AE2 52 is generated.
  • the subscription mode 61 for the inventory electronic tag AE2 52 can be determined according to the status of the inventory electronic tag AE2 52. For example, as described above, if the inventory electronic tag AE2 shows that it is in stock, a short-term subscription can be established, and if the inventory electronic tag AE2 shows that it is out of stock, a long-term subscription can be established.
  • the retail server CSE 53 when the retail server CSE 53 creates subscription resources for the shelf electronic tags AE1 51 and the inventory electronic tags AE2 52, it can be determined based on the status of the inventory electronic tags AE2 52 for the shelf electronic tags AE1 51 and the inventory electronic tags AE2 52's subscription model 61. For example, as described above, if the inventory electronic tag AE2 shows that it is in stock, a short-term subscription can be established, and if the inventory electronic tag AE2 shows that it is out of stock, a long-term subscription can be established.
  • the retail server CSE 53 updates the status 63 of the shelf electronic label AE1 51. Subsequently, when the event notification rule 64 is satisfied, the event notification 65 is sent to the notified party (for example, the shelf management application AE3 54) according to the determined subscription mode.
  • the notified party for example, the shelf management application AE3 54
  • Fig. 7 shows a second example for subscribing to resources according to the present disclosure.
  • a shopping terminal e.g., a user
  • initiates a subscription so as to know the status of the desired product in a timely manner.
  • the retail server CSE53 receives electronic tags from the shelf AE1 51 (first entity), inventory electronic tags AE2 52 (second entity), and the shopping terminal AE3 66 (the second entity) as a subscriber.
  • the registration request of the three entities thereby establishing the association relationship with the shelf electronic label AE151, the inventory electronic label AE2 52, and the shopping terminal AE3 66, and follow the shelf electronic label AE1 51, the inventory electronic label AE2 52 and the shopping terminal AE3 66.
  • Status changes update their status.
  • the retail server CSE 53 determines whether the goods associated with the electronic shelf tag AE1 51 and the goods associated with the electronic inventory tag AE2 52 are for the same type of goods, and if so, the shelf electronic tag AE1 51 is established. Association with inventory electronic label AE2 52.
  • the retail server CSE 53 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 associated object inventory electronic tag AE2 52. If the shelf electronic label AE1 51 has an associated object inventory electronic label AE2 52, the retail server CSE 53 can create a subscription resource for the inventory electronic label AE2 52, and send a subscription response to the shopping terminal AE3 66 (or other entity), the subscription response Indicates the result of generating a subscription to the inventory electronic tag AE2 52; in some embodiments, the retail server CSE 53 can also create subscription resources for the shelf electronic tag AE1 51 and the inventory electronic tag AE252, and send it to the shopping terminal AE3 66 (or other entity ) Send a subscription response, the subscription response instructs to generate the result of the subscription to the shelf electronic label AE1 51 and the inventory electronic label AE2 52.
  • the subscription mode for the inventory electronic label AE2 52 can be determined according to the status of the inventory electronic label AE2 52. For example, if the inventory electronic label AE2 shows that it is in stock, a short-term subscription can be established; if the inventory electronic label AE2 shows that it is out of stock, a long-term subscription can be established.
  • the retail server CSE 53 when the retail server CSE 53 creates subscription resources for the shelf electronic tags AE1 51 and the inventory electronic tags AE2 52, it can be determined based on the status of the inventory electronic tags AE2 52 for the shelf electronic tags AE1 51 and the inventory electronic tags AE2 52 subscription model. For example, as described above, if the inventory electronic tag AE2 shows that it is in stock, a short-term subscription can be established, and if the inventory electronic tag AE2 shows that it is out of stock, a long-term subscription can be established.
  • the retail server CSE 53 updates the status 63 of the shelf electronic label AE1 51. Subsequently, when the event notification rule is satisfied, the event notification is sent to the notified party (for example, the shopping terminal AE3 66) according to the determined subscription mode.
  • the notified party for example, the shopping terminal AE3 66
  • Fig. 8 shows a third example for subscribing to resources according to the present disclosure.
  • an association rule may be included in the subscription request sent by the application entity, and then the general service entity establishes an association between different objects according to the association rule.
  • the retail server CSE 53 receives electronic tags from the shelf AE1 51 (first entity), inventory electronic tags AE2 52 (second entity), and the shopping terminal AE3 66 (the second entity) as a subscriber.
  • the registration request of the three entities thereby establishing the association relationship with the shelf electronic label AE151, the inventory electronic label AE2 52, and the shopping terminal AE3 66, and follow the shelf electronic label AE1 51, the inventory electronic label AE2 52 and the shopping terminal AE3 66.
  • Status changes update their status.
  • the retail server CSE 53 establishes the shelf electronic label AE1 51 and the inventory electronic label according to the association rules contained in the subscription request.
  • the retail server CSE 53 can create a subscription resource for the inventory electronic label AE2 52, and send a subscription response to the shopping terminal AE3 66 (or to other entities), and the subscription response indicates that the result of the subscription to the inventory electronic label AE2 52 is generated
  • the retail server CSE 53 may also create subscription resources for the shelf electronic label AE1 51 and the inventory electronic label AE2 52, and send a subscription response to the shopping terminal AE3 66 (or other entities).
  • the subscription response indicates that The result of the subscription of shelf electronic label AE1 51 and inventory electronic label AE2 52.
  • the subscription mode for the inventory electronic label AE2 52 can be determined according to the status of the inventory electronic label AE2 52. For example, as described above, if the inventory electronic tag AE2 shows that it is in stock, a short-term subscription can be established, and if the inventory electronic tag AE2 shows that it is out of stock, a long-term subscription can be established.
  • the retail server CSE 53 when the retail server CSE 53 creates subscription resources for the shelf electronic tags AE1 51 and the inventory electronic tags AE2 52, it can be determined based on the status of the inventory electronic tags AE2 52 for the shelf electronic tags AE1 51 and the inventory electronic tags AE2 52 subscription model. For example, as described above, if the inventory electronic tag AE2 shows that it is in stock, a short-term subscription can be established, and if the inventory electronic tag AE2 shows that it is out of stock, a long-term subscription can be established.
  • the retail server CSE53 updates the status of the shelf electronic label AE1 51. Subsequently, when the event notification rule is satisfied, the event notification is sent to the notified party (for example, the shopping terminal AE3 66) according to the determined subscription mode.
  • the notified party for example, the shopping terminal AE3 66
  • the subscription to the second entity associated with the first entity can be realized, thereby making the subscribed resources more abundant.
  • different subscription modes can be created for the state of the second entity, so as to achieve diversification of modes in different situations.
  • FIG. 9 is a schematic diagram of an apparatus 1000 for subscribing to resources according to an embodiment of the present disclosure. Since the function of the apparatus for subscribing to resources of this embodiment is the same as the method described above with reference to FIG. 1 in detail, a detailed description of the same content is omitted here for simplicity.
  • the apparatus 1000 for subscribing to resources 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 apparatus 1000 for subscribing to resources is shown as including only 4 units in FIG. 9, this is only illustrative, and the apparatus 1000 for subscribing to resources may also include one or more other units. These units have nothing to do with the inventive concept, so they are omitted here.
  • the receiving unit 1001 enables the service entity to receive a subscription request from a third entity to the first entity.
  • the first entity (AE1) may be a shelf electronic label
  • the third entity (AE3) may be a shelf management application or a shopping terminal.
  • the general service entity receives a subscription request from AE3 (shelf management application or shopping terminal) to the shelf electronic label AE1.
  • the determining unit 1002 determines a second entity associated with the first entity.
  • the second entity (AE2) may be an inventory electronic tag.
  • the determining unit 1002 can determine the inventory electronic tag associated with the shelf electronic tag.
  • the determining unit 1002 may determine the second entity associated with the 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 is determined that the second entity is associated with the first entity; if the first entity and the second entity are for different objects, it is determined that the second entity is not associated with the first entity .
  • the determining unit 1002 may also determine the second entity associated with the first entity based on the association rule included in the subscription request.
  • the association rule may be included in the subscription request sent by the shopping terminal received by the receiving unit 1001.
  • the association rule may indicate that an entity bound to a commodity of the same category as the commodity associated with the first entity is used as the second entity. Then the general service entity can determine the second entity associated with the first entity according to the association rule.
  • the generating unit 1003 After the determining unit 1002 determines the second entity associated with the first entity, next, the generating unit 1003 generates at least a subscription to the second entity.
  • generating a subscription to the second entity includes one of two methods: (1) creating a subscription resource to the second entity; (2) creating a subscription to the first entity and the second entity Subscribe to resources.
  • 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
  • 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. The following describes the generation unit 1003 generating subscription to the second entity with reference to FIGS. 3-4.
  • FIG. 3 shows a flowchart of a method 200 for generating a subscription to a second entity according to an embodiment of the present disclosure.
  • the subscription to the second entity may be generated in the following manner including: determining a subscription mode for the second entity based on the state of the second entity (S301); and according to the determined subscription mode , Generating a subscription to the second entity (S302).
  • the status of the second entity can be classified into two states: in stock and out of stock.
  • the state of the second entity is not limited to this, and the second entity can be classified into any appropriate state according to the situation, and there is no limitation here.
  • the subscription mode includes long-term subscription, short-term subscription, additional information subscription, scheduled information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc.
  • One or more of the message priority, the validity period of the subscription resource, the notification content, and the number of notification messages under different subscription modes are different. Different subscription modes can be selected for different situations (for example, the state of the second entity), thereby improving user experience.
  • the subscription mode can be divided into long-term subscription and short-term subscription according to the length of the notification validity period reserved for subscription resources.
  • the notification validity period of the long-term subscription is longer than that of the short-term subscription.
  • a longer notification validity period for example, 1 month
  • a shorter notification validity period for example, real-time transmission
  • a notification can be sent to the notified party when the event notification rule is met within the validity period.
  • the subscription mode can be divided into additional information subscription and scheduled information subscription.
  • additional information subscription For example, in the case of a reservation information subscription model, for a certain product, when the event notification rules are met, detailed reservation information such as price, material, discount and other related products related to the reservation information request can be sent to the notified party. , The reservation information request can be included in the subscription request.
  • the notified party can also send additional detailed information such as price, material, discount and other related products that are similar to the product, and the additional detailed information is not included in the subscription request.
  • the subscription mode can be divided into a high priority subscription and a low priority subscription.
  • the notification can be sent first in time, or multiple notifications can be sent to ensure that the notified party can receive the notification.
  • the subscription mode can be divided into high-frequency message subscription and low-frequency message subscription according to the amount of notification information for subscription resources. For example, in the case of high-frequency information subscription mode, you can set a short minimum notification time interval (for example, 2 hours). When the event notification rule is met, a notification is sent to the notified party. The time between two consecutive notifications Not shorter than the minimum notification time interval. For example, in the case of low-frequency information subscription mode, you can set a longer minimum notification time interval (for example, 24 hours). When the event notification rule is met, a notification is sent to the notified party. The time between two consecutive notifications is not Shorter than the minimum notification interval.
  • a subscription mode for the second entity may be determined for the state of the second entity (for example, the state of in-stock or out-of-stock).
  • a long-term subscription for example, you can set the notification validity period to 1 month.
  • a short-term subscription for example, when the event notification rules are met, a notification message is sent in real time.
  • high priority subscription low priority subscription
  • high frequency message subscription high frequency message subscription
  • low frequency message subscription low frequency message subscription
  • low frequency message subscription can also be selected. It should be understood that the above subscription mode is just an example. For different situations, you can choose one of long-term subscription, short-term subscription, additional information subscription, scheduled information subscription, high priority subscription, low priority subscription, high frequency message subscription, low frequency message subscription, etc. Or more, you can also choose other suitable subscription modes, which will not be repeated here.
  • step S302 After the subscription mode is determined, next, in step S302, according to the determined subscription mode, the generating unit 1003 generates a subscription to the second entity.
  • FIG. 4 shows a flowchart of another method 300 for generating a subscription to a second entity according to an embodiment of the present disclosure.
  • generating a subscription to the second entity in the following manner includes: determining a subscription mode for the first entity and the second entity based on the state of the second entity (S301); The determined subscription mode generates subscriptions to the first entity and the second entity (S302).
  • the selection of the subscription mode described in FIG. 4 is similar to the selection of the subscription mode described in FIG. 3 above, and will not be repeated here.
  • the sending unit 1004 sends a subscription response, where the subscription response is used to indicate the result of the subscription.
  • a subscription response may be sent to a third entity, or a subscription response may be sent to other entities, where the subscription response is used to indicate the result of the generated subscription.
  • the subscription response is used to indicate the result of creating a subscription resource to the second entity; in some embodiments, when creating a subscription resource to the second entity, the subscription response is used to indicate a result of the creation of the subscription resource for the first entity and the second entity.
  • the subscription request may include multiple notified parties for receiving event notifications related to the subscription request.
  • the general service entity When the event notification rule of the subscriber is satisfied, the general service entity will send an event notification to all notified parties included in the subscription request. For example, when the manhole cover is moved, the manhole cover movement sensor will sense this change and send update data to the general service entity.
  • the general service entity can determine whether the event notification rule is met based on the update data of the manhole cover movement sensor, for example, When the subscription condition is the movement of the manhole cover, at this time, the general service entity determines that the event notification rule is satisfied, and sends an event notification to all notified parties included in the subscription request for subscribing to the event notification of the manhole cover movement, that is, notify all The notified party's manhole cover was moved.
  • FIG. 10 is a schematic diagram of a device 1100 for subscribing to resources according to an embodiment of the present disclosure. Since the function of the device for subscribing to resources of this embodiment is the same as that of the method described above with reference to FIG. 1, a detailed description of the same content is omitted here for simplicity.
  • the device 1100 for subscribing to resources includes a memory 1101 and a processor 1102. It should be noted that although the device 1100 for subscribing to resources is shown as including only 2 devices in FIG. 10, this is only illustrative, and the device 1100 for subscribing to resources may also include one or more other devices. These devices have nothing to do with the inventive concept, so they are omitted here.
  • the device for subscribing to resources of the present disclosure includes: a memory 1101 configured to store computer-readable instructions; and a processor 1102 configured to run the computer-readable instructions stored in the memory, wherein the processing
  • the following steps are executed when the computer readable instruction is executed by the server: a service entity receives a subscription request from a third entity to a first entity; determines a second entity associated with the first entity; generates at least a subscription to the second entity ; Send a subscription response, the subscription response is used to indicate the result of the subscription.
  • FIG. 11 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure.
  • the present disclosure also includes a computer-readable storage medium on which computer-readable instructions are stored.
  • the computer executes a method for subscribing to resources.
  • the method includes: a service entity receiving a subscription request from a third entity to a first entity; determining a second entity associated with the first entity; generating at least a subscription to the second entity; sending a subscription response, the subscription response Used to indicate the result of the generation of the subscription.

Abstract

一种用于物联网领域的订阅资源的方法、装置、设备和存储介质，该用于订阅资源的方法包括：服务实体接收第三实体对第一实体的订阅请求（S101）；确定与所述第一实体关联的第二实体（S102）；生成至少对所述第二实体的订阅（S103）；发送订阅响应，所述订阅响应用于指示所述订阅的结果（S104）。上述方法可以使得订阅的资源更加丰富。

Description

物联网领域的订阅资源的方法、装置、设备和存储介质
相关申请的交叉引用
本申请要求于2019年5月23日提交的中国专利申请号201910433275.7的优先权，该中国专利申请的全文通过引用的方式结合于此以作为本申请的一部分。
技术领域
本申请涉及资源订阅领域，并且具体涉及一种用于物联网领域的订阅资源的方法、装置、设备和存储介质。
背景技术
随着信息技术尤其是互联网技术的发展，用于实现信息化、远程管理控制和智能化的物联网技术逐渐成熟。物联网利用局部网络或互联网等通信技术把传感器、控制器、机器、人员和物品等通过新的方式联接在一起，形成人与物、物与物之间的连接。随着物联网技术在各个应用领域的快速发展，越来越多的设备连接至物联网，出现了诸如智能家居、智能交通、智慧健康等各种新的应用领域。
随着物联网的发展，越来越多的应用实体接入到云端，通过应用实体不断数字化，在云端为应用实体形成了对应的虚拟实体(称为数字孪生)。应用通过控制云端的虚拟实体，可以实现对应用实体的状态获取、命令下发等操作。为了使得应用实体接入云端，需要通过注册的方式接入到物联网平台，物联网平台为应用实体生成对应的资源，应用通过订阅应用实体对应的资源，可以获取应用实体的状态变化。
发明内容
本申请提供了一种用于物联网领域的订阅资源的方法、装置、设备和存储介质。
根据本公开的一个方面，提供了一种用于订阅资源的方法，包括：服务实体接收第三实体对第一实体的订阅请求；确定与所述第一实体关联的第二 实体；生成至少对所述第二实体的订阅；发送订阅响应，所述订阅响应用于指示所述订阅的结果。
根据本公开的一个方面，提供了另一种用于订阅资源的方法，包括：发送对第一实体的订阅请求；接收针对所述订阅请求的订阅响应，其中，所述第二实体与所述第一实体相关联，所述订阅响应用于指示生成至少对所述第二实体的订阅的结果。
根据本公开的另一个方面，提供了一种用于订阅资源的装置，包括：接收单元，用于使服务实体接收第三实体对第一实体的订阅请求；确定单元，用于确定与所述第一实体关联的第二实体；生成单元，用于生成至少对所述第二实体的订阅；发送单元，用于发送订阅响应，所述订阅响应用于指示所述订阅的结果。
根据本公开的又一个方面，提供了一种用于订阅资源的设备，包括：存储器，配置为存储计算机可读指令；以及处理器，配置为运行存储在所述存储器中的所述计算机可读指令，其中，所述处理器运行所述计算机可读指令时执行以下步骤：服务实体接收第三实体对第一实体的订阅请求；确定与所述第一实体关联的第二实体；生成至少对所述第二实体的订阅；发送订阅响应，所述订阅响应用于指示所述订阅的结果。
根据本公开的再一个方面，提供了一种计算机可读存储介质，其上存储计算机可读指令，当所述计算机可读指令由计算机执行时，所述计算机执行用于订阅资源的方法，所述方法包括：服务实体接收第三实体对第一实体的订阅请求；确定与所述第一实体关联的第二实体；生成至少对所述第二实体的订阅；发送订阅响应，所述订阅响应用于指示所述订阅的结果。
在本公开的上述方面中，通过基于第二实体的状态向第三实体发送订阅响应，该订阅响应用于指示生成对所述第二实体的订阅的结果，可以实现对与第一实体关联的第二实体的订阅，从而使得订阅的资源更加丰富。此外，可以针对第二实体的状态创建不同的订阅模式，从而实现不同情况下模式的多样化。
附图说明
通过结合附图对本公开实施例进行更详细的描述，本公开的上述以及其它目的、特征和优势将变得更加明显。附图用来提供对本公开实施例的进一步 理解，并且构成说明书的一部分，与本公开实施例一起用于解释本公开，并不构成对本公开的限制。在附图中，相同的参考标记通常代表相同部件或步骤。
图1是用于实现本公开实施例的订阅资源的系统的示意图；
图2是根据本公开实施例的用于订阅资源的方法的流程图；
图3是根据本公开实施例的生成对第二实体的订阅的一种方法的流程图；
图4是根据本公开实施例的生成对第二实体的订阅的另一方法的流程图；
图5是根据本公开实施例的用于订阅资源的另一方法的流程图；
图6是根据本公开第一示例的用于订阅资源方法的示意图；
图7是根据本公开第二示例的用于订阅资源方法的示意图；
图8是根据本公开第三示例的用于订阅资源方法的示意图；
图9是根据本公开实施例的用于订阅资源的装置的示意图；
图10是根据本公开实施例的用于订阅资源的设备的示意图；
图11是根据本公开实施例的计算机可读存储介质的示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本公开一部分的实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在无需创造性劳动的前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开中使用的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“包括”或者“包含”等类似的词语意指出现该词前面的元件或者物件涵盖出现在该词后面列举的元件或者物件及其等同，而不排除其他元件或者物件。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。
在一些实施方式中，通常由发送方(例如，作为订阅方)向接收方(例如，服务实体)发送创建订阅资源的请求，然后接收方在被订阅资源下创建订阅，然后由接收方向被通知方发送订阅的响应。接收方只针对发送方的订阅请求中指定的目标资源进行订阅，导致订阅的内容无法满足应用的需求。
本申请中使用了流程图用来说明根据本申请的实施例的方法的步骤。应当理解的是，前面或后面的步骤不一定按照顺序来精确的进行。相反，可以按 照倒序或同时处理各种步骤。同时，也可以将其他操作添加到这些过程中，或从这些过程移除某一步或数步。
物联网可以作为互联网的一种延伸，它包括互联网及互联网上所有的资源，兼容互联网所有的应用。随着物联网技术在各个领域的应用，出现了诸如智能家居、智能交通、智慧健康等各种新的智慧物联的应用领域。
随着物联网技术的发展，越来越多的终端设备接入到物联网平台，如烟雾报警器、火灾警报器、井盖移动传感器等。所述物联网平台例如可以实施为通用服务实体(Common Service Entity，CSE)，终端设备可以通过向通用服务实体发送注册信息的方式来与所述通用服务实体连接，所述通用服务实体对接入到其的终端设备进行管理。所述终端设备可以表示为应用实体(Application Entity，AE)，接入到通用服务实体的应用实体可以与该通用服务实体进行数据传输和信息交互等操作。需要注意的是，本文中所描述的应用实体可以是物联网终端设备，或者也可以是物联网终端设备中的应用软件模块等、或者也可以是物联网服务器中的应用软件模块。
应用实体(Application Entity，AE)、通用服务实体(Common Service Entity，CSE)是逻辑实体，物理设备包括逻辑实体，相对简单的终端设备可以只包括应用实体，相对复杂的终端设备可包括应用实体和通用服务实体。比如，服务器至少包括通用服务实体，也可以同时包括应用实体。终端设备包括的通用服务实体和服务器包括的通用服务实体的区别在于功能的差异，一般的，服务器的通用服务实体包括的功能更多，如包括设备管理等功能。本文中所描述的通用服务实体可以是物联网终端设备中的服务软件模块，或者也可以是物联网服务器中的服务软件模块。
在本公开中，可以针对订阅方对期望应用实体的订阅请求，生成与期望应用实体相关联的应用实体的订阅，并且可以针对与期望应用实体相关联的应用实体的状态，生成不同的订阅模式，从而可以实现订阅的多样化。
首先，参照图1来描述用于实现本公开实施例的用于订阅资源的系统。
如图1所示，在物联网系统中，订阅请求的发起方可以为应用实体，或通用服务实体。以应用实体为例，应用实体向通用服务实体发送针对对象11的订阅请求10。例如，通用服务实体在接收到针对对象11的订阅请求后，可以直接创建针对对象11的订阅，并向应用实体发送指示生成对对象11的订阅的订阅响应16。在一些实施方式，如图1所示，通用服务实体可以在接收 到针对对象11的订阅请求后，判断是否存在关联对象13，如果存在关联对象13，则可以通过判断关联对象的状态14，生成对关联对象13或者对象11与关联对象13的订阅，然后由通用服务实体向应用实体发送指示生成对关联对象13或者对象11与关联对象13的订阅的订阅响应16。通过上述方式，可以实现对与对象关联的关联对象的订阅，从而使得订阅的资源更加丰富。例如，订阅请求的发起方不知道关联对象或无权限知道关联对象的情况下，订阅请求的发起方通过图1描述的系统，可以实现对关联对象的订阅，丰富了订阅的资源，提升了系统的效率。需要说明的是，第二实体可以是一个或多个实体。
下面参照图2描述根据本公开实施例的用于物联网领域的订阅资源的方法100。该方法可以由通用服务实体执行(例如，零售服务器)。该物联网订阅资源包括以下的步骤S101-步骤S104。
在步骤S101，服务实体接收第三实体对第一实体的订阅请求。
在步骤S102，确定与所述第一实体关联的第二实体。
在步骤S103，生成至少对所述第二实体的订阅。
在步骤S104，发送订阅响应，所述订阅响应用于指示所述订阅的结果。
如图2所示，在步骤S101中，服务实体接收第三实体对第一实体的订阅请求。例如，服务实体可以接收来自第三实体的请求，该请求中携带相关信息，该相关信息中包含有对第一实体的订阅请求。
例如，第一实体(AE1)可以是服务实体管理的、用于指示相应商品信息的虚拟电子标签。该虚拟电子标签是物理电子标签的数字孪生，包括电子标签标识、商品的标识等属性，通过商品的标识(ID)与相应商品相关联(或绑定到相应商品)。例如，该第一实体可以是虚拟的货架电子标签，其通过商品的标识与货架上的相应商品相关联；该第三实体(AE3)可以是货架管理应用，也可以是虚拟购物终端。例如，在该步骤中，通用服务实体接收AE3(货架管理应用或购物终端)对货架电子标签AE1的订阅请求。
接下来，在步骤S102中，确定与所述第一实体关联的第二实体。
例如，第二实体(AE2)可以服务实体管理的、用于指示相应商品信息的虚拟电子标签。例如，该第二实体可以是虚拟的库存电子标签，其通过商品的标识与库存中的相应商品相关联。例如，在该步骤中，可以判断库存电子标签AE2与货架电子标签AE1关联。
例如，通用服务实体可以通过判断第一实体和第二实体是否针对同一对 象来确定与第一实体关联的第二实体。例如，如果第一实体和第二实体针对同一对象，则确定第二实体与第一实体相关联；如果第一实体和第二实体针对不同对象，则确定第二实体不与第一实体相关联。
例如，如果与第一实体相关联的商品和与第二实体相关联的商品属于同一类，则认为第一实体和第二实体针对同一对象。作为一个示例，与第一实体相关联的商品为富士苹果，与第二实体相关联的商品为黄元帅苹果，则可以判断这两个商品属于同一类(都属于苹果)，即可以认为第一实体和第二实体针对同一对象。作为另一个示例，与第一实体相关联的商品为富士苹果，与第二实体相关联的商品为香蕉，则可以判断这两个商品不属于同一类，即可以认为第一实体和第二实体针对不同对象。
再例如，如果与第一实体相关联的商品和与第二实体相关联的商品完全相同，则认为第一实体和第二实体针对同一对象。作为一个示例，与第一实体相关联的商品为富士苹果，与第二实体相关联的商品为富士苹果，则可以判断这两个商品完全相同，即可以认为第一实体和第二实体针对同一对象。
另外，例如，通用服务实体可通过判断所述第一实体和所述第二实体是否属于同一组、或判断所述第一实体的关联属性是否包括第二实体、或判断所述第二实体的关联属性是否包括第一实体来确定与第一实体关联的第二实体。当确定满足条件时，则说明第一实体和第二实体相关联。
例如，可以根据预定规则将不同的商品分成不同的组，通过服务实体可以通过判断与相应商品相关联(或绑定到相应商品)的第一实体和与相应商品相关联(或绑定到相应商品)的第二实体是否属于预先确定的同一组，来确定与所述第一实体关联的第二实体。作为一个示例，可以根据预定规则将货架中的苹果与库存中的香蕉分为同一组，那么在与货架上的苹果相关联的货架电子标签作为第一实体的情况下，服务实体可以通过确定与货架上的苹果相关联的货架电子标签属于相同组的实体来确定与该第一实体相关联的第二实体(即库存电子标签)。
在一些实施方式，通用服务实体还可以基于所述订阅请求中包含的关联规则，确定与所述第一实体关联的第二实体。
例如，该关联规则可以包含在通用服务实体接收的购物终端发送的订阅请求中。例如，该关联规则可以指示将与第一实体相关联的商品的类别相同的商品绑定的实体作为第二实体。然后通用服务实体可以根据该关联规则确定 与第一实体关联的第二实体。
在一些实施方式，计算第一实体和第二实体之间存在关联强度，关联强度大于预设阈值时，判断第一实体与第二实体关联。
例如，第一实体和第二实体的关联强度通过判断第一实体和第二实体对应的商品的类别差异，当商品类别的差异较小，说明关联强度较高，类别的差异较大，则说明关联强度较低。
需要说明的是，第二实体可以是一个或多个实体。
在确定了与所述第一实体关联的第二实体后，接下来，在步骤S103中，生成对所述第二实体的订阅。这里，生成对所述第二实体的订阅包括两种方法中的一个：(1)创建对所述第二实体的订阅资源；(2)创建对所述第一实体和所述第二实体的订阅资源。
图3为根据本公开实施例的生成对第二实体的订阅的一种方法200的流程图，图4为根据本公开实施例的生成对第二实体的订阅的另一方法200的流程图。下面参照图3-4描述生成对所述第二实体的订阅。
图3所示为根据本公开实施例的生成对第二实体的订阅的一种方法200的流程图。如图3所示，可以通过以下方式生成对所述第二实体的订阅包括：基于所述第二实体的状态，确定针对所述第二实体的订阅模式(S301)；根据所确定的订阅模式，生成对所述第二实体的订阅(S302)。
例如，在第二实体是零售领域下的虚拟电子标签的情况下，该第二实体的状态可以分类为有货和无货两种状态。应当认识到，第二实体的状态不限于此，可以根据情况将第二实体分类为任何适当的状态，这里不做限制。
例如，订阅模式包括长期订阅、短期订阅、附加信息订阅、预定信息订阅、高优先订阅、低优先订阅、高频消息订阅、低频消息订阅等。不同订阅模式下的消息优先级、订阅资源的有效期、通知内容、通知消息的数量等的一个或多个不同。可以针对不同的情况(例如，第二实体的状态)选择不同的订阅模式，从而提升用户体验。接下来详细介绍各个不同的订阅模式。
例如，根据对订阅资源保留的通知有效期的长短，可以将订阅模式分为长期订阅和短期订阅，长期订阅的通知有效期比短期订阅更长。例如，在长期订阅模式的情况下，可以设置较长的通知有效期(例如，1个月)，在该有效期内满足事件通知规则时，都可以向被通知方发送通知。然而，例如在短期订阅模式的情况下，可以设置较短的通知有效期(例如，实时发送)，在该有效 期内满足事件通知规则时，可以向被通知方发送通知。
例如，根据针对订阅资源的通知的内容，可以将订阅模式分为附加信息订阅和预定信息订阅。例如，在预定信息订阅模式的情况下，针对某一商品，可以在满足事件通知规则时，向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息，该预定信息请求可以包含在订阅请求中。例如，在附加信息订阅模式的情况下，针对某一商品，可以在满足事件通知规则时，除了向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息外，还可以向被通知方发送与该商品类似的商品相关联的价格、材质、折扣等附加详细信息，该附加详细信息未包含在订阅请求中。
例如，根据针对订阅资源的通知的优先级，可以将订阅模式分为高优先订阅和低优先订阅。例如，相比于低优先订阅模式，在高优先订阅模式的情况下，可以在时间上先发送通知，或者发送多次通知以保证被通知方可以接收到该通知。
例如，根据针对订阅资源的通知的信息的数量，可以将订阅模式分为高频消息订阅和低频消息订阅。例如，在高频信息订阅模式的情况下，可以设置较短的最小通知时间间隔(例如，2小时)，在满足事件通知规则时，向被通知方发送通知，连续两次通知之间的时间不短于该最小通知时间间隔。例如，在低频信息订阅模式的情况下，可以设置较长的最小通知时间间隔(例如，24小时)，在满足事件通知规则时，向被通知方发送通知，连续两次通知之间的时间不短于该最小通知时间间隔。
继续参见图3，例如，在步骤S301中，可以针对第二实体的状态确定针对所述第二实体的订阅模式。第二实体的状态通过第二实体的属性进行判断，第二实体的属性包括对象属性(例如，第二实体对象为商品，对象属性为商品的信息，包括商品的数量、大小)、环境属性(例如第二实体周围的人、事、物、声音、光线等)。通过判断对象属性，可以根据对象属性的变化，及时对对象的变化进行调整，实现订阅模式的多样化,有利于快速根据环境变化作出调整，提升了效率；通过判断环境属性的变化，及时对对象的环境进行调整，实现订阅模式的多样化，有利于快速根据环境变化作出调整，提升了效率。
在一个示例中，第一实体为货架电子标签，与第一实体关联的第二实体为库存电子标签，第一实体和第二实体均针对同一商品A，第一实体包括商 品A的货架数量，第二实体包括商品A的库存数量，在第二实体显示商品A的库存数量为零的情况下，可以选择长期订阅(例如，可以将通知有效期设置为1个月，在该有效期内满足事件通知规则时，都可以向被通知方发送通知)；而在第二实体显示商品A的库存数量不为零的情况下，可以选择短期订阅(例如，例如，可以将通知有效期设置为1个星期，在满足事件通知规则时，向被通知方发送通知消息)。
在另一个示例中，针对某一商品，在库存有货的情况下，可以选择预定信息订阅(例如，可以在满足事件通知规则时，向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息)；而在库存无货的情况下，可以选择附加信息订阅(例如，除了向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息外，还可以向被通知方发送与该商品类似的商品相关联的价格、材质、折扣等附加详细信息)。
在一个示例中，可以同时使用多种订阅模式，第一实体为货架电子标签，与第一实体关联的第二实体为库存电子标签，第一实体和第二实体均针对同一商品A，第一实体包括商品A的货架数量，第二实体包括商品A的库存数量，在第二实体显示商品A的库存数量为零的情况下，可以选择长期订阅和低频订阅(例如，可以将通知有效期设置为1个月，在该有效期内满足事件通知规则时，对事件进行缓存和综合等处理，将处理后的事件向被通知方发送通知)，同时满足了长期订阅和低频订阅的要求；而在第二实体显示商品A的库存数量不为零的情况下，可以选择短期订阅和高频订阅(例如，例如，可以将通知有效期设置为1个星期，在满足事件通知规则时，不对事件进行处理，直接向被通知方发送通知消息)。
类似的，还可以选择高优先订阅(满足事件通知规则时优先发送通知)、低优先订阅(满足事件通知规则且无高优先级事件待发送时发送通知)、高频消息订阅(不对事件进行处理，满足时间通知规则则直接发送通知)以及低频消息订阅(对事件进行处理后发送通知，包括事件缓存、事件整合等)中的一个或多个。应该理解，上述订阅模式仅仅是示例，针对不同情况，可以选择长期订阅、短期订阅、附加信息订阅、预定信息订阅、高优先订阅、低优先订阅、高频消息订阅、低频消息订阅等中的一个或多个，还可以选择其他合适的订阅模式，在此不再赘述。
在确定了订阅模式后，接下来，在步骤S302中，根据所确定的订阅模式，生成对所述第二实体的订阅。
图4所示为根据本公开实施例的生成对第二实体的订阅的另一方法300的流程图。如图4所示，可以通过以下方式生成对对所述第二实体的订阅包括：基于所述第二实体的状态，确定针对所述第一实体和第二实体的订阅模式(S301)；根据所确定的订阅模式，生成对所述第一实体和第二实体的订阅(S302)。图4所述的订阅模式的选择与上述图3介绍到的订阅模式的选择类似，这里不再赘述。
在生成了对第二实体的订阅后，返回到图1，在步骤S104中，发送订阅响应，所述订阅响应用于指示所述订阅的结果。例如，可以向第三实体发送订阅响应，也可以向其他实体发送订阅响应，该订阅响应用于指示所述生成的订阅的结果。
例如，在创建对所述第二实体的订阅资源的情况下，所述订阅响应用于指示所述创建对所述第二实体的订阅资源的结果；在一些实施方式，在创建对所述第一实体和所述第二实体的订阅资源的情况下，所述订阅响应用于指示所述创建对所述第一实体和所述第二实体的订阅资源的结果。
在完成订阅的创建后，接下来，在满足该事件通知规则的情况下，基于确定的订阅模式，向被通知方发送事件通知，该事件通知规则包含在订阅请求中。
这里，订阅请求中可以包括多个被通知方，用于接收与该订阅请求相关的事件通知。当满足订阅方的事件通知规则时，通用服务实体将发送事件通知给该订阅请求中包括的所有被通知方。例如，在井盖被移动时，井盖移动传感器将感测到这一变化，并向通用服务实体发送更新数据，通用服务实体可以基于该井盖移动传感器的更新数据来确定是否满足事件通知规则，例如，订阅条件为井盖移动的情况下，此时，通用服务实体确定满足所述事件通知规则，并向请求订阅井盖移动的事件通知的订阅请求中包括的所有被通知方发送事件通知，即，通知所有被通知方井盖被移动的事件。
下面参照图5描述根据本公开实施例的用于订阅资源的另一方法400。该方法可以由应用实体(例如，上述第三实体AE3)执行。
如图5所示，在步骤S401中，发送对第一实体的订阅请求。在步骤S402中，接收针对所述订阅请求的订阅响应，其中，所述第二实体与所述第一实体 相关联，所述订阅响应用于指示生成至少对所述第二实体的订阅的结果。
例如，第一实体(AE1)可以是服务实体管理的、用于指示相应商品信息的虚拟电子标签。该虚拟电子标签通过商品的标识(ID)与相应商品相关联(或绑定到相应商品)。例如，该第一实体可以是虚拟的货架电子标签；该第三实体(AE3)可以是货架管理应用，也可以是虚拟的购物终端。例如，在该步骤中，AE3(例如，货架管理应用或购物终端)向通用服务实体发送对货架电子标签AE1的订阅请求。然后，AE3接收针对所述订阅请求的订阅响应，其中，所述第二实体与所述第一实体相关联，所述订阅响应用于指示生成至少对所述第二实体的订阅的结果。
这里，订阅请求中可以包含建立所述第一应用实体和所述第二应用实体之间的关联关系的关联规则。使得通用服务实体还可以基于所述订阅请求中包含的关联规则，确定与所述第一实体关联的第二实体。例如，该关联规则可以指示将与第一实体相关联的商品的类别相同的商品绑定的实体作为第二实体。
这里，订阅响应是基于所述第二应用实体的状态确定的针对所述订阅请求的订阅模式生成的。
例如，该订阅响应是通过以下方式形成的：基于所述第二实体的状态，确定针对所述第二实体的订阅模式；根据所确定的订阅模式，生成对所述第二实体的订阅，该订阅响应用于指示生成至少对第二实体的订阅的结果。
在一些实施方式，该订阅响应也可以通过以下方式形成：基于所述第二实体的状态，确定针对所述第一实体和第二实体的订阅模式；根据所确定的订阅模式，生成对所述第一实体和第二实体的订阅，该订阅响应用于指示生成对第一实体和第二实体的订阅的结果。生成订阅响应的方法与在图2中描述的方法相同，这里不再赘述。
接下来，在满足该事件通知规则的情况下，接收基于确定的订阅模式的事件通知。
下面，将结合图6-8详细描述根据本公开实施例的用于订阅资源的示例。图6是根据本公开第一示例的用于订阅资源方法的示意图，图7是根据本公开第二示例的用于订阅资源方法的示意图，图8是根据本公开第三示例的用于订阅资源方法的示意图。
物联网可以由通用服务实体和一系列的应用实体组成，所述通用服务实 体可以是零售服务器等，所述应用实体可以是各种传感器设备，也可以是诸如手机的用户终端，还可以是设备中的软件模块等，诸如手机应用程序等。所述通用服务实体对于其连接的应用实体进行管理，并进行诸如注册、数据传输、执行任务等的操作。
第一示例
图6所示为根据本公开的用于订阅资源的第一示例。在该示例中，例如，由商场或超市的货架管理应用实体发起订阅，以及时调整商场或超市的货物状态。
如图6所示，例如，零售服务器CSE 53(服务实体)接收来自货架电子标签AE1 51(第一实体)、库存电子标签AE2 52(第二实体)以及作为订阅方的货架管理应用AE3 54(第三实体)的注册请求，由此建立与货架电子标签AE1 51、库存电子标签AE2 52以及货架管理应用AE3 54的关联关系，并随着货架电子标签AE1 51、库存电子标签AE2 52以及货架管理应用AE3 54的状态变化更新他们的状态55。接下来，零售服务器CSE 53判断与货架电子标签AE1 51相关联的商品和与库存电子标签AE2 52相关联的商品是否针对于同一类商品56，如果是，则建立货架电子标签AE1 51与库存电子标签AE252之间的关联57。
在货架管理应用AE3 54向零售服务器CSE 53发出对货架电子标签AE151的订阅请求59的情况下，零售服务器CSE 53首先判断货架电子标签AE151是否存在关联对象库存电子标签AE2 52(图6中标号为60)。如果货架电子标签AE1 51存在关联对象库存电子标签AE2 52，则零售服务器CSE 53可以创建对库存电子标签AE2 52的订阅资源，并向零售服务器CSE 53(或其他实体)发送订阅响应62，该订阅响应指示生成对库存电子标签AE2 52的订阅的结果；在一些实施方式，零售服务器CSE 53还可以创建对货架电子标签AE1 51和库存电子标签AE2 52的订阅资源，并向零售服务器CSE 53(或其他实体)发送订阅响应62，该订阅响应指示生成对货架电子标签AE1 51与库存电子标签AE2 52的订阅的结果。
进一步，在零售服务器CSE 53创建对库存电子标签AE2 52的订阅资源时，可以根据库存电子标签AE2 52的状态，确定针对库存电子标签AE2 52的订阅模式61。例如，如上所述，如果库存电子标签AE2显示有货，则可以建立短期类订阅，如果库存电子标签AE2显示无货，则可以建立长期类订阅。
在一些实施方式，在零售服务器CSE 53创建对货架电子标签AE1 51与库存电子标签AE2 52的订阅资源时，可以根据库存电子标签AE2 52的状态，确定针对货架电子标签AE1 51与库存电子标签AE2 52的订阅模式61。例如，如上所述，如果库存电子标签AE2显示有货，则可以建立短期类订阅，如果库存电子标签AE2显示无货，则可以建立长期类订阅。
接下来，零售服务器CSE 53更新货架电子标签AE1 51的状态63。随后，在满足事件通知规则64的情况下，根据上述确定的订阅模式，向被通知方(例如，货架管理应用AE3 54)发送事件通知65。
第二示例
图7所示为根据本公开的用于订阅资源的第二示例。在该示例中，例如，由购物终端(例如，用户)发起订阅，以及时了解期望购买的商品的状态。
如图7所示，例如，零售服务器CSE 53(服务实体)接收来自货架电子标签AE1 51(第一实体)、库存电子标签AE2 52(第二实体)以及作为订阅方的购物终端AE3 66(第三实体)的注册请求，由此建立与货架电子标签AE151、库存电子标签AE2 52以及购物终端AE3 66的关联关系，并随着货架电子标签AE1 51、库存电子标签AE2 52以及购物终端AE3 66的状态变化更新他们的状态。接下来，与图6类似，零售服务器CSE 53判断与货架电子标签AE1 51相关联的商品和与库存电子标签AE2 52相关联的商品是否针对同一类商品，如果是，则建立货架电子标签AE1 51与库存电子标签AE2 52之间的关联。
在购物终端AE3 66向零售服务器CSE 53发出对货架电子标签AE1 51的订阅请求的情况下，零售服务器CSE 53首先判断货架电子标签AE1 51是否存在关联对象库存电子标签AE2 52。如果货架电子标签AE1 51存在关联对象库存电子标签AE2 52，则零售服务器CSE 53可以创建对库存电子标签AE2 52的订阅资源，并向购物终端AE3 66(或其他实体)发送订阅响应，该订阅响应指示生成对库存电子标签AE2 52的订阅的结果；在一些实施方式，零售服务器CSE 53还可以创建对货架电子标签AE1 51和库存电子标签AE252的订阅资源，并向购物终端AE3 66(或其他实体)发送订阅响应，该订阅响应指示生成对货架电子标签AE1 51与库存电子标签AE2 52的订阅的结果。
进一步，在零售服务器CSE 53创建对库存电子标签AE2 52的订阅资源时，可以根据库存电子标签AE2 52的状态，确定针对库存电子标签AE2 52 的订阅模式。例如，如果库存电子标签AE2显示有货，则可以建立短期类订阅，如果库存电子标签AE2显示无货，则可以建立长期类订阅。
在一些实施方式，在零售服务器CSE 53创建对货架电子标签AE1 51与库存电子标签AE2 52的订阅资源时，可以根据库存电子标签AE2 52的状态，确定针对货架电子标签AE1 51与库存电子标签AE2 52的订阅模式。例如，如上所述，如果库存电子标签AE2显示有货，则可以建立短期类订阅，如果库存电子标签AE2显示无货，则可以建立长期类订阅。
接下来，零售服务器CSE 53更新货架电子标签AE1 51的状态63。随后，在满足该事件通知规则的情况下，根据上述确定的订阅模式，向被通知方(例如，购物终端AE3 66)发送事件通知。
第三示例
图8所示为根据本公开的用于订阅资源的第三示例。在该示例中，例如，可以在应用实体发送的订阅请求中包含关联规则，然后由通用服务实体根据该关联规则建立不同对象之间的关联。
如图8所示，例如，零售服务器CSE 53(服务实体)接收来自货架电子标签AE1 51(第一实体)、库存电子标签AE2 52(第二实体)以及作为订阅方的购物终端AE3 66(第三实体)的注册请求，由此建立与货架电子标签AE151、库存电子标签AE2 52以及购物终端AE3 66的关联关系，并随着货架电子标签AE1 51、库存电子标签AE2 52以及购物终端AE3 66的状态变化更新他们的状态。
接下来，在购物终端AE3 66向零售服务器CSE 53发出对货架电子标签AE1 51的订阅请求71的情况下，零售服务器CSE 53根据订阅请求中包含的关联规则建立货架电子标签AE1 51与库存电子标签AE2 52之间的关联。接下来，零售服务器CSE 53可以创建对库存电子标签AE2 52的订阅资源，并向购物终端AE3 66(或向其他实体)发送订阅响应，该订阅响应指示生成对库存电子标签AE2 52的订阅的结果；在一些实施方式，零售服务器CSE 53还可以创建对货架电子标签AE1 51和库存电子标签AE2 52的订阅资源，并向购物终端AE3 66(或其他实体)发送订阅响应，该订阅响应指示生成对货架电子标签AE1 51与库存电子标签AE2 52的订阅的结果。
进一步，在零售服务器CSE 53创建对库存电子标签AE2 52的订阅资源时，可以根据库存电子标签AE2 52的状态，确定针对库存电子标签AE2 52 的订阅模式。例如，如上所述，如果库存电子标签AE2显示有货，则可以建立短期类订阅，如果库存电子标签AE2显示无货，则可以建立长期类订阅。
在一些实施方式，在零售服务器CSE 53创建对货架电子标签AE1 51与库存电子标签AE2 52的订阅资源时，可以根据库存电子标签AE2 52的状态，确定针对货架电子标签AE1 51与库存电子标签AE2 52的订阅模式。例如，如上所述，如果库存电子标签AE2显示有货，则可以建立短期类订阅，如果库存电子标签AE2显示无货，则可以建立长期类订阅。
接下来，零售服务器CSE 53更新货架电子标签AE1 51的状态。随后，在满足事件通知规则的情况下，根据上述确定的订阅模式，向被通知方(例如，购物终端AE3 66)发送事件通知。
可以看出，通过上述用于订阅资源的方法，可以实现对与第一实体关联的第二实体的订阅，从而使得订阅的资源更加丰富。此外，可以针对第二实体的状态创建不同的订阅模式，从而实现不同情况下模式的多样化。
下面，参照图9描述根据本公开实施例的用于订阅资源的装置1000。图9是根据本公开实施例的用于订阅资源的装置1000的示意图。由于本实施例的用于订阅资源的装置的功能与在上文中参照图1描述的方法的细节相同，因此在这里为了简单起见，省略对相同内容的详细描述。
如图9所示，根据本公开实施例的用于订阅资源的装置1000包括接收单元1001、确定单元1002、生成单元1003以及发送单元1004。需要注意的是，尽管在图9中用于订阅资源的装置1000被示出为只包括4个单元，但这只是示意性的，用于订阅资源的装置1000也可以包括一个或多个其他单元，这些单元与发明构思无关，因此在这里被省略。
接收单元1001使服务实体接收第三实体对第一实体的订阅请求。
例如，第一实体(AE1)可以是货架电子标签；该第三实体(AE3)可以是货架管理应用，也可以是购物终端。例如，在该步骤中，通用服务实体接收AE3(货架管理应用或购物终端)对货架电子标签AE1的订阅请求。
接下来，确定单元1002确定与所述第一实体关联的第二实体。
例如，第二实体(AE2)可以是库存电子标签。例如，在该步骤中，确定单元1002可以判断与货架电子标签关联的库存电子标签。
例如，确定单元1002可以通过判断第一实体和第二实体是否针对同一对象来确定与第一实体关联的第二实体。例如，如果第一实体和第二实体针对同 一对象，则确定第二实体与第一实体相关联；如果第一实体和第二实体针对不同对象，则确定第二实体不与第一实体相关联。
在一些实施方式，确定单元1002还可以基于所述订阅请求中包含的关联规则，确定与所述第一实体关联的第二实体。
例如，该关联规则可以包含在接收单元1001接收的购物终端发送的订阅请求中。例如，该关联规则可以指示将与第一实体相关联的商品的类别相同的商品绑定的实体作为第二实体。然后通用服务实体可以根据该关联规则确定与第一实体关联的第二实体。
在确定单元1002确定了与所述第一实体关联的第二实体后，接下来，生成单元1003生成至少对所述第二实体的订阅。这里，生成对所述第二实体的订阅包括两种方法中的一个：(1)创建对所述第二实体的订阅资源；(2)创建对所述第一实体和所述第二实体的订阅资源。
图3为根据本公开实施例的生成对第二实体的订阅的一种方法200的流程图，图4为根据本公开实施例的生成对第二实体的订阅的另一方法200的流程图。下面参照图3-4描述生成单元1003生成对所述第二实体的订阅。
图3所示为根据本公开实施例的生成对第二实体的订阅的方法200的流程图。如图3所示，可以通过以下方式生成对所述第二实体的订阅包括：基于所述第二实体的状态，确定针对所述第二实体的订阅模式(S301)；根据所确定的订阅模式，生成对所述第二实体的订阅(S302)。
例如，在第二实体是零售领域下的虚拟电子标签的情况下，该第二实体的状态可以分类为有货和无货两种状态。应当认识到，第二实体的状态不限于此，可以根据情况将第二实体分类为任何适当的状态，这里不做限制。例如，订阅模式包括长期订阅、短期订阅、附加信息订阅、预定信息订阅、高优先订阅、低优先订阅、高频消息订阅、低频消息订阅等。不同订阅模式下的消息优先级、订阅资源的有效期、通知内容、通知消息的数量等的一个或多个不同。可以针对不同的情况(例如，第二实体的状态)选择不同的订阅模式，从而提升用户体验。接下来详细介绍各个不同的订阅模式。
例如，根据对订阅资源保留的通知有效期的长短，可以将订阅模式分为长期订阅和短期订阅，长期订阅的通知有效期比短期订阅更长。例如，在长期订阅模式的情况下，可以设置较长的通知有效期(例如，1个月)，在该有效期内满足事件通知规则时，都可以向被通知方发送通知。然而，例如在短期订 阅模式的情况下，可以设置较短的通知有效期(例如，实时发送)，在该有效期内满足事件通知规则时，可以向被通知方发送通知。
例如，根据针对订阅资源的通知的内容，可以将订阅模式分为附加信息订阅和预定信息订阅。例如，在预定信息订阅模式的情况下，针对某一商品，可以在满足事件通知规则时，向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息，该预定信息请求可以包含在订阅请求中。例如，在附加信息订阅模式的情况下，针对某一商品，可以在满足事件通知规则时，除了向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息外，还可以向被通知方发送与该商品类似的商品相关联的价格、材质、折扣等附加详细信息，该附加详细信息未包含在订阅请求中。
例如，根据针对订阅资源的通知的优先级，可以将订阅模式分为高优先订阅和低优先订阅。例如，相比于低优先订阅模式，在高优先订阅模式的情况下，可以在时间上先发送通知，或者发送多次通知以保证被通知方可以接收到该通知。
例如，根据针对订阅资源的通知的信息的数量，可以将订阅模式分为高频消息订阅和低频消息订阅。例如，在高频信息订阅模式的情况下，可以设置较短的最小通知时间间隔(例如，2小时)，在满足事件通知规则时，向被通知方发送通知，连续两次通知之间的时间不短于该最小通知时间间隔。例如，在低频信息订阅模式的情况下，可以设置较长的最小通知时间间隔(例如，24小时)，在满足事件通知规则时，向被通知方发送通知，连续两次通知之间的时间不短于该最小通知时间间隔。
继续参见图3，例如，在步骤S301中，可以针对第二实体的状态(例如，有货或无货的状态)，确定针对所述第二实体的订阅模式。
在一个示例中，针对某一商品，在库存无货的情况下，可以选择长期订阅(例如，可以将通知有效期设置为1个月，在该有效期内满足事件通知规则时，都可以向被通知方发送通知)；而在库存有货的情况下，可以选择短期订阅(例如，在满足事件通知规则时，实时发送通知消息)。
在另一个示例中，针对某一商品，在库存有货的情况下，可以选择预定信息订阅(例如，可以在满足事件通知规则时，向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息)；而在库存无 货的情况下，可以选择附加信息订阅(例如，除了向被通知方发送针对预定信息请求的、与该商品相关联的价格、材质、折扣等详细预定信息外，还可以向被通知方发送与该商品类似的商品相关联的价格、材质、折扣等附加详细信息)。
类似的，还可以选择高优先订阅、低优先订阅、高频消息订阅以及低频消息订阅中的一个或多个。应该理解，上述订阅模式仅仅是示例，针对不同情况，可以选择长期订阅、短期订阅、附加信息订阅、预定信息订阅、高优先订阅、低优先订阅、高频消息订阅、低频消息订阅等中的一个或多个，还可以选择其他合适的订阅模式，在此不再赘述。
在确定了订阅模式后，接下来，在步骤S302中，根据所确定的订阅模式，生成单元1003生成对所述第二实体的订阅。
图4所示为根据本公开实施例的生成对第二实体的订阅的另一方法300的流程图。如图4所示，可以通过以下方式生成对对所述第二实体的订阅包括：基于所述第二实体的状态，确定针对所述第一实体和第二实体的订阅模式(S301)；根据所确定的订阅模式，生成对所述第一实体和第二实体的订阅(S302)。图4所述的订阅模式的选择与上述图3介绍到的订阅模式的选择类似，这里不再赘述。
在生成单元1003生成了对第二实体的订阅后，发送单元1004发送订阅响应，所述订阅响应用于指示所述订阅的结果。例如，可以向第三实体发送订阅响应，也可以向其他实体发送订阅响应，该订阅响应用于指示所述生成的订阅的结果。
例如，在创建对所述第二实体的订阅资源的情况下，所述订阅响应用于指示所述创建对所述第二实体的订阅资源的结果；在一些实施方式，在创建对所述第一实体和所述第二实体的订阅资源的情况下，所述订阅响应用于指示所述创建对所述第一实体和所述第二实体的订阅资源的结果。
在完成订阅的创建后，接下来，在满足该事件通知规则的情况下，基于确定的订阅模式，向被通知方发送事件通知，该事件通知规则包含在订阅请求中。
这里，订阅请求中可以包括多个被通知方，用于接收与该订阅请求相关的事件通知。当满足订阅方的事件通知规则时，通用服务实体将发送事件通知给该订阅请求中包括的所有被通知方。例如，在井盖被移动时，井盖移动传感器 将感测到这一变化，并向通用服务实体发送更新数据，通用服务实体可以基于该井盖移动传感器的更新数据来确定是否满足事件通知规则，例如，订阅条件为井盖移动的情况下，此时，通用服务实体确定满足所述事件通知规则，并向请求订阅井盖移动的事件通知的订阅请求中包括的所有被通知方发送事件通知，即，通知所有被通知方井盖被移动的事件。
下面，参照图10描述根据本公开实施例的用于订阅资源1100的设备。图10是根据本公开实施例的用于订阅资源的设备1100的示意图。由于本实施例的用于订阅资源的设备的功能与在上文中参照图1描述的方法的细节相同，因此在这里为了简单起见，省略对相同内容的详细描述。
如图10所示，用于订阅资源的设备1100包括存储器1101和处理器1102。需要注意的是，尽管在图10中用于订阅资源的设备1100被示出为只包括2个设备，但这只是示意性的，用于订阅资源的设备1100也可以包括一个或多个其他设备，这些设备与发明构思无关，因此在这里被省略。
本公开的用于订阅资源的设备，包括：存储器1101，配置为存储计算机可读指令；以及处理器1102，配置为运行存储在所述存储器中的所述计算机可读指令，其中，所述处理器运行所述计算机可读指令时执行以下步骤：服务实体接收第三实体对第一实体的订阅请求；确定与所述第一实体关联的第二实体；生成至少对所述第二实体的订阅；发送订阅响应，所述订阅响应用于指示所述订阅的结果。
图11是根据本公开实施例的计算机可读存储介质的示意图。
如图11所示，本公开还包括一种计算机可读存储介质，其上存储计算机可读指令，当所述计算机可读指令由计算机执行时，所述计算机执行用于订阅资源的方法，所述方法包括：服务实体接收第三实体对第一实体的订阅请求；确定与所述第一实体关联的第二实体；生成至少对所述第二实体的订阅；发送订阅响应，所述订阅响应用于指示所述生成对所述订阅的结果。
本领域技术人员可以理解，本申请的各方面可以通过若干具有可专利性的种类或情况进行说明和描述，包括任何新的和有用的工序、机器、产品或物质的组合，或对他们的任何新的和有用的改进。相应地，本申请的各个方面可以完全由硬件执行、可以完全由软件(包括固件、常驻软件、微码等)执行、也可以由硬件和软件组合执行。以上硬件或软件均可被称为“数据块”、“模块”、“引擎”、“单元”、“组件”或“系统”。此外，本申请的各方面可能表现 为位于一个或多个计算机可读介质中的计算机产品，该产品包括计算机可读程序编码。
本申请使用了特定词语来描述本申请的实施例。如“一个实施例”、“一实施例”、和/或“一些实施例”意指与本申请至少一个实施例相关的某一特征、结构或特点。因此，应强调并注意的是，本说明书中在不同位置两次或多次提及的“一实施例”或“一个实施例”或“一替代性实施例”并不一定是指同一实施例。此外，本申请的一个或多个实施例中的某些特征、结构或特点可以进行适当的组合。
除非另有定义，这里使用的所有术语(包括技术和科学术语)具有与本公开所属领域的普通技术人员共同理解的相同含义。还应当理解，诸如在通常字典里定义的那些术语应当被解释为具有与它们在相关技术的上下文中的含义相一致的含义，而不应用理想化或极度形式化的意义来解释，除非这里明确地这样定义。
以上是对本公开的说明，而不应被认为是对其的限制。尽管描述了本公开的若干示例性实施例，但本领域技术人员将容易地理解，在不背离本公开的新颖教学和优点的前提下可以对示例性实施例进行许多修改。因此，所有这些修改都意图包含在权利要求书所限定的本公开范围内。应当理解，上面是对本公开的说明，而不应被认为是限于所公开的特定实施例，并且对所公开的实施例以及其他实施例的修改意图包含在所附权利要求书的范围内。本公开由权利要求书及其等效物限定。

Claims (20)

  1. 一种用于物联网领域的订阅资源的方法，包括：
    服务实体接收第三实体对第一实体的订阅请求；
    服务实体确定与所述第一实体关联的第二实体；
    服务实体生成至少对所述第二实体的订阅；
    服务实体发送订阅响应，所述订阅响应用于指示所述订阅的结果。
  2. 根据权利要求1所述的方法，其中，
    所述生成至少对所述第二实体的订阅包括：
    创建对所述第二实体的订阅资源；
    所述订阅响应用于指示所述订阅的结果包括：
    所述订阅响应用于指示所述创建对所述第二实体的订阅资源的结果。
  3. 根据权利要求1所述的方法，其中，所述生成至少对所述第二实体的订阅包括：生成对所述第一实体和所述第二实体的订阅。
  4. 根据权利要求3所述的方法，其中，
    生成对所述第一实体和所述第二实体的订阅包括：
    创建对所述第一实体和所述第二实体的订阅资源；
    所述订阅响应用于指示所述订阅的结果包括：
    所述订阅响应用于指示所述创建对所述第一实体和所述第二实体的订阅资源的结果。
  5. 根据权利要求1所述的方法，所述生成至少对所述第二实体的订阅包括：
    基于所述第二实体的状态，确定针对所述第二实体的订阅模式；
    根据所确定的订阅模式，生成对所述第二实体的订阅。
  6. 根据权利要求3所述的方法，所述生成对所述第一实体和所述第二实体的订阅包括：
    基于所述第二实体的状态，确定针对所述第一实体和第二实体的订阅模式；
    根据所确定的订阅模式，生成对所述第一实体和第二实体的订阅。
  7. 根据权利要求1所述的方法，其中，所述确定与所述第一实体关联的第二实体包括：
    判断所述第一实体和所述第二实体是否针对同一对象，
    如果所述第一实体和所述第二实体针对同一对象，则确定所述第二实体与所述第一实体相关联。
  8. 根据权利要求1所述的方法，其中，所述确定与所述第一实体关联的第二实体包括：
    判断所述第一实体和所述第二实体是否属于同一组；或，
    判断所述第一实体的关联属性是否包括第二实体；或，
    判断所述第二实体的关联属性是否包括第一实体。
  9. 根据权利要求1所述的方法，其中，所述确定与所述第一实体关联的第二实体包括：
    基于所述订阅请求中包含的关联规则，确定与所述第一实体关联的第二实体。
  10. 根据权利要求9所述的方法，其中，
    所述关联规则指示将与第一实体相关联的商品的类别相同的商品绑定的实体作为所述第二实体。
  11. 根据权利要求5所述的方法，其中，
    所述订阅模式包括长期订阅、短期订阅、附加信息订阅、预定信息订阅、高优先订阅、低优先订阅、高频消息订阅、低频消息订阅中的一个或多个。
  12. 一种用于物联网订阅资源的方法，包括：
    发送对第一实体的订阅请求；
    接收针对所述订阅请求的订阅响应，
    其中，所述第一实体与第二实体相关联，所述订阅响应用于指示生成至少对所述第二实体的订阅的结果。
  13. 根据权利要求12所述的方法，所述订阅响应用于指示生成至少对所述第二实体的订阅的结果包括：
    所述订阅响应用于指示生成对所述第一实体和所述第二实体的订阅的结果。
  14. 根据权利要求12所述的方法，其中，
    所述订阅请求中包含关联规则，所述关联规则用于确定与所述第一实体关联的第二实体。
  15. 根据权利要求14所述的方法，其中，
    所述关联规则指示将与第一实体相关联的商品的类别相同的商品绑定的实体作为所述第二实体。
  16. 一种用于物联网订阅资源的装置，包括：
    接收单元，用于使服务实体接收第三实体对第一实体的订阅请求；
    确定单元，用于确定与所述第一实体关联的第二实体；
    生成单元，用于生成至少对所述第二实体的订阅；
    发送单元，用于发送订阅响应，所述订阅响应用于指示所述订阅的结果。
  17. 根据权利要求16所述的装置，其中，
    所述生成单元生成对所述第一实体和所述第二实体的订阅。
  18. 根据权利要求16所述的装置，其中，
    所述生成单元基于所述第二实体的状态，确定针对所述第二实体的订阅模式；
    根据所确定的订阅模式，生成对所述第二实体的订阅。
  19. 一种用于物联网订阅资源的设备，包括：
    存储器，配置为存储计算机可读指令；以及
    处理器，配置为运行存储在所述存储器中的所述计算机可读指令，
    其中，所述处理器运行所述计算机可读指令时执行以下步骤：
    服务实体接收第三实体对第一实体的订阅请求；
    确定与所述第一实体关联的第二实体；
    生成至少对所述第二实体的订阅；
    发送订阅响应，所述订阅响应用于指示所述订阅的结果。
  20. 一种计算机可读存储介质，其上存储计算机可读指令，当所述计算机可读指令由计算机执行时，所述计算机执行用于物联网订阅资源的方法，所述方法包括：
    服务实体接收第三实体对第一实体的订阅请求；
    确定与所述第一实体关联的第二实体；
    生成至少对所述第二实体的订阅；
    发送订阅响应，所述订阅响应用于指示所述订阅的结果。
PCT/CN2020/091525 2019-05-23 2020-05-21 物联网领域的订阅资源的方法、装置、设备和存储介质 WO2020233658A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20810267.3A EP3975598A4 (en) 2019-05-23 2020-05-21 METHOD, APPARATUS AND DEVICE FOR SUBSCRIBING TO RESOURCES IN THE FIELD OF THE INTERNET OF THINGS, AND STORAGE MEDIUM
KR1020217041695A KR20220011687A (ko) 2019-05-23 2020-05-21 사물 인터넷 분야에서 리소스들을 구독하기 위한 방법, 장치 및 디바이스, 및 저장 매체
JP2021569527A JP2022534064A (ja) 2019-05-23 2020-05-21 モノのインターネット分野においてリソースを購読する方法、装置、デバイス及び記憶媒体
US17/611,923 US20220256007A1 (en) 2019-05-23 2020-05-21 Method, apparatus, and device for subscribing resources in field of internet of things, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910433275.7 2019-05-23
CN201910433275.7A CN111984895A (zh) 2019-05-23 2019-05-23 用于订阅资源的方法、装置、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2020233658A1 true WO2020233658A1 (zh) 2020-11-26

Family

ID=73437375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/091525 WO2020233658A1 (zh) 2019-05-23 2020-05-21 物联网领域的订阅资源的方法、装置、设备和存储介质

Country Status (6)

Country Link
US (1) US20220256007A1 (zh)
EP (1) EP3975598A4 (zh)
JP (1) JP2022534064A (zh)
KR (1) KR20220011687A (zh)
CN (1) CN111984895A (zh)
WO (1) WO2020233658A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114791860A (zh) * 2021-01-26 2022-07-26 京东方科技集团股份有限公司 一种新型订阅应用的方法、设备和介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1663216A (zh) * 2002-06-14 2005-08-31 诺基亚公司 使用sip协议的事件订阅方法与系统
CN101742475A (zh) * 2008-11-12 2010-06-16 华为技术有限公司 订阅和通知的方法、装置和系统
CN106327114A (zh) * 2015-06-25 2017-01-11 阿里巴巴集团控股有限公司 仓库资源信息处理、提供库存信息的方法及装置
US20170134523A1 (en) * 2014-06-13 2017-05-11 Zte Corporation Resource Subscription Processing Method and Device
CN106973118A (zh) * 2017-05-12 2017-07-21 京东方科技集团股份有限公司 生成和订阅通知的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9330190B2 (en) * 2006-12-11 2016-05-03 Swift Creek Systems, Llc Method and system for providing data handling information for use by a publish/subscribe client
CN103227803A (zh) * 2012-01-30 2013-07-31 华为技术有限公司 一种物联网资源获取的方法、客户端和物联网资源装置
US10708341B2 (en) * 2013-05-21 2020-07-07 Convida Wireless, Llc Lightweight IoT information model
CN109495524B (zh) * 2017-09-11 2022-03-04 华为云计算技术有限公司 一种物联网资源订阅的方法、设备和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1663216A (zh) * 2002-06-14 2005-08-31 诺基亚公司 使用sip协议的事件订阅方法与系统
CN101742475A (zh) * 2008-11-12 2010-06-16 华为技术有限公司 订阅和通知的方法、装置和系统
US20170134523A1 (en) * 2014-06-13 2017-05-11 Zte Corporation Resource Subscription Processing Method and Device
CN106327114A (zh) * 2015-06-25 2017-01-11 阿里巴巴集团控股有限公司 仓库资源信息处理、提供库存信息的方法及装置
CN106973118A (zh) * 2017-05-12 2017-07-21 京东方科技集团股份有限公司 生成和订阅通知的方法和装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP3975598A4 (en) 2023-07-19
JP2022534064A (ja) 2022-07-27
US20220256007A1 (en) 2022-08-11
EP3975598A1 (en) 2022-03-30
KR20220011687A (ko) 2022-01-28
CN111984895A (zh) 2020-11-24

Similar Documents

Publication Publication Date Title
US20230015178A1 (en) Techniques for messaging bot rich communication
JP6815382B2 (ja) デバイスクラウドの管理
AU2016301394B2 (en) Managing a device cloud
US7512653B2 (en) System and method for dynamically grouping messaging buddies in an electronic network
EP3493485B1 (en) Method, apparatus and system for notification
US20150006296A1 (en) NOTIFICATION DISMISSAL IN AN INTERNET OF THINGS (IoT) ENVIRONMENT
CN108337279A (zh) 一种智能设备的控制方法及装置
WO2020112793A2 (en) Framework for dynamic brokerage and management of topics and data at the service layer
JP7412490B2 (ja) メッセージと対応するタスクを生成、処理、管理するコンピュータプログラム、及び電子機器
WO2018197271A1 (en) Geo-location fences-based transient messages
US10394629B2 (en) Managing a plug-in application recipe via an interface
CN107968805B (zh) 一种事件通知方法及服务器
WO2020237548A1 (zh) 资源订阅方法、设备、服务器以及计算机存储介质
WO2016065842A1 (zh) M2m群组及其通告资源创建、信息交互方法和存储介质
WO2020233658A1 (zh) 物联网领域的订阅资源的方法、装置、设备和存储介质
EP2686981B1 (en) Method and system for managing contact information in a universal plug and play home network environment
CN111262893B (zh) 用于事件通知的方法、服务器设备、事件通知装置、介质
US20180019959A1 (en) Communication system with hidden content and method thereof
CN113315689A (zh) 信息处理方法、系统、电子设备和可读存储介质
CN110520878A (zh) 有组织的可编程内部网推送通知
WO2021143834A1 (zh) 群组更新方法、消息发送方法及装置
US10735355B1 (en) Intelligent determination of whether to initiate a communication session for a user based on proximity to client device
US8473599B2 (en) Communication network list management sending updated member data from a provisioning system to a list manager and then to an application server
KR20230174908A (ko) K-콘텐츠 크라우드 펀딩 플랫폼
CN115359791A (zh) 一种智慧家庭系统及控制方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20810267

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021569527

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217041695

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020810267

Country of ref document: EP

Effective date: 20211223