Control method and system

Abstract

The embodiment of the invention discloses a control method and system, and belongs to the technical field of computers. The method comprises the following steps: a management layer device receives a first control request sent by a service layer device; the management layer device verifies the first control request based on the access control information of the first control layer device to obtain a verification result; the management layer equipment sends the first control request to the first control layer equipment under the condition that the verification result indicates that the first control request meets the access control information; and the first control layer equipment responds to the first control request. In the embodiment of the invention, the service layer equipment cannot directly call the interface of the control layer equipment, so that the situation that the control layer equipment is abnormal due to the fact that the service layer equipment directly sends the control request to the control layer equipment is avoided, and the safety of the control layer equipment can be ensured.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a control method and system. Background Technology

[0002] With the development of network technology, controllers have become an indispensable part of networks, enabling the control of various devices. Currently, users can send control requests to the controller through their devices, allowing the controller to respond to these requests and control other devices or perform other operations. However, current controllers suffer from poor security. Summary of the Invention

[0003] This application provides a control method and system that can improve the security of control layer devices. The technical solution is as follows:

[0004] On one hand, a control method is provided, applied to a control system, the control system including service layer devices, management layer devices, and a first control layer device; the method includes:

[0005] The management layer device receives a first control request sent by the service layer device, the first control request instructing the first control layer device to perform an operation;

[0006] The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged in by the device that sent the control request.

[0007] When the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0008] The first control layer device responds to the first control request.

[0009] On the other hand, a control system is provided, which includes a business layer device, a management layer device, and a first control layer device;

[0010] The management layer device is configured to receive a first control request sent by the service layer device, wherein the first control request instructs the first control layer device to perform an operation.

[0011] The management layer device is used to verify the first control request based on the access control information of the first control layer device and obtain a verification result. The access control information indicates at least one of an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier of the device that sent the control request.

[0012] The management layer device is configured to send the first control request to the first control layer device when the verification result indicates that the first control request satisfies the access control information.

[0013] The first control layer device is used to respond to the first control request.

[0014] In one possible implementation, the first control request carries the object identifier of the service layer device login, and the access control information includes the object identifier that can send the control request to the first control layer device;

[0015] The management layer device is configured to query the access control information based on the object identifier carried in the first control request; if the access control information includes the object identifier carried in the first control request, a first verification result is obtained, the first verification result indicating that the first control request satisfies the access control information; if the access control information does not include the object identifier carried in the first control request, a second verification result is obtained, the second verification result indicating that the first control request does not satisfy the access control information.

[0016] In another possible implementation, the first control request carries the object identifier of the service layer device login, and the access control information includes object information corresponding to the object that can send the control request to the first control layer device;

[0017] The management layer device is configured to: obtain object information corresponding to the first control request based on the object identifier carried in the first control request, wherein the object information corresponding to the first control request describes the object indicated by the carried object identifier; verify the object information corresponding to the first control request based on the object information in the access control information; obtain a first verification result if the matching degree between the object information corresponding to the first control request and the object information in the access control information is not less than a first threshold, wherein the first verification result indicates that the first control request satisfies the access control information; and obtain a second verification result if the matching degree between the object information corresponding to the first control request and the object information in the access control information is less than the first threshold, wherein the second verification result indicates that the first control request does not satisfy the access control information.

[0018] In another possible implementation, the access control information includes a request type for a control request that can be sent to the first control layer device; the management layer device is configured to query the access control information based on the request type of the first control request; if the access control information includes the request type of the first control request, a first verification result is obtained, the first verification result indicating that the first control request satisfies the access control information; if the access control information does not include the request type of the first control request, a second verification result is obtained, the second verification result indicating that the first control request does not satisfy the access control information.

[0019] In another possible implementation, the first control request carries the object identifier of the service layer device login, and the access control information includes a correspondence between object identifiers and request types. The correspondence indicates the object identifiers that can send control requests to the first control layer device and the request types that the object identifiers can send control requests to. The management layer device is used to query the access control information based on the request type of the first control request and the object identifier carried by the first control request. If the access control information includes the correspondence between the request type of the first control request and the object identifier carried by the first control request, the first verification result is obtained.

[0020] In another possible implementation, the first control request carries an interface identifier of the first control layer device; the access control information indicates the interface identifiers that the first control layer device can access; the management layer device is configured to query the access control information based on the interface identifier carried in the first control request; if the access control information includes the interface identifier carried in the first control request, a first verification result is obtained, the first verification result indicating that the first control request satisfies the access control information; if the access control information does not include the interface identifier carried in the first control request, a second verification result is obtained, the second verification result indicating that the first control request does not satisfy the access control information.

[0021] In another possible implementation, the access control information includes a preset number of times an object can send control requests to the first control layer device; the management layer device is configured to verify the first control request based on the access control information and the historical request information of the initiating object, wherein the initiating object is the object indicated by the object identifier logged into the management layer device, and the historical request information indicates the historical control requests sent by the initiating object to the first control layer device; if the number of control requests sent by the initiating object to the first control layer device is less than the preset number corresponding to the initiating object, a first verification result is obtained, and the first verification result indicates that the first control request satisfies the access control information; if the number of control requests sent by the initiating object to the first control layer device is not less than the preset number corresponding to the initiating object, a second verification result is obtained, and the second verification result indicates that the first control request does not satisfy the access control information.

[0022] In another possible implementation, the preset number is the number of times an object can send control requests to the first control layer device in a single period; the management layer device is used to obtain the first verification result when the number of control requests sent by the initiating object to the first control layer device in the current period is less than the preset number corresponding to the initiating object.

[0023] In another possible implementation, the access control information indicates the data range of a preset field in a control request that can be sent to the first control layer device; the management layer device is configured to verify the data of the preset field in the first control request based on the data range of the preset field in the access control information; if the data of the preset field in the first control request belongs to the data range, a first verification result is obtained, indicating that the first control request satisfies the access control information; if the data of the preset field in the first control request does not belong to the data range, a second verification result is obtained, indicating that the first control request does not satisfy the access control information.

[0024] In another possible implementation, the management layer device is configured to verify the first control request based on the access control information, when the first control layer device is a control layer device indicated by device information, and obtain the verification result, wherein the device information indicates the destination device indicated by the control request to be verified.

[0025] In another possible implementation, the control system further includes a second control layer device;

[0026] The management layer device is further configured to receive a second control request sent by the service layer device, the second control request instructing the second control layer device to perform an operation; and to send the second control request to the second control layer device if the second control layer device is not the control layer device indicated by the device information.

[0027] In another possible implementation, the first control request carries the interface identifier of the first control layer device; the management layer device is used to verify the first control request based on the access control information, and obtain the verification result, provided that the risk level of the interface corresponding to the first control request is not lower than the second threshold, and the interface corresponding to the first control request is the interface indicated by the interface identifier carried by the first control request.

[0028] In another possible implementation, the management layer device is further configured to send the first control request to the first control layer device when the risk level of the interface corresponding to the first control request is lower than the second threshold.

[0029] In another possible implementation, the management layer device is further configured to perform state detection on the first control layer device; if the first control layer device is in an abnormal state, control the first control layer device to stop responding to the first control request; or, if the first control layer device is in an abnormal state, send a rollback command to the first control layer device, and the first control layer device rolls back in response to the rollback command.

[0030] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 This is a schematic diagram of the structure of an implementation environment provided in an embodiment of this application;

[0033] Figure 2 This is a flowchart of a control method provided in an embodiment of this application;

[0034] Figure 3 This is a flowchart of another control method provided in an embodiment of this application;

[0035] Figure 4This is a flowchart of another control method provided in the embodiments of this application;

[0036] Figure 5 This is a flowchart of another control method provided in the embodiments of this application;

[0037] Figure 6 This is a flowchart of another control method provided in the embodiments of this application;

[0038] Figure 7 This is a flowchart of another control method provided in the embodiments of this application;

[0039] Figure 8 This is a flowchart of another control method provided in the embodiments of this application;

[0040] Figure 9 This is a flowchart of another control method provided in the embodiments of this application;

[0041] Figure 10 This is a schematic diagram of a control system provided in an embodiment of this application;

[0042] Figure 11 This is a flowchart illustrating the configuration of access control information provided in an embodiment of this application;

[0043] Figure 12 This is a schematic diagram illustrating a role hierarchy and constraints between roles, provided in an embodiment of this application.

[0044] Figure 13 This is a flowchart of another control method provided in the embodiments of this application;

[0045] Figure 14 This is a flowchart illustrating the risk levels of a configuration control interface provided in an embodiment of this application;

[0046] Figure 15 This is a flowchart illustrating the configuration of access permissions provided in an embodiment of this application;

[0047] Figure 16 This is a flowchart illustrating a configuration security control method provided in an embodiment of this application;

[0048] Figure 17 This is a flowchart of configuring a parameter center provided in an embodiment of this application;

[0049] Figure 18 This is a schematic diagram of a configuration interface provided in an embodiment of this application;

[0050] Figure 19 This is a schematic diagram of the structure of a control system provided in an embodiment of this application;

[0051] Figure 20This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0052] Figure 21 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

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

[0054] The terms "first," "second," etc., used in this application may be used to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of this application, a first verification result may be referred to as a second verification result, and similarly, a second verification result may be referred to as a first verification result.

[0055] As used in this application, the terms "at least one," "multiple," "each," and "any" have different meanings: at least one includes one, two, or more; multiple includes two or more; each refers to each of the corresponding multiple; and any refers to any one of the multiple. For example, multiple control layer devices include three control layer devices, where each refers to each of the three control layer devices, and any refers to any one of the three control layer devices, which could be the first control layer device, the second control layer device, or the third control layer device.

[0056] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, control requests, access control information, object information, and historical request information involved in this application were all obtained with full authorization.

[0057] The control method provided in this application embodiment is applied to a control system. Figure 1 This is a schematic diagram of a control system provided in an embodiment of this application. See also... Figure 1 The control system includes a business layer device 101, a management layer device 102, and multiple control layer devices 103. The business layer device 101 and the management layer device 102 are connected wirelessly or wiredly, and the management layer device 102 is connected wirelessly or wiredly to each control layer device 103.

[0058] The service layer device 101 is used to trigger a control request to any control layer device 103 by sending the control request to the management layer device 102 through the connection with the management layer device 102. The management layer device 102 is used to receive the control request sent by the service layer device 101, verify the control request, and forward the control request to the corresponding control layer device 103 if the verification is successful, so that the control layer device 103 can respond to the received control request.

[0059] The multiple control layer devices 103 include either a first control layer device or a second control layer device. Optionally, the service layer device 101 is a terminal or a server. Optionally, the server is an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Optionally, the terminal is a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, smart voice interaction device, smart home appliance, or vehicle terminal, but is not limited to these. Optionally, the management layer device 102 is a terminal or a server. Optionally, the control layer device 103 is a controller. In this embodiment, different control layer devices 103 are used to control different devices; or, different control layer devices 103 are used to control different services.

[0060] In this embodiment, the multiple control layer devices 103 are independent of each other. The multiple control layer devices 103 may be integrated on the same device, in which case the multiple control layer devices 103 are sub-devices of that device; or, the multiple control layer devices 103 may be distributed on different devices; or, the multiple control layer devices 103 are devices in a distributed system.

[0061] For example, control layer device 103 is a controller, and multiple controllers are integrated on the same device; or, two controllers are deployed on device 1, and the remaining controllers are deployed on device 2; or, multiple controllers are controllers on various node devices in a distributed system.

[0062] It should be noted that the embodiments of this application are described with the example of a control system including a service layer device 101. In another embodiment, the control system includes multiple service layer devices 101. Each service layer device 101 is connected to the management layer device 102 wirelessly or wiredly, and each service layer device 101 can trigger a control request and send a control request to the management layer device 102.

[0063] It should be noted that the embodiments in this application are described in terms of the independent operation of the service layer device 101, the management layer device 102, and the multiple control layer devices 103. In another embodiment, any two or three of the service layer device 101, the management layer device 102, or the control layer device 103 can be integrated into the same device. If the same device includes at least two of the service layer device 101, the management layer device 102, or the control layer device 103, then the service layer device 101, the management layer device 102, or the control layer device 103 can be a sub-device or module included in the device.

[0064] For example, the service layer device 101 is a terminal, and the server includes a management layer device 102 and multiple control layer devices 103. Taking the management layer device 102 as the management module in the server and the control layer devices 103 as controllers as an example, the server includes a management module and multiple controllers. The terminal can trigger a control request to any controller and send the control request to the server. The server receives the control request through the management module, and if the control request passes the verification, it sends the control request to the corresponding controller. The management module can be any form of functional module, such as a virtual service or microservice in the server.

[0065] For example, the business layer device 101 is a terminal, multiple control layer devices 103 are controllers, and these controllers are controllers on various node devices in the distributed system. The management layer device 102 is a virtual service or microservice deployed on any server, which can be any node device in the distributed system or a device outside the distributed system. The terminal can trigger a control request to any controller and send the control request to the server. The server, through the management layer device 102, sends the control request to the corresponding controller if the control request passes verification.

[0066] Figure 2 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 2 As shown, the method includes:

[0067] 201. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0068] In this embodiment, the service layer device can trigger a control request for any control layer device in the control system, while the management layer device can manage control requests for each control layer device in the control system, i.e., receive control requests sent by the service layer device and verify them. The management layer device will only send a control request to the corresponding control layer device if the control request passes verification, so that the control layer device can respond to the control request. This avoids the situation where the service layer device directly sends a control request to the control layer device, which could cause the control layer device to malfunction, thus ensuring the security of the control layer device.

[0069] The first control layer device is a device used to execute certain control commands or control other devices. For example, the first control layer device is a controller, which can be of any type, such as a TIX (a public network switching platform) controller, a DCI (Data Center Interconnection) controller, a VDCI (Virtual Data Center Infrastructure) controller, or a DCN (Data Center Network) controller. The first control request can be any request. For example, the first control request instructs the first control layer device to control the controlled device, such as instructing the first control layer device to detect the network status of the data center network.

[0070] In this embodiment, the management layer device consolidates the interfaces of various control layer devices in the control system. These interfaces are also called the northbound interfaces of the control layer devices. Service layer devices typically send control requests to the northbound interfaces of the control layer devices to instruct them to perform operations. However, when the management layer device consolidates the northbound interfaces of the control layer devices, when a service layer device triggers a control request for any control layer device, it cannot directly send the control request to the control layer device. Instead, it sends the control request to the management layer device, which receives the control request. At this point, the control layer device cannot receive the control request from the service layer device. If the management layer device verifies the control request, it forwards it to the corresponding control layer device. Only then can the control layer device receive the control request from the service layer device. This prevents service layer devices from directly calling the interfaces of the control layer devices, ensuring the security of the control layer devices.

[0071] 202. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains the verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged in by the device that sent the control request.

[0072] In this embodiment of the application, the control layer device in the control system corresponds to access control information, which can restrict control requests to the control layer device. For example, the access control information can restrict the objects that send control requests to the control layer device, such as restricting objects with the permission to send control requests to the control layer device; or, it can restrict the control requests sent to the control layer, such as restricting the request type, sending time, or sending address of the control request.

[0073] In this embodiment of the application, when the management layer device receives a first control request sent by the service layer device, it determines the first control layer device corresponding to the first control request, and verifies the first control request based on the access control information of the first control layer device to verify whether the first control request meets the access control information. That is, it verifies whether the object that sent the first control request can send a control request to the first control layer device, or verifies whether the first control request is a control request that can be sent to the first control layer device.

[0074] In this context, the business layer device login uses object identifiers. Different object identifiers represent different objects, and these identifiers can be represented in any form, such as an account, nickname, or other type of identifier. For example, an object identifier could be an account. Access control information can also be represented in any form, such as text. The verification result indicates whether the first control request satisfies the access control information; that is, it indicates whether the first control request has passed verification. If the verification result indicates that the first control request satisfies the access control information, then the first control request has passed verification; if the verification result indicates that the first control request does not satisfy the access control information, then the first control request has failed verification.

[0075] 203. When the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0076] In this embodiment of the application, if the verification result indicates that the first control request meets the access control information, it means that the service layer device can send the first control request to the first control layer device, and the management layer device sends the first control request to the first control layer device.

[0077] 204. The first control layer device responds to the first control request.

[0078] In this embodiment of the application, when the first control layer device receives the first control request, it responds to the first control request so that the service layer device can control the first control layer device.

[0079] For example, if a first control request instructs a first control layer device to detect the network status of a data center network, then upon receiving the first control request, the first control layer device will respond by detecting the network status of the data center network and obtaining the network status of the data center network.

[0080] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0081] exist Figure 2 Based on the illustrated embodiments, in this embodiment, the object identifier carried in the control request is verified according to the object identifier in the access control information. The specific process is detailed in the following embodiments.

[0082] Figure 3 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 3 As shown, the method includes:

[0083] 301. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0084] In one possible implementation, the first control request includes the identifier of the first control layer device and control instructions.

[0085] The identifier of the first control layer device is used to represent the first control layer device, and different control layer devices have different identifiers. The control command indicates the operation to be performed on the control layer device. The control command can be represented in any form, for example, the control command can be represented in text form.

[0086] Optionally, the first control request may also include an object identifier. The object identifier is the object identifier for the service layer device login, indicating the object that initiated the first control request.

[0087] In one possible implementation, the management layer device provides a request interface, and the service layer device can send a first control request to the request interface of the management layer device, and then the service layer device receives the first control request through the request interface.

[0088] In this embodiment, the request interface provided by the management layer device is equivalent to a service entry point. The service layer device can call this service entry point to send a control request to the management layer device for any control layer device, thus ensuring normal communication between the service layer device and the management layer device in the control system.

[0089] In one possible implementation, the process of the service layer device sending the first control request includes: the service layer device displaying a service configuration interface, and, in response to the confirmation operation in the service configuration interface, sending the first control request to the management layer device.

[0090] In this context, the identifier of the control layer device entered in the service configuration interface indicates the first control layer device, and the identifier of the operation to be executed entered in the service configuration interface is the operation to be executed by the first control layer device as indicated by the first control request.

[0091] In this embodiment of the application, the user can input the identifier of the control layer device and the identifier of the operation to be performed by the control layer device in the service configuration interface through the service layer device. The confirmation operation in the service configuration interface is equivalent to the confirmation operation of the input identifier. Then, a first control request is generated based on the input identifier of the control layer device and the identifier of the operation to be performed, and sent to the management layer device.

[0092] Optionally, the service configuration interface includes a device input area and an operation input area.

[0093] In this embodiment, the user can manually input the identifier of any control layer device and the identifier of any operation in the device input area and operation input area through the service layer device. Alternatively, when the user clicks the device input area through the service layer device, the service layer device displays multiple candidate device identifiers, each indicating a control layer device. In response to the selection of any candidate device identifier, the selected candidate device identifier is displayed in the device input area, and the control layer device indicated by the selected candidate device identifier is the control layer device to be controlled. Similarly, when the user clicks the operation input area through the service layer device, the service layer device displays multiple candidate operation identifiers. In response to the selection of any candidate operation identifier, the selected candidate operation identifier is displayed in the device input area, and the selected candidate operation identifier indicates the operation to be performed by the control layer device.

[0094] 302. The management layer device queries the access control information of the first control layer device based on the object identifier carried in the first control request. The access control information includes the object identifier that can send a control request to the first control layer device.

[0095] In this embodiment, the first control request carries the object identifier of the service layer device login. The object identifier in the access control information has the permission to send a control request to the first control layer device. When the management layer device receives the first control request, it queries the access control information based on the object identifier carried in the first control request to determine whether the access control information of the first control layer device contains the object identifier carried in the first control request, that is, to determine whether the object identifier carried in the first control request has the permission to send a control request to the first control layer device. If the object identifier carried in the first control request has the permission to send a control request to the first control layer device, the management layer device will send the first control request to the first control layer device to ensure the accuracy of the control request sent to the first control layer device and thus ensure the security of the first control layer device.

[0096] The access control information includes multiple object identifiers, each indicating an object that can send a control request to the first control layer device. Each object identifier has the authority to send a control request to the first control layer device, and different object identifiers among the multiple object identifiers represent different objects.

[0097] In one possible implementation, the management layer device stores access control information of each control layer device in the control system. The process of obtaining the access control information of the first control layer device includes: when the management layer device receives a first control request, it obtains the access control information of the first control layer device from the locally stored access control information based on the identifier of the first control layer device carried in the first control request.

[0098] In this embodiment, the first control request also carries an identifier of a first control layer device to indicate which control layer device the first control request instructs to perform the operation. Upon receiving the first control request, the management layer device can obtain the carried identifier from the first control request. This identifier indicates the first control layer device, and based on the carried identifier, the management layer device can retrieve the access control information of the first control layer device from multiple locally stored access control information sets. This ensures the accuracy of the retrieved access control information and, consequently, the accuracy of subsequent verification.

[0099] Optionally, if the management layer device stores a correspondence between access control information and the identifier of the control layer device, then by querying the correspondence based on the identifier of any control layer device, the access control information of that control layer device can be obtained.

[0100] Optionally, access control information is represented in the form of a list. The access control list corresponding to the identifier of any control layer device includes object identifiers that represent objects with permission to send control requests to that control layer device. Through an ACL (Access Control List), it is possible to represent objects with permission to send control requests to each control layer device.

[0101] 303. When the access control information includes the object identifier carried in the first control request, the management equipment obtains a first verification result, and the first verification result indicates that the first control request satisfies the access control information.

[0102] In this embodiment of the application, the access control information includes the object identifier carried by the first control request, indicating that the first control request has been verified. The first verification result indicates that the verification has been passed, and also indicates that the service layer device can send the first control request to the first control layer device.

[0103] 304. Upon receiving the first verification result, the management layer device sends a first control request to the first control layer device.

[0104] In this embodiment of the application, if the management layer device determines that the business layer device can send a first control request to the first control layer device after obtaining the first verification result, then the management layer device sends the first control request to the first control layer device so that the first control layer device can respond to the first control request in the future.

[0105] In one possible implementation, the control system further includes a gateway layer device, then step 304 includes: the management layer device sending a first control request to the gateway layer device, the gateway layer device receiving the first control request, and sending a first control request to the first control layer device.

[0106] In this embodiment of the application, the control system further includes a gateway layer device. The gateway layer device is used to realize communication between the management layer device and the control layer device. Through the gateway layer device, the management layer device can send a first control request to the first control layer device to ensure the communication connection between the management layer device and the control layer device, and to ensure that the management layer device can manage the control requests of the control layer device.

[0107] Optionally, upon receiving the first control request, the gateway layer device calls the interface of the first control layer device according to the interface address indicated by the first control request and sends the first control request to that interface.

[0108] In this embodiment of the application, the first control request carries the interface address of the first control layer device. The gateway layer device can call the corresponding interface according to the interface address, and then send the first control request to the interface to ensure the accuracy of sending the first control request to the first control layer device.

[0109] Optionally, upon receiving the first control request, the gateway layer device performs frequency limiting detection on the interface address indicated by the first control request. If the frequency limiting detection of the interface address passes, the gateway layer device calls the interface of the first control layer device according to the interface address indicated by the first control request and sends the first control request to that interface.

[0110] In this embodiment, the interface of the first control layer device is subject to frequency limiting. That is, the interface of the first control layer device can only receive a certain number of control requests within a certain period, or the interface of the first control layer device can receive a certain total number of control requests. Therefore, upon receiving a first control request, a frequency limiting detection is performed on the interface address indicated by the first control request to determine whether the number of control requests received by the interface indicated by that interface address reaches the total number that can be received or the number that can be received within the period. If the number of control requests received by the interface indicated by the interface address does not reach the total number that can be received, or if the number of control requests received by the interface indicated by the interface address does not reach the number that can be received within the current period, then the frequency limiting detection of the interface address passes. Thus, after receiving the first control request, the gateway layer device, upon passing the frequency limiting detection of the interface address, calls the interface of the first control layer device according to the interface address indicated by the first control request and sends the first control request to that interface. This avoids sending more control requests to the first control layer device than the interface of the first control layer device can receive, preventing the first control layer device from malfunctioning due to excessive control requests and ensuring the operational security and stability of the first control layer device.

[0111] It should be noted that in this embodiment, the object identifier carried in the control request is verified according to the object identifier included in the access control information. In another embodiment, steps 302-304 above do not need to be performed. Instead, other methods are adopted. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged by the device that sent the control request. If the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0112] 305. The first control layer device responds to the first control request.

[0113] Step 305 is the same as step 204 above, and will not be repeated here.

[0114] 306. After the first control layer device finishes responding to the first control request, it obtains the response result and sends the response result to the management layer device.

[0115] The response result refers to the result obtained by the first control layer device after responding to the first control request. For example, if the first control request instructs the first control layer device to detect the network status of the data center network, then after receiving the first control request, the first control layer device responds to the first control request by detecting the network status of the data center network and obtaining the network status of the data center network; that is, the response result is the network status of the data center network.

[0116] In this embodiment, after the first control layer finishes responding to the first control request, it can obtain the response result and return the response result to the service layer device through the management layer device, so that the service layer device can receive and display the response result, and the user can know the situation of the first control layer device responding to the first control request.

[0117] 307. The management layer device receives the response result and sends the response result to the business layer device.

[0118] 308. The service layer device receives the response result and displays the response result.

[0119] It should be noted that the embodiments of this application are illustrated by the example that the first control layer device also returns a response result to the service layer device. In another embodiment, it is not necessary to perform the above steps 306-308. That is, the first control layer device only needs to respond to the first control request and does not need to return a response result.

[0120] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0121] It should be noted that the above Figure 3 The illustrated embodiment is based on obtaining a first verification result. In another embodiment, after step 302, a second verification result may be obtained to indicate that the first control request failed verification. That is, the method further includes: the management device obtains a second verification result when the access control information does not include the object identifier carried by the first control request. The second verification result indicates that the first control request does not satisfy the access control information.

[0122] In this embodiment of the application, the access control information does not include the object identifier carried in the first control request, which indicates that the verification of the first control request failed and that the service layer device cannot send the first control request to the first control layer device. In other words, the object identifier carried in the first control request does not have the permission to send a control request to the first control layer device.

[0123] In one possible implementation, the method further includes: upon obtaining a second verification result, the management layer device sends a failure notification to the service layer device, and the service layer device receives and displays the failure notification.

[0124] In this embodiment, upon receiving the second verification result, the management layer device sends a failure notification to the service layer device, indicating that sending the first control request to the first control layer device failed. The notification also indicates that the object identifier carried in the first control request does not have the authority to send a control request to the first control layer device. This allows the user to be aware of the control failure, preventing repeated sending of control requests to the first control layer and thus avoiding an increase in pending control requests to the management layer device, thereby ensuring the operational performance of the management layer device. Furthermore, if the object identifier carried in the first control request does not have the authority to send a control request to the first control layer device, the management layer device will not send the first control request again, ensuring the accuracy of the control requests sent to the first control layer device and thus guaranteeing the security of the first control layer device.

[0125] exist Figure 3 Based on the illustrated embodiment, in this embodiment of the application, the first control request is verified according to the object information included in the access control information. The specific process is detailed in the following embodiment.

[0126] Figure 4 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 4 As shown, the method includes:

[0127] 401. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0128] Step 401 is the same as step 301 above, and will not be repeated here.

[0129] 402. The management equipment obtains the object information corresponding to the first control request based on the object identifier carried in the first control request. The object information corresponding to the first control request is used to describe the object indicated by the object identifier carried.

[0130] In this embodiment, the first control request carries an object identifier for login to the service layer device. The management layer device obtains the object information corresponding to the object identifier based on this identifier; that is, it obtains the object information corresponding to the object identifier. The object information corresponding to the object identifier is equivalent to the object information corresponding to the first control request. Then, based on the object information in the access control information of the first control layer device, the management layer device verifies the object information corresponding to the first control request to check whether the object identifier carried in the first control request has the permission to send a control request to the first control layer device. If the object identifier carried in the first control request has the permission to send a control request to the first control layer device, the management layer device sends the first control request to the first control layer device to ensure the accuracy of the control request sent to the first control layer device, thereby ensuring the security of the first control layer device.

[0131] The object information is used to represent and describe the object. This object information can be represented in any form, such as text. Optionally, the object information includes multiple dimensions of sub-information, which are used to describe the object from different perspectives. For example, the multiple dimensions corresponding to the object information might be the object's department, location, qualifications, level, etc.

[0132] In this embodiment, access permissions to the control layer device are restricted according to multiple dimensions of sub-information in the object information, which enables more granular control over access permissions to the control layer device. By configuring multiple dimensions of sub-information, it is equivalent to enabling access permissions to the control layer device for objects with these multiple dimensions of sub-information, which facilitates the configuration of access permissions. It is not necessary to enable access permissions to the control layer device for each object separately, thus ensuring the efficiency and convenience of configuring permissions.

[0133] In one possible implementation, the process of obtaining object information includes: the management device retrieving the object information corresponding to the object identifier carried in the first control request from the server.

[0134] In this embodiment, the server stores object information corresponding to each object identifier. The management layer device can retrieve the object information corresponding to the object identifier carried in the first control request from the server, ensuring the accuracy of the obtained object information.

[0135] The server can be of any type. For example, the server is used to manage the object information corresponding to each object identifier. For instance, the server is the management server of an enterprise's internal system, which can manage the information of each employee within the enterprise.

[0136] 403. The management layer device verifies the object information corresponding to the first control request based on the object information in the access control information of the first control layer device.

[0137] In this embodiment, the access control information of the first control layer device includes object information corresponding to an object capable of sending a control request to the first control layer device, indicating that an object matching the object information has the permission to send a control request to the first control layer device. The object information in the access control information is then used to verify whether the object information corresponding to the first control request matches the object information in the access control information, which is equivalent to verifying whether the object corresponding to the first control request has the permission to send a first control request to the first control layer device.

[0138] The object information in the access control information indicates the object that can send control requests to the first control layer device.

[0139] In one possible implementation, the object information includes sub-information of multiple dimensions. Taking the object information in the access control information as reference object information and the object information corresponding to the first control request as first object information as an example, step 303 includes: comparing the sub-information of each dimension in the reference object information with the sub-information of the same dimension in the first object information to obtain a first value. The first value refers to the number of dimensions that are the same in the corresponding sub-information of the reference object information and the first object information. The ratio of the first value to the second value is determined as the matching degree between the object information corresponding to the first control request and the object information in the access control information. The second value is the total number of multiple dimensions corresponding to the reference object information.

[0140] In this embodiment of the application, considering that the dimensions corresponding to the first object information and the reference object information may differ, the sub-information in the first object information is compared with the sub-information of the multiple dimensions in the reference object information according to the multiple dimensions in the reference object information, so as to determine whether the sub-information of each dimension in the first object information and the reference object information are the same, and to determine the number of dimensions with the same sub-information. Then, combined with the total number of multiple dimensions corresponding to the reference object information, the matching degree is determined to ensure the accuracy of the matching degree.

[0141] For example, if the reference object information includes sub-information in three dimensions: department, location, and qualifications, and the first object information also includes sub-information in these three dimensions, then the first object information is compared with the sub-information in the department, location, and qualifications dimensions of the reference object information. If the number of identical dimensions in the corresponding sub-information is 2, then the matching degree is 2 / 3; or, if the number of identical dimensions in the corresponding sub-information is 3, then the matching degree is 1.

[0142] It should be noted that, in this embodiment of the application, when comparing the sub-information of each dimension in the reference object information with the sub-information of the same dimension in the first object information, the first quantity is determined by taking the sub-information corresponding to the same dimension as being the same. In another embodiment, the sub-information of any dimension in the reference object information is the lower limit value corresponding to that dimension. If the sub-information of the same dimension in the first object information is higher than the lower limit value corresponding to that dimension in the reference object information, it is also determined that the sub-information of the first object information and the reference object information in that dimension are matched. In this case, the first quantity will be increased by 1.

[0143] For example, if the reference object information includes four dimensions of sub-information: department, location, seniority, and level, and the first object information also includes these four dimensions of sub-information, then the first object information is compared with the sub-information of the department, location, and seniority dimensions in the reference object information. If the sub-information of the department and location dimensions are the same, but the sub-information of seniority dimensions are different, and the sub-information of the level dimension in the reference object information is 3, while the sub-information of the level dimension in the first object information is 5, that is, the sub-information of the level dimension in the first object information is higher than that in the reference object information, then the determined first quantity is 3, and the determined matching degree is 3 / 4.

[0144] Optionally, object information in access control information can be configured using RBAC (Role-Based Access Control) to identify objects with the characteristics described in the object information as those authorized to send control requests to the first control layer device. Alternatively, object information in access control information can be configured using ABAC (Attribute-Based Access Control) to determine objects with the permission to send control requests to the first control layer device based on object characteristics, operation type (equivalent to request type), and other attributes. For example, configuring object information in access control information using ABAC instructs personnel in a department to send control requests to the first control layer device through the business layer device during working hours on the office network. ABAC has more control variables than RBAC, allowing for more granular control over access permissions to the control layer device. In this embodiment, an object can have multiple roles, i.e., multiple identities. ABAC's role-based permission allocation avoids permission invalidation due to personnel changes; ABAC's permission configuration combines multiple attributes, thus supporting flexible permission allocation. For example, if a role is specified to have access to any control layer device, then every object that owns that role will have access to that control layer device.

[0145] 404. If the matching degree between the object information corresponding to the first control request and the object information in the access control information is not less than the first threshold, the management equipment obtains the first verification result, and the first verification result indicates that the first control request satisfies the access control information.

[0146] In this embodiment, the first threshold is equivalent to the lower limit of the matching degree between the object information corresponding to the control request and the object information in the access control information. If the matching degree between the object information corresponding to the first control request and the object information in the access control information is not less than the first threshold, it indicates that the object represented by the object information corresponding to the first control request has the permission to send a control request to the first control layer device; if the matching degree between the object information corresponding to the first control request and the object information in the access control information is less than the first threshold, it indicates that the object represented by the object information corresponding to the first control request does not have the permission to send a control request to the first control layer device.

[0147] The first threshold can be any value, for example, 0.8 or 1. If the first threshold is 1, it means that the object represented by the object information corresponding to the first control request has the permission to send a control request to the first control layer device only when the object information corresponding to the first control request completely matches the object information in the access control information.

[0148] 405. Upon receiving the first verification result, the management layer device sends a first control request to the first control layer device.

[0149] Step 405 is the same as step 304 above, and will not be repeated here.

[0150] It should be noted that in this embodiment, the first control request is verified according to the object information included in the access control information. In another embodiment, steps 402-405 above do not need to be performed. Instead, other methods are adopted. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged by the device that sent the control request. If the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0151] 406. The first control layer device responds to the first control request.

[0152] Step 406 is the same as step 204 above, and will not be repeated here.

[0153] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0154] It should be noted that the above Figure 4 The illustrated embodiment is based on obtaining a first verification result. In another embodiment, after step 403, a second verification result may be obtained to indicate that the verification failed. That is, the method further includes: if the matching degree between the object information corresponding to the first control request and the object information in the access control information is less than a first threshold, the management device obtains a second verification result, and the second verification result indicates that the first control request does not meet the access control information.

[0155] In this embodiment of the application, if the matching degree between the object information corresponding to the first control request and the object information in the access control information is less than the first threshold, it indicates that the verification of the first control request has failed, and it also indicates that the service layer device cannot send the first control request to the first control layer device. That is, the object identifier carried by the first control request does not have the permission to send a control request to the first control layer device.

[0156] exist Figure 2 Based on the illustrated embodiment, in this embodiment of the application, the first control request is verified according to the request type specified by the access control information. The specific process is detailed in the following embodiment.

[0157] Figure 5 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 5 As shown, the method includes:

[0158] 501. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0159] Step 501 is the same as step 301 above, and will not be repeated here.

[0160] 502. The management layer device queries the access control information based on the request type of the first control request.

[0161] In this embodiment, the access control information includes the request type of the control request that can be sent to the first control layer device. The request type in the access control information is equivalent to the request type of the control request that the first control layer device can receive. When the management layer device receives the first control request, it queries the access control information based on the request type of the first control request to determine whether the access control information of the first control layer device contains the request type of the first control request. That is, it determines whether the first control request is a control request that the first control layer device can receive. If the first control request is a control request that the first control layer device can receive, the management layer device sends the first control request to the first control layer device to ensure the accuracy of the control request sent to the first control layer device and thus ensure the security of the first control layer device.

[0162] The access control information includes multiple request types, which indicate control requests that can be sent to the first control layer device. Different request types are used to perform different functions; that is, different request types instruct the control layer device to perform different operations. For example, multiple request types may be query, storage, and update. A query request instructs the control layer device to perform a query operation, a storage request instructs the control layer device to perform a data storage operation, and an update request instructs the control layer device to perform an update operation.

[0163] In one possible implementation, the first control request carries the object identifier of the business layer device login, and the access control information includes the correspondence between the object identifier and the request type. The correspondence indicates the object identifier that can send the control request to the first control layer device and the request type that the object identifier can send the control request to. Then, step 502 includes: the management layer device queries the access control information based on the request type of the first control request and the object identifier carried by the first control request.

[0164] In this embodiment, the access control information of the first control layer device includes the object relationship between the object identifier and the request type, indicating the objects that can send control requests to the first control layer device and the type of control request that each object can send to the first control layer device. In other words, it is equivalent to indicating the objects that can send control requests to the first control layer device and the control requests that can be sent to the first control layer device.

[0165] In this embodiment, the access control information of the first control layer device indicates the objects that can send control requests to the first control layer device and the types of control requests that each object can send to the first control layer device. Therefore, after receiving the first control request, the management layer device queries the access control information based on the object identifier carried by the first control request and the request type of the first control request to check whether the access control information includes the correspondence between the object identifier carried by the first control request and the request type of the first control request. In this way, control requests sent to the first control layer device can be restricted from multiple dimensions, which can meet different user needs, flexibly configure the objects that send control requests to the first control layer device or the control requests sent to the first control layer device, ensure the flexibility of permission configuration, and also ensure the accuracy of the control requests sent to the first control layer device, thereby ensuring the security of the first control layer device.

[0166] For example, the access control information includes object identifier 1 and the corresponding request type 1 and request type 2. That is, the object represented by object identifier 1 can send a control request belonging to request type 1 or request type 2 to the first control layer device.

[0167] 503. When the access control information includes the request type of the first control request, the management device obtains a first verification result, which indicates that the first control request satisfies the access control information.

[0168] In this embodiment of the application, the access control information includes the request type of the first control request, indicating that the first control request has been verified, and the obtained first verification result indicates that the verification has been passed, and also indicates that the service layer device can send the first control request to the first control layer device.

[0169] In one possible implementation, the access control information includes the correspondence between object identifiers and request types. In this case, step 503 includes: the management device obtaining a first verification result when the access control information includes the correspondence between the request type of the first control request and the object identifier carried by the first control request.

[0170] In this embodiment of the application, the access control information includes the correspondence between the request type of the first control request and the object identifier carried by the first control request, indicating that the object identifier can send a control request of the request type to the first control layer device, that is, the service layer device can send the first control request to the first control layer device.

[0171] 504. Upon receiving the first verification result, the management layer device sends a first control request to the first control layer device.

[0172] Step 504 is the same as step 304 above, and will not be repeated here.

[0173] It should be noted that in this embodiment, the first control request is verified according to the request type specified by the access control information. In another embodiment, steps 502-504 above do not need to be performed. Instead, other methods are adopted. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged by the device that sent the control request. If the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0174] 505. The first control layer device responds to the first control request.

[0175] Step 505 is the same as step 204 above, and will not be repeated here.

[0176] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0177] It should be noted that the above Figure 5 The illustrated embodiment is based on obtaining a first verification result. In another embodiment, after step 502, a second verification result may be obtained to indicate that the verification failed. That is, the method further includes: when the access control information does not include the request type of the first control request, the management device obtains a second verification result, and the second verification result indicates that the first control request does not satisfy the access control information.

[0178] In this embodiment of the application, the access control information does not include the request type of the first control request, which indicates that the verification of the first control request failed, and also indicates that the service layer device cannot send the first control request to the first control layer device. In other words, the service layer device cannot send a control request of this type to the first control layer device.

[0179] In one possible implementation, the access control information includes the correspondence between object identifiers and request types. The process of obtaining the second verification result includes: the management device obtaining the second verification result when the access control information does not include the correspondence between the request type of the first control request and the object identifier carried by the first control request.

[0180] In this embodiment of the application, if the access control information does not include the correspondence between the request type of the first control request and the object identifier carried by the first control request, it means that the access control information does not include the object identifier carried by the first control request, or the access control information does not include the request type of the first control request, or the access control information includes the object identifier carried by the first control request but the request type corresponding to the object identifier does not include the request type of the first control request; then it means that the first control request cannot be sent to the first control layer device.

[0181] exist Figure 2 Based on the illustrated embodiment, in this embodiment of the application, the first control request is verified according to the interface specified by the access control information. The specific process is detailed in the following embodiment.

[0182] Figure 6 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 6 As shown, the method includes:

[0183] 601. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0184] Step 601 is the same as step 301 above, and will not be repeated here.

[0185] 602. The management layer device queries the access control information of the first control layer device based on the interface identifier carried in the first control request. The access control information indicates the interface identifiers that the first control layer device can access.

[0186] In this embodiment, the first control layer device has one or more interfaces, each with a different interface identifier. The interface identifier in the access control information of the first control layer device indicates the interface on which the first control layer device can receive control requests. Upon receiving a first control request, the management layer device queries the access control information of the first control layer device according to the interface identifier carried in the first control request. This queries whether the access control information includes the interface identifier carried in the first control request; that is, it verifies whether the interface indicated by the interface identifier carried in the first control request is an interface on which the first control layer device can receive control requests. This ensures that if the interface indicated by the interface identifier carried in the first control request is an interface on which the first control layer device can receive control requests, the management layer device sends the first control request to the first control layer device. This avoids the situation where the first control layer device cannot receive the first control request sent to the interface indicated by the interface identifier carried in the first control request, thus ensuring the accuracy of the control requests sent to the first control layer device and consequently, the security of the first control layer device.

[0187] The first control request carries an interface identifier, which is the interface identifier of the first control layer device, indicating that the first control request should be sent to the interface indicated by the interface identifier. The access control information of the first control layer device, including the interface identifier, is equivalent to indicating the control request that can be sent to the first control layer device.

[0188] In one possible implementation, different interfaces correspond to request types, and the request type corresponding to an interface indicates that the interface can receive control requests belonging to that request type. The access control information of the first control layer device includes at least one interface identifier and the request type corresponding to each interface identifier. Then, step 602 includes: the management layer device queries the access control information of the first control layer device based on the interface identifier and request type carried by the first control request.

[0189] In this embodiment of the application, the access control information of the first control layer device includes interface identifiers and corresponding request types, so as to indicate the interfaces that the first control layer device can receive control requests and what type of control requests each interface can receive, which is equivalent to indicating the control requests that can be sent to the first control layer device.

[0190] In this embodiment, the access control information of the first control layer device indicates the interfaces that the first control layer device can receive control requests and the types of control requests that each interface can receive. Therefore, after receiving the first control request, the management layer device queries the access control information based on the interface identifier and request type carried by the first control request to check whether the access control information includes the correspondence between the interface identifier carried by the first control request and the request type of the first control request. In this way, control requests sent to the first control layer device can be restricted from multiple dimensions, which can meet different user needs, flexibly configure the objects or control requests sent to the first control layer device, ensure the flexibility of permission configuration, and also ensure the accuracy of control requests sent to the first control layer device, thereby ensuring the security of the first control layer device.

[0191] 603. When the access control information includes the interface identifier carried by the first control request, the management layer device obtains a first verification result, and the first verification result indicates that the first control request satisfies the access control information.

[0192] In this embodiment of the application, the access control information includes the interface identifier carried by the first control request, indicating that the first control request has been verified. The first verification result indicates that the verification has been passed, and also indicates that the service layer device can send the first control request to the first control layer device.

[0193] In one possible implementation, the access control information of the first control layer device includes at least one interface identifier and a request type corresponding to each interface identifier. Then, step 603 includes: the management layer device obtaining a first verification result when the access control information includes the correspondence between the request type of the first control request and the interface identifier carried by the first control request.

[0194] In this embodiment of the application, the access control information includes the correspondence between the request type of the first control request and the interface identifier carried by the first control request, indicating that a control request of the request type can be sent to the interface indicated by the interface identifier carried by the first control request. That is, the service layer device can send the first control request to the first control layer device.

[0195] 604. Upon receiving the first verification result, the management layer device sends a first control request to the first control layer device.

[0196] Step 504 is the same as step 304 above, and will not be repeated here.

[0197] It should be noted that in this embodiment, the first control request is verified according to the interface specified by the access control information. In another embodiment, steps 602-604 above do not need to be performed. Instead, other methods are adopted. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged by the device that sent the control request. If the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0198] 605. The first control layer device responds to the first control request.

[0199] Step 605 is the same as step 204 above, and will not be repeated here.

[0200] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0201] It should be noted that the above Figure 6 The illustrated embodiment is based on obtaining a first verification result. In another embodiment, after step 602, a second verification result may be obtained to indicate that the verification failed. That is, the method further includes: the management device obtains a second verification result when the access control information does not include the interface identifier carried by the first control request. The second verification result indicates that the first control request does not meet the access control information.

[0202] In this embodiment of the application, the access control information does not include the interface identifier carried by the first control request, which indicates that the verification of the first control request failed, and also indicates that the service layer device cannot send the first control request to the first control layer device. That is, the service layer device cannot send the control request to the interface indicated by the interface identifier in the first control layer device.

[0203] In one possible implementation, the access control information of the first control layer device includes at least one interface identifier and the request type corresponding to each interface identifier. Then, the process of obtaining the second verification result includes: the management layer device obtains the second verification result when the access control information does not include the correspondence between the request type of the first control request and the interface identifier carried by the first control request.

[0204] In this embodiment of the application, if the access control information does not include the correspondence between the request type of the first control request and the interface identifier carried by the first control request, it means that the access control information does not include the interface identifier carried by the first control request, or the access control information does not include the request type of the first control request, or the access control information includes the interface identifier carried by the first control request but the request type corresponding to the interface identifier does not include the request type of the first control request; then it means that the first control request cannot be sent to the first control layer device.

[0205] exist Figure 2 Based on the illustrated embodiment, in this embodiment, the first control request is verified according to the number of times specified in the access control information and the historical request information. For details of the process, please refer to the following embodiment.

[0206] Figure 7 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 7 As shown, the method includes:

[0207] 701. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0208] Step 701 is the same as step 301 above, and will not be repeated here.

[0209] 702. The management layer device verifies the first control request based on the access control information of the first control layer device and the historical request information of the initiating object. The initiating object is the object indicated by the object identifier logged in by the management layer device. The historical request information indicates the historical control requests sent by the initiating object to the first control layer device. The access control information includes the preset number of times the object can send control requests to the first control layer device.

[0210] In this embodiment, the access control information includes a preset number of times each object can send control requests to the first control layer device. After receiving the first control request, the management layer device verifies the first control request based on the access control information and the corresponding historical request information. This verifies whether the number of control requests sent by the initiating object to the first control layer device exceeds the preset number for that initiating object in the access control information. This ensures that the management layer device sends the first control request to the first control layer device only when the number of control requests sent by the initiating object to the first control layer device is less than the preset number for the initiating object. This avoids the situation where the number of control requests sent by the initiating object to the first control layer device exceeds the preset number for the initiating object, thus ensuring the accuracy of the control requests sent to the first control layer device and thereby ensuring the security of the first control layer device.

[0211] The preset number of times can be any number of times, for example, 10 times. The access control information includes a preset number of times that an object can send control requests to the first control layer device, which is equivalent to indicating the control requests that can be sent to the first control layer device.

[0212] In this embodiment of the application, the access control information can determine the preset number of times that the initiating object of the first control request can send a control request to the first control layer device. The historical request information can reflect the number of historical control requests sent by the initiating object to the first control layer device. Therefore, by verifying the first control request based on the access control information of the first control layer device and the historical request information of the initiating object, it can be determined whether the number of times the initiating object has sent a control request to the first control layer device exceeds the preset number. Thus, it can be determined whether the number of times the initiating object sends a control request to the first control layer device after sending the first control request to the first control layer device exceeds the preset number.

[0213] In this embodiment, the access control information includes a preset number of times an object can send control requests to the first control layer device. This is equivalent to using a quantity lock to control the number of control requests an object can send to the first control layer device, thereby limiting the maximum number of control requests an object can send to the first control layer device. For example, taking the first control layer device as a controller, the quantity lock can limit the maximum number of times object A can call the controller's northbound interface.

[0214] In one possible implementation, the access control information includes a correspondence between object identifiers and preset number of times. This correspondence reflects the preset number of times that each object identifier indicates an object can send a control request to the first control layer device.

[0215] Optionally, step 702 includes: the management layer device queries the correspondence included in the access control information of the first control layer device based on the object identifier carried in the first control request to obtain the preset number of times corresponding to the object identifier; based on the historical request information of the initiating object, it determines the number of times the initiating object sends historical control requests to the first control layer device; and compares the preset number of times corresponding to the object identifier with the number of times historical control requests are sent.

[0216] The object identifier carried in the first control request indicates the object that initiated the first control request. The preset number of times corresponding to the object identifier is the same as the preset number of times corresponding to the initiating object.

[0217] Optionally, if the historical request information indicates the historical control requests sent by the initiating object to each control layer device, then based on the identifier of the first control layer device carried in the first control request, the number of times the initiating object sent historical control requests to the first control layer device can be obtained from the historical request information.

[0218] In this embodiment of the application, the historical request information indicates the historical control requests sent by the initiating object to each control layer device. By querying based on the identifier of the first control layer device, the historical control requests sent by the initiating object to the first control layer device can be determined, and thus the number of times the initiating object sent historical control requests to the first control layer device can be determined.

[0219] 703. When the number of control requests sent by the initiating object to the first control layer device is less than the preset number corresponding to the initiating object, the management layer device obtains the first verification result, which indicates that the first control request satisfies the access control information.

[0220] In this embodiment of the application, if the number of control requests sent by the initiating object of the first control request to the first control layer device is less than the preset number corresponding to the initiating object, it means that the number of control requests sent by the initiating object to the first control layer device has not yet reached the preset number corresponding to the initiating object. Therefore, after sending the first control request to the first control layer device this time, the number of control requests sent by the initiating object to the first control layer device will not exceed the preset number corresponding to the initiating object. Thus, it indicates that the first control request has passed the verification, and the obtained first verification result indicates that the verification has passed. It also indicates that the service layer device can send the first control request to the first control layer device.

[0221] In one possible implementation, the preset number is the number of times an object can send control requests to the first control layer device in a single cycle; then step 703 includes: if the number of control requests sent by the initiating object to the first control layer device in the current cycle is less than the preset number corresponding to the initiating object, the management layer device obtains a first verification result.

[0222] In this embodiment, the access control information includes a preset number of times each object can send control requests to the first control layer device within a single period. If the number of control requests sent by the object initiating the first control request to the first control layer device in the current period is less than the preset number corresponding to the initiating object, it indicates that the number of control requests sent by the initiating object to the first control layer device in the current period has not yet reached the preset number corresponding to the initiating object. Therefore, after sending the first control request to the first control layer device in the current period, the number of control requests sent by the initiating object to the first control layer device in the current period will not exceed the preset number corresponding to the initiating object. Thus, it indicates that the first control request has passed the verification, and the obtained first verification result indicates that the verification has passed. It also indicates that the service layer device can send the first control request to the first control layer device, thus avoiding the situation where the number of control requests sent by the initiating object to the first control layer device exceeds the preset number corresponding to the initiating object, thereby ensuring the accuracy of the control requests sent to the first control layer device and thus ensuring the security of the first control layer device.

[0223] The duration of a single cycle can be arbitrary, such as 1 day or 1 minute. The current cycle refers to the time period whose duration is the same as the unit cycle and whose end time is the time when the management device receives the first control request. For example, if the duration of a single cycle is 1 day and the management device receives the first control request at 10:00 AM, then the current cycle refers to the time period from 10:00 AM yesterday to 10:00 AM today.

[0224] In this embodiment, the access control information includes a preset number of times an object can send control requests to the first control layer device within a single cycle. This is equivalent to using a frequency lock to control the number of control requests an object can send to the first control layer device, thereby limiting the maximum number of control requests an object can send to the first control layer device within a single cycle. For example, a frequency lock can control the number of control requests an object can initiate against a specific control layer device within a single cycle.

[0225] Optionally, the access control information includes a preset number of times an object can send each type of control request to the first control layer device within a single period. In this embodiment, an object can send control requests of multiple request types to any control layer device, and the access control information indicates the preset number of times an object can send each type of control request to the first control layer device within a single period. Then, if the number of times the initiating object sends a control request of the first request type to the first control layer device within the current period is less than the preset number corresponding to the first request type, the management layer device obtains a first verification result, where the first request type is the request type to which the first control request belongs.

[0226] In this embodiment, a frequency lock is used to control the control requests sent by an object to the first control layer device, thereby limiting the maximum number of control requests sent by the object to the first control layer device within a single cycle. For example, a frequency lock can control the preset number of times an object sends each type of control request to a specific control layer device within a single cycle.

[0227] Optionally, the management layer device queries the historical request information based on the time point and duration of the period in which the first control request is received, to obtain the number of times the initiating object sends historical control requests to the first control layer device within the current period.

[0228] 704. Upon receiving the first verification result, the management layer device sends a first control request to the first control layer device.

[0229] Step 704 is the same as step 304 above, and will not be repeated here.

[0230] It should be noted that in this embodiment, the first control request is verified according to the number of times specified in the access control information and the historical request information. In another embodiment, steps 702-704 above do not need to be performed. Instead, other methods are adopted. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged by the device that sent the control request. If the verification result indicates that the first control request satisfies the access control information, the management layer device sends the first control request to the first control layer device.

[0231] 705. The first control layer device responds to the first control request.

[0232] Step 705 is the same as step 204 above, and will not be repeated here.

[0233] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0234] It should be noted that the above Figure 7 The illustrated embodiment is based on obtaining a first verification result. In another embodiment, after step 702, a second verification result may also be obtained. That is, the method further includes: the management layer device obtains a second verification result when the number of control requests sent by the initiating object to the first control layer device is not less than the preset number corresponding to the initiating object. The second verification result indicates that the first control request does not meet the access control information.

[0235] In this embodiment of the application, the number of control requests sent by the initiating object to the first control layer device is not less than the preset number corresponding to the initiating object. This means that if the first control request is sent to the first control layer device, the number of control requests sent by the initiating object to the first control layer device will exceed the preset number corresponding to the initiating object. This indicates that the verification of the first control request has failed, and also indicates that the service layer device cannot send the first control request to the first control layer device.

[0236] In one possible implementation, the preset number is the number of times an object can send control requests to the first control layer device within a single cycle; then the process of obtaining the second verification result includes: the management layer device obtains the second verification result if the number of control requests sent by the initiating object to the first control layer device within the current cycle is not less than the preset number corresponding to the initiating object.

[0237] In this embodiment of the application, the number of control requests sent by the initiating object to the first control layer device in the current period is not less than the preset number corresponding to the initiating object. If, after sending the first control request to the first control layer device in the current period, the number of control requests sent by the initiating object to the first control layer device in the current period exceeds the preset number corresponding to the initiating object, it indicates that the verification of the first control request has failed. The obtained second verification result indicates that the verification has failed, which also indicates that the service layer device cannot send the first control request to the first control layer device.

[0238] exist Figure 2 Based on the illustrated embodiment, in this embodiment of the application, the first control request is verified according to the data range of the preset fields in the access control information. For details of the process, please refer to the following embodiment.

[0239] Figure 8 This is a flowchart of a control method provided in an embodiment of this application, applied to a control system. The control system includes a service layer device, a management layer device, and a first control layer device; as shown... Figure 8 As shown, the method includes:

[0240] 801. The management layer device receives a first control request sent by the service layer device. The first control request instructs the first control layer device to perform an operation.

[0241] Step 801 is the same as step 301 above, and will not be repeated here.

[0242] 802. The management layer device verifies the data of the preset fields in the first control request based on the data range of the preset fields in the access control information of the first control layer device.

[0243] In this embodiment, the access control information indicates the data range of a preset field in a control request that can be sent to the first control layer device. The preset field is a field included in the control request. After receiving the first control request, the management layer device verifies the data of the preset field in the first control request based on the data range of the preset field in the access control information. This verifies whether the data of the preset field in the first control request belongs to the data range specified by the access control information. If the data of the preset field in the first control request belongs to the data range specified by the access control information, the management layer device sends the first control request to the first control layer device. This avoids situations where the control request sent to the first control layer device does not meet the access control information, thereby ensuring the accuracy of the control request sent to the first control layer device and thus ensuring the security of the first control layer device.

[0244] The access control information indicates the data range of preset fields in the control requests that can be sent to the first control layer device, essentially indicating the control requests that can be sent to the first control layer device. The preset fields can be any fields, such as time fields or space fields. The data range of the time field in the access control information indicates the valid time range for sending the control request, and the data range of the space field indicates the physical space range for sending the control request, such as an address range. For example, the data range of the time field in the access control information indicates working hours on a weekday; that is, if the first control request is sent by the business layer device during working hours on a weekday, then the data in the time field of the first control request can fall within the data range of the time field in the access control information. As another example, the data range of the space field in the access control information indicates the office network address range; that is, if the first control request is sent by the business layer device through the office network, then the data in the space field of the first control request can fall within the data range of the space field in the access control information.

[0245] In this embodiment of the application, the access control information indicates the data range of a preset field in the control request that can be sent to the first control layer device. This is equivalent to controlling the control request sent by the object to the first control layer device through a range lock, so that the control request within the range defined by the range lock can be sent to the first control layer.

[0246] 803. If the data in the preset field of the first control request is within the data range, the management equipment obtains the first verification result, which indicates that the first control request satisfies the access control information.

[0247] In this embodiment of the application, the data in the preset field of the first control request belongs to the data range, indicating that the first control request is a control request that can be sent to the first control layer device, indicating that the first control request has passed the verification, and the obtained first verification result indicates that the verification has passed, and also indicates that the service layer device can send the first control request to the first control layer device.

[0248] 804. Upon receiving the first verification result, the management layer device sends a first control request to the first control layer device.

[0249] Step 804 is the same as step 304 above, and will not be repeated here.

[0250] It should be noted that in this embodiment, the first control request is verified according to the data range of the preset fields in the access control information. In another embodiment, steps 802-804 above do not need to be performed. Instead, other methods are adopted. The management layer device verifies the first control request based on the access control information of the first control layer device and obtains a verification result. The access control information indicates at least one of the following: an object that can send a control request to the first control layer device or a control request that can be sent to the first control layer device. The object is the object indicated by the object identifier logged by the device that sent the control request. If the verification result indicates that the first control request meets the access control information, the management layer device sends the first control request to the first control layer device.

[0251] 805. The first control layer device responds to the first control request.

[0252] Step 705 is the same as step 204 above, and will not be repeated here.

[0253] In the solution provided in this application embodiment, the control system includes a service layer device, a management layer device, and a control layer device. The management layer device has the function of verifying control requests from the control layer device. When a service layer device triggers a control request to any control layer device, it sends the control request to the management layer device. The management layer device verifies the control request based on the access control information of the control layer device. Only if the verification passes will the management layer device send the control request to the control layer device, allowing the control layer device to respond. This prevents service layer devices from directly sending control requests to the control layer device, avoiding situations where direct sending of control requests by service layer devices could lead to control layer device malfunctions, thus ensuring the security of the control layer device. Furthermore, the function of verifying control requests from each control layer device in the control system is integrated into the management layer device. This eliminates the need to deploy separate verification mechanisms for each control layer device, improving the development efficiency of each device. Moreover, the control layer device does not need to verify the control request again after receiving it, reducing its workload and improving its efficiency. This also prevents downtime due to heavy workloads and ensures the stability of the control layer device.

[0254] It should be noted that the above Figure 8 The illustrated embodiment is based on obtaining a first verification result. In another embodiment, after step 802, a second verification result may also be obtained. That is, the method further includes obtaining a second verification result when the data of the preset field in the first control request does not belong to the data range. The second verification result indicates that the first control request does not satisfy the access control information.

[0255] In this embodiment of the application, if the data in the preset field of the first control request does not belong to the data range, it means that the first control request is a control request that cannot be sent to the first control layer device. This indicates that the verification of the first control request has failed, and also indicates that the service layer device cannot send the first control request to the first control layer device.

[0256] In the above Figure 8 Based on the embodiments shown, Figure 8 and Figure 3 The illustrated embodiments can be combined. The access control information of the first control layer device not only indicates the object identifier with the permission to send control requests to the first control layer device, but also indicates the data range of preset fields in the control requests that can be sent to the first control layer device. Thus, controlling the control requests sent by the object to the first control layer device through the data range of the preset fields and the object identifier is equivalent to controlling the control requests sent by the object to the first control layer device through a range lock. For example, through a range lock, the data range of the preset fields is set, and as described above... Figure 3 The illustrated embodiment sets up a whitelist or blacklist, and uses the data range of the preset field and the whitelist or blacklist as the range defined by the range lock, and then controls the control requests sent by the object to the first control layer device according to the range defined by the range lock.

[0257] It should be noted that, in the above Figures 2 to 8 Based on the illustrated embodiments, in this application embodiment, when the management layer device receives a control request sent by the service layer device, it will first verify whether the destination device indicated by the control request is a control layer device that needs to verify the control request. The control request will only be verified if the destination device indicated by the received control request is a control layer device that needs to verify the control request. That is, the process of verifying the control request includes: if the first control layer device is the control layer device indicated by the device information, the first control request is verified based on the access control information to obtain the verification result, and the device information indicates the destination device indicated by the control request to be verified.

[0258] In this embodiment, the control system includes multiple control layer devices. There may be situations where control requests destined for certain control layer devices do not require verification. Therefore, the management layer device stores device information to indicate which control requests corresponding to which control layer devices require verification. Upon receiving a first control request, the management layer device queries the device information to determine if the first control layer device is the device indicated by the device information. If it is, the first control layer device is verified to obtain the verification result. In this way, by setting the device information, it is possible to specify which control requests corresponding to which control layer devices require verification, eliminating the need for the management layer device to verify all control requests, thus reducing its workload and improving its efficiency.

[0259] The destination device indicated by the control request can be any control layer device in the control system. Device information can be represented in any form, for example, in text form. Optionally, the device information includes identifiers of multiple control layer devices, and the identifiers in the device information indicate the destination device indicated by the control request to be verified.

[0260] Optionally, based on the identifier of the first control layer device carried in the first control request, a query is performed from the device information. If the identifier of the first control layer device is found, the first control request is verified based on the access control information to obtain the verification result.

[0261] Among them, the identification of the first control layer device can be found in the device information, indicating that the first control layer device is the control layer device indicated by the device information.

[0262] In one possible implementation, the control system further includes a second control layer device; the method further includes: a management layer device receiving a second control request sent by a service layer device, the second control request instructing the second control layer device to perform an operation; and the management layer device sending a second control request to the second control layer device when the second control layer device is not the control layer device indicated by device information.

[0263] In this embodiment of the application, the control system further includes a second control layer device. The second control layer device is not the destination device indicated by the control request to be verified. That is, when the management layer device receives a control request for the second control layer device, it does not need to verify the control request. Therefore, when the second control request is received, the second control request can be sent directly to the second control layer device without further verification of the second control request, thereby reducing the workload of the management layer device and improving the working efficiency of the management layer device.

[0264] Optionally, based on the identifier of the second control layer device carried in the second control request, a query is performed in the device information. If the identifier of the second control layer device is not found, a second control request is sent to the second control layer device.

[0265] If the identifier of the second control layer device cannot be found in the device information, it means that the second control layer device is not the control layer device indicated by the device information.

[0266] It should be noted that, in the above Figures 2 to 8 Based on the embodiments shown, in this embodiment, when the management layer device receives a control request sent by the service layer device, it will first determine whether to verify the control request according to the risk level of the interface indicated by the interface identifier carried in the control request. That is, the process of verifying the control request includes: if the risk level of the interface corresponding to the first control request is not lower than the second threshold, the management layer device verifies the first control request based on the access control information and obtains the verification result. The interface corresponding to the first control request is the interface indicated by the interface identifier carried in the first control request.

[0267] The first control request carries the interface identifier of the first control layer device, and the interface corresponding to the first control request is the interface indicated by the interface identifier carried in the first control request. The second threshold is any risk level; for example, the second threshold represents risk level 3.

[0268] In this embodiment, if the risk level of an interface is not lower than the second threshold, the interface is a high-risk interface; if the risk level of an interface is lower than the second threshold, the interface is a low-risk interface. When the management layer device receives a control request sent by the service layer device, it determines the risk level of the interface indicated by the interface identifier carried in the control request. The first control request will only be verified if the interface corresponding to the first control request is a high-risk interface. If the interface corresponding to the first control request is a low-risk interface, the first control request does not need to be verified. This reduces the workload of the management layer device and improves its efficiency.

[0269] Optionally, the management layer device stores a correspondence between interface identifiers and risk levels. Based on the interface identifier carried in the first control request, the management layer device queries the correspondence to obtain the risk level of the interface corresponding to the first control request.

[0270] In this embodiment of the application, different interfaces of the same control layer device have different interface identifiers, and interfaces of different control layer devices also have different interface identifiers. Therefore, based on the correspondence between interface identifiers and risk levels in the management layer device, the risk level of any interface identifier can be queried.

[0271] Optionally, the method further includes: when the risk level of the interface corresponding to the first control request is lower than a second threshold, the management layer device sends a first control request to the first control layer device.

[0272] In this embodiment, considering that control requests sent to low-risk interfaces may not have a significant impact on the operating status of the control layer device, there is no need to verify control requests for low-risk interfaces. Therefore, when the risk level of the interface corresponding to the first control request is lower than the second threshold, the management layer device determines that the interface corresponding to the first control request is a low-risk interface and directly sends the first control request to the first control layer device without further verification of the first control request, thereby reducing the workload of the management layer device and improving its working efficiency.

[0273] Based on the embodiments shown above, the management layer device will also detect the status of the first control layer device during the process of the first control layer device responding to the first control request, so as to ensure the normal operation of the first control layer device. That is, the method also includes the following two methods.

[0274] The first method involves the management layer device performing status detection on the first control layer device; if the first control layer device is in an abnormal state, the management layer device is controlled to stop responding to the first control request.

[0275] In this embodiment of the application, during the process of the first control layer device responding to the first control request, the first control layer device is subjected to state detection to detect whether the first control layer device is in an abnormal state. In order to ensure the normal operation of the first control layer device and the security and stability of the control layer device, the first control layer device can be controlled to stop responding to the first control request in a timely manner if the first control layer device is in an abnormal state.

[0276] Among them, abnormal states refer to situations such as the first control layer device being in a downtime state or the packet loss rate of the first control layer device being greater than the third threshold, where the third threshold is any value.

[0277] Optionally, the process of the management layer device performing status detection on the first control layer device includes: the management layer device sending a status detection command to the status detection device, the status detection command instructing the status detection of the first control layer device, the status detection device responding to the status detection command performing status detection on the first control layer device, obtaining the status of the first control layer device, and sending the status of the first control layer device to the management layer device.

[0278] In this embodiment, the state detection device is used to detect the state of the control layer device.

[0279] Optionally, the process of controlling the first control layer device to stop responding to the first control request includes: when the first control layer device is in an abnormal state, the management layer device generates a control command according to the control strategy, the control command instructs the first control layer device to stop responding to the first control request, and sends the control command to the first control layer device, and the first control layer device responds to the control command and stops responding to the first control request.

[0280] In this embodiment, the management layer device stores a control strategy. The control strategy instructs each control layer device how to generate control commands or what kind of control commands to generate in an abnormal state. Therefore, when the first control layer device is in an abnormal state, the management layer device generates control commands according to the control strategy and sends control commands to the first control layer device to control the first control layer device to stop responding to the first control request, ensuring the accuracy of the generated control commands, and thus enabling timely control of the first control layer device to ensure control accuracy and the normal operation of the first control layer device.

[0281] The second method is as follows: The management layer device performs status detection on the first control layer device; if the first control layer device is in an abnormal state, a rollback command is sent to the first control layer device, and the first control layer device responds to the rollback command and rolls back.

[0282] In this embodiment of the application, during the process of the first control layer device responding to the first control request, the first control layer device is subjected to state detection to detect whether the first control layer device is in an abnormal state. If the first control layer device is in an abnormal state, a rollback command is sent to the first control layer device to instruct the first control layer device to roll back in response to the rollback command, that is, to stop responding to the first control request and roll back the part that has already been responded to, so that the state of the first control layer device is restored to the state before responding to the first control request, thereby ensuring the normal operation of the first control layer device and ensuring the security and stability of the control layer device.

[0283] Optionally, the process of generating a rollback instruction includes: when the first control layer device is in an abnormal state, the management layer device generates a rollback instruction according to the control strategy.

[0284] In this embodiment, the management layer device stores a control policy. The control policy instructs each control layer device how to generate a rollback instruction or what kind of rollback instruction to generate in an abnormal state. Therefore, when the first control layer device is in an abnormal state, the management layer device generates a rollback instruction according to the control policy and sends the rollback instruction to the first control layer device to control the first control layer device to roll back, thereby eliminating the abnormal state of the first control layer device, ensuring the accuracy of the generated rollback instruction, and ensuring that the first control layer device can operate normally.

[0285] In this embodiment, the management layer device can detect the status of each control layer device in real time. Once a control layer device is in an abnormal state, it can control the control layer device to stop responding to the control request being executed, and can take fallback measures to control the execution device to roll back in order to eliminate the fault, so that the control layer device can restore the state before responding to the control request.

[0286] For example, by being familiar with the possible scenarios when various control layer devices execute different control requests, developers can also determine which data from the control layer devices can reveal their status. Based on these scenarios, they can manually configure control strategies and deploy them in the management layer devices. This allows the management layer devices to monitor the status of the control layer devices in real time and generate corresponding instructions, such as control commands or rollback commands, according to the control strategies when the control layer devices are in an abnormal state. This enables the control layer devices to eliminate the abnormal state and ensure their normal operation.

[0287] It should be noted that the above embodiments are illustrated by taking the control of the first control layer device by the service layer device as an example. In another embodiment, the control system includes multiple service layer devices, a management layer device, and multiple control layer devices. According to the above method, any service layer device can initiate a control request for any control layer device. And according to the method provided in the above embodiments, if the management layer device verifies the control request, it sends the control request to the control layer device so that the control layer device can respond to the control request.

[0288] It should be noted that the above Figures 2 to 8 The illustrated embodiments provide optional solutions that can be combined arbitrarily. Based on the above... Figures 2 to 8 The illustrated embodiments, combined with examples, provide a flowchart of a control method, taking a control layer device as a controller as an example, such as... Figure 9 As shown, the method includes:

[0289] Step 1: The service layer device calls the service entry point provided by the management layer device and sends a control request to the management layer device.

[0290] Among them, the business layer devices are the devices corresponding to the Netops (network management) process or third-party devices.

[0291] Step 2: After receiving the control request, the management layer device determines whether the controller indicated by the control request is the controller of the control request to be verified. If the controller indicated by the control request is the controller of the control request to be verified, proceed to step 3. If the controller indicated by the control request is not the controller of the control request to be verified, the management layer device sends the control request to the controller indicated by the control request.

[0292] Step 3: The management layer device determines the risk level of the interface indicated by the interface identifier carried in the control request. If the interface indicated by the interface identifier is a low-risk interface, the management layer device sends the control request to the controller indicated by the control request. If the interface indicated by the interface identifier is a high-risk interface, the management layer device executes Step 4.

[0293] Step 4: Management equipment as described above Figures 2 to 8 In the illustrated embodiment, based on the access control information of the controller indicated by the control request, it verifies whether the object initiating the control request has the permission to send the control request to the controller, and performs the verification according to the quantity lock, frequency lock and range lock mentioned above. If the control request passes the verification, the control request is sent to the controller indicated by the control request.

[0294] In this embodiment, the constructed management layer device consolidates the northbound interfaces of each controller in the control system. When a business layer device sends a control request to a controller, the management layer device can first obtain the control request sent by the business layer device. At this time, the controller cannot receive the control request sent by the business layer device. If the management layer device verifies the control request, it forwards the control request to the corresponding controller. Only then can the controller receive the control request sent by the business layer device. In this way, the business layer device cannot directly call the controller's interface. The management layer device consolidates the northbound interfaces of each controller in the control system, and can perform security verification on control requests that call high-risk interfaces, thus ensuring the security of the control layer device.

[0295] Based on the embodiments shown above, this application provides a schematic diagram of a control system, as follows: Figure 10 As shown, the controller is taken as an example of a control layer device.

[0296] The management layer device provides a service entry point for the service layer devices, enabling them to send control requests to the management layer device. Furthermore, the management layer device can schedule operation dashboards to display the status of control requests sent by each service layer device to each controller. The management layer device deploys a service security layer, an interface layer, and a business logic arrangement; the business logic arrangement stores access control information for each controller.

[0297] The management layer devices, through the interface layer, can obtain access control information from each controller from the business logic arrangement, as described above. Figures 2 to 8The embodiment shown can verify the control request received at the service entry point. The verification process includes permission management, operation frequency limiting, grayscale control or security checks. If the control request passes verification, the control request is sent to the controller indicated by the control request.

[0298] The management layer devices connect to the traffic light system, which can monitor the status of each controller in real time. The management layer devices can obtain the status of each controller from the traffic light system through the business security layer, or detect the status of each controller through the business security layer. The business security layer stores control policies (EOPs), enabling the management layer devices to generate corresponding instructions, such as control commands or rollback commands, according to the control policies when any controller is in an abnormal state. This allows the control layer devices to eliminate the abnormal state and ensure the normal operation of the control layer devices.

[0299] Furthermore, the management layer devices connect to the Perm (a management system) system, allowing administrators to access the Perm system and configure access control information for each controller within the business logic structure. The configuration process is as follows: Figure 11 As shown, the Perm system is used to manage the SDK (Software Development Kit) permission management module in order to configure access control information for each controller.

[0300] Furthermore, the management layer devices and the NC (Internal Control Unit) change system can create or modify access control information for the devices at the control layer through the NC change system.

[0301] Building upon the embodiments described above, the interface layer in the management layer device performs security control over the various interfaces of the controller. For example, it checks whether the business layer devices' calls to the controller's interfaces are compliant (limiting the permissions of objects that can call the controller's interfaces, or whether quantity locks, frequency locks, and range locks are satisfied). Business layer devices no longer directly call the controller's interfaces; instead, they uniformly call the business entry point (SDK / general node) provided by the management layer device. The management layer device consolidates the controller's northbound interfaces, integrating capabilities such as permission management, security checks, and canary deployments into a unified business entry point, thereby ensuring the secure and controllable use of the controller's interfaces by business layer devices. Specifically, permission control and security control ensure the security of the controller interfaces. Permission control is responsible for controlling which object has access permissions to which interface of which controller; that is, indicating which object can control which controller to perform which operations. For example, if the object is an automation tool such as fault self-healing / automatic tuning, the automation tool can only use some scheduling functions of the fine-grained controller, such as the fine-grained inbound static scheduling function of the fine-grained controller. Security control involves controlling three security locks: quantity lock, frequency lock, and range lock. It is represented by the correspondence between object identifier, controller identifier, and request type (equivalent to operation type). If the northbound interface of a controller is empty, the default restriction configuration when the northbound interface is empty will be used for management. For example, "Object1 + Fine-grained Controller + Fine-grained Inbound Static Scheduling" means that Object1 has the permission for fine-grained inbound static scheduling of the fine-grained controller.

[0302] Furthermore, in this embodiment, an object may have multiple roles, meaning an object may have multiple identities, and constraints exist between different roles. Higher-level roles have more permissions, while lower-level roles can only inherit a portion of the permissions held by the higher-level roles. For example, in a department, department managers have more permissions, while ordinary employees in the department have only a portion of the permissions held by the department managers. Configuring access control information for each controller according to RBAC allows for configuration based on role hierarchy and constraints between roles. Figure 12 As shown, RBAC0 is at a lower level than RBAC1 and RBAC2, RBAC1 is at a lower level than RBAC3, and RBAC2 can constrain RBAC3. Furthermore, by configuring the roles and permissions of each object, the permissions possessed by each object are reflected, such as... Figure 12 As shown, object identifier 1 has the role indicated by role identifier 1, and role identifier 1 corresponds to permission 1. Therefore, the object indicated by object identifier 1 has permission 1. This configuration method can ensure the convenience of configuring access control information.

[0303] In the above Figures 2 to 8Based on the embodiments shown, this application provides a flowchart of a control method, taking a control layer device as a controller as an example, such as... Figure 13 As shown, the method includes:

[0304] Step 1: Operation and management personnel trigger business operations through business layer devices. Business layer devices can display a front-end interface. Through the front-end interface displayed by the operation and management personnel, relevant parameters can be configured, such as controller parameters, request types, interface parameters, etc. Controller parameters indicate which controller is being controlled, request types indicate what type of control request is being sent to the controller, and also reflect what type of operation is being instructed to be performed by the controller, and interface parameters indicate which interface of the controller is being called, etc.

[0305] The front-end interface is equivalent to the interface of the operation front-end.

[0306] Step 2: The service layer device responds to the confirmation operation in the front-end interface by sending the parameters configured in the front-end interface to the network management (Netops) device.

[0307] Step 3: The network management device performs a frequency limiting check on the control requests to restrict the frequency at which the control system initiates control requests. If the frequency limiting check passes, a control request is generated based on the parameters configured in the front-end interface sent by the service layer device. If the control request instructs other service processes, the network management device executes those other service processes according to the control request. If the control request instructs a controller in the control system to perform an operation, the network management device sends the control request to the interface layer in the management layer device.

[0308] Step 4: The interface layer in the management layer receives the control request and performs a validity check on the identifier or other information carried in the control request to ensure the format of the information is accurate. If the validity check of the control request passes, proceed as described above. Figures 2 to 8 The illustrated embodiment performs permission verification on the control request, and performs verification based on range lock, quantity lock, and frequency lock; if the verification passes, the control request is sent to the gateway layer device; furthermore, the interface layer can also store the control request so that the stored control request can be used to verify newly received control requests in the future.

[0309] Among them, the fallback check is equivalent to the verification process corresponding to the frequency lock, the grayscale check is equivalent to the verification corresponding to the range lock, and the fatal risk check indicates the check of the configured risk type, such as checking the risk level of the interface called by the control request, or checking whether the control request will cause the controller to malfunction.

[0310] Step 5: When the gateway layer device receives a control request, it performs frequency limiting detection on the interface address indicated by the control request. If the frequency limiting detection of the interface address passes, it calls the interface of the first control layer device according to the interface address indicated by the control request and sends the control request to that interface.

[0311] Step 6: The controller receives the control request, responds to the control request, obtains the response result, and sends the response result to the gateway layer device.

[0312] Step 7: The gateway layer device receives the response result and sends the response result to the interface layer.

[0313] Step 8: The interface layer in the management device receives the response result and sends the response result to the network management device. In addition, the interface layer can also store the response result and the corresponding control request so as to view the historical control requests and response results later, so as to ensure that the controller can be rolled back in the future.

[0314] Step 9: The network management device receives the response result and sends the response result to the service layer device, which then receives and displays the response result.

[0315] Based on the embodiments described above, administrators can configure the risk level of controller interfaces and set corresponding control policies for high-risk interfaces to ensure the security of calls to these interfaces. Furthermore, when any control request points to any high-risk interface, the control request will only be sent to the high-risk interface if the request passes verification, preventing business layer devices from arbitrarily calling controller interfaces and sending control requests to them. The process for configuring the risk level of a control interface is as follows: Figure 14 As shown, when an administrator initiates a new request or a modification request through the device, the new request indicates that a risk level be configured for a certain interface of a certain controller, and the modification request indicates that the risk level of a certain interface be modified. This is equivalent to initiating an approval process. After other relevant personnel review and approve the approval process, the new request or modification request becomes effective. That is, the risk level of a certain interface of a certain controller is successfully configured, or the modification request indicates that the risk level of a certain interface is successfully modified.

[0316] In this embodiment, for controllers involving high-risk interfaces, corresponding access control information is configured to establish user access permissions for controllers including high-risk interfaces. The process for configuring access permissions is as follows: Figure 15As shown, both regular users and administrators can configure permissions for controllers. Regular users can manage their own permissions, such as requesting additional access to a specific controller's interface. Regular users can only view their own assigned permission role configuration. They can adjust permissions for their assigned role, triggering an approval process that requires product team approval to take effect. Administrators, on the other hand, are responsible for managing the permissions of all users for each controller globally, triggering an approval process that requires review and approval by other relevant personnel before taking effect.

[0317] In this embodiment, security control configuration involves setting quantity locks, frequency locks, and range locks for each role or controller. This method allows for security checks on controllers, including those with high-risk interfaces. The security control configuration process is as follows: Figure 16 As shown, regular users can only view the security control configurations available to their own roles, while administrators can view all security control configurations. Administrators and the product team are responsible for creating and adjusting security control configurations. When an administrator creates or modifies a security control configuration, an approval process is triggered, and the configuration takes effect only after being reviewed and approved by other relevant personnel.

[0318] In the above Figure 14 and Figure 16 Based on the illustrated embodiment, the parameter center can be configured for various controllers, such as... Figure 17 The configuration shown specifies the interface risk level, data lock, frequency lock, and range lock for each controller. This ensures that after configuration, each controller can be applied to various business scenarios, such as operational or system maintenance scenarios, while guaranteeing controller security. Ordinary interfaces are low-risk interfaces, and high-risk interfaces are high-risk interfaces.

[0319] Furthermore, in this embodiment of the application, the administrator can also base their decisions on, for example... Figure 18 The configuration interface shown allows you to configure the scheduling operations available to each group or section. This includes configuring node type, task type, task name, task description, and request information such as the controller, the type of operation the controller performs, and the controller's API (Application Programming Interface) name. After configuring as described above, a convenient entry point is provided for subsequent scheduling controller operations. When users schedule the controller through business-side devices, the business-layer device will display this convenient entry point on the front-end interface for users to select, eliminating the need for manual data input and ensuring the convenience of the scheduling controller.

[0320] The solution provided in this application embodiment implements unified access control and three-lock (quantity lock, frequency lock, and range lock) security checks for controller access. It supports the business control security requirements compiled by various controller product teams, ensuring the security of upper-layer business calls to controller interfaces. By setting quantity locks, frequency locks, and range locks for high-risk controller interfaces, the security of high-risk interfaces is guaranteed. Unified orchestration of controller services provides unified orchestration capabilities for various types of controllers, standardizing operational processes to achieve complete coverage of all controller business scenarios. This improves operational quality and efficiency, provides a unified safety net for controller behavior, and completes the operational control of controllers, successfully realizing a standardized process for controlled and standardized calls to controllers for business operations.

[0321] In this embodiment, unified security management is implemented for the basic network controller, and the controller scheduling access process is standardized. By accessing systems such as AAA (Authentication Authorization Auditing), traffic light system, Ngate (a type of gateway), and Netops, the security management of the distributed controller in the basic network is realized.

[0322] Figure 19 This is a schematic diagram of the structure of a control system provided in an embodiment of this application, such as... Figure 19 As shown, the control system includes a business layer device 1901, a management layer device 1902, and a first control layer device 1903;

[0323] Management layer device 1902 is used to receive a first control request sent by service layer device 1901, the first control request instructing first control layer device 1903 to perform an operation;

[0324] Management layer device 1902 is used to verify a first control request based on access control information of first control layer device 1903 and obtain a verification result. The access control information indicates at least one of the following: an object that can send a control request to first control layer device 1903 or a control request that can be sent to first control layer device 1903. The object is the object indicated by the object identifier logged by the device that sent the control request.

[0325] Management layer device 1902 is used to send a first control request to first control layer device 1903 when the verification result indicates that the first control request satisfies the access control information;

[0326] First control layer device 1903 is used to respond to a first control request.

[0327] In one possible implementation, the first control request carries the object identifier of the service layer device 1901 that is logged in, and the access control information includes the object identifier that can send the control request to the first control layer device 1903.

[0328] Management device 1902 is used to query access control information based on the object identifier carried in the first control request; if the access control information includes the object identifier carried in the first control request, a first verification result is obtained, indicating that the first control request satisfies the access control information; if the access control information does not include the object identifier carried in the first control request, a second verification result is obtained, indicating that the first control request does not satisfy the access control information.

[0329] In another possible implementation, the first control request carries the object identifier of the service layer device 1901 that is logged in, and the access control information includes object information corresponding to the object that can send a control request to the first control layer device 1903;

[0330] The management layer device 1902 is used to obtain object information corresponding to the first control request based on the object identifier carried in the first control request, wherein the object information corresponding to the first control request describes the object indicated by the carried object identifier; to verify the object information corresponding to the first control request based on the object information in the access control information; if the matching degree between the object information corresponding to the first control request and the object information in the access control information is not less than a first threshold, a first verification result is obtained, wherein the first verification result indicates that the first control request satisfies the access control information; if the matching degree between the object information corresponding to the first control request and the object information in the access control information is less than the first threshold, a second verification result is obtained, wherein the second verification result indicates that the first control request does not satisfy the access control information.

[0331] In another possible implementation, the access control information includes the request type of a control request that can be sent to the first control layer device 1903; the management layer device 1902 is configured to query the access control information based on the request type of the first control request; if the access control information includes the request type of the first control request, a first verification result is obtained, indicating that the first control request satisfies the access control information; if the access control information does not include the request type of the first control request, a second verification result is obtained, indicating that the first control request does not satisfy the access control information.

[0332] In another possible implementation, the first control request carries the object identifier of the service layer device 1901 that is logged in. The access control information includes the correspondence between the object identifier and the request type. The correspondence indicates the object identifier that can send a control request to the first control layer device and the request type that the object identifier can send a control request to. The management layer device 1902 is used to query the access control information based on the request type of the first control request and the object identifier carried in the first control request. If the access control information includes the correspondence between the request type of the first control request and the object identifier carried in the first control request, a first verification result is obtained.

[0333] In another possible implementation, the first control request carries the interface identifier of the first control layer device 1903; the access control information indicates the interface identifier that the first control layer device 1903 can access; the management layer device 1902 is used to query the access control information based on the interface identifier carried in the first control request; if the access control information includes the interface identifier carried in the first control request, a first verification result is obtained, indicating that the first control request satisfies the access control information; if the access control information does not include the interface identifier carried in the first control request, a second verification result is obtained, indicating that the first control request does not satisfy the access control information.

[0334] In another possible implementation, the access control information includes a preset number of times an object can send control requests to the first control layer device 1903; the management layer device 1902 is used to verify the first control request based on the access control information and the historical request information of the initiating object, wherein the initiating object is the object indicated by the object identifier logged in by the management layer device 1902, and the historical request information indicates the historical control requests sent by the initiating object to the first control layer device 1903; if the number of control requests sent by the initiating object to the first control layer device 1903 is less than the preset number corresponding to the initiating object, a first verification result is obtained, indicating that the first control request satisfies the access control information; if the number of control requests sent by the initiating object to the first control layer device 1903 is not less than the preset number corresponding to the initiating object, a second verification result is obtained, indicating that the first control request does not satisfy the access control information.

[0335] In another possible implementation, the preset number is the number of times an object can send control requests to the first control layer device 1903 in a single cycle; the management layer device 1902 is used to obtain a first verification result when the number of control requests sent by the initiating object to the first control layer device 1903 in the current cycle is less than the preset number corresponding to the initiating object.

[0336] In another possible implementation, the access control information indicates the data range of a preset field in a control request that can be sent to the first control layer device 1903; the management layer device 1902 is used to verify the data of the preset field in the first control request based on the data range of the preset field in the access control information; if the data of the preset field in the first control request falls within the data range, a first verification result is obtained, indicating that the first control request satisfies the access control information; if the data of the preset field in the first control request does not fall within the data range, a second verification result is obtained, indicating that the first control request does not satisfy the access control information.

[0337] In another possible implementation, the management layer device 1902 is used to verify the first control request based on access control information when the first control layer device 1903 is a control layer device indicated by device information, and obtain a verification result. The device information indicates the destination device indicated by the control request to be verified.

[0338] In another possible implementation, the control system also includes a second control layer device;

[0339] The management layer device 1902 is also configured to receive a second control request sent by the service layer device 1901, the second control request instructing the second control layer device to perform an operation; and to send a second control request to the second control layer device if the second control layer device is not the control layer device indicated by the device information.

[0340] In another possible implementation, the first control request carries the interface identifier of the first control layer device 1903; the management layer device 1902 is used to verify the first control request based on access control information, and obtain the verification result, provided that the risk level of the interface corresponding to the first control request is not lower than the second threshold, and the interface corresponding to the first control request is the interface indicated by the interface identifier carried by the first control request.

[0341] In another possible implementation, the management layer device 1902 is also used to send a first control request to the first control layer device 1903 when the risk level of the interface corresponding to the first control request is lower than the second threshold.

[0342] In another possible implementation, the management layer device 1902 is also used to perform status detection on the first control layer device 1903; if the first control layer device 1903 is in an abnormal state, control the first control layer device 1903 to stop responding to the first control request; or, if the first control layer device 1903 is in an abnormal state, send a rollback command to the first control layer device 1903, and the first control layer device 1903 rolls back in response to the rollback command.

[0343] This application also provides a computer device, wherein the business layer device, management layer device, or control layer device in the above embodiments is a computer device, the computer device includes a processor and a memory, the memory stores at least one computer program, the at least one computer program is loaded and executed by the processor to implement the operations performed by the business layer device, management layer device, or control layer device in the control method of the above embodiments.

[0344] Optionally, the computer device is provided as a terminal. Figure 20 A structural block diagram of a terminal 2000 provided in an exemplary embodiment of this application is shown. The terminal 2000 includes a processor 2001 and a memory 2002.

[0345] Processor 2001 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 2001 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 2001 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 2001 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 2001 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0346] The memory 2002 may include one or more computer-readable storage media, which may be non-transitory. The memory 2002 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices.

[0347] In some embodiments, the terminal 2000 may also optionally include a peripheral device interface 2003 and at least one peripheral device. The processor 2001, memory 2002, and peripheral device interface 2003 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 2003 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: radio frequency circuitry 2004, display screen 2005, camera assembly 2006, audio circuitry 2007, and power supply 2008.

[0348] Peripheral device interface 2003 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 2001 and memory 2002. In some embodiments, processor 2001, memory 2002 and peripheral device interface 2003 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 2001, memory 2002 and peripheral device interface 2003 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0349] The radio frequency (RF) circuit 2004 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 2004 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 2004 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 2004 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 2004 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 2004 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0350] Display screen 2005 is used to display a UI (User Interface). This UI may include graphics, text, icons, video, and any combination thereof. When display screen 2005 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 2001 for processing. In this case, display screen 2005 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 2005, disposed on the front panel of terminal 2000; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal 2000 or in a folded design; in still other embodiments, display screen 2005 may be a flexible display screen, disposed on a curved or folded surface of terminal 2000. Furthermore, display screen 2005 may also be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 2005 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0351] The camera assembly 2006 is used to acquire images or videos. Optionally, the camera assembly 2006 includes a front-facing camera and a rear-facing camera. The front-facing camera is disposed on the front panel of the terminal, and the rear-facing camera is disposed on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 2006 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0352] The audio circuit 2007 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 2001 for processing, or to the radio frequency circuit 2004 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 2000. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 2001 or the radio frequency circuit 2004 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 2007 may also include a headphone jack.

[0353] Power supply 2008 is used to power the various components in terminal 2000. Power supply 2008 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 2008 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0354] Those skilled in the art will understand that Figure 20 The structure shown does not constitute a limitation on the terminal 2000, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0355] Optionally, the computer equipment is provided as a server. Figure 21 This is a schematic diagram of a server structure provided in an embodiment of this application. The server 2100 can vary significantly due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 2101 and one or more memories 2102. The memories 2102 store at least one computer program, which is loaded and executed by the processor 2101 to implement the methods provided in the above-described method embodiments. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated upon here.

[0356] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0357] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present application should be included within the protection scope of the present application.

Claims

1. A control method characterized by, The method is applied to a control system, the control system comprising a service layer device, a management layer device and a first control layer device; the method comprising: The management layer device receives a first control request sent by the service layer device, the first control request indicating the first control layer device to perform an operation; The management layer device checks the first control request based on access control information of the first control layer device, to obtain a checking result, the access control information indicating at least one of an object capable of sending a control request to the first control layer device or a control request capable of being sent to the first control layer device, the object being an object indicated by an object identifier of a device sending a control request; The management layer device sends the first control request to the first control layer device in a case where the checking result indicates that the first control request satisfies the access control information; The first control layer device responds to the first control request.

2. The method of claim 1, wherein, The first control request carries an object identifier of the service layer device logging in, and the access control information comprises an object identifier capable of sending a control request to the first control layer device; The management layer device checks the first control request based on access control information of the first control layer device, to obtain a checking result, comprising: The management layer device queries the access control information based on the object identifier carried by the first control request; The management layer device obtains a first checking result in a case where the access control information comprises the object identifier carried by the first control request, the first checking result indicating that the first control request satisfies the access control information; The management layer device obtains a second checking result in a case where the access control information does not comprise the object identifier carried by the first control request, the second checking result indicating that the first control request does not satisfy the access control information.

3. The method of claim 1, wherein, The first control request carries an object identifier of the service layer device logging in, and the access control information comprises object information corresponding to an object capable of sending a control request to the first control layer device; The management layer device checks the first control request based on access control information of the first control layer device, to obtain a checking result, comprising: The management layer device acquires object information corresponding to the first control request based on the object identifier carried by the first control request, the object information corresponding to the first control request being used to describe an object indicated by the object identifier; The management layer device checks the object information corresponding to the first control request based on object information in the access control information; The management layer device obtains a first checking result in a case where a matching degree between the object information corresponding to the first control request and the object information in the access control information is not less than a first threshold, the first checking result indicating that the first control request satisfies the access control information; The management layer device obtains a second check result in a case where a matching degree between the object information corresponding to the first control request and the object information in the access control information is less than the first threshold value, and the second check result indicates that the first control request does not satisfy the access control information.

4. The method of claim 1, wherein, The access control information includes a request type of a control request that can be sent to the first control layer device. The management layer device checks the first control request based on the access control information of the first control layer device, and obtains a check result, including: The management layer device queries the access control information based on the request type of the first control request; The management layer device obtains a first check result in a case where the access control information includes the request type of the first control request, and the first check result indicates that the first control request satisfies the access control information; The management layer device obtains a second check result in a case where the access control information does not include the request type of the first control request, and the second check result indicates that the first control request does not satisfy the access control information.

5. The method of claim 4, wherein, The first control request carries an object identifier of the service layer device login, and the access control information includes a corresponding relationship between an object identifier and a request type, and the corresponding relationship indicates an object identifier that can send a control request to the first control layer device and a request type of the object identifier that can send a control request; The management layer device queries the access control information based on the request type of the first control request, including: The management layer device queries the access control information based on the request type of the first control request and the object identifier carried by the first control request; The management layer device obtains a first check result in a case where the access control information includes the request type of the first control request, including: The management layer device obtains the first check result in a case where the access control information includes the corresponding relationship between the request type of the first control request and the object identifier carried by the first control request.

6. The method of claim 1, wherein, The first control request carries an interface identifier of the first control layer device; and the access control information indicates an interface identifier of the first control layer device that can be accessed. The management layer device checks the first control request based on the access control information of the first control layer device, and obtains a check result, including: The management layer device queries the access control information based on the interface identifier carried by the first control request; The management layer device obtains a first check result in a case where the access control information includes the interface identifier carried by the first control request, and the first check result indicates that the first control request satisfies the access control information; The management layer device obtains a second check result in a case where the access control information does not include the interface identifier carried by the first control request, and the second check result indicates that the first control request does not satisfy the access control information.

7. The method of claim 1, wherein, The access control information comprises a preset number of times that an object can send a control request to the first control layer device; The management layer device checks the first control request based on the access control information of the first control layer device, and obtains a checking result, comprising: The management layer device checks the first control request based on the access control information and historical request information of an initiating object, wherein the initiating object is indicated by an object identifier logged in the management layer device, and the historical request information indicates historical control requests sent by the initiating object to the first control layer device; The management layer device obtains a first checking result in a case where the number of control requests sent by the initiating object to the first control layer device is less than the preset number of times corresponding to the initiating object, wherein the first checking result indicates that the first control request satisfies the access control information; The management layer device obtains a second checking result in a case where the number of control requests sent by the initiating object to the first control layer device is not less than the preset number of times corresponding to the initiating object, wherein the second checking result indicates that the first control request does not satisfy the access control information.

8. The method of claim 7, wherein, The preset number of times is the number of control requests that an object can send to the first control layer device in a single period; and the management layer device obtains a first checking result in a case where the number of control requests sent by the initiating object to the first control layer device is less than the preset number of times corresponding to the initiating object, comprising: The management layer device obtains the first checking result in a case where the number of control requests sent by the initiating object to the first control layer device in a current period is less than the preset number of times corresponding to the initiating object.

9. The method of claim 1, wherein, The access control information indicates a data range of a preset field in a control request that can be sent to the first control layer device; The management layer device checks the first control request based on the access control information of the first control layer device, and obtains a checking result, comprising: The management layer device checks data of the preset field in the first control request based on the data range of the preset field in the access control information; The management layer device obtains a first checking result in a case where the data of the preset field in the first control request belongs to the data range, wherein the first checking result indicates that the first control request satisfies the access control information; The management layer device obtains a second checking result in a case where the data of the preset field in the first control request does not belong to the data range, wherein the second checking result indicates that the first control request does not satisfy the access control information.

10. The method of claim 1, wherein, The management layer device checks the first control request based on the access control information of the first control layer device, and obtains a checking result, comprising: The management layer device checks the first control request based on the access control information in a case where the first control layer device is a control layer device indicated by device information, wherein the device information indicates a destination device indicated by the first control request.

11. The method of claim 10, wherein, The control system further comprises a second control layer device; and the method further comprises: The management layer device receives a second control request sent by the service layer device, and the second control request indicates that a second control layer device performs an operation; The management layer device sends the second control request to the second control layer device in a case where the second control layer device is not the control layer device indicated by the device information.

12. The method of claim 1, wherein, The first control request carries an interface identifier of the first control layer device; The management layer device checks the first control request based on access control information of the first control layer device, and obtains a checking result, including: In a case where a risk level of an interface corresponding to the first control request is not lower than a second threshold, the management layer device checks the first control request based on the access control information, and obtains the checking result, the interface corresponding to the first control request being an interface indicated by an interface identifier carried by the first control request.

13. The method of claim 12, wherein, After the management layer device receives the first control request sent by the service layer device, the method further comprises: The management layer device sends the first control request to the first control layer device in a case where a risk level of an interface corresponding to the first control request is lower than the second threshold.

14. The method of claim 1, wherein, After the management layer device sends the first control request to the first control layer device in a case where the checking result indicates that the first control request satisfies the access control information, the method further comprises: The management layer device detects a state of the first control layer device; In a case where the first control layer device is in an abnormal state, the management layer device controls the first control layer device to stop responding to the first control request, or sends a rollback instruction to the first control layer device in a case where the first control layer device is in an abnormal state, and the first control layer device responds to the rollback instruction to perform rollback.

15. A control system characterized by, The control system comprises a service layer device, a management layer device and a first control layer device; The management layer device receives a first control request sent by the service layer device, and the first control request indicates that the first control layer device performs an operation; The management layer device checks the first control request based on access control information of the first control layer device, and obtains a checking result, the access control information indicating at least one of an object to which a device sending a control request logs in or a control request that can be sent to the first control layer device, the object being an object indicated by an object identifier of the device sending the control request; The management layer device sends the first control request to the first control layer device in a case where the checking result indicates that the first control request satisfies the access control information; The first control layer device responds to the first control request.

Images