WO2021102643A1

WO2021102643A1 - Method and apparatus for notification of member update in collection resource

Info

Publication number: WO2021102643A1
Application number: PCT/CN2019/120680
Authority: WO
Inventors: 吕小强
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-11-25
Filing date: 2019-11-25
Publication date: 2021-06-03
Also published as: CN113994643B; CN113994643A

Abstract

Provided in some embodiments of the present application is a method for the notification of a member update in a collection resource. The method comprises: detecting whether there is member update in a collection resource (301); if so, recording an updated member in a member update resource (302); and sending a member update notification message to a subscription device subscribing to a member update notification (303). By means of the method, a subscription device can determine, by initiating one type of subscription to a target collection resource by means of only one interface, the changed content and the content after the change of the collection resource, so as to save system resources. Moreover, the subscription target device also does not need to maintain more subscription relationships, thereby simplifying the processing flow.

Description

Method and device for notifying update of collective resource members

Technical field

This application relates to the technical field of the Internet of Things, and in particular to a notification technology for member updates of collective resources.

Background technique

There is a subscription technology in the Internet of Things technology. The subscription device can subscribe to a specific resource or function of the target device, and the above resources can be called target resources. When the target resource changes, it will actively notify the subscribing device. For example, the mobile phone subscribes to the onoff state of the smart door at home. When the state of the smart door changes from off (onoff=0) to open (onoff=1), the smart door will actively send a notification message to the mobile phone, in the notification message Including the current state of the smart door is on (onoff = 1).

In addition to monitoring changes in a specific value of the subscription target device (such as whether the state of the light is on or off), the subscription technology can also be used to detect changes in specific resource members. When the members included in the target resource change, it will also actively notify the subscribing device. In other words, there is also a kind of resource, which can be called a collective resource. A collective resource can contain multiple resources, and the contained resource is called a member of the collective resource. For example, a collective resource can be generated, and smart devices such as smart doors, refrigerators, air conditioners, and lights in the home can be used as members of the collective resource. If you need to know the change of the collection resource, such as adding a new member or deleting a member, you need to initiate a subscription request for the collection resource member update to the subscription target device. The subscription target device receives the subscription device’s collection resource member update After the subscription request is made, if a change in the collection resource is detected, a notification message is sent to the subscription device, and the notification message carries the changed collection resource.

The inventor found that the related technology has at least the following problems: Because the notification message for the member update of the collective resource includes the current member of the collective resource, that is, the member after the change. Therefore, the subscribing device needs to subscribe to multiple information at the same time, such as subscribing to the notification of adding members, subscribing to the notification of deleting members, etc., resulting in the need to receive two notification messages when the members change, such as the notification message of member update subscription and the increase The notification message of the member can determine the changed content and the changed content of the collection resource.

Summary of the invention

A technical problem to be solved by some embodiments of this application is that the subscription device can determine the changed content and the changed content of the collection resource through a notification message updated by a member, saving system resources, and subscribing to the target device can also be There is no need to maintain more subscription relationships, which simplifies the processing flow.

An embodiment of the present application provides a method for notifying member updates of a collective resource. The method includes: if a member update is detected in the collective resource, recording the updated member of the collective resource in a first resource in the collective resource; Send a member update notification message to the subscribing device subscribed to the member update notification, where the notification message includes the first resource.

An embodiment of the present application also provides a device for notifying member updates of collective resources. The device includes: a recording module configured to record the updated information in the first resource in the collective resource after the member update is detected in the collective resource. A member in a collective resource; a sending module, used to send a member update notification message to a subscription device subscribed to a member update notification, the notification message including the first resource.

An embodiment of the present application further provides an electronic device, including: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores one or more programs that can be executed by the at least one processor ; One or more programs contain instructions that, when executed by at least one processor, cause at least one processor to execute the aforementioned method for notifying member updates of collective resources.

An embodiment of the present application also provides a non-volatile computer storage medium that stores a program that can be executed by a processor. When the program is executed by the processor, the aforementioned method for notifying the update of collective resource members is implemented.

For the prior art, the embodiment of this application now creates a resource dedicated to recording member changes for the collection resource in advance, that is, the first resource. Therefore, as long as the subscription device completes the subscription for member update, it will subscribe after the member update occurs. The target device will send a notification message of the updated collection resource to the subscribing device, and the first resource, as one of the members of the collection resource, will be carried in the notification message of the member update subscription, so that the subscribing device can only send a subscription request message You can get all the information in the notification message, such as the updated collection resource and the changes in the collection resource. At the same time, the subscription target device does not need to maintain more subscription relationships, which simplifies the processing flow.

In addition, the structure of the first resource includes: a first field for recording the modification mode, and a second field for recording the modified member; the updated member is recorded in the first resource in the collection resource, including: In one field, the modification mode of the modified member in the collective resource is recorded; in the second field, the identifier of the modified member in the collective resource is recorded. Through the modification of the first field record, the second field records the identifier of the modified member, so that the first resource can accurately and effectively record the changes in the collection resource.

In addition, recording the modification method of the modified member in the collection resource in the first field includes: recording the creation interface in the first field, which is used to indicate that the modification method of the modified member is member addition; or, in the first field In the record delete interface, it is used to indicate that the modification method of the modified member is member deletion; or, the record link addition interface in the first field is used to indicate that the modification method of the modified member is member link addition; or, in The link deletion interface is recorded in the first field, which is used to indicate that the modification method of the modified member is member link deletion.

In addition, the second field is an array, and the identifier of the modified member is recorded through an array, so that a notification message can carry multiple modified member information.

In addition, the creation of the first resource is triggered after receiving the subscription request of the subscription device.

In addition, the creation of the first resource is triggered after the collective resource is generated and it is determined that the collective resource is a collective resource that allows subscription.

In addition, the following methods are used to detect whether the collective resource has a member update: if it is detected that the collective resource is modified by any of the following interfaces, it is determined that the collective resource has a member update: the creation interface for creating new members, The delete interface for deleting members, the link addition interface for adding member links, and the link deletion interface for deleting member links. Since the members of the collection resource can be modified by creating an interface, deleting an interface, linking a new interface, and linking a delete interface, when it is detected that the collection resource is modified by any one of the interfaces, it is determined that there is a member update for the collection resource. In order to ensure that the first resource resource can record the changes of the collective resource in a timely and accurate manner.

Description of the drawings

One or more embodiments are exemplified by the pictures in the corresponding drawings, and these exemplified descriptions do not constitute a limitation on the embodiments.

Figure 1 is an interactive flow chart of a message subscription/notification cycle in related technologies;

Figure 2 is an interactive flowchart of subscription devices initiating various types of subscriptions in related technologies;

Fig. 3 is a flowchart of a method for notifying update of collective resource members according to the first embodiment of the present application;

FIG. 4 is an interactive flowchart of the method for notifying the update of collective resource members according to the first embodiment of the present application;

FIG. 5 is an interactive flowchart of the method for notifying update of collective resource members according to the second embodiment of the present application; FIG.

Fig. 6 is a schematic structural diagram of a notification device for updating members of a collective resource according to a third embodiment of the present application;

Fig. 7 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, some embodiments of the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not used to limit the present application.

The first embodiment of the present application relates to a method for notifying updates of collective resource members. This embodiment is applied to a subscription target device, and a subscription process between the subscription target device and the subscription device is shown in FIG. 1. The subscribing device initiates a subscription request message to the subscribing target device. The request message carries the identity of the subscribing device Fr, the subscribed resource identity To, the message request identity Ri used to complete the request and response binding, and the operation type Op (such as Delete operation, add operation, etc.) and the subscription identifier Obs used to indicate that the request message is a subscription message. After receiving the subscription request message, the subscription target device authenticates the request, establishes a monitoring mechanism, and replies a response message to the subscription device. The purpose of this message is to answer the subscription request message of the subscribing device: the subscription message has been received and monitoring is started. When the subscription target device detects that the message requested by the subscription device has changed, it will send a notification message to notify the subscription device of the changed content. The message request identifier (Ri) of the above subscription request message, response message, and notification message are the same. So far, a message subscription/notification cycle is completed. If the subscription content needs to be canceled, a request message is sent again, and the subscription identifier Obs parameter is set to cancel the subscription.

Figure 1 shows the subscription process of a subscription type for a certain resource (the resource can be a collection resource) on the subscription target device. However, the interface that can complete the change of the subscription collection resource member includes: member update interface (oic.if .ll), create interface (oic.if.create), delete interface (oic.if.delete), link add interface (oic.if.linkadd), and link delete interface (oic.if.linkremove). Therefore, in the current related technology, it is necessary to initiate various types of subscription processes for the same collective resource through various types of interfaces. As shown in Figure 2, steps 10 and 11 are completed through the member update interface (oic.if.ll). The membership of the collection resource updates the subscription for changes. After this type of subscription is completed, the subscription device can only obtain the member information after the collection resource has changed. It needs to compare with the member information of the previous version to know the changed member; steps 20 and 21, through the creation interface (oic.if.create) to complete the creation of a new member's subscription to the collection resource. After completing this type of subscription, the subscription device will only receive a new member in the collection resource. To the notification message, the notification message is the information of the newly created member; in steps 30 and 31, the subscription of the deleted member of the collection resource is completed through the delete interface (oic.if.delete). After this type of subscription is completed, the subscribed device is in the Only when the member is deleted from the collection resource, the notification message will be received, and the notification message is the information of the deleted member; Steps 40 and 41, complete the addition of the collection resource through the link addition interface (oic.if.linkadd) New member link subscription. After this type of subscription is completed, the subscribing device will only receive a notification message when a new member link is added to the collection resource. The notification message is the information of the newly added new member link; step 50 And 51. The subscription of the delete member link of the collection resource is completed through the link delete interface (oic.if.linkremove). After this type of subscription is completed, the subscription device will only receive the member link when the member link is deleted from the collection resource. To the notification message, the notification message is the information of the deleted member link. It can be seen that the subscription device needs to initiate various types of subscriptions through multiple interfaces in order to determine the changed content and the changed content of the collection resource.

This embodiment aims to solve how to make the subscribing device initiate a type of subscription to the target collection resource through only one interface, so that the changed content and the changed content of the collection resource can be determined, so as to save system resources and subscribe to the target device at the same time. It is also unnecessary to maintain more subscription relationships, which simplifies the processing flow.

In this embodiment, the first resource is created for the collective resource subscribed by the subscribing device in advance, and the created first resource is used as one of the members in the collective resource. Once a member update is detected in the collection resource, the updated member is recorded in the first resource, such as adding a new member to the collection resource, or deleting a member from the collection resource, etc.; to subscribe to a member update notification The member update notification message sent by the subscribing device includes the first resource. Since the first resource is one of the members of the collective resource, the notification message for member update will carry the first resource with the updated member information, so that the subscribing device can determine the changed content of the collective resource through a notification message And the changed content. The following specifically describes the implementation details of the method for notification of member update of a collective resource in this embodiment. The following content is provided for ease of understanding and is not necessary for implementing this solution.

As shown in FIG. 3, in step 301, the subscription target device detects whether there is a member update in the collective resource. If there is a member update, it proceeds to step 302; otherwise, it returns to step 301 to continue to detect whether there is a member update in the collective resource. Among them, the collective resource is the collective resource subscribed by the subscribed device.

Specifically, due to the creation of interfaces (oic.if.create), deletion of interfaces (oic.if.delete), link addition (oic.if.linkadd) and link deletion interfaces (oic.if.linkremove), all The modification of the collection resource can be completed. Among them, when the collection resource is modified by the oic.if.create interface, it means to create a new resource, and by adding a link to the newly created resource in the collection resource, the new resource is regarded as one of the collection resources New member; when the collection resource is modified by the oic.if.delete interface, it means to delete a specified resource and delete the resource from the member list of the collection resource; when the collection resource is oic.if.linkadd When the interface is modified, it means that a new specified resource is added as a member to the collection resource. The specified resource has already been established, and the specified resource is added to the collection resource as a new member by adding a link; When the collection resource is modified by the oic.if.linkremove interface, it means that in the collection resource, a specified member is deleted by deleting the member link, and the resource corresponding to the deleted member remains unchanged.

Therefore, in this step, the subscription target device needs to monitor in real time whether the collection resource subscribed by the subscribed device is any one of oic.if.create, oic.if.delete, oic.if.linkadd, and oic.if.linkremove The interface is modified. If it is detected that the collective resource has been modified by any one of the interfaces, it is determined that there is a member update for the collective resource, and step 302 is entered.

Step 302: Record the updated member in the member update resource. Specifically, a new first resource is created for the collection resource in advance: member update resource. For example, after receiving the subscription request of the subscribing device, the creation of the member update resource is triggered. As a new member in the collection resource, the member update resource is dedicated to recording member changes in the collection resource, and the member update resource is prohibited from being deleted, and is always a member of the collection resource. The member update resource can be created directly in the collection resource or outside the collection resource. By adding the link to the member update resource in the collection resource, the newly created member update resource is regarded as a member of the collection resource. . The embodiment of this application does not limit the creation location of the member update resource. Since the member update resource is created for the collection resource, in specific implementation, priority can be given to directly creating the member update resource in the collection resource.

Specifically, the structure of the first resource, that is, the member update resource includes at least: a first field for recording the modification mode, and a second field for recording the modified member.

In a specific application, the member update resource can be set to the following structure:

/updateinformation (member update resource)

{

rt:oic.r.updateinfo

if:oic.if.r

update_method://Modify the interface used by the resource create delete linkadd linkremove

update_target://ID of the member being modified

Among them, rt represents the resource type, oic.r.updateinfo is the type used to indicate the member update resource; if represents the access interface, oic.if.r represents the read-only interface, that is, the member update resource is only allowed to be read and cannot be modified; update_method is used to record the modification method of the updated member, that is, the first field mentioned above. The modification method includes any one of member addition, member deletion, member link addition, and member link deletion, that is, it can be in the first field Record any one of the interfaces of oic.if.create, oic.if.delete, oic.if.linkadd, and oic.if.linkremove to indicate the modification method of the updated member; update_target is used to record the identification of the modified member, That is, the second field mentioned above.

It is worth mentioning that update_target can be in the form of an array, such as [A; B; C; D...], where A, B, C, and D all represent the members to be modified. Because when the collection resource is modified through any one of the interfaces of oic.if.create, oic.if.delete, oic.if.linkadd, and oic.if.linkremove, the modified member may be greater than one. Therefore, pass The update_target is designed as an array form, which can carry multiple modified member information in one notification message.

It can be seen that every time a member update is detected in the collection resource, the update method can be recorded by the update_method in the member update resource, and the updated member can be recorded by the update_targe in the member update resource.

Step 303: Send a member update notification message to the subscribing device subscribed to the member update notification. Specifically, the subscribing device in this embodiment initiates a subscription request to the subscribing target device through the member update interface (oic.if.ll), and once the subscribing target device detects that the collection resource has been updated, it sends a notification to the subscribing device The notification message includes all members of the updated collection resource, that is, the member update resource that records the content of the member change will also be one of the members of the collection resource. The notification message is carried in the notification message and sent to the subscribing device, so that the subscribing device The changed collection resource and the changes in the collection resource can be obtained directly through the notification message.

After step 303, return to step 301 to continue to detect whether there is a member update in the collective resource. Each time it is detected that the collection resource has been modified by any one of the interfaces of oic.if.create, oic.if.delete, oic.if.linkadd and oic.if.linkremove, it is necessary to enter

steps

302 and 303 to Ensure that the subscription device can obtain the changes in the collection resources and the changed content in a timely manner.

The interaction flow between the subscription device and the subscription target device in this embodiment is shown in FIG. 4, in step 401, the subscription device sends a subscription request for a collection of resources to the subscription target device. In this embodiment, the subscribing device only needs to send a subscription request to the subscribing target device through the oic.if.ll interface to subscribe to the member update notification of a certain collection resource, instead of using oic.if.create, oic.if.delete , Oic.if.linkadd, and oic.if.linkremove interfaces send subscription requests to the subscription target device. In practical applications, if the subscription target device receives a subscription request initiated by the subscription device through any one of the interfaces of oic.if.create, oic.if.delete, oic.if.linkadd, and oic.if.linkremove, the subscription target device An error response can be directly fed back to the subscribing device to indicate that the subscribing device only needs to initiate a subscription through the oic.if.ll interface.

In step 402, after the subscription target device receives the subscription request sent through the oic.if.ll interface, it creates a first resource for the subscribed collection resource, that is, creates a member update resource for the collection resource, which is used to record the collection resource The updated members and the specific structure of member update resources have been described in detail above, so I won't repeat them here.

In step 403, after the subscription target device confirms that it can complete the subscription of the collection resource, it starts to monitor the target resource, and returns to the subscribing device a response message of successful subscription.

In step 404, when the membership of the subscribed collection resource changes, such as when the collection resource is modified by the oic.if.create, oic.if.delete, oic.if.linkadd or oic.if.linkremove interface, The subscription target device will complete the modification of the member update resource according to the way the collection resource is modified and the modified member.

For example, the collection resource originally contained 3 members: smart switch 1, smart TV, and member update resources. When the collection resource is modified through the oic.if.create interface (for example, smart switch 2 is also added to the collection resource), Modify the member update resource, record the modification mode as member addition in the update_method of the member update resource, and record the identification of the smart switch 2 in the update_target of the member update resource. The revised collection resource contains 4 members: smart switch 1, smart switch 2, smart TV, and member update resources.

In step 405, the subscription target device generates a notification message, and the notification message includes all members of the modified collection resource. In response to the above case, the revised member update resources are as follows:

The modified collection resources are as follows:

In step 406, the subscription target device sends the generated notification message to the subscription device. Through the above-mentioned notification message, the subscribing device can obtain the current status of the members of the subscribed collection resource and the current updated members in one notification message.

It can be seen that, compared with the need in the prior art, the subscription is initiated through the collection of resources through interfaces such as oic.if.ll, oic.if.create, oic.if.delete, oic.if.linkadd, and oic.if.linkremove. In other words, the subscription device of this embodiment only needs to initiate a subscription request through oic.if.ll, which simplifies the process of subscribing to collection resource member changes, and the subscription target device does not need to maintain more subscription relationships, which reduces the subscription target device. Burden. Moreover, in the current related technology, after the collection resource is modified by the interface of create, delete, linkadd, linkremove, etc., the notification message for the respective interface will be triggered, and the subscription message of oic.if.ll will also be triggered. The subscription device needs to be combined Only these two notification messages can determine the change of the collective resource. In this embodiment, the subscribing device can obtain all the information in the notification message only by sending a subscription message through the oic.if.ll interface, which simplifies the information interaction between the subscribing device and the subscription target device.

The second embodiment of the present application relates to a method for notifying updates of collective resource members. This embodiment is roughly the same as the first embodiment. The difference is that in the first embodiment, the creation of the first resource is triggered after the subscription request of the subscribing device is received. However, in this embodiment, the creation of the first resource is triggered after the collection resource is generated and it is determined that the collection resource is a collection resource allowed to be subscribed.

The interaction flow between the subscription device and the subscription target device of this embodiment is shown in Figure 5. In step 501, when the subscription target device generates a collection resource that is allowed to be subscribed, it triggers the creation of the first resource for the collection resource, that is, the creation of a member for the collection resource. Update resources. The role and structure of the member update resource have been described in detail in the first embodiment, and will not be repeated here.

Step 502: The subscribing device sends a subscription request to the subscribing target device through the oic.if.ll interface to subscribe to the member update notification of the collection resource. This step is similar to step 401, and will not be repeated here.

Step 503: After the subscription target device confirms that it can complete the subscription of the collection resource, it starts to monitor the target resource, and returns to the subscribing device a response message of successful subscription.

Step 504: When the membership of the subscribed collective resource changes, the subscription target device will complete the modification of the member update resource according to the way the collective resource is modified and the modified member.

Step 505: The subscription target device generates a notification message, and the notification message includes all members of the modified collection resource.

Step 506: The subscription target device sends the generated notification message to the subscription device.

Steps 503 to 506 are similar to steps 403 to 406 in the first embodiment, and will not be repeated here.

It can be seen that member update resources can be created not only during the subscription process, but also when the collection resource is generated. That is, if a collection resource supports subscription, a member update resource can be created when the collection resource is generated. , That is, the member update resource, even if there is no subscription relationship, the member update resource is always included in the collection resource as one of the members. Member update resources can be created at different times, so that the embodiments of the present application can be implemented flexibly.

The third embodiment of the present application relates to a notification device for member update of a collective resource. As shown in FIG. 6, it includes: a recording module 601, which is used to perform a record in the first resource in the collective resource after the member update is detected in the collective resource. Record the members in the updated collection resource; the sending module 602 is configured to send a member update notification message to the subscription device subscribed to the member update notification, and the notification message includes the first resource.

In a specific example, the structure of the first resource includes at least: a first field for recording the modification mode, and a second field for recording the modified member. The recording module 601 includes: a first field recording submodule 6011, used to record in the first field the modification mode of the member that is modified in the collection resource; the second field recording submodule 6012, used to record the collection resource in the second field The ID of the modified member in.

In a specific example, the first field recording submodule 6011 is specifically used to record the creation interface in the first field, and is used to indicate that the modification method of the modified member is member addition; or, to record the deletion interface in the first field , Used to indicate that the modification method of the modified member is member deletion; or, record the link addition interface in the first field, which is used to indicate that the modification method of the modified member is member link addition; or, in the first field The record link deletion interface is used to indicate that the modification method of the modified member is member link deletion.

In a specific example, the second field may be an array.

In a specific example, the first resource is specifically triggered to be created after receiving a subscription request from the subscribing device; or, the first resource is specifically triggered to be created after generating a collective resource and determining that the collective resource is a collective resource that allows subscription.

In a specific example, the recording module 601 detects whether the collective resource has a member update in the following way: if it is detected that the collective resource has been modified by any of the following interfaces, it is determined that the collective resource has a member update: the creation of a new member Interface, delete interface for deleting members, link addition interface for adding member links, and link deletion interface for deleting member links.

It is not difficult to find that this embodiment is an example of a device corresponding to the first or second embodiment, and this embodiment can be implemented in cooperation with the first or second embodiment. The related technical details mentioned in the first or second embodiment are still valid in this embodiment, and in order to reduce repetition, they will not be repeated here. Correspondingly, the related technical details mentioned in this embodiment can also be applied in the first or second embodiment.

In addition, the modules involved in this embodiment are all logical modules. In practical applications, a logical unit can be a physical unit, it can also be a part of a physical unit, or it can be implemented as a combination of multiple physical units. . In addition, in order to highlight the innovative part of the present invention, this embodiment does not introduce units that are not closely related to solving the technical problems proposed by the present invention, but this does not indicate that there are no other units in this embodiment.

The fourth embodiment of the present application relates to an electronic device. The electronic device can be any kind of Internet of Things devices that can be subscribed. As shown in FIG. 7, the electronic device includes: at least one processor 701; The memory 702 communicatively connected to the processor 701; and a communication component 703 that is communicatively connected to the processor 701 and the memory 702. The communication component 703 receives and sends data under the control of the processor 701; wherein the memory 702 stores at least one The instructions executed by the processor 701 are executed by at least one processor 701 to implement the method for notifying an update of a collective resource member in any one of the foregoing embodiments of the present application.

The memory 702 and the processor 701 are connected in a bus manner. The bus may include any number of interconnected buses and bridges. The bus connects one or more various circuits of the processor 701 and the memory 702 together. The bus can also connect various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all well-known in the art, and therefore, no further description will be given herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on the transmission medium. The data processed by the processor is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 701.

The processor 701 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 702 may be used to store data used by the processor 701 when performing operations.

The above-mentioned products can execute the methods provided in the various embodiments of the present application, and have the corresponding functional modules and beneficial effects for executing the methods. For technical details that are not described in detail in this embodiment, please refer to the methods provided in the embodiments of this application.

The fifth embodiment of the present invention relates to a non-volatile storage medium for storing computer-readable programs. The computer readable program implements the above method embodiments when executed by the processor.

That is, those skilled in the art can understand that all or part of the steps in the method of the foregoing embodiments can be implemented by instructing relevant hardware through a program. The program is stored in a storage medium and includes several instructions to enable a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) that executes all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Those of ordinary skill in the art can understand that the above-mentioned embodiments are specific embodiments for realizing the present application, and in actual applications, various changes can be made to them in form and details without departing from the spirit and spirit of the present application. range.

Claims

A notification method for member update of collection resources, including:

If a member update is detected in the collective resource, the updated member in the collective resource is recorded in the first resource in the collective resource; a member update notification message is sent to the subscription device subscribed to the member update notification, wherein, The notification message includes the first resource.
The method according to claim 1, wherein the structure of the first resource includes at least: a first field for recording the modification mode, and a second field for recording the modified member;

The member in the collective resource that is updated in the first resource in the collective resource includes:

Record the modification mode of the modified member in the collection resource in the first field;

The identification of the modified member in the collection resource is recorded in the second field.
3. The method according to claim 2, wherein the recording in the first field the modification mode of the modified member in the collective resource comprises:

Record the creation interface in the first field, which is used to indicate that the modification method of the modified member is member addition; or,

Record the delete interface in the first field, which is used to indicate that the modification method of the modified member is member deletion; or,

Record the link addition interface in the first field, which is used to indicate that the modification method of the modified member is member link addition; or,

The link deletion interface is recorded in the first field, which is used to indicate that the modification mode of the modified member is member link deletion.
The method of claim 2 or 3, wherein the second field is an array.
The method according to any one of claims 1 to 4, wherein the creation of the first resource is triggered after receiving the subscription request of the subscription device.
The method according to any one of claims 1 to 4, wherein the creation of the first resource is triggered after generating the collective resource and determining that the collective resource is a collective resource that allows subscription.
The method according to any one of claims 1 to 6, wherein the detection of whether there is a member update of the collective resource is performed in the following manner:

If it is detected that the collective resource is modified by any one of the following interfaces, it is determined that there is a member update for the collective resource:

The creation interface used to create new members, the delete interface used to delete members, the link addition interface used to add member links, and the link delete interface used to delete member links.
A notification device for member update of a collective resource includes:

A recording module, configured to record the updated member in the collective resource in the first resource in the collective resource after detecting that the collective resource has a member update;

The sending module is configured to send a member update notification message to the subscription device subscribed to the member update notification, and the notification message includes the first resource.
8. The apparatus according to claim 8, wherein the structure of the first resource at least comprises: a first field for recording a modification method, and a second field for recording the member that is modified;

The recording module includes:

The first field recording sub-module is used to record the modification mode of the modified member in the collection resource in the first field;

The second field recording submodule is used to record the identifier of the modified member in the collection resource in the second field.
The apparatus according to claim 9, wherein the first field recording submodule is specifically configured to record a creation interface in the first field, and is used to indicate that the modification method of the modified member is member addition; or, The deletion interface is recorded in the first field, which is used to indicate that the modification method of the modified member is member deletion; or, the link addition interface is recorded in the first field to indicate that the modification method of the modified member is The member link is added; or, the link deletion interface is recorded in the first field, which is used to indicate that the modification method of the modified member is the member link deletion.
The device according to claim 9 or 10, wherein the second field is an array.
The apparatus according to any one of claims 8 to 11, wherein the first resource is specifically triggered to be created after receiving a subscription request of the subscription device.
The apparatus according to any one of claims 8 to 11, wherein the first resource is specifically triggered to be created after the collective resource is generated and it is determined that the collective resource is a collective resource that allows subscription.
The apparatus according to any one of claims 8 to 13, wherein the recording module specifically determines that the collective resource has a member update after detecting that the collective resource is modified by any one of the following interfaces:

The creation interface used to create new members, the delete interface used to delete members, the link addition interface used to add member links, and the link delete interface used to delete member links.
An electronic device including:

At least one processor;

A memory, which is in communication connection with the at least one processor; wherein,

The memory stores one or more programs that can be executed by the at least one processor;

The one or more programs include instructions that, when executed by at least one processor, cause the at least one processor to execute the method for notifying an update of a collective resource member according to any one of claims 1 to 7 .
A computer-readable storage medium storing a program executable by a processor, and when the program is executed by the processor, the method for notifying the update of collective resource members according to any one of claims 1 to 7 is realized.