Access method of a computing device, computing cluster and computing device

Abstract

Embodiments of the present application provide an access method of a computing device, a computing cluster and a computing device. The access method of the computing device is applied to a first computing device, and is used for receiving data corresponding to a second computing device. The access method of the computing device comprises: receiving an authentication result of the second computing device; the authentication result is generated by an authentication system, and comprises an authentication level and a data template; the data template is obtained by matching device identification information of the second computing device from a preset knowledge base, and is executable logic used for automatically analyzing interface information of the second computing device to output target interface information; based on the authentication level and the data template, a target data template corresponding to the second computing device is determined; based on the target data template, target interface information of the second computing device is obtained; and based on the target interface information, a connection with the second computing device is established. By using the above method, the interface information of the second computing device can be automatically analyzed through the authentication level and the data template, without the need to separately develop adaptation codes for different devices, so that quick access is realized, and the access efficiency of the computing device is effectively improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for accessing a computing device, a computing cluster, and a computing device. Background Technology

[0002] Centralized architectures typically employ a "central platform + computing devices" model. In this architecture, the central platform authenticates the computing devices to be connected. If authentication is successful, the computing device can be managed by the central platform and perform subsequent tasks.

[0003] However, in the existing access methods for computing devices, after the computing device is authenticated by the central platform, it still needs to rely on manual development and static configuration to obtain its interface information, which leads to low efficiency in accessing computing devices. Summary of the Invention

[0004] This application provides a method for accessing computing devices, a computing cluster, and computing devices. By using authentication levels and data templates, the interface information of a second computing device can be automatically parsed without the need to develop separate adaptation code for different computing devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions: In a first aspect, embodiments of this application provide a method for accessing a computing device, applied to a first computing device, for receiving data corresponding to a second computing device. The method includes: receiving an authentication result for the second computing device; the authentication result is generated by an authentication system and includes an authentication level and a data template; the data template is executable logic obtained by matching the device identification information of the second computing device from a preset knowledge base, used to automatically parse the interface information of the second computing device to output target interface information; determining a target data template corresponding to the second computing device based on the authentication level and the data template; obtaining target interface information of the second computing device based on the target data template; and establishing a connection with the second computing device based on the target interface information.

[0006] Based on this scheme, the first computing device receives the authentication result (authentication level and data template) returned by the authentication system. This data template, dynamically matched with the device identification information of the second computing device from a pre-defined knowledge base, forms an executable logical form. This allows the first computing device to automatically identify and parse the interface information of the second computing device, thus enabling computing device access. In this way, the entire computing device access process requires no manual code modification. Since the data template is a universal parsing logic carrier, when a new type of computing device is accessed, its corresponding data template is obtained from the knowledge base, eliminating the need to write separate code for each type of computing device. This achieves rapid access and effectively improves the access efficiency of computing devices.

[0007] In one possible implementation, the target data template corresponding to the second computing device is determined based on the authentication level and the data template, including: when the authentication level is the first level, the data template is used as the target data template.

[0008] Based on this scheme, for second-level computing devices at the first level, the data template provided by the authentication system can be directly used as the target data template for interface parsing without additional processing. Even if the computing device does not support standard management protocols such as Redfish, it can effectively improve the access efficiency of the computing device. At the same time, by linking the authentication level with the data template, differentiated access processing mechanisms can be implemented for computing devices with different authentication levels, thereby achieving fine-grained control over the computing device access process.

[0009] In another possible implementation, the target data template corresponding to the second computing device is determined based on the authentication level and the data template, including: receiving a new authentication result for the second computing device when the authentication level is the second level; the new authentication result includes the updated authentication level and the target data template; wherein the target data template includes a supplementary data template and a data template.

[0010] Based on this scheme, for second-level computing devices, their data templates can be dynamically expanded through supplementary authentication. The target data template obtained by combining the dynamic data template with the data template provided by the authentication system is used for interface parsing. This allows for on-demand enhancement of interface parsing capabilities and effectively addresses access difficulties caused by computing devices not supporting standard management protocols such as Redfish or insufficient initial authentication information, thus significantly improving the access efficiency of computing devices. Furthermore, by linking authentication levels with data templates, differentiated access processing mechanisms can be implemented for computing devices with different authentication levels, thereby achieving fine-grained control over the computing device access process.

[0011] In another possible implementation, after obtaining the authentication result for the second computing device, the method further includes: if the authentication level is level two, obtaining the target interface information of the second computing device based on the communication connection between the operating systems of the first and second computing devices; and connecting the target device to the first computing device based on the target interface information.

[0012] Based on this scheme, even if a second-level computing device does not support standard management protocols such as Redfish, it can still obtain its interface information and achieve basic access capabilities through the communication connection established between the first computing device and its operating system. This effectively compensates for the coverage blind spots of unknown or non-standard devices when relying solely on pre-set data templates, significantly improving compatibility with heterogeneous or edge devices while maintaining system security boundaries.

[0013] In another possible implementation, before obtaining the authentication result for the second computing device, the method further includes: obtaining the device identification information of the second computing device; querying the authentication status of the second computing device based on the device identification information; the authentication status is used to indicate whether the second computing device has completed authentication; and if the second computing device has not completed authentication, generating alarm information to indicate that the second computing device is in an unauthenticated state.

[0014] Based on this scheme, the first computing device can quickly determine the authentication status of the second computing device through device identification information at the initial stage of access and promptly alert to unauthenticated computing devices. In this way, unauthenticated computing devices can be identified at the beginning of the computing device access process, effectively preventing unauthenticated computing devices from being mistakenly accessed, thereby strengthening the security boundary of access and providing a foundation for subsequent computing device access.

[0015] Secondly, this application also provides another method for accessing a computing device, applied to an authentication system, for authenticating the identity of a second computing device. The method includes: obtaining device identification information of the second computing device; matching a corresponding data template from a preset knowledge base based on the device identification information; and generating an authentication result for the second computing device based on the data template, so that a first computing device can perform an access operation for the second computing device based on the authentication result. The authentication result includes an authentication level and a data template. The data template is executable logic obtained by matching the device identification information of the second computing device from a preset knowledge base, used to automatically parse the interface information of the second computing device to output target interface information.

[0016] Based on this scheme, the authentication system obtains the device identification information of the second computing device and intelligently matches and outputs a structured authentication result, namely the authentication level and data template, based on the device identification. In this way, it realizes the reliable verification of the device identity and also provides executable logic that can be used to automatically parse its interface information. The first computing device does not need to pre-build adaptation code, and can complete the automatic access of the device based on the authentication result, effectively improving the access efficiency of computing devices.

[0017] In one possible implementation, obtaining the device identification information of the second computing device includes: receiving alarm information sent by the first computing device; the alarm information including the device identification information of the second computing device; or, in response to a user's input operation, obtaining the device identification information of the second computing device.

[0018] Based on this scheme, the authentication system can obtain device identification information in two ways: passively responding to unauthenticated device alarms reported by the first computing device to automatically trigger the authentication process, and also supporting maintenance personnel to actively initiate authentication requests for specific devices. In this way, the system can obtain device identification information in two ways, taking into account the flexibility of automated processing and manual intervention, and effectively improving the timeliness of the authentication system's response.

[0019] In one possible implementation, after generating the authentication result of the second computing device based on the data template, the method further includes: if the authentication level is the second authentication level, obtaining a supplementary data template matching the second computing device from a preset knowledge base, merging the supplementary data template with the data template to obtain a target data template; and generating a new authentication result for the second computing device based on the target data template.

[0020] Based on this scheme, the authentication system can dynamically add data template content according to the authentication level of the computing device to form a complete data template. In the case of insufficient initial authentication information or incomplete verification of device capabilities, the interface parsing capabilities can be expanded on demand by introducing supplementary templates. In this way, the authentication results are always matched with the actual capabilities of the device, which significantly improves the access efficiency of computing devices.

[0021] Thirdly, embodiments of this application provide an access device for a computing device, comprising: a receiving module for receiving an authentication result for a second computing device; the authentication result is generated by an authentication system and includes an authentication level and a data template; the data template is executable logic obtained by matching the device identification information of the second computing device from a preset knowledge base, used to automatically parse the interface information of the second computing device to output target interface information; a determining module for determining a target data template corresponding to the second computing device based on the authentication level and the data template; a first obtaining module for obtaining the target interface information of the second computing device based on the target data template; and a connecting module for establishing a connection with the second computing device based on the target interface information.

[0022] In one possible implementation, a module is defined to use the data template as the target data template when the authentication level is Level 1.

[0023] In another possible implementation, a determining module is configured to receive a new authentication result for a second computing device when the authentication level is second level; the new authentication result includes an updated authentication level and a target data template; wherein the target data template includes a supplementary data template and a data template.

[0024] In another possible implementation, the first acquisition module is used to acquire the target interface information of the second computing device based on the communication connection between the operating systems of the first and second computing devices when the authentication level is the second level; the connection module is used to connect the target device to the first computing device based on the target interface information.

[0025] In another possible implementation, a first acquisition module is used to acquire device identification information of the second computing device; a query module is used to query the authentication status of the second computing device based on the device identification information; the authentication status is used to indicate whether the second computing device has completed authentication; and a first generation module is used to generate alarm information if the second computing device has not completed authentication, the alarm information being used to indicate that the second computing device is in an unauthenticated state.

[0026] Fourthly, embodiments of this application provide another access device for a computing device, the device comprising: a second acquisition module for acquiring device identification information of a second computing device; a matching module for matching a corresponding data template from a preset knowledge base based on the device identification information; and a second generation module for generating an authentication result of the second computing device based on the data template, so that a first computing device performs an access operation of the second computing device based on the authentication result; wherein, the authentication result includes an authentication level and a data template; the data template is executable logic obtained by matching the device identification information of the second computing device from a preset knowledge base, used to automatically parse the interface information of the second computing device to output target interface information.

[0027] In one possible implementation, the second acquisition module is used to receive alarm information sent by the first computing device; the alarm information includes device identification information of the second computing device; or, in response to user input, acquire the device identification information of the second computing device.

[0028] In another possible implementation, the second generation module is further configured to, when the authentication level is the second authentication level, obtain a supplementary data template matching the second computing device from a preset knowledge base, and merge the supplementary data template with the data template to obtain a target data template; the second generation module is further configured to generate a new authentication result for the second computing device based on the target data template.

[0029] Fifthly, embodiments of this application provide a computing cluster, which includes: at least one second computing device; a first computing device, configured to receive authentication results for the second computing device and perform access operations for the second computing device based on the authentication results; and an authentication system, configured to obtain device identification information of the second computing device and generate authentication results based on the device identification information. The authentication results include an authentication level and a data template, wherein the data template is executable logic obtained by matching the device identification information of the second computing device from a preset knowledge base, used to automatically parse the interface information of the second computing device to output target interface information.

[0030] In a sixth aspect, embodiments of this application also provide a computing device, including: a processor and a memory; the processor and the memory are coupled; the memory is used to store program instructions; the processor is used to execute the program instructions to perform the method as described in either the first or second aspect above.

[0031] In a seventh aspect, embodiments of this application provide a chip for performing the methods described in any one of the first and second aspects above.

[0032] Eighthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a computer, implement the method as described in either the first or second aspect.

[0033] Ninthly, embodiments of this application provide a program product including a computer program that, when executed by a processor, implements the method as described in either the first or second aspect. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of a system structure provided in an embodiment of this application; Figure 2 This is a schematic diagram of a computing cluster scenario provided in an embodiment of this application; Figure 3 This is a first flowchart illustrating a method for accessing a computing device provided in an embodiment of this application; Figure 4 This is the first interactive schematic diagram of a computing device access method provided in an embodiment of this application; Figure 5 This is a schematic diagram of a process for generating authentication results for a second computing device, provided in an embodiment of this application. Figure 6 This is a schematic diagram of a process for determining an authentication level provided in an embodiment of this application; Figure 7 This is a schematic flowchart of a method for determining a target data template provided in an embodiment of this application; Figure 8 This is a schematic diagram of a forwarding process from the out-of-band acquisition module to the resource management module provided in an embodiment of this application; Figure 9 This is a second interactive schematic diagram of a computing device access method provided in an embodiment of this application; Figure 10 This is a second flowchart illustrating a method for accessing a computing device provided in an embodiment of this application; Figure 11 This is a third interactive schematic diagram of a computing device access method provided in an embodiment of this application; Figure 12 This is a schematic diagram of the third process of a computing device access method provided in an embodiment of this application; Figure 13 This is a schematic diagram of the fourth process of a computing device access method provided in an embodiment of this application; Figure 14 This is a fifth flowchart illustrating a method for accessing a computing device provided in an embodiment of this application; Figure 15This is a schematic diagram of the sixth process of a computing device access method provided in an embodiment of this application; Figure 16 This is a schematic diagram of an access device for a computing device provided in an embodiment of this application; Figure 17 This is a schematic diagram of another computing device access device provided in an embodiment of this application; Figure 18 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0035] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. To facilitate a clear description of the technical solutions of the embodiments of this application, the use of terms such as "first," "second," etc., in the embodiments of this application is for illustrative purposes and to distinguish the objects being described. There is no particular order between them, nor does it indicate a specific limitation on the number of devices in the embodiments of this application, and they do not constitute any limitation on the embodiments of this application.

[0036] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of this application.

[0037] It should be noted that many specific details are set forth in the following description in order to provide a full understanding of this application. However, this application may also be implemented in other ways different from those described herein. Therefore, the scope of protection of this application is not limited to the specific embodiments disclosed below.

[0038] The following explanations of the technical terms mentioned in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0039] The knowledge base is a data warehouse used to store device information, data templates, and sets of parsing rules. It includes interface descriptions, protocol specifications, field mapping relationships, and executable parsing logic corresponding to various computing devices. This knowledge base supports the system's real-time identification and automatic adaptation capabilities for new devices. Simultaneously, when faced with unknown or incompletely informational devices, it allows maintenance personnel to manually supplement or correct missing templates and rules, thereby continuously improving the system's coverage and compatibility.

[0040] The embodiments of this application will now be described with reference to the accompanying drawings.

[0041] Individual computing devices, limited by hardware performance, resource availability, or environmental conditions, often struggle to efficiently complete complex computing tasks. For example, in some scenarios, the device's processing power is limited, resulting in lengthy task execution times; while in others, the task itself is large enough to exceed the capacity of a single device. To improve overall processing efficiency and resource utilization, tasks or data are typically uploaded to a central node with greater computing power for centralized processing. Based on this need, the industry widely adopts a centralized architecture of "central platform + computing devices." In this architecture, multiple computing devices can submit their tasks or data to a central platform, which then centrally schedules resources and coordinates the processing flow.

[0042] Figure 1 This is a schematic diagram of a system structure provided in an embodiment of this application.

[0043] like Figure 1 As shown, this centralized architecture includes a central platform 10 and multiple computing devices, such as computing devices 11A, 11B, 11C, 11D, and 11E. The central platform 10 acts as the core management node, responsible for device authentication, access control, and task coordination. Each computing device acts as a distributed node, capable of proactively initiating access requests or responding to scheduling instructions from the central platform. The computing devices, as providers of computing resources, undertake the actual data processing and computation tasks, and perform operations such as status reporting, resource registration, and security authentication according to the unified policies of the central platform 10.

[0044] Under the aforementioned centralized architecture, to achieve efficient and automated access to new computing devices, this application provides a method for accessing computing devices. The following is in conjunction with... Figure 2 Please provide a detailed explanation.

[0045] Figure 2 This is a schematic diagram of a computing cluster scenario provided in an embodiment of this application.

[0046] like Figure 2 As shown, the computing cluster 200 includes at least one second computing device 201 (two are illustrated in the figure), a first computing device 202, and an authentication system 203. The first computing device 202 deploys a centralized platform to receive authentication results for the second computing device 201 and execute access operations for the second computing device 201 based on the authentication results. The authentication system 203 is used to perform authentication operations on the second computing device 201.

[0047] Specifically, the first computing device 202 first obtains the device identification information of the second computing device 201; and queries its authentication status based on the identification information. If the query result shows that the device has not yet completed authentication, the first computing device 202 generates an alarm message to indicate that the second computing device 201 is in an unauthenticated state and does not have access permission. Subsequently, the authentication system 203 obtains the device identification information of the second computing device 201 and matches the corresponding data template from a preset knowledge base based on the identification information; the authentication system 203 generates an authentication result containing the authentication level and the data template based on the data template. Then, the first computing device 202 obtains the authentication result, combines the authentication level and the data template therein, determines the target data template applicable to the second computing device 201, and obtains its target interface information based on the target data template. Finally, the second computing device 201 is connected to the first computing device 202 according to the target interface information.

[0048] In summary, by using authentication levels and data templates, the interface information of the second computing device can be automatically parsed without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0049] The following describes a specific embodiment of the method for accessing computing devices with reference to the accompanying drawings.

[0050] Figure 3 This is a first flowchart illustrating a method for accessing a computing device provided in an embodiment of this application.

[0051] like Figure 3 As shown, the method for connecting a computing device includes the following steps: S1: The first computing device obtains the device identification information of the second computing device.

[0052] The first computing device deploys a centralized platform to receive data from the second computing device, which is any one of the multiple edge computing devices connected to the first computing device.

[0053] Figure 4 This is the first interactive schematic diagram of a computing device access method provided in the embodiments of this application.

[0054] like Figure 4 As shown, in one implementation, step S1 includes step S1001.

[0055] S1001: The authentication management module of the first computing device responds to the input operation of the operation and maintenance user and obtains the device identification information of the second computing device. The authentication management module is responsible for the compatibility authentication management of the first computing device and can be used to count the authentication level and data template of each computing device's identity or type. The device identification information is used to characterize the identity or type of the second computing device, such as device model, serial number, hardware fingerprint, MAC address, or manufacturer-defined device code.

[0056] For example, when the operation and maintenance user enters "second computing device A" in the operation interface of the first computing device, the first computing device parses the input and obtains the device identification information A1 corresponding to "second computing device A".

[0057] It should be noted that before executing the above process (such as step S1), the first computing device needs to complete local initialization. Specifically, during the initial system deployment phase, when the first computing device is first racked and powered on, its resource management module will check whether the operating system is installed: if it is installed, the built-in management service suite (such as LiveOSAgent) will be automatically started, and the LiveOS Agent will report the basic information of the local system (such as device identifier, IP address, OS version) to the resource management module to complete self-registration; if it is not installed, the resource management module will send a registration notification to the computing management module, and the computing management module will distribute the operating system image through PXE boot, Redfish virtual media mounting, or similar mechanisms to complete the installation. After the installation is completed, the computing management module will report the device information to the resource management module. Among them, the LiveOS Agent is deployed locally on the first computing device and is responsible for collecting the local hardware and runtime status; the computing management module is deployed on the management service platform of the data center control plane and is responsible for triggering the installation and receiving the reported information.

[0058] S2: The first computing device generates alarm information based on the device identification information.

[0059] Figure 5 This is a schematic diagram of a process for generating authentication results for a second computing device, provided in an embodiment of this application.

[0060] like Figure 5 As shown, step S2 includes steps S21-S22.

[0061] S21: The first computing device queries the authentication status of the second computing device based on the device identification information.

[0062] Continue as Figure 4 As shown, step S21 includes step S1002.

[0063] S1002: The authentication management module of the first computing device queries the authentication status of the second computing device based on the device identification information.

[0064] The authentication status indicates whether the second computing device has completed authentication. The authentication status includes either no authentication or authentication completed. The first computing device queries its local authentication list to determine the authentication status of the second computing device. If device identification information A1 exists in the local authentication list, the second computing device is determined to be authenticated; if device identification information A1 does not exist in the local authentication list, the second computing device is determined to be unauthenticated.

[0065] In this embodiment, the authentication status of the second computing device is described as not having been authenticated.

[0066] S22: If the second computing device fails to complete authentication, the first computing device generates an alarm message.

[0067] Continue to combine Figure 4 As shown, step S22 includes step S1003.

[0068] S1003: If the second computing device fails to complete authentication, the authentication management module of the first computing device generates an alarm message.

[0069] The alarm information is used to indicate that the second computing device is in an unauthenticated state.

[0070] Continuing with the example above, if the authentication status of the second computing device is not authenticated, the first computing device generates alarm message A2: "The second computing device corresponding to device identification information A1 has not completed authentication. Please perform the authentication operation."

[0071] It should be noted that alarm information can serve as a trigger to initiate the formal authentication process for the device. This can be done by notifying maintenance personnel to intervene or by automatically sending an authentication request to the authentication system.

[0072] The following examples illustrate steps S1004 and S1005 respectively.

[0073] S1004: In response to the input operation of the operation and maintenance user, the authentication system obtains the device identification information of the second computing device.

[0074] The second authentication request includes the device identification information of the second computing device.

[0075] It should be noted that the authentication system is used to authenticate the identity of the second computing device. It can be deployed on a standalone computing device (such as a third computing device) or integrated as a service module on the host where the first computing device is located. The specific deployment method is not limited.

[0076] S1005: The authentication management module of the first computing device sends an authentication request for the second computing device to the authentication system based on the alarm information.

[0077] It should be noted that in actual application scenarios, either step S1004 or S1005 can be selected. In this embodiment of the application, for ease of explanation, steps S1004 and S1005 are used as examples for illustration.

[0078] S3: The authentication system generates the authentication result of the second computing device based on the device identification information.

[0079] The certification results include the certification level and the data template.

[0080] Continue to combine Figure 5 As shown, step S3 includes steps S31-S32.

[0081] S31: The authentication system matches the corresponding data template from a preset knowledge base based on the device identification information.

[0082] Continue to combine Figure 4 As shown, step S31 includes step S1006.

[0083] S1006: In response to an authentication request, the authentication system matches the corresponding data template from a pre-set knowledge base based on the device identification information.

[0084] The data template is an executable logic that matches the device identification information of the second computing device from a preset knowledge base. It is used to automatically parse the interface information of the second computing device to output the target interface information. In other words, the data template is a file that defines the rules for extracting data fields from computing devices in a structured format, used to uniformly describe the data collection and interface parsing logic for a specific model of computing device. This template can contain multiple attributes, such as field identifiers, target computing device interface addresses, response data examples, JSON path rules, and feature configuration items. Specifically, the field identifier (id) is used to uniquely identify a data metric; the target computing device interface address (url) is used to obtain response data; the response data example (data) describes the structure of the returned result; the JSON path rule (jsonpath) is used to extract specific field values ​​from the response data; and the feature configuration item (advanced) allows certain data metrics to use advanced features for data extraction, such as paginated log collection.

[0085] The authentication system, based on device identification information, calls a JSONPath parsing engine to verify the grammatical validity of templates in the knowledge base. Based on the defined URL and JSONPath rules, it dynamically parses the interface responses returned by the target device (such as a second computing device supporting the Redfish protocol) and extracts the required data metrics, i.e., the data template. In this way, computing devices from different manufacturers and models can achieve automated interface identification and data collection based on their proprietary templates, eliminating the need to develop hard-coded adapters for each type of computing device, thus significantly improving the system's versatility and scalability.

[0086] Continuing with the example above, the authentication system matches the corresponding data template A3 from the preset knowledge base based on the device identification information A1.

[0087] It should be noted that the above data template can be a complete data template of the second computing device, or it can reflect the partial credibility of the identity of the second computing device or the incompleteness of the interface information.

[0088] S32: The authentication system determines the authentication result of the second computing device based on the data template.

[0089] Continue to combine Figure 4 As shown, step S32 includes steps S1007-S1008.

[0090] S1007: The authentication system determines the authentication level of the second computing device as Level 2 based on the data template.

[0091] The authentication level characterizes the trustworthiness or access permission level of the second computing device, and its value can be dynamically determined according to a preset policy. The authentication level can include either Level 1 (high) or Level 2 (low). Level 1 indicates that the second computing device is a known and trusted computing device with complete identity and interface information; the corresponding data template is a complete template and can be directly used for subsequent interface parsing. The second computing device can be accessed without restriction by the first computing device. Level 2 indicates that the second computing device's identity is partially trustworthy or its interface information is incomplete; the corresponding data template is an incomplete template, requiring subsequent control through supplementary authentication, manual intervention, or restrictive policies.

[0092] Figure 6 This is a schematic diagram of a process for determining the authentication level provided in an embodiment of this application.

[0093] like Figure 6 As shown, the method for determining the second computing device certification level in step S1007 includes the following steps: S601: The authentication system determines whether a data template is a complete data template.

[0094] S602: If the authentication system determines that the data template is a complete data template, it determines that the authentication level of the second computing device is Level 1.

[0095] Continuing with the example above, if the authentication system determines that data template A3 is the complete data template of the second computing device, then the authentication level of the second computing device is determined to be the second level, such as low level.

[0096] S603: If the authentication system determines that the data template is not a complete data template, it determines that the authentication level of the second computing device is Level 2.

[0097] Continuing with the above example, in this embodiment, the second computing device is described as having a partially trusted identity or incomplete interface information, meaning its authentication level is Level 2 (low). Specifically, if the authentication system determines that data template A3 is a partial data template of the second computing device, then the authentication level of the second computing device is determined to be Level 2 (low).

[0098] S1008: The authentication system obtains the authentication result of the second computing device based on the data template and the second level.

[0099] In this embodiment of the application, the example is taken as the second level of authentication and a partial data template.

[0100] Continuing with the example above, the authentication system generates an authentication result A4 for the second computing device based on data template A3. Authentication result A4 includes the authentication level as Level 2 and data template A3.

[0101] It should be noted that after the authentication system obtains the authentication result, it needs to send the authentication result to the first computing device. The following will continue to illustrate this with an example in conjunction with step S1009.

[0102] S1009: The authentication system sends the authentication result to the authentication management module of the first computing device.

[0103] Continuing with the example above, the authentication system sends the authentication result A4, which includes the authentication level as Level 2 and the data template A3, to the authentication management module of the first computing device.

[0104] It should be noted that the authentication management module of the first computing device can display the above authentication results to the operation and maintenance user, allowing the user to determine whether manual intervention is required. If manual intervention is deemed necessary, the operation and maintenance user can collaborate with the development user to supplement and improve the current data template A3, thereby constructing a complete and usable data template, i.e., the target data template. The following section provides an illustrative explanation of this process in conjunction with step S4.

[0105] S4: Based on the authentication result, the first computing device determines the target data template corresponding to the second computing device.

[0106] Continuing with the example above, when the first computing device is based on authentication level 2 and data template A3 is a partial data template, to ensure the second computing device can be accurately and completely accessed, the data template needs to be supplemented to form a complete data template, i.e., the target data template. The following section will specifically address this. Figure 7 Please provide an explanation.

[0107] Figure 7 This is a schematic flowchart of a method for determining a target data template provided in an embodiment of this application.

[0108] like Figure 7 As shown, step S4 includes steps S41-S42.

[0109] S41: Developers store supplementary data templates in a pre-defined knowledge base based on collaborative interactions with operations and maintenance users.

[0110] Continue to combine Figure 4 As shown, step S41 includes step S1010.

[0111] S1010: Developers store supplementary data templates in a pre-defined knowledge base.

[0112] In this scenario, the first computing device can display missing fields or uncovered interface information to the operations and maintenance personnel and prompt that a user with development privileges (hereinafter referred to as "developer user") needs to complete the template. The developer user writes the missing template content, i.e., the supplementary data template, based on the actual device interface documentation or detection results, and writes it into the preset knowledge base through the management interface, associating it with the original partial data template.

[0113] Because the data template on which the original authentication relies is incomplete, the authentication result only reflects a partial trust status of the device. After the knowledge base is updated, the authentication process can be re-executed to verify whether the device meets the complete access conditions and output an authentication result containing complete parsing capabilities.

[0114] It should be noted that the above method uses manual completion. Alternatively, automatic completion can be used. The first computing device or authentication system, based on a preset automatic discovery mechanism (such as actively probing device interfaces, parsing Redfish response structures, and calling device self-description APIs), dynamically derives rules for extracting missing fields, automatically generates supplementary data templates, and automatically stores them in the knowledge base. No specific limitations are specified here.

[0115] S42: The authentication system generates a new authentication result for the second computing device based on the device identification information.

[0116] Continue to combine Figure 4 As shown, step S42 includes steps S1011-S1013.

[0117] S1011: When the authentication level is the second authentication level, the authentication system retrieves a supplementary data template that matches the second computing device from a preset knowledge base based on the device identification information.

[0118] The specific details of step S1011 can be found in step S31 above, and will not be repeated here.

[0119] Continuing with the example above, the authentication system obtains supplementary data template A5 that matches the second computing device based on the device identification information.

[0120] It should be noted that at this time, the authentication system can trigger authentication of the second computing device based on existing records or by the device identification information A re-entered by the operation and maintenance user; no specific limitation is made here.

[0121] S1012: The authentication system obtains the target data template based on the data template and the supplementary data template.

[0122] For example, the authentication system obtains the target data template A6 based on data template A3 and supplementary data template A5.

[0123] S1013: The authentication system generates a new authentication result for the second computing device based on the target data template.

[0124] The specific details of step S1013 can be found in step S32 above, and will not be repeated here.

[0125] For example, the authentication system is based on device identification information A1, including authentication level: Level 1, and a new authentication result A7 based on target data template A6.

[0126] It should be noted that after the authentication system obtains the new authentication result, it needs to send the authentication result to the first computing device. The following will continue to illustrate this with an example in conjunction with step S1014.

[0127] S1014: The authentication system sends a new authentication result to the authentication management module of the first computing device.

[0128] Continuing with the example above, the authentication system sends a new authentication result A7 to the authentication management module of the first computing device, which includes the authentication level as Level 1 and the target data template A6.

[0129] It should be noted that, to ensure consistent understanding of the device status across all functional modules of the system, the new authentication result needs to be synchronized to other processing modules in the first computing device, such as the resource management module. The resource management module can update the device's permission level, interface resolution rules, and related resource configuration information. This will be explained in conjunction with step S1015 below.

[0130] S1015: The out-of-band acquisition module obtains new authentication results from the authentication management module and synchronizes them to the resource management module.

[0131] Figure 8 This is a schematic diagram of a forwarding process from the out-of-band acquisition module to the resource management module, provided in an embodiment of this application.

[0132] like Figure 8 As shown, step S1015 includes steps S1015a-S1015b.

[0133] S1015a: The out-of-band acquisition module reads the authentication level and target data template from the new authentication results in the authentication management module.

[0134] Among them, the out-of-band acquisition module (bmc-poller), as the device access layer, is a functional unit in the first computing device used to communicate with the computing device through a management channel independent of the business network.

[0135] Continuing with the example above, the out-of-band acquisition module reads the authentication result A7 from the authentication management module, which includes the authentication level as Level 1 and the target data template A6.

[0136] S1015b: The out-of-band acquisition module sends the authentication level and target data template from the new authentication result to the resource management module.

[0137] The resource management module is responsible for maintaining the runtime status information of the second computing device, including authentication level, access permissions, and associated parsing templates. When it receives a notification that the authentication level has been upgraded from level two to level one, this module automatically updates its internal device registry, achieving a seamless refresh of the device status without manual intervention.

[0138] Specifically, based on the received information, the resource management module identifies that the authentication level of the second computing device has been upgraded from Level 2 to Level 1, and updates its internal device registry accordingly: on the one hand, it elevates the device's access permissions, and on the other hand, it loads the corresponding target data template for subsequent out-of-band data collection and resource scheduling. After the second computing device's authentication level is updated to Level 1, the first computing device can automatically initiate the interface information collection process for that device based on the complete target data template.

[0139] It should be noted that step S1015 also includes step S1015c.

[0140] S1015c: When the out-of-band acquisition module reads a new authentication result from the authentication management module, ignore the access request from the second computing device.

[0141] The following explanation will continue with step S5.

[0142] S5: The first computing device obtains the target interface information of the second computing device based on the target data template.

[0143] Continue to combine Figure 4 As shown, step S5 includes step S1016.

[0144] S1016: The out-of-band acquisition module of the first computing device sends a request message to the second computing device based on the target data template.

[0145] Among them, the out-of-band acquisition module (bmc-poller) serves as the device access layer. It can extract data based on the data template sent by the authentication management module and parse it using the jsonpath parsing engine.

[0146] Continuing with the example above, the out-of-band acquisition module constructs a request message based on the attributes in the target data template A6, such as the URL, and sends it to the second computing device to obtain its device information.

[0147] It should be noted that this module is mainly responsible for request initiation and raw data reception, and does not perform structured parsing operations; subsequent field extraction and interface information generation are completed by the computing power resource processing module based on the same target data template (see step S1017).

[0148] S1017: The second computing device responds to the request message and returns device information to the out-of-band acquisition module of the first computing device.

[0149] The device information of the second computing device can be generated by the second computing device according to the protocol specifications of its own management interface, and its data format must be consistent with the protocol type adapted to the target data template.

[0150] For example, if the target data template is defined based on the Redfish protocol, the raw device information returned by the second computing device is JSON format data conforming to the Redfish standard, and the content may include structured information such as hardware configuration, firmware version, sensor status, and network interface list.

[0151] It should be noted that the above explanation uses the Redfish protocol as an example only; in other implementations, the target data template can also be defined based on other out-of-band management protocols such as IPMI, SNMP, SSH CLI script parsing, and vendor-specific REST APIs. Correspondingly, the raw device information returned by the second computing device will follow the data format of the corresponding protocol (such as binary TLV, XML, text logs, or custom JSON). This application does not limit the specific protocol type; as long as the target data template matches the actual response format of the device, automated collection and parsing can be achieved.

[0152] S1018: The out-of-band acquisition module of the first computing device sends device information to the computing power resource processing module of the first computing device.

[0153] Following the example above, after the out-of-band acquisition module receives the device information returned by the second computing device (such as JSON format hardware status data under the Redfish protocol), it encapsulates it and transmits it to the computing resource processing module.

[0154] S1019: The computing power resource processing module of the first computing device parses the device information based on the parsing rules defined in the target data template to obtain the target interface information of the second computing device.

[0155] Parsing rules include, but are not limited to, JSONPath expressions, field mapping relationships, or protocol-specific extraction logic; target interface information includes key parameters that can be used for device access, resource scheduling, or status monitoring, such as management IP address, BMC port, number of GPUs, memory capacity, or network interface list.

[0156] Following the example above, the computing power resource processing module of the first computing device obtains the target interface information A8 of the second computing device.

[0157] S6: The first computing device establishes a connection with the second computing device based on the target interface information.

[0158] Continue to combine Figure 4 As shown, step S6 includes steps S1020-S1021.

[0159] S1020: The computing power resource processing module of the first computing device sends the target interface information to the out-of-band acquisition module of the first computing device.

[0160] Continuing with the example above, the computing power resource processing module of the first computing device sends the target interface information A8 to the out-of-band acquisition module of the first computing device.

[0161] S1021: The out-of-band acquisition module of the first computing device establishes a connection with the second computing device based on the target interface information.

[0162] Continuing with the example above, the first computing device establishes a connection with the second computing device based on the target interface information A8, enabling the second computing device to access the first computing device.

[0163] It should be noted that step S1015 can be executed in parallel with steps S1016-S1021, or they can be executed sequentially; no specific limitation is made here.

[0164] In summary, when the authentication level of the second computing device is upgraded from Level 2 (partially trusted, incomplete template) to Level 1 (fully trusted, complete template), the first computing device can automatically parse the interface information of the device based on the complete target data template, without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0165] Corresponding to the above embodiments, this application also provides an embodiment of another device access method. The following is a detailed description... Figure 3 and Figure 9 An example is provided.

[0166] Figure 9 This is a second interactive schematic diagram of a computing device access method provided in an embodiment of this application.

[0167] Continue as Figure 3 As shown, the method for connecting a computing device includes the following steps: S1: The first computing device obtains the device identification information of the second computing device.

[0168] like Figure 9 As shown, in one implementation, step S1 includes step S2001.

[0169] S2001: The authentication management module of the first computing device responds to the input operation of the operation and maintenance user and obtains the device identification information of the second computing device.

[0170] The specific details of step S2001 can be found in step S1001 above, and will not be repeated here.

[0171] S2: The first computing device generates alarm information based on the device identification information.

[0172] Continue to combine Figure 9 As shown, step S2 includes steps S2002-S2003.

[0173] S2002: The authentication management module of the first computing device queries the authentication status of the second computing device based on the device identification information.

[0174] S2003: If the second computing device fails to complete authentication, the authentication management module of the first computing device generates an alarm message.

[0175] The specific details of steps S2002-S2003 can be found in steps S1002-S1003 above, and will not be repeated here.

[0176] It should be noted that alarm information can serve as a trigger to initiate the formal authentication process for the device. This can be done by notifying maintenance personnel to intervene or by automatically sending an authentication request to the authentication system.

[0177] The following examples illustrate steps S2004 and S2005 respectively.

[0178] S2004: In response to the input operation of the operation and maintenance user, the authentication system obtains the device identification information of the second computing device.

[0179] The second authentication request includes the device identification information of the second computing device.

[0180] S2005: The authentication management module of the first computing device sends an authentication request for the second computing device to the authentication system based on the alarm information.

[0181] The specific details of steps S2004-S2005 can be found in steps S1004-S1005 above, and will not be repeated here.

[0182] S3: The authentication system generates the authentication result of the second computing device based on the device identification information.

[0183] Continue to combine Figure 9 As shown, step S3 includes steps S2006-S2008.

[0184] S2006: The authentication system matches the corresponding data template from a preset knowledge base based on the device identification information.

[0185] The specific details of step S2006 can be found in step S1006 above, and will not be repeated here.

[0186] S2007: The authentication system determines the authentication level of the second computing device as Level 1 based on the data template.

[0187] The specific content of step S2007 can be referred to the similar step S1007 above, and will not be repeated here.

[0188] For example, if the authentication system determines that data template A3 is a complete data template of the second computing device, then the authentication level of the second computing device is determined to be the first level, such as advanced.

[0189] S2008: The authentication system obtains the authentication result of the second computing device based on the data template and the first level.

[0190] In this embodiment of the application, since the authentication level of the second computing device is the first level, the first level is used to indicate that the second computing device is a known and trusted computing device with complete identity information and interface information. The corresponding data template is a complete template that can be directly used for subsequent interface parsing. The second computing device can be accessed by the first computing device without restriction.

[0191] The specific content of step S2008 can be referred to the similar step S1008 above, and will not be repeated here.

[0192] It should be noted that after the authentication system obtains the authentication result, it needs to send the authentication result to the first computing device. The following will continue to illustrate this with an example based on step S2009.

[0193] S2009: The authentication system sends the authentication result to the authentication management module of the first computing device.

[0194] The specific content of step S2009 can be referred to the similar step S1009 above, and will not be repeated here.

[0195] Continuing with the example above, the authentication system sends authentication result B, which includes the authentication level as Level 1 and data template A3, to the authentication management module of the first computing device.

[0196] S4: Based on the authentication result, the first computing device determines the target data template corresponding to the second computing device.

[0197] Continue to combine Figure 9 As shown, step S4 includes step S2010.

[0198] S2010: When the authentication level of the first computing device is Level 1, the authentication management module will use the data template as the target data template.

[0199] The target data template is a complete data template with complete identity and interface information.

[0200] Continuing with the example above, the authentication management module of the first computing device uses data template A3 as the target data template B1 when the authentication level is Level 1.

[0201] S2011: The out-of-band acquisition module reads the authentication level and target data template from the authentication results in the authentication management module.

[0202] The specific content of step S2011 can be referred to the similar step S1015a mentioned above, and will not be repeated here.

[0203] S5: The first computing device obtains the target interface information of the second computing device based on the target data template.

[0204] Continue to combine Figure 9 As shown, step S5 includes steps S2012-S2015.

[0205] S2012: The out-of-band acquisition module of the first computing device sends a request message to the second computing device based on the target data template.

[0206] S2013: The second computing device responds to the request message and returns device information to the out-of-band acquisition module of the first computing device.

[0207] S2014: The out-of-band acquisition module of the first computing device sends device information to the computing power resource processing module of the first computing device.

[0208] S2015: The computing power resource processing module of the first computing device parses the device information based on the parsing rules defined in the target data template to obtain the target interface information of the second computing device.

[0209] The specific details of steps S2012-S2015 can be found in steps S1016-S1019, and will not be repeated here.

[0210] S6: The first computing device establishes a connection with the second computing device based on the target interface information.

[0211] Continue to combine Figure 9 As shown, step S6 includes steps S2016-S2017.

[0212] S2016: The computing power resource processing module of the first computing device sends the target interface information to the out-of-band acquisition module of the first computing device.

[0213] The specific details of step S2016 can be found in step S1020 above, and will not be repeated here.

[0214] S2017: The out-of-band acquisition module of the first computing device establishes a connection with the second computing device based on the target interface information.

[0215] The specific details of step S2017 can be found in step S1021 above, and will not be repeated here.

[0216] In summary, when the authentication level of the second computing device is Level 1 (fully trusted, complete template), the first computing device can automatically parse the interface information of the device based on the complete target data template, without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0217] Corresponding to the above embodiments, this application also provides an embodiment of another device access method. The following describes... Figure 10 and Figure 11 An example is provided.

[0218] Figure 10 This is a second flowchart illustrating a method for accessing a computing device provided in an embodiment of this application.

[0219] like Figure 10 As shown, the method for connecting a computing device includes the following steps: S01: The first computing device obtains the device identification information of the second computing device.

[0220] Figure 11 This is the third interactive schematic diagram of a computing device access method provided in the embodiments of this application.

[0221] like Figure 11 As shown, in one implementation, step S01 includes step S3001.

[0222] S3001: The authentication management module of the first computing device responds to the input operation of the operation and maintenance user and obtains the device identification information of the second computing device.

[0223] The specific details of step S3001 can be found in step S1001 above, and will not be repeated here.

[0224] S02: The first computing device generates alarm information based on the device identification information.

[0225] Continue to combine Figure 11 As shown, step S02 includes steps S3002-S3003.

[0226] S3002: The authentication management module of the first computing device queries the authentication status of the second computing device based on the device identification information.

[0227] S3003: If the second computing device fails to complete authentication, the authentication management module of the first computing device generates an alarm message.

[0228] The specific details of steps S3002-S3003 can be found in steps S1002-S1003 above, and will not be repeated here.

[0229] It should be noted that alarm information can serve as a trigger to initiate the formal authentication process for the device. This can be done by notifying maintenance personnel to intervene or by automatically sending an authentication request to the authentication system.

[0230] The following examples illustrate steps S3004 and S3005 respectively.

[0231] S3004: In response to the input operation of the operation and maintenance user, the authentication system obtains the device identification information of the second computing device.

[0232] The second authentication request includes the device identification information of the second computing device.

[0233] S3005: The authentication management module of the first computing device sends an authentication request for the second computing device to the authentication system based on the alarm information.

[0234] The specific details of steps S3004-S3005 above can be found in steps S1004-S1005 above, and will not be repeated here.

[0235] S03: The authentication system generates the authentication result of the second computing device based on the device identification information.

[0236] Continue to combine Figure 11 As shown, step S03 includes steps S3006-S3008.

[0237] S3006: The authentication system matches the corresponding data template from a preset knowledge base based on the device identification information.

[0238] The specific details of step S3006 can be found in step S1006 above, and will not be repeated here.

[0239] S3007: The authentication system determines the authentication level of the second computing device as Level 1 based on the data template.

[0240] The specific content of step S3007 can be referred to the similar step S1007 above, and will not be repeated here.

[0241] For example, if the authentication system determines that data template A3 is a complete data template of the second computing device, then the authentication level of the second computing device is determined to be the first level, such as advanced.

[0242] S3008: The authentication system obtains the authentication result of the second computing device based on the data template and the first level.

[0243] In this embodiment of the application, since the authentication level of the second computing device is the first level, the first level is used to indicate that the second computing device is a known and trusted computing device with complete identity information and interface information. The corresponding data template is a complete template that can be directly used for subsequent interface parsing. The second computing device can be accessed by the first computing device without restriction.

[0244] The specific content of step S3008 can be referred to the similar step S1008 above, and will not be repeated here.

[0245] It should be noted that after the authentication system obtains the authentication result, it needs to send the authentication result to the first computing device. The following will continue to illustrate this with an example in conjunction with step S3009.

[0246] S3009: The authentication system sends the authentication result to the authentication management module and resource management module of the first computing device.

[0247] The specific content of step S3009 can be referred to the similar step S1009 above, and will not be repeated here.

[0248] Continuing with the example above, the authentication system sends the authentication result C, which includes the authentication level as Level 2 and the data template A3, to the authentication management module of the first computing device.

[0249] It should be noted that, in this embodiment of the application, although the system has the ability to perform out-of-band acquisition through data templates, it can still access the second computing device when the authentication result is determined to be the second level. That is, it no longer relies on the data templates of the first and second embodiments mentioned above, but directly performs in-band acquisition based on the installed operating system. The following is a detailed explanation in conjunction with step S04.

[0250] S04: If the first computing device determines that the authentication result is Level 2, it obtains the target interface information of the second computing device based on the communication connection between the operating systems of the first computing device and the operating systems of the second computing device.

[0251] Continue to combine Figure 11 As shown, step S04 includes step S3010.

[0252] S3010: If the resource management module of the first computing device determines that the authentication result is Level 2, the resource management module of the first computing device determines whether the operating system of the first computing device is installed.

[0253] An operating system (OS) is the core system software that manages the hardware and software resources of a computing device. It is responsible for processor scheduling, memory allocation, device control, and file management, and provides a user interface and runtime environment for users and applications. It not only supports concurrent multitasking and network communication, but also bears critical responsibilities for security protection, access control, and system stability. In security authentication scenarios (such as Level 2 authentication), the operating system's installation status, integrity, and security configuration directly affect whether the device meets the corresponding trust and compliance requirements.

[0254] S3011: When installed, the LiveOS Agent of the first computing device reports basic information about the local system to the resource management module.

[0255] The basic information of the local system may include device identifier, IP address, OS version, etc.

[0256] For example, when the first computing device has an operating system installed, its built-in LiveOS Agent is automatically activated after the system starts up and collects key system information, including: the device's unique identifier (such as the motherboard serial number or chip ID), the currently assigned IP address (such as 192.xxxxx), the operating system version, and the architecture type. Subsequently, the LiveOS Agent reports the above information to the resource management module in real time through a local secure channel.

[0257] S3012: If the operating system is not installed, the resource management module notifies the computing management module to install the operating system.

[0258] The computing management module can complete the installation by distributing the operating system image through PXE boot, Redfish virtual media mounting, or similar mechanisms.

[0259] For example, assuming the first computing device has no operating system, the resource management module immediately triggers the installation process; the computing management module remotely mounts an image that conforms to the security baseline through the Redfish interface to complete the installation.

[0260] S3013: The computing management module reports basic information about the local system (such as device identifier, IP address, OS version) to the resource management module.

[0261] Continuing with the example above, the computing management module collects key system information from the local machine, including: the device's unique identifier (such as the motherboard serial number or chip ID), the currently assigned IP address (such as 192.xxxxx), the operating system version, and the architecture type. Subsequently, the LiveOS Agent reports the above information to the resource management module in real time through a local secure channel.

[0262] S3014: Based on the communication connection between the operating system of the first computing device and the operating system of the second computing device, the operating system of the first computing device obtains the target interface information of the second computing device.

[0263] The operating system of the first computing device actively queries or receives interface metadata from the second computing device through the communication connection, thereby obtaining its target interface information.

[0264] S05: The first computing device establishes a connection with the second computing device based on the target interface information.

[0265] Continue to combine Figure 11 As shown, step S05 includes step S3015.

[0266] S3015: The operating system of the first computing device establishes a connection with the second computing device based on the target interface information.

[0267] The operating system of the first computing device constructs a compliant HTTP request header based on the target interface information and initiates a connection carrying valid credentials. After the second computing device verifies the connection, the two parties establish a trusted session connection, which can be used to perform operations such as device status query and configuration distribution.

[0268] In summary, once the authentication level of the second computing device is determined to be Level 2, the target interface information can be automatically obtained and parsed in-band based on the communication connection between operating systems. This eliminates the need to develop separate adaptation code for different devices, enabling rapid access and effectively improving the access efficiency of computing devices.

[0269] Corresponding to the above embodiments, this application also provides an embodiment of another device access method. The following describes... Figure 12 An example is provided.

[0270] Figure 12 This is a third flowchart illustrating a method for accessing a computing device provided in an embodiment of this application.

[0271] like Figure 12 As shown, the method for connecting a computing device includes the following steps: S001: The first computing device obtains the device identification information of the second computing device.

[0272] The specific details of step S0032 can be found in step S1 above, and will not be repeated here.

[0273] S002: The first computing device queries the authentication status of the second computing device based on the device identification information.

[0274] The first computing device queries its local authentication list to determine if device identifier information A1 exists, thereby determining the authentication status of the second computing device. The authentication status indicates whether the second computing device has completed authentication. Authentication status includes either no authentication or authentication completed.

[0275] In this embodiment, the authentication status of the second computing device is described as already authenticated.

[0276] S003: If the second computing device completes the authentication, the first computing device determines the authentication level of the second computing device.

[0277] Continuing with step S13, step S003 includes steps S0031-S0033.

[0278] S0031: If the second computing device completes the authentication, the first computing device determines whether the authentication level of the second computing device is Level 1.

[0279] S0032: If the certification level of the second computing device is determined to be Level 1, a target data template is determined based on the data template and the supplementary data template.

[0280] The specific details of step S0032 can be found in step S4 above, and will not be repeated here.

[0281] S0033: If it is determined that the certification level of the second computing device is not Level 1, the data template shall be used as the target data template.

[0282] The specific details of step S0033 can be found in step S2010 above, and will not be repeated here.

[0283] S004: The first computing device obtains the target interface information of the second computing device based on the target data template.

[0284] The specific details of step S004 can be found in step S5 above, and will not be repeated here.

[0285] S005: The first computing device establishes a connection with the second computing device based on the target interface information.

[0286] The specific details of step S005 can be found in step S6 above, and will not be repeated here.

[0287] In summary, once the first computing device recognizes the second computing device as an authenticated device for the first time, it can automatically parse the interface information of the device based on its authentication level and corresponding data template, without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0288] Corresponding to the above embodiments, this application also provides a complete embodiment of a device access method. The following describes the method in conjunction with... Figure 13 An example is provided. Figure 13 This is a schematic diagram of the fourth process of a computing device access method provided in an embodiment of this application.

[0289] like Figure 13 As shown, the method for connecting a computing device includes the following steps: S1301: The first computing device obtains the device identification information of the second computing device.

[0290] The specific details of step S1301 can be found in step S1001 above, and will not be repeated here.

[0291] S1302: The first computing device determines whether the second computing device has been authenticated based on the device identification information.

[0292] The specific details of step S1302 can be found in step S002 above, and will not be repeated here.

[0293] S1303: If the second computing device has not completed authentication, the authentication system obtains the device identification information.

[0294] The specific details of step S1303 can be found in steps S1004 or S1005 above, and will not be repeated here.

[0295] S1304: The authentication system matches the corresponding data template from a preset knowledge base based on the device identification information.

[0296] The specific details of step S1304 can be found in step S31 above, and will not be repeated here.

[0297] S1305: The authentication system determines whether a data template is a complete data template.

[0298] S1306: If the data template is not a complete data template, the authentication system determines the authentication level of the second computing device to be Level 2.

[0299] The specific details of steps S1305-S1306 can be found in step S1007 above, and will not be repeated here.

[0300] S1307: The authentication system obtains the authentication result of the second computing device based on the data template and the second level.

[0301] The specific details of step S1307 can be found in step S1008 above, and will not be repeated here.

[0302] S1308: When the certification level is Level 2, the first computing device determines the target data template corresponding to the second computing device based on the data template and the supplementary data template.

[0303] The specific details of step S1308 can be found in step S4 above, and will not be repeated here.

[0304] S1309: The first computing device obtains the target interface information of the second computing device based on the target data template.

[0305] The specific details of step S1309 can be found in step S5 above, and will not be repeated here.

[0306] S1310: The first computing device establishes a connection with the second computing device based on the target interface information.

[0307] The specific details of step S1310 can be found in step S6 above, and will not be repeated here.

[0308] S1311: When the authentication level is Level 2, obtain the target interface information of the second computing device based on the communication connection between the operating system of the first computing device and the operating system of the second computing device.

[0309] The specific details of step S1311 can be found in step S04 above, and will not be repeated here.

[0310] S1312: The operating system of the first computing device establishes a connection with the second computing device based on the target interface information.

[0311] The specific details of step S1312 can be found in step S3014 above, and will not be repeated here.

[0312] S1313: If the data template is a complete data template, determine the certification level of the second computing device as Level 1.

[0313] The specific details of step S1313 can be found in step S2007 above, and will not be repeated here.

[0314] S1314: If the authentication level is Level 1, determine the target data template corresponding to the second computing device and execute S1309.

[0315] S1315: If the second computing device has completed the certification, determine whether the certification level of the certification result is Level 1.

[0316] S1316: If the certification level in the certification result is Level 1, proceed to step S1314.

[0317] S1317: If the certification level in the certification result is not the first level, proceed to step S1306.

[0318] In summary, by using authentication levels and data templates, the interface information of the second computing device can be automatically parsed without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0319] Corresponding to the above embodiments, this application also provides an embodiment of a device access method with a first computing device as the execution subject, which will be described below in conjunction with... Figure 14 An example is provided. Figure 14 This is a fifth flowchart illustrating a method for accessing a computing device provided in an embodiment of this application.

[0320] like Figure 14 As shown, the method for connecting a computing device includes the following steps: S141: Receive the authentication result for the second computing device.

[0321] The authentication result is generated by the authentication system and includes the authentication level and data template. The data template is an executable logic that is matched from a preset knowledge base based on the device identification information of the second computing device and is used to automatically parse the interface information of the second computing device in order to output the target interface information.

[0322] The specific details of step S141 can be found in step S4 above, and will not be repeated here.

[0323] S142: Based on the authentication level and data template, determine the target data template corresponding to the second computing device.

[0324] The specific details of step S142 can be found in step S5 above, and will not be repeated here.

[0325] S143: Based on the target data template, obtain the target interface information of the second computing device.

[0326] The details of step S143 can be found in step S6 above, and will not be repeated here.

[0327] S144: Based on the target interface information, connect the second computing device to the first computing device.

[0328] The details of step S144 can be found in step S7 above, and will not be repeated here.

[0329] In summary, by using authentication levels and data templates, the first computing device can automatically parse the interface information of the second computing device without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0330] Corresponding to the above embodiments, this application also provides an embodiment of a device access method with an authentication system as the execution subject, which will be described below in conjunction with... Figure 15 An example is provided.

[0331] Figure 15 This is a sixth flowchart illustrating a method for accessing a computing device provided in an embodiment of this application.

[0332] like Figure 15 As shown, the method for connecting a computing device includes the following steps: S151: Obtain the device identification information of the second computing device.

[0333] The specific details of step S151 can be found in step S3 above, and will not be repeated here.

[0334] S152: Based on the device identification information, match the corresponding data template from the preset knowledge base.

[0335] The specific details of step S152 can be found in step S31 above, and will not be repeated here.

[0336] S153: Based on the data template, generate the authentication result of the second computing device so that the first computing device can perform the access operation of the second computing device based on the authentication result.

[0337] The authentication result includes the authentication level and the data template. The data template is an executable logic that is matched from a preset knowledge base based on the device identification information of the second computing device, and is used to automatically parse the interface information of the second computing device in order to output the target interface information.

[0338] The specific details of step S153 can be found in step S32 above, and will not be repeated here.

[0339] In summary, by using authentication levels and data templates, the first computing device can automatically parse the interface information of the second computing device without the need to develop separate adaptation code for different devices, thereby achieving rapid access and effectively improving the access efficiency of computing devices.

[0340] Corresponding to the aforementioned embodiments of the device access method, this application also provides an embodiment of a device access device.

[0341] Figure 16 This is a schematic diagram of an access device for a computing device provided in an embodiment of this application.

[0342] like Figure 16 As shown, the access device 1600 for the computing device includes: a receiving module 1601, a first acquisition module 1602, a connection module 1603, a determination module 1604, and a first generation module 1605.

[0343] The receiving module 1601 is used to receive the authentication result for the second computing device; the authentication result is generated by the authentication system and includes the authentication level and data template; the data template is an executable logic that is matched from a preset knowledge base based on the device identification information of the second computing device and is used to automatically parse the interface information of the second computing device to output the target interface information; the determining module is used to determine the target data template corresponding to the second computing device based on the authentication level and the data template; the first obtaining module 1602 is used to obtain the target interface information of the second computing device based on the target data template; and the connecting module 1603 is used to establish a connection with the second computing device based on the target interface information.

[0344] In one possible implementation, module 1604 is used to use the data template as the target data template when the authentication level is Level 1.

[0345] In another possible implementation, the determining module 1604 is configured to receive a new authentication result for the second computing device when the authentication level is the second level; the new authentication result includes an updated authentication level and a target data template; wherein the target data template includes a supplementary data template and a data template.

[0346] In another possible implementation, the first acquisition module 1602 is used to acquire the target interface information of the second computing device based on the communication connection between the operating systems of the first computing device and the operating systems of the second computing device when the authentication level is the second level; the connection module is used to connect the target device to the first computing device based on the target interface information.

[0347] In another possible implementation, the first acquisition module 1602 is used to acquire the device identification information of the second computing device; the query module is used to query the authentication status of the second computing device based on the device identification information; the authentication status is used to indicate whether the second computing device has completed authentication; the first generation module 1605 is used to generate alarm information if the second computing device has not completed authentication, and the alarm information is used to indicate that the second computing device is in an unauthenticated state.

[0348] Corresponding to the aforementioned embodiments of the device access method, this application also provides an embodiment of another device access device.

[0349] Figure 17 This is a schematic diagram of another computing device access device provided in an embodiment of this application.

[0350] like Figure 17 As shown, the access device 1700 for the computing device includes: a second acquisition module 1701, a matching module 1702, and a second generation module 1703.

[0351] The second acquisition module 1701 is used to acquire the device identification information of the second computing device; the matching module 1702 is used to match the corresponding data template from a preset knowledge base based on the device identification information; the second generation module 1703 is used to generate the authentication result of the second computing device based on the data template, so that the first computing device can perform the access operation of the second computing device based on the authentication result; wherein, the authentication result includes the authentication level and the data template; the data template is an executable logic that is matched from the preset knowledge base according to the device identification information of the second computing device and is used to automatically parse the interface information of the second computing device to output the target interface information.

[0352] In one possible implementation, the second acquisition module 1701 is used to receive alarm information sent by the first computing device; the alarm information includes device identification information of the second computing device; or, in response to user input, acquire the device identification information of the second computing device.

[0353] In another possible implementation, the second generation module 1703 is further configured to, when the authentication level is the second authentication level, obtain a supplementary data template matching the second computing device from a preset knowledge base, and merge the supplementary data template with the data template to obtain a target data template; the second generation module 1703 is further configured to generate a new authentication result for the second computing device based on the target data template.

[0354] Figure 18 This is a schematic diagram of a computing device provided in an embodiment of this application.

[0355] like Figure 18 As shown, the computing device 1800 includes a processor 1801 and a memory 1802. Exemplarily, the computing device 1800 may also include a communications interface 1803 and a communications bus 1804.

[0356] The processor 1801, memory 1802, and communication interface 1803 communicate with each other via communication bus 1804. The communication interface 1803 may include a transmitter and receiver for communicating with other devices or communication networks, and may be a wired interface (port), such as a fiber distributed data interface (FDDI) or a gigabit Ethernet interface (GE).

[0357] In some embodiments, the processor 1801 is used to execute program 1805, specifically performing the relevant steps in the above-described device access execution method embodiments. Specifically, program 1805 may include program code, which includes computer-executable instructions.

[0358] For example, processor 1801 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement some embodiments of this application. Computing device 1800 may include one or more processors, which may be processors of the same type, such as one or more CPUs; or they may be processors of different types, such as one or more CPUs and one or more ASICs. The CPU may be a single-core CPU or a multi-core CPU.

[0359] In some embodiments, memory 1802 is used to store program 1805. Memory 1802 may include high-speed random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device.

[0360] Specifically, program 1805 can be called by processor 1801 to cause computing device 1800 to perform device access operations.

[0361] Some embodiments of this application provide a computer-readable storage medium storing at least one executable instruction that, when executed on a computing device 1800, causes the computing device 1800 to perform the device access method described above.

[0362] For example, the computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, a floppy disk, and an optical data storage device.

[0363] This application provides a chip system in some embodiments, which is applied to a server. The chip system includes one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines. The interface circuits are used to receive signals from the server's memory and send signals to the processors, the signals including computer instructions stored in the memory. When the server processor executes the computer instructions, the server performs various steps in the device access method shown in the above-described method embodiments.

[0364] The beneficial effects that the readable storage medium provided in some embodiments of this application can achieve can be referred to the beneficial effects in the corresponding inference task execution method provided above, and will not be repeated here.

[0365] It should be noted that, in this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0366] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0367] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0368] For the purposes of this specification, "computer-readable medium" can mean any means that can contain, store, communicate, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0369] More specific examples of computer-readable media (a non-exhaustive list) include the following: electrical connections having one or more wires (electronic devices), portable computer disks (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM).

[0370] Furthermore, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory. It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof.

[0371] In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc. The above embodiments are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the technical solutions of this application should be included within the scope of protection of this application.

Claims

1. A method for accessing a computing device, characterized in that, Applied to a first computing device, used to receive data corresponding to a second computing device, the access method of the computing device includes: Receive the authentication result for the second computing device; the authentication result is generated by the authentication system and includes the authentication level and data template; the data template is an executable logic that is matched from a preset knowledge base based on the device identification information of the second computing device and is used to automatically parse the interface information of the second computing device to output the target interface information; Based on the authentication level and the data template, determine the target data template corresponding to the second computing device; Based on the target data template, obtain the target interface information of the second computing device; Based on the target interface information, a connection is established with the second computing device.

2. The method for accessing a computing device according to claim 1, characterized in that, The step of determining the target data template corresponding to the second computing device based on the authentication level and the data template includes: When the authentication level is Level 1, the data template is used as the target data template.

3. The method for accessing a computing device according to claim 1, characterized in that, The step of determining the target data template corresponding to the second computing device based on the authentication level and the data template includes: If the authentication level is Level 2, a new authentication result is received for the second computing device; the new authentication result includes the updated authentication level and the target data template; wherein, the target data template includes a supplementary data template and the data template.

4. The method for accessing a computing device according to any one of claims 1-3, characterized in that, After obtaining the authentication result for the second computing device, the process also includes: When the authentication level is the second level, the target interface information of the second computing device is obtained based on the communication connection between the operating system of the first computing device and the operating system of the second computing device. Based on the target interface information, the target device is connected to the first computing device.

5. The method for accessing a computing device according to any one of claims 1-4, characterized in that, Before obtaining the authentication result for the second computing device, the process also includes: Obtain the device identification information of the second computing device; Based on the device identification information, query the authentication status of the second computing device; the authentication status is used to indicate whether the second computing device has completed authentication. If the second computing device fails to complete authentication, an alarm message is generated, which indicates that the second computing device is in an unauthenticated state.

6. A method for accessing a computing device, characterized in that, Applied to an authentication system for authenticating the identity of a second computing device, the access method for the computing device includes: Obtain the device identification information of the second computing device; Based on the device identification information, a corresponding data template is matched from a preset knowledge base; Based on the data template, an authentication result for the second computing device is generated, so that the first computing device can perform an access operation for the second computing device based on the authentication result; wherein, the authentication result includes an authentication level and the data template; the data template is an executable logic that is matched from a preset knowledge base based on the device identification information of the second computing device, and is used to automatically parse the interface information of the second computing device to output target interface information.

7. The method for accessing a computing device according to claim 6, characterized in that, The step of obtaining the device identification information of the second computing device includes: Receive alarm information sent by the first computing device; the alarm information includes the device identification information of the second computing device; Alternatively, in response to user input, the device identification information of the second computing device can be obtained.

8. The method for accessing a computing device according to claim 6 or 7, characterized in that, After generating the authentication result of the second computing device based on the data template, the process further includes: When the authentication level is the second authentication level, a supplementary data template matching the second computing device is obtained from the preset knowledge base, and the supplementary data template is merged with the data template to obtain the target data template; Based on the target data template, a new authentication result for the second computing device is generated.

9. A computing cluster, characterized in that, include: At least one second computing device, A first computing device is configured to receive an authentication result for the second computing device and perform an access operation for the second computing device based on the authentication result. An authentication system is used to obtain the device identification information of the second computing device and generate the authentication result based on the device identification information; The authentication result includes an authentication level and a data template. The data template is an executable logic that is matched from a preset knowledge base based on the device identification information of the second computing device, and is used to automatically parse the interface information of the second computing device to output the target interface information.

10. A computing device, characterized in that, The computing device includes a memory and a processor; the memory and the processor are coupled; the memory is used to store computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the computing device to perform the access method of the computing device as described in any one of claims 1 to 8.

Images