Processing method and device for proxy subscription, computer equipment and storage medium

Abstract

The invention discloses a processing method and device for proxy subscription, computer equipment and a storage medium, and belongs to the technical field of Internet of Things. The method comprises: executing a first operation in the case of cancelling a proxy subscription permission of a proxy device to the source node (301); the first operation is used for stopping executing actions related to proxy subscription with the proxy equipment; wherein the proxy subscription permission comprises the permission that the proxy device serves as a proxy of the client node to subscribe the resources in the source node. According to the scheme, the subscription relationship management efficiency is improved.

Description

Processing method, device, computer equipment and storage medium for proxy subscription Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a processing method, apparatus, computer equipment, and storage medium for proxy subscription. Background Art

[0002] With the continuous development of Internet of Things (IoT) technology, more and more IoT devices have brought great convenience to users' production and life in many fields such as smart homes and industrial production.

[0003] In related technologies, when a proxy device has proxy-related permissions for a source node, a client device in the Internet of Things can subscribe to resources from the source node (e.g., a server device) through the proxy device to achieve control and management of the source node. The proxy-related permissions can be set by the user through device configuration.

[0004] Summary of the Invention

[0005] The present invention provides a method, apparatus, computer device, and storage medium for processing proxy subscriptions. This solution can improve the security of proxy subscription scenarios. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides a method for processing proxy subscriptions, the method being executed by a source node, the method comprising:

[0007] In the case of canceling the proxy subscription authority of the proxy device to the source node, performing a first operation; the first operation is used to stop actions related to the proxy subscription between the proxy device and the source node;

[0008] The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0009] In one aspect, an embodiment of the present application provides a method for processing proxy subscriptions, which is executed by a proxy device. The method includes:

[0010] When the proxy subscription authority of the proxy device to the source node is revoked, performing a second operation; the second operation is used to stop performing actions related to the proxy subscription from the source node;

[0011] The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0012] On the other hand, an embodiment of the present application provides a processing device for proxy subscription, the device comprising:

[0013] A processing module, configured to, when the proxy subscription authority of the proxy device to the source node is revoked, perform a first operation for stopping actions related to the proxy subscription performed with the proxy device;

[0014] The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0015] On the other hand, an embodiment of the present application provides a processing device for proxy subscription, the device comprising:

[0016] a processing module, configured to, when the proxy subscription authority of the proxy device to the source node is revoked, perform a second operation; wherein the second operation is configured to stop performing actions related to the proxy subscription from the source node;

[0017] The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0018] On the other hand, an embodiment of the present application provides a computer device, wherein the computer device is implemented as a proxy device or a source node, and the computer device includes a processor, a memory, and a transceiver;

[0019] The memory stores a computer program, and the processor executes the computer program so that the computer device implements the above-mentioned processing method for proxy subscription.

[0020] On the other hand, an embodiment of the present application provides a computer device, which includes a processor, a memory, and a transceiver. The memory stores a computer program, and the computer program is used to be executed by the processor to implement the above-mentioned processing method for proxy subscription.

[0021] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above-mentioned processing method for proxy subscription.

[0022] On the other hand, the present application further provides a chip, which is used to run in a computer device so that the computer device executes the above-mentioned processing method for proxy subscription.

[0023] In another aspect, the present application provides a computer program product, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned processing method for proxy subscription.

[0024] On the other hand, the present application provides a computer program, which is executed by a processor of a computer device to implement the above-mentioned processing method for proxy subscription.

[0025] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0026] In the case where the proxy device's authority to subscribe to resources in the source node as an agent is revoked, the source node can execute a first operation for stopping actions related to proxy subscription between the source node and the proxy device. This process does not require the user to perform additional operational steps to stop actions related to proxy subscription between the source node and the proxy device, thereby improving the efficiency of subscription relationship management. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0028] FIG1 is a schematic diagram of a network architecture of the Internet of Things provided by one embodiment of the present application;

[0029] FIG2 is a schematic diagram of a proxy subscription initiation process provided by an embodiment of the present application;

[0030] FIG3 is a flowchart of a processing method for proxy subscription provided by one embodiment of the present application;

[0031] FIG4 is a framework diagram of a processing flow for proxy subscription provided in one embodiment of the present application;

[0032] FIG5 is a framework diagram of a processing flow for proxy subscription provided by one embodiment of the present application;

[0033] FIG6 is a flowchart of a processing method for proxy subscription provided by one embodiment of the present application;

[0034] FIG7 is a flowchart of a processing method for proxy subscription provided by one embodiment of the present application;

[0035] FIG8 is a framework diagram of a processing flow for proxy subscription provided in one embodiment of the present application;

[0036] FIG9 is a framework diagram of a processing flow for proxy subscription provided in one embodiment of the present application;

[0037] FIG10 is a framework diagram of a processing flow for proxy subscription provided in one embodiment of the present application;

[0038] FIG11 is a framework diagram of a processing flow for proxy subscription provided in one embodiment of the present application;

[0039] FIG12 is a block diagram of a processing device for proxy subscription provided by one embodiment of the present application;

[0040] FIG13 is a block diagram of a processing device for proxy subscription provided by one embodiment of the present application;

[0041] FIG14 is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0043] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0044] Please refer to Figure 1, which shows a schematic diagram of the network architecture of the Internet of Things provided by one embodiment of the present application. The network architecture of the Internet of Things may include: a source node 110 (shown as source node 110a and source node 110b in Figure 1), a client device 120 (shown as client device 120a and client device 120b in Figure 1), an agent device 130, and a configuration device 140; optionally, the network architecture may also include a cloud server 150;

[0045] The source node 110 may be a device in the Internet of Things that is used to provide a server function corresponding to the Internet of Things protocol.

[0046] For example, the source node 110 may be a smart home device, such as a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, a smart speaker, a smart switch, and the like.

[0047] Alternatively, the source node 110 may be industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.

[0048] Alternatively, the source node 110 may be a commercial service device, such as an unmanned vending machine, etc.

[0049] Alternatively, the source node 110 may be an intelligent monitoring device, such as a monitoring camera, an infrared sensor, a sound sensor, a temperature sensor, and the like.

[0050] In one possible implementation, the client device 120 may be a user-side terminal device. For example, the client device 120 may be a smart controller, a smart remote control, a smart phone, a tablet computer, a smart watch, a smart TV, a gateway, etc. Alternatively, the client device 120 may be a personal computer, such as a desktop computer, a portable computer, a personal workstation, etc.

[0051] Alternatively, the client device 120 may also be another device that provides a server function corresponding to the Internet of Things protocol.

[0052] In another possible implementation, the client device 120 is a client entity (which may be a virtual entity) running on the terminal device. For example, the client device 120 may be an application (Application, APP) running in the terminal device for accessing, controlling, and managing the IoT device.

[0053] In a possible implementation, the proxy device 130 is connected to the source node 110 and the client device 120 at the same time, and provides a service for the client device 120 to subscribe to resources on behalf of the source node 110 .

[0054] The configuration device 140 may be a terminal device on the user side, for example, a smart phone, a tablet computer, a smart watch, a smart TV, etc.

[0055] In another possible implementation, the configuration device 140 may also be a client entity (which may be a virtual entity) running on a terminal device. For example, the configuration device 140 may be an APP running in a smart phone for managing and configuring the source node 110, the client device 120, and the proxy device 130.

[0056] The cloud server 150 is a server deployed on the network side. For example, the cloud server 150 can store relevant information about each source node 110, such as the current resource status, bound accounts, etc. The cloud server 150 can also provide a service interface for remote access to the source nodes 110, so that users can remotely manage or control the source nodes 110.

[0057] In an embodiment of the present application, the above-mentioned source node 110, client device 120, proxy device 130, configuration device 140, and cloud server 150 can be electronic devices that meet the same or different IoT protocols. For example, they can be electronic devices that meet the Matter protocol (or the Connected Home over IP Working Group (CHIP) project) under the Connectivity Standards Alliance (CSA) (or Zigbee Alliance).

[0058] For example, if the IoT devices such as the source node 110, the client device 120, the proxy device 130, and the configuration device 140 are Matter devices, the data model of the Matter device has the following characteristics:

[0059] 1) A Matter device contains one or more endpoints, which are represented by endpoint numbers (also abbreviated as endpoint-no).

[0060] For example, a Matter device is a spotlight with three bulbs, and each bulb corresponds to an endpoint. In other words, an actual physical device can contain multiple endpoints (of course, it can also contain only one endpoint); for another example, a Matter device is a socket with four jacks, and each jack can correspond to an Endpoint.

[0061] 2) Each Endpoint corresponds to one or more device types (Device Type), which are represented by device identifiers (Device ID).

[0062] For example, a Matter device is an air conditioner, which includes a thermostat and a fan. The thermostat and fan correspond to the same endpoint, the thermostat corresponds to one device type, and the fan corresponds to another device type. The thermostat and fan can be controlled through the same endpoint.

[0063] 3) Each Endpoint contains multiple clusters. Clusters are divided into two types: server and client, and the corresponding Cluster IDs are the same.

[0064] 4) Each Cluster contains multiple attributes, events, and commands, which are represented by Attribute ID, Event ID, and Command ID respectively. Attributes and Events have corresponding data types.

[0065] The IoT devices such as the source node 110, client device 120, proxy device 130 and configuration device 140 mentioned above can also be Zigbee devices. The data model of the Zigbee device is similar to the data model structure of the Matter device, except that there is no Event in the data model of the Zigbee device.

[0066] 1) Proxy subscription

[0067] In various embodiments of the present application, client devices in the Internet of Things can subscribe to resources from a source node through a proxy device; for example, in the network architecture shown in FIG. 1 above, client device 120b can subscribe to resources from source node 110b through a proxy device 130.

[0068] Please refer to Figure 2, which shows a schematic diagram of the proxy subscription initiation process provided by an embodiment of the present application. As shown in Figure 2, the process of the client device initiating the proxy subscription is as follows:

[0069] S21, the client device (Client) sends a subscription request (SubscribeRequest) to the proxy device (Proxy) to initiate resource subscription to the source node, so as to request to subscribe to the C1 resource on the above source node.

[0070] The C1 resource may be any resource on the source node, including functional resources such as switches.

[0071] In some scenarios, the client device may also be referred to as a subscription device, and the above-mentioned source node may also be referred to as a subscription target device or a subscription target node, etc.

[0072] S22, the proxy device sends a report data (ReportData) message to the source node to notify the client device that it temporarily does not have the resources of the source node.

[0073] During this process, the proxy device can check whether the client device has the subscription permission to the C1 resource on the source node, such as the browse (View) permission. Among them, when the proxy device has the proxy browse (ProxyView) permission on the Access Control Lists (ACL) cluster (cluster) resource of the source node, it can subscribe to or read the ACL Cluster. Based on this, the proxy device can obtain the subscription permission of the client device to the C1 resource on the source node, and then determine whether the client device can subscribe to the C1 resource. Optionally, when the subscribing device directly subscribes to the C1 resource on the above-mentioned source node, or when subscribing to the above-mentioned C1 resource through the proxy device, it needs to have the permission to subscribe to the C1 resource on the source node (View permission), for example, the access control entry (Access Control Entry, ACE) corresponding to the client device is required on the ACL Cluster of the source node.

[0074] After receiving the ReportData message, the client device may send a status response (StatusResponse) to the proxy device. After receiving the status response, the proxy device may send a subscription response (SubscribeResponse) to the client device.

[0075] S23, the proxy device initiates a subscription to the C1 resource on the source node.

[0076] During this process, the proxy device can send a subscription request to the source node to request to subscribe to the C1 resource on the source node. The source node sends a ReportData message to the proxy device, which contains subscription data of the C1 resource, such as the status of the C1 resource.

[0077] Optionally, after receiving the ReportData message sent by the source node, the proxy device sends a StatusResponse message to the source node. After receiving the StatusResponse message, the source node sends a SubscribeResponse message to the proxy device.

[0078] S24, after the proxy device successfully subscribes to the source node, it processes the subscription process of the client device.

[0079] During this process, the proxy device may send a ReportData message to the client device, which includes subscription data of the subscribed C1 resource; after receiving the ReportData message, the client device may send a StatusResponse message to the proxy device.

[0080] 2) Access Control List Cluster ACL Cluster

[0081] The ACL Cluster is deployed on each Node (corresponding to the Source device mentioned above), and each Node has an instance. When the Node receives a subscription request, it first checks the ACL to see if the requester has subscription permissions.

[0082] Attributes in ACL Cluster can be as shown in the following Table 1.

[0083] Table 1

[0084]

[0085] The definition of the access control entry AccessControlEntryStruct in the ACL in Table 1 above may be as shown in Table 2 below.

[0086] Table 2

[0087] IDNameTypeAccessConformance0FabricIndex RWM1PrivilegeAccessControlEntryPrivilegeEnumRWSM2AuthModeAccessControlEntryAuthmodeEnumRWSM3SubjectsList[SubjectID]RWSM4TargetsList[TargetStruct]RWSM

[0088] The definition of the access control entry privilege enumeration AccessControlEntryPrivilegeEnum in Table 2 above can be as follows:

[0089] View permissions: Read and Subscribe (except ACL Cluster);

[0090] Proxy view: read and subscribe (including ACLCluster);

[0091] Operation permission Operate: View + execute the main functions of the device (except ACL Cluster);

[0092] Management permissions Manage: Operate + modify configuration data (except ACL Cluster);

[0093] Management permissions Administer: Manage + subscribe and modify ACL Cluster.

[0094] The definition of the access control entry authentication mode enumeration AccessControlEntryAuthmodeEnum in Table 2 can be shown in Table 3:

[0095] Table 3

[0096] ValueNameDescription1PASEPasscode Authenticated Session2CASECertificate Authenticated Session3GROUPGroup Authenticated Session

[0097] For example, the code for Access Control Cluster can be as follows:

[0098]

[0099]

[0100] Before a proxy device subscribes to a target resource on a source node on behalf of a client device, it may first query the source node whether the client device has permission to subscribe to the target resource on the source node. In one possible solution, the proxy device may subscribe to the aforementioned ACL cluster with the source node, and then query the ACL cluster to determine whether the client device has subscription permission. However, during this process, the proxy device may obtain all ACE records on the source node, thereby expanding the proxy device's permissions and affecting the security of subscription permission queries performed through the proxy device.

[0101] 3) Proxy configuration cluster

[0102] The proxy device stores a proxy configuration cluster, which contains a list of devices that the proxy device can subscribe to. The proxy configuration cluster can be as shown in Table 4 below.

[0103] Table 4

[0104]

[0105] The structure of ConfigurationStruct in Table 4 above may be as shown in Table 5 below.

[0106] Table 5

[0107]

[0108] As shown in Tables 4 and 5 above, the configurationList attribute stores the identifiers of nodes that can be proxied for subscription. The SourceList specifies the nodes that can be proxied for subscription. The ProxyAllNodes identifier proxies all nodes.

[0109] A proxy device directly subscribes to a node. Within a system, a proxy device can subscribe to another proxy device to ultimately complete the client's subscription to the source: a subscription path of client → proxy device 1 → proxy device 2 … → source. In this process, a proxy device subscribing to the source is considered an upstream subscription, while a client subscribing to a proxy device is considered a downstream subscription.

[0110] 4) Valid Proxies Cluster

[0111] The source device (source node) stores a Valid Proxies Cluster. Instances of this cluster store all proxy devices supported by the source. Only one of these proxy devices can access resources on the source device. The Valid Proxies Cluster can contain the attributes shown in Table 6 below.

[0112] Table 6

[0113] IDNameTypeRangeQualityAccessDefaultConformance0ValidProxyListList[ValidProxyStruct]N / AN FRWemptyM

[0114] The structure of ValidProxyStruct in Table 6 above may be as shown in Table 7 below.

[0115] Table 7

[0116]

[0117] The commands corresponding to the above Valid Proxies Cluster may be as shown in Table 8 below.

[0118] Table 8

[0119]

[0120] In Table 8, the Get Valid Proxies Request is typically used by a client to obtain a proxy list from a source. The client then sends a broadcast message to search for proxies, collects all responding proxies, and then combines the proxy list obtained from the source to determine the range of available proxies. Finally, the user selects a proxy device based on other criteria.

[0121] For the above solution, if Client A selects Proxy A as the proxy device and subscribes to Attribute A of Source A, but the administrator may later delete Proxy A from the proxy list ValidProxyList in the Valid Proxies Cluster, then how to handle the existing proxy browsing permissions and proxy subscription relationships is a problem that this application needs to solve.

[0122] Please refer to FIG3 , which shows a flowchart of a processing method for proxy subscription provided by one embodiment of the present application. The method may be executed by a source node, for example, the source node may be the source node 110 in the network architecture shown in FIG1 . The method may include the following steps:

[0123] Step 301, when canceling the proxy subscription authority of the proxy device to the source node, perform a first operation; the first operation is used to stop actions related to proxy subscription between the proxy device; the proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0124] In some embodiments, the first operation includes at least one of the following operations:

[0125] Ending a first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device;

[0126] Deleting the information corresponding to the first subscription relationship in the subscription list of the source node;

[0127] The proxy browsing permission information of the proxy device is deleted; the proxy browsing permission information is used to indicate that the proxy device has the permission to proxy browse the information in the source node.

[0128] In some embodiments, ending the first subscription relationship includes:

[0129] Stop sending the report data message corresponding to the first subscription relationship to the proxy device.

[0130] In some embodiments, the method further comprises:

[0131] receiving a first subscription request sent by the proxy device; the first subscription request is used to re-establish the first subscription relationship;

[0132] A subscription error message is returned to the proxy device.

[0133] In some embodiments, returning a subscription error message to the proxy device includes:

[0134] An error response message indicating that there is no valid proxy is returned to the proxy device.

[0135] In some embodiments, ending the first subscription relationship includes:

[0136] A first report data message is sent to the proxy device; the first report data message is a report data message corresponding to the first subscription relationship and includes error information.

[0137] In some embodiments, the error message includes a no valid agent error code.

[0138] In some embodiments, the proxy browsing permission information is used to indicate that the proxy device has the permission to perform proxy browsing of the access control list (ACL) cluster in the source node.

[0139] In some embodiments, when the proxy subscription authority of the proxy device to the source node is canceled, performing the first operation includes:

[0140] The first operation is performed when the identification information of the proxy device is deleted from the valid proxy list of the source node.

[0141] In some embodiments, when the proxy subscription authority of the proxy device to the source node is canceled, performing the first operation includes:

[0142] When receiving the first deletion instruction, executing the first operation;

[0143] The first deletion instruction is an instruction generated when deleting the identification information of the proxy device from the valid proxy list of the source node.

[0144] To sum up, in the solution shown in the embodiment of the present application, when the authority of the proxy device to subscribe to resources in the source node as an agent is revoked, the source node can execute a first operation for stopping actions related to proxy subscription between the source node and the proxy device. This process does not require the user to additionally execute actions related to stopping proxy subscription between the source node and the proxy device, thereby improving the security of the proxy subscription scenario.

[0145] Based on the content shown in Figure 3 of the present application, taking the first operation including deleting the proxy browsing permission information of the proxy device as an example, in an exemplary solution, the source node is provided with the proxy browsing permission information of the proxy device, and the proxy browsing permission information is used to indicate that the proxy device has the proxy browsing permission Proxy view of the source node, that is, the proxy device can read and subscribe to resources including the ACL Cluster in the source node.

[0146] Please refer to Figure 4, which shows a framework diagram of the processing flow for proxy subscription provided by one embodiment of the present application. In one possible application scenario, as shown in Figure 4, source node 41 is provided with proxy browsing permission information for proxy device 42, indicating that proxy device 42 is allowed to read and subscribe to resources including the ACL Cluster in source node 41; at the same time, the Valid Proxies Cluster of source node 41 contains the node ID of proxy device 42, indicating that proxy device 42 is allowed to subscribe to resources in source node 41 as a proxy.

[0147] As shown in Figure 4 , when client device A initiates a proxy subscription request to proxy device 42 to request proxy device 42 to subscribe to resources on its behalf, proxy device 42 can subscribe to the corresponding resources from source node 41 and send the subscribed resources to client device A. When the user cancels the permission of proxy device 42 to subscribe to resources in source node 41 as a proxy by configuring the device, that is, removes the Node ID of proxy device 42 from the Valid Proxies Cluster of source node 41, source node 41 can delete the proxy browsing permission information of proxy device 42.

[0148] Based on the content shown in Figure 3 of the present application, taking the first operation including terminating the first subscription relationship as an example, please refer to Figure 5, which shows a framework diagram of the processing flow for proxy subscription provided by an embodiment of the present application. In one possible application scenario, as shown in Figure 5, the Valid Proxies Cluster of the source node 51 includes the node ID of the proxy device 52, indicating that the proxy device 52 is allowed to have the authority to subscribe to the resources in the source node 51 as a proxy.

[0149] As shown in Figure 5 , when client device A initiates a proxy subscription request to proxy device 52 to request proxy device 52 to subscribe to resources on its behalf, proxy device 52 can subscribe to the corresponding resources from source node 51 and send the subscribed resources to client device A. When the user cancels the proxy device 52's permission to subscribe to resources in source node 51 as a proxy by configuring the device, that is, removes the proxy device 52's Node ID from the source node 51's Valid Proxies Cluster, the source node 51 can initiate the cancellation of the existing first subscription relationship with proxy device 52 on both sides.

[0150] Based on the solutions shown in Figures 3 to 5 above, please refer to Figure 6, which shows a method flow chart of a method for processing proxy subscriptions provided by an exemplary embodiment of the present application. The method is executed by a proxy device, which can be the proxy device 130 in the network architecture shown in Figure 1. As shown in Figure 6, the method includes:

[0151] Step 601, when the proxy subscription authority of the proxy device to the source node is revoked, perform a second operation; the second operation is used to stop the proxy subscription-related actions from the source node; the proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0152] In some embodiments, the second operation includes at least one of the following operations:

[0153] Ending the second subscription relationship; the second subscription relationship is a downstream subscription relationship corresponding to the first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device;

[0154] And, delete the identification information of the source node from the agent configuration cluster.

[0155] In some embodiments, ending the second subscription relationship includes:

[0156] Sending a first subscription request to the source node; the first subscription request is used to re-establish the first subscription relationship;

[0157] In case of receiving a subscription error message returned by the source node, the second subscription relationship is terminated.

[0158] In some embodiments, the error response message is used to indicate that there is no valid agent.

[0159] In some embodiments, ending the second subscription relationship includes:

[0160] When the report data message corresponding to the first subscription relationship and containing error information is received, the second subscription relationship is terminated.

[0161] In some embodiments, the error message includes a no valid agent error code.

[0162] To sum up, in the solution shown in the embodiment of the present application, when the authority of the proxy device to subscribe to resources in the source node as an agent is revoked, the proxy device can execute a second operation for stopping actions related to proxy subscription from the source node. This process does not require the user to perform additional operational steps to stop the proxy device from performing actions related to proxy subscription from the source node, thereby improving the efficiency of subscription relationship management.

[0163] Based on the solutions shown in Figures 3 to 6 above, please refer to Figure 7, which shows a flowchart of a processing method for proxy subscription provided by an embodiment of the present application. The method can be interactively executed by a proxy device, a configuration device, and a source node. For example, the proxy device, the configuration device, and the source node can be the proxy device 130, the configuration device 140, and the source node 110 in the network architecture shown in Figure 1, respectively. The method may include the following steps:

[0164] Step 701: The configuration device cancels the proxy subscription authority of the proxy device to the source node.

[0165] In some embodiments, the user may cancel the proxy subscription permission of the proxy device to the source node through the configuration device.

[0166] For example, the user selects the option to cancel the proxy device's proxy subscription permission for the source node in the configuration device. At this time, the configuration device can send a removal instruction to the source node; the removal instruction can be used to trigger the source node to delete the identification information (such as Node ID) of the proxy device from the valid proxy list (such as ValidProxyList in Valid Proxies Cluster, as shown in Table 6 and Table 7).

[0167] Step 702: The source node deletes the identification information of the proxy device from the valid proxy list of the source node.

[0168] In some embodiments, after the source node receives the removal instruction sent by the configuration device, it deletes the Node ID of the proxy device from the local ValidProxyList. After that, the proxy device will not be used as a valid proxy for the source node, or in other words, the client device will not query the proxy device when querying the valid proxy of the source node.

[0169] Step 703: The source node deletes the proxy subscription authority information of the proxy device in the source node.

[0170] In some embodiments, the proxy subscription permission information is used to indicate that the proxy device has permission to proxy-subscribe to the access control list (ACL) cluster in the source node.

[0171] The proxy subscription permission information may be used to indicate that the proxy device has the Proxy view permission for the source node. With the Proxy view permission, the proxy device may read and subscribe to resources including the ACL Cluster in the source node.

[0172] In some embodiments, when canceling the proxy subscription permission of the proxy device to the source node, deleting the proxy subscription permission information of the proxy device in the source node includes:

[0173] In a case where the identification information of the proxy device is deleted from the valid proxy list of the source node, the proxy subscription authority information of the proxy device in the source node is deleted.

[0174] In an embodiment of the present application, the above-mentioned step of deleting the proxy subscription permission information of the proxy device can be automatically executed by the source node. For example, when the source node completes the action of deleting the Node ID of the proxy device from the local ValidProxyList, the step of deleting the Proxy view permission of the proxy device is automatically executed; or when the source node receives a removal instruction that triggers the deletion of the Node ID of the proxy device from the ValidProxyList, the step of deleting the Proxy view permission of the proxy device can be automatically triggered.

[0175] In some embodiments, when canceling the proxy subscription permission of the proxy device to the source node, deleting the proxy subscription permission information of the proxy device in the source node includes:

[0176] In the case of receiving the first deletion instruction, deleting the proxy subscription authority information of the proxy device in the source node;

[0177] The first deletion instruction may be an instruction sent by the configuration device when deleting the identification information of the proxy device from the valid proxy list of the source node.

[0178] In an embodiment of the present application, the step of deleting the proxy device's proxy subscription permission information can be triggered by the configuration device to be executed by the source node. For example, the configuration device can cancel the proxy device's proxy subscription permission for the source node and can also send a first deletion instruction to the source node. After receiving the first deletion instruction, the source node can delete the proxy device's proxy view permission according to the first deletion instruction.

[0179] In some embodiments, the first delete instruction may be sent to the source node independently of the remove instruction. For example, the first delete instruction and the remove instruction may be sent to the source node by the configuration device via different messages. Alternatively, the first delete instruction and the remove instruction may be sent to the source node by the configuration device via the same message, for example, the first delete instruction and the remove instruction may be carried in different fields of the message.

[0180] In some embodiments, the first deletion instruction may also be carried in the removal instruction and sent to the source node. For example, the removal instruction may carry a deletion flag (i.e., the first deletion instruction), which is used to instruct the source node to delete the proxy view permission of the proxy device. After receiving the removal instruction, the source node deletes the Node ID of the proxy device from the local ValidProxyList. At the same time, the source node detects that the removal instruction also carries a deletion flag, and deletes the proxy view permission of the proxy device according to the deletion flag.

[0181] Step 704: The source node checks whether a first subscription relationship exists in the source node; the first subscription relationship is a subscription relationship between the source node and the proxy device.

[0182] In some embodiments, the source node can check whether the first subscription relationship exists by checking whether there is a subscription initiated from the proxy device in the subscription list (for example, querying whether there is the NodeID of the proxy device in the subscription list, or querying whether there is a subscription relationship record associated with the NodeID of the proxy device in the subscription list).

[0183] If the source node determines that there is a subscription initiated by the proxy device in the subscription list, it determines that the first subscription relationship exists.

[0184] Step 705: If the first subscription relationship exists in the source node, the source node terminates the first subscription relationship.

[0185] When the source node determines that the subscription initiated by the proxy device exists in the subscription list, it may terminate the subscription initiated by the proxy device.

[0186] In some embodiments, the source node may also delete the information corresponding to the first subscription relationship in the subscription list of the source node.

[0187] Step 706: The proxy device terminates the second subscription relationship; the second subscription relationship is a downstream subscription relationship corresponding to the first subscription relationship.

[0188] In some embodiments, the proxy device may also delete identification information of the source node from the proxy configuration cluster.

[0189] In some embodiments, the process of the source node ending the first subscription relationship may include:

[0190] Stop sending the report data message corresponding to the first subscription relationship to the proxy device.

[0191] Among them, after the source node detects that there is a subscription initiated from the proxy device in the subscription list (that is, there is a first subscription relationship), it can stop sending the report data message corresponding to the first subscription relationship to the proxy device (please refer to step S24 in Figure 2 above), thereby ending the above-mentioned first subscription relationship.

[0192] In some embodiments, the method further comprises:

[0193] The source node receives a first subscription request sent by the proxy device; the first subscription request is used to re-establish the first subscription relationship;

[0194] The source node returns a subscription error message to the proxy device.

[0195] Among them, when the proxy device cannot receive the report data message corresponding to the first subscription relationship sent by the source node, it may re-initiate to establish the first subscription relationship, that is, send a first subscription request to the source node. At this time, the source node can return a subscription error message to the proxy device. After receiving the subscription error message, the proxy device can cancel the above-mentioned first subscription relationship on the proxy device side, for example, no longer send the subscription request for re-establishing the first subscription relationship, and delete the node ID of the source node (SourceNode) in the sourcelist in the proxy configuration cluster maintained by the proxy device.

[0196] Accordingly, the process of the proxy device terminating the second subscription relationship may include: sending a first subscription request to the source node; the first subscription request is used to re-establish the first subscription relationship; and terminating the second subscription relationship upon receiving a subscription error message returned by the source node.

[0197] The above-mentioned termination of the second subscription relationship may include sending a notification message of a proxy subscription error to the client device corresponding to the second subscription relationship.

[0198] In some embodiments, returning a subscription error message to the proxy device includes:

[0199] An error response message indicating that there is no valid proxy is returned to the proxy device.

[0200] The subscription error message may be an error response message indicating "No valid proxy".

[0201] In some embodiments, the process of ending the first subscription relationship may include:

[0202] A first report data message is sent to the proxy device; the first report data message is a report data message corresponding to the first subscription relationship and includes error information.

[0203] In an embodiment of the present application, after the source node detects that there is a subscription initiated from the proxy device in the subscription list (that is, there is a first subscription relationship), it can send the last report data message corresponding to the first subscription relationship to the proxy device. The report data message can include an error message. After the proxy device receives the subscription error message, it can cancel the above-mentioned first subscription relationship on the proxy device side, for example, by deleting the node ID of the source node (SourceNode) in the sourcelist in the proxy configuration cluster maintained by the proxy device.

[0204] In some embodiments, the error message includes a no valid agent error code.

[0205] In the embodiment of the present application, the above error information may include No Valid Proxy ErrorCode.

[0206] Correspondingly, the process of the proxy device terminating the second subscription relationship may include: terminating the second subscription relationship in case of receiving a report data message corresponding to the first subscription relationship and containing error information.

[0207] To summarize, according to the solution shown in the embodiment of the present application, when the permission of the proxy device to subscribe to resources in the source node as an agent is revoked, the source node can delete the proxy device's permission to browse the information in the source node as an agent, thereby avoiding the situation where the proxy device can still view the information in the source node after the proxy subscription permission is revoked, thereby improving the security of the proxy subscription scenario.

[0208] Based on the content shown in Figure 7 above of the present application, taking the first operation including deleting the proxy browsing permission information of the proxy device and terminating the first subscription relationship, and the first operation including terminating the second subscription relationship as an example, the source node is set with the proxy browsing permission information of the proxy device, and the proxy browsing permission information is used to indicate that the proxy device has the proxy browsing permission Proxy view of the source node.

[0209] Please refer to Figure 8, which shows a framework diagram of the processing flow for proxy subscription provided by one embodiment of the present application. In one possible application scenario, as shown in Figure 8, source node 81 is provided with proxy browsing permission information for proxy device 82, indicating that proxy device 82 is allowed to read and subscribe to resources including the ACL Cluster in source node 81; at the same time, the Valid Proxies Cluster of source node 81 contains the node ID of proxy device 82, indicating that proxy device 82 is allowed to subscribe to resources in source node 81 as a proxy.

[0210] As shown in Figure 8, when client device A initiates a proxy subscription request to proxy device 82, requesting proxy device 82 to subscribe to resources on its behalf, proxy device 82 can subscribe to the corresponding resources from source node 81 and send the subscribed resources to client device A. When the user cancels proxy device 82's permission to subscribe to resources in source node 81 by configuring the device, that is, removes proxy device 82's Node ID from source node 81's Valid Proxies Cluster, source node 81 can delete proxy device 82's proxy browsing permission information. At the same time, source node 81 initiates the cancellation of the existing first subscription relationship with proxy device 82 on both sides of source node 81 and proxy device 82, and proxy device 82 can cancel the downstream subscription relationship of the first subscription relationship.

[0211] Based on the scheme shown in Figures 7 or 8 above, please refer to Figure 9, which shows a framework diagram of a process flow for proxy subscription provided by one embodiment of the present application. Taking the above-mentioned proxy device as ProxyNode, the client node as ClientNode, and the source node as SourceNode as an example, as shown in Figure 9, the process flow for proxy subscription may include the following steps:

[0212] S901: The ClientNode and the ProxyNode have completed the subscription of a resource on the SourceNode.

[0213] In step S902, the subscription relationship between ProxyNode and SourceNode has been established, which can be understood as the proxy service of the subscription in step S901.

[0214] S903: The validproxylist attribute in the Valid Proxies Cluster on the SourceNode is modified to delete the Node ID of the ProxyNode from the validproxylist. The ProxyNode here is the proxy device involved in steps S901 and S902.

[0215] S904: After the SourceNode completes the operation of step S903, if the ProxyNode is not a proxy device supported by the SourceNode, the ProxyView permission of the ProxyNode to the ACL Cluster should be deleted.

[0216] ① If the ProxyNode loses the ProxyView permission for the ACL Cluster, it cannot subscribe to the resources on the SourceNode for other Client proxies.

[0217] ② The deletion action may be initiated by the admin device (ie, the configuration device), or may be automatically executed by the SourceNode during or after the completion of step S903.

[0218] S905: Check whether the subscription list contains a subscription initiated from the ProxyNode.

[0219] S906: If it exists, then terminate the subscription relationship. One method is to stop sending ReportData messages to the ProxyNode. In this way, the subscription relationship between the SourceNode and the ProxyNode can be terminated by not sending ReportData messages.

[0220] S907: After the ProxyNode fails to receive the ReportData message, it determines that the subscription relationship is lost. The ProxyNode may then initiate a re-subscription process, which involves sending a new subscription request to the SourceNode.

[0221] S908 , the SourceNode sends an error response of “No valid proxy” to the new subscription request in step S907 .

[0222] S909: After the ProxyNode fails to establish a subscription relationship with the SourceNode, the ProxyNode ends the subscription relationship with the ClientNode.

[0223] Please refer to Figure 10, which shows a framework diagram of a process flow for proxy subscription provided by one embodiment of the present application. Taking the above-mentioned proxy device as ProxyNode, the client node as ClientNode, and the source node as SourceNode as an example, as shown in Figure 10, the process flow for proxy subscription may include the following steps:

[0224] S1001: The ClientNode and the ProxyNode have completed the subscription of a resource on the SourceNode.

[0225] S1002, the subscription relationship between ProxyNode and SourceNode has also been established, which can be understood as the proxy service of the subscription in step S1001.

[0226] S1003: The validproxylist attribute in the Valid Proxies Cluster on the SourceNode is modified to delete the Node ID of the ProxyNode from the validproxylist. The ProxyNode here is the proxy device involved in steps S1001 and S1002.

[0227] S1004: After the SourceNode completes the operation of step S1003, if the ProxyNode is not a proxy device supported by the SourceNode, the ProxyView permission of the ProxyNode to the ACL Cluster should be deleted.

[0228] Note1: If the ProxyNode loses the ProxyView permission for the ACL Cluster, it cannot subscribe to resources on the SourceNode for other Client proxies.

[0229] Note 2: The deletion action may be initiated by the admin device, or it may be automatically executed by the SourceNode during or after the completion of step S1003.

[0230] S1005: Check whether the subscription list contains a subscription initiated from the ProxyNode.

[0231] S1006: If yes, the SourceNode sends a ReportData message to the ProxyNode, which includes a No Valid Proxy ErrorCode.

[0232] S1007: After receiving the above information, the ProxyNode terminates its subscription relationship with the SourceNode and may delete the SourceNode ID from the sourcelist in the proxy configuration cluster it maintains.

[0233] S1008: The ProxyNode terminates the downstream subscription relationship with the ClientNode.

[0234] Among them, the schemes shown in Figures 3 to 10 above are only illustrated by taking the source node canceling the first subscription relationship as an example. In some embodiments, the source node can also maintain the existing proxy subscription relationship of the proxy device to the resources in the source node when canceling the proxy subscription authority of the proxy device to the source node.

[0235] Please refer to Figure 11, which shows a framework diagram of a process flow for proxy subscription provided by one embodiment of the present application. Taking the above-mentioned proxy device as ProxyNode, the client node as ClientNode, and the source node as SourceNode as an example, as shown in Figure 11, the process flow for proxy subscription may include the following steps:

[0236] S1101: The ClientNode and the ProxyNode have completed the subscription for a resource on the SourceNode.

[0237] S1102, the ProxyNode and SourceNode have also established a subscription relationship, which can be understood as a proxy service for the subscription in step S1101.

[0238] S1103: The validproxylist attribute in the Valid Proxies Cluster on the SourceNode is modified to remove the Node ID of the ProxyNode from the validproxylist. The ProxyNode here is the proxy device in the prerequisite.

[0239] S1104: The subscription relationship between the ClientNode, the ProxyNode, and the SourceNode is not affected and continues to be maintained.

[0240] S1105: If the ClientNode needs to subscribe to another resource located on the SourceNode, it may re-initiate the Proxy discovery process, that is, before or after sending a broadcast query for available proxies, it will go to the SourceNode to obtain the validproxieslist (available proxy list). The ProxyNode is no longer in the list.

[0241] S1106: ClientNode broadcasts a request to obtain a valid proxy and receives a response from one or more proxy devices.

[0242] S1107: The client determines the available proxies using the validproxylist and a subset of the response message from step S1106. It is foreseeable that the proxy node that has been deleted from the validproxylist is not in the aforementioned subset. In other words, the deleted proxy node cannot become a proxy for the client node.

[0243] That is, the ProxyNode will not become a proxy for any Client subscribing to the SourceNode.

[0244] The solution shown in the above embodiment of the present application clarifies how to handle existing proxies when a proxy is removed from the validproxieslist; browsing permissions and subscription relationships can reduce connection disruptions or failure to reflect user intent caused by inconsistent scene understanding among cross-brand interoperable products, thereby improving the stability of the solution.

[0245] Please refer to Figure 12, which shows a block diagram of a processing device for proxy subscription provided by one embodiment of the present application. The device has the functions performed by the source node in each of the above-mentioned method embodiments. As shown in Figure 12, the processing device 1200 for proxy subscription may include:

[0246] The processing module 1201 is configured to execute a first operation when the proxy subscription authority of the proxy device to the source node is revoked; the first operation is configured to stop actions related to the proxy subscription executed with the proxy device;

[0247] The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0248] In some embodiments, the processing module 1201 is configured to perform at least one of the following operations:

[0249] Ending a first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device;

[0250] Deleting information corresponding to the first subscription relationship from the subscription list of the source node;

[0251] The proxy browsing permission information of the proxy device is deleted; the proxy browsing permission information is used to indicate that the proxy device has the permission to perform proxy browsing on the information in the source node.

[0252] In some embodiments, the processing module 1201 is configured to stop sending the report data message corresponding to the first subscription relationship to the proxy device.

[0253] In some embodiments, the apparatus further comprises:

[0254] A receiving module, configured to receive a first subscription request sent by the proxy device; the first subscription request is used to re-establish the first subscription relationship;

[0255] The sending module is configured to return a subscription error message to the proxy device.

[0256] In some embodiments, the sending module is configured to return an error response message indicating that there is no valid proxy to the proxy device.

[0257] In some embodiments, the processing module 1201 is configured to send a first report data message to the proxy device; the first report data message is a report data message corresponding to the first subscription relationship and includes error information.

[0258] In some embodiments, the error message includes a no valid agent error code.

[0259] In some embodiments, the proxy browsing permission information is used to indicate that the proxy device has the permission to perform proxy browsing of an access control list (ACL) cluster in the source node.

[0260] In some embodiments, the processing module 1201 is configured to perform the first operation when the identification information of the proxy device is deleted from the valid proxy list of the source node.

[0261] In some embodiments, the processing module 1201 is configured to execute the first operation upon receiving the first deletion instruction;

[0262] The first deletion instruction is an instruction generated when deleting the identification information of the proxy device from the valid proxy list of the source node.

[0263] Please refer to Figure 13, which shows a block diagram of a processing device for proxy subscription provided by one embodiment of the present application. The device has the functions performed by the proxy device in the above-mentioned various method embodiments. As shown in Figure 13, the processing device 1300 for proxy subscription may include:

[0264] Processing module 1301 is configured to execute a second operation when the proxy subscription authority of the proxy device to the source node is revoked; the second operation is configured to stop performing actions related to the proxy subscription from the source node;

[0265] The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0266] In some embodiments, the processing module 1301 is configured to perform at least one of the following operations:

[0267] Ending the second subscription relationship; the second subscription relationship is a downstream subscription relationship corresponding to the first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device;

[0268] And, deleting the identification information of the source node from the proxy configuration cluster.

[0269] In some embodiments, the processing module 1301 is used to:

[0270] Sending a first subscription request to the source node; the first subscription request is used to re-establish the first subscription relationship;

[0271] In case of receiving a subscription error message returned by the source node, the second subscription relationship is terminated.

[0272] In some embodiments, the error response message is used to indicate that there is no valid agent.

[0273] In some embodiments, the processing module 1301 is configured to terminate the second subscription relationship upon receiving a report data message corresponding to the first subscription relationship and containing error information.

[0274] In some embodiments, the error message includes a no valid agent error code.

[0275] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0276] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0277] Please refer to FIG14 , which shows a schematic diagram of the structure of a computer device 1400 provided in one embodiment of the present application. The computer device 1400 may include: a processor 1401 , a receiver 1402 , a transmitter 1403 , a memory 1404 , and a bus 1405 .

[0278] The processor 1401 includes one or more processing cores. The processor 1401 executes various functional applications and information processing by running software programs and modules.

[0279] The receiver 1402 and the transmitter 1403 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0280] The memory 1404 is connected to the processor 1401 via a bus 1405 .

[0281] The memory 1404 may be used to store a computer program, and the processor 1401 may be used to execute the computer program to implement each step in the above method embodiment.

[0282] In addition, the memory 1404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0283] In an exemplary scenario, when the computer device 1400 is implemented as a source node, the processor is configured to perform a first operation while canceling the proxy subscription permission of the proxy device to the source node; the first operation is configured to stop actions related to proxy subscription between the proxy device and the proxy device; wherein the proxy subscription permission includes the permission of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0284] In an exemplary scenario, when the computer device 1400 is implemented as a proxy device, the processor is configured to perform a second operation when the proxy device's proxy subscription authority for the source node is revoked; the second operation is configured to stop actions related to proxy subscription from the source node; wherein the proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

[0285] The processes executed by the processor 1401 and / or the transceiver 1402 in the computer device 1400 may refer to the steps executed by the source node or the proxy device in the above-mentioned method embodiments.

[0286] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement all or part of the steps performed by the proxy device or source node in the above-mentioned various method embodiments.

[0287] The present application also provides a chip, which is used to run in a computer device so that the computer device executes all or part of the steps executed by the proxy device or the source node in the above-mentioned various method embodiments.

[0288] The present application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform all or part of the steps performed by the proxy device or source node in each of the above-mentioned method embodiments.

[0289] The present application also provides a computer program, which is executed by a processor of a computer device to implement all or part of the steps performed by the proxy device or the source node in the above-mentioned various method embodiments.

[0290] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0291] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A processing method for proxy subscription, characterized in that: The method is performed by a source node, and includes: In the case of canceling the proxy subscription authority of the proxy device to the source node, performing a first operation; the first operation is used to stop actions related to the proxy subscription between the proxy device and the source node; The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

2. The method according to claim 1, characterized in that The first operation includes at least one of the following operations: Ending a first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device; Deleting information corresponding to the first subscription relationship from the subscription list of the source node; Deleting the proxy browsing permission information of the proxy device; The proxy browsing authority information is used to indicate that the proxy device has authority to perform proxy browsing of information in the source node.

3. The method according to claim 2, characterized in that The terminating the first subscription relationship includes: Stop sending the report data message corresponding to the first subscription relationship to the proxy device.

4. The method according to claim 3, characterized in that The method further comprises: receiving a first subscription request sent by the proxy device, wherein the first subscription request is used to re-establish the first subscription relationship; A subscription error message is returned to the proxy device.

5. The method according to claim 4, characterized in that The returning a subscription error message to the proxy device includes: An error response message indicating that there is no valid agent is returned to the agent device.

6. The method according to claim 2, characterized in that The terminating the first subscription relationship includes: A first report data message is sent to the proxy device; the first report data message is a report data message corresponding to the first subscription relationship and includes error information.

7. The method according to claim 6, characterized in that The error message includes a no valid agent error code.

8. The method according to any one of claims 2 to 7, characterized in that: The proxy browsing permission information is used to indicate that the proxy device has the permission to perform proxy browsing of the access control list (ACL) cluster in the source node.

9. The method according to any one of claims 1 to 8, characterized in that: In the case of canceling the proxy subscription authority of the proxy device to the source node, performing the first operation includes: In a case where the identification information of the proxy device is deleted from the valid proxy list of the source node, the first operation is performed.

10. The method according to any one of claims 1 to 8, characterized in that: In the case of canceling the proxy subscription authority of the proxy device to the source node, performing the first operation includes: Upon receiving the first deletion instruction, executing the first operation; The first deletion instruction is an instruction generated when deleting the identification information of the proxy device from the valid proxy list of the source node.

11. A processing method for proxy subscription, characterized in that: The method is performed by an agent device, and includes: When the proxy subscription authority of the proxy device to the source node is revoked, performing a second operation; the second operation is used to stop performing actions related to the proxy subscription from the source node; The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

12. The method according to claim 11, characterized in that The second operation includes at least one of the following operations: Ending the second subscription relationship; the second subscription relationship is a downstream subscription relationship corresponding to the first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device; And, deleting the identification information of the source node from the proxy configuration cluster.

13. The method according to claim 12, characterized in that The terminating the second subscription relationship includes: Sending a first subscription request to the source node; the first subscription request is used to re-establish the first subscription relationship; In case of receiving a subscription error message returned by the source node, the second subscription relationship is terminated.

14. The method according to claim 13, characterized in that The error response message is used to indicate that there is no valid agent.

15. The method according to claim 12, characterized in that The terminating the second subscription relationship includes: Upon receiving the report data message corresponding to the first subscription relationship and containing error information, the second subscription relationship is terminated.

16. The method according to claim 15, characterized in that The error message includes a no valid agent error code.

17. A processing device for proxy subscription, characterized in that: The device comprises: A processing module, configured to, when the proxy subscription authority of the proxy device to the source node is revoked, perform a first operation for stopping actions related to the proxy subscription performed with the proxy device; The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

18. The device according to claim 17, characterized in that The processing module is configured to perform at least one of the following operations: Ending a first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device; Deleting information corresponding to the first subscription relationship from the subscription list of the source node; Deleting the proxy browsing permission information of the proxy device; The proxy browsing authority information is used to indicate that the proxy device has authority to perform proxy browsing of information in the source node.

19. The device according to claim 18, characterized in that The processing module is configured to stop sending the report data message corresponding to the first subscription relationship to the proxy device.

20. The device according to claim 19, characterized in that The device further comprises: A receiving module, configured to receive a first subscription request sent by the proxy device; the first subscription request is used to re-establish the first subscription relationship; The sending module is configured to return a subscription error message to the proxy device.

21. The device according to claim 20, characterized in that The sending module is configured to return an error response message indicating that there is no valid proxy to the proxy device.

22. The device according to claim 18, characterized in that The processing module is configured to send a first report data message to the proxy device; the first report data message is a report data message corresponding to the first subscription relationship and contains error information.

23. The device according to claim 22, characterized in that The error message includes a no valid agent error code.

24. The device according to any one of claims 18 to 23, characterized in that The proxy browsing permission information is used to indicate that the proxy device has the permission to perform proxy browsing of the access control list (ACL) cluster in the source node.

25. The device according to any one of claims 17 to 24, characterized in that The processing module is configured to perform the first operation when the identification information of the proxy device is deleted from the valid proxy list of the source node.

26. The device according to any one of claims 17 to 24, characterized in that The processing module is configured to execute the first operation upon receiving the first deletion instruction; The first deletion instruction is an instruction generated when deleting the identification information of the proxy device from the valid proxy list of the source node.

27. A processing device for proxy subscription, characterized in that: The device comprises: a processing module, configured to, when the proxy subscription authority of the proxy device to the source node is revoked, perform a second operation; wherein the second operation is configured to stop performing actions related to the proxy subscription from the source node; The proxy subscription authority includes the authority of the proxy device to subscribe to resources in the source node as an agent of the client node.

28. The device according to claim 27, characterized in that The processing module is configured to perform at least one of the following operations: Ending the second subscription relationship; the second subscription relationship is a downstream subscription relationship corresponding to the first subscription relationship; the first subscription relationship is a subscription relationship between the source node and the proxy device; And, deleting the identification information of the source node from the proxy configuration cluster.

29. The device according to claim 28, characterized in that The processing module is used to: Sending a first subscription request to the source node; the first subscription request is used to re-establish the first subscription relationship; In case of receiving a subscription error message returned by the source node, the second subscription relationship is terminated.

30. The device according to claim 29, characterized in that The error response message is used to indicate that there is no valid agent.

31. The device according to claim 28, characterized in that The processing module is configured to terminate the second subscription relationship upon receiving a report data message corresponding to the first subscription relationship and containing error information.

32. The device according to claim 31, characterized in that The error message includes a no valid agent error code.

33. A computer device, characterized in that: The computer device includes a processor, a memory and a transceiver; A computer program is stored in the memory, and the processor executes the computer program so that the computer device implements the processing method for proxy subscription as shown in any one of claims 1 to 10 above, or the computer device executes the processing method for proxy subscription as shown in any one of claims 11 to 16.

34. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is used to be executed by a processor to implement the processing method for proxy subscription as shown in any one of claims 1 to 10, or to enable the computer device to execute the processing method for proxy subscription as shown in any one of claims 11 to 16.

35. A chip, characterized in that: The chip is used to run in a computer device so that the computer device executes the processing method for proxy subscription as shown in any one of claims 1 to 10, or the computer device executes the processing method for proxy subscription as shown in any one of claims 11 to 16.

36. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; the processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the computer device executes the processing method for proxy subscription as shown in any one of claims 1 to 10, or the computer device executes the processing method for proxy subscription as shown in any one of claims 11 to 16.

37. A computer program, characterized in that The computer program is executed by a processor of a computer device to implement the processing method for proxy subscription as claimed in any one of claims 1 to 10, or to enable the computer device to execute the processing method for proxy subscription as claimed in any one of claims 11 to 16.

Images