Device registration method and apparatus
Patent Information
- Application Number
- CN202310462831.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-04-26
- Publication Date
- 2026-10-27
- Estimated Expiration
- 2043-04-26
Smart Images
Figure CN116506401B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a device registration method and apparatus. Background Technology
[0002] In scenarios such as the Internet of Things (IoT) or edge computing, electronic devices need to apply for device registration with target platforms such as cloud management platforms. Device onboarding refers to setting up registration information, including keys and configuration files, in electronic devices to enable secure connection and interaction with target platforms.
[0003] Currently, the registration information required for device registration is pre-loaded into the operating system as a file at the factory stage. However, pre-loading registration information into the operating system as a file is quite complex. Summary of the Invention
[0004] On the one hand, this application provides a device registration method, including:
[0005] The electronic device obtains target registration information from the target server through its baseboard management controller. The target registration information is the information required for the electronic device to apply for registration with the target platform. The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection.
[0006] If the electronic device has an operating system, the target registration information is obtained from the baseboard management controller through the operating system;
[0007] Apply for device registration with the target platform based on the target registration information.
[0008] One possible implementation also includes:
[0009] The target registration information is stored in the internal storage area of the baseboard management controller;
[0010] The step of obtaining the target registration information from the baseboard management controller through the operating system includes:
[0011] The target registration information is obtained from the internal storage area of the baseboard management controller through the operating system.
[0012] Another possible implementation includes:
[0013] The device activation request is sent to the target server via the baseboard management controller of the electronic device;
[0014] In response to the activation instruction of the target server, a communication connection is established between the baseboard management controller and the target server;
[0015] The process of obtaining target registration information from the target server via the baseboard management controller of the electronic device includes:
[0016] Based on the communication connection, target registration information is obtained from the target server through the baseboard management controller of the electronic device.
[0017] Another possible implementation includes:
[0018] Install an operating system and a connection engine for connecting to the target platform on the electronic device;
[0019] The step of obtaining the target registration information from the baseboard management controller through the operating system includes:
[0020] The connection engine is run through this operating system;
[0021] The connection engine sends a registration information request to the operating system.
[0022] The operating system responds to the registration information request, obtains the target registration information from the baseboard management controller, and sends the target registration information to the connection engine.
[0023] In another possible implementation, the target registration information is the registration information obtained by the target server from the target platform according to the configured registration requirement information, which is required for applying for registration with the target platform. The registration requirement information indicates: at least one candidate platform to which registration needs to be applied for with the help of the target server and the number of devices to be applied for registration with the candidate platform, wherein the target platform belongs to the at least one candidate platform.
[0024] Another possible implementation includes:
[0025] The electronic device's unique target key is determined by the electronic device's baseboard management controller;
[0026] The step of obtaining target registration information from the target server through the baseboard management controller of the electronic device based on the communication connection includes:
[0027] Based on the communication connection, a registration information request is sent to the target server through the baseboard management controller. The registration information request carries the target key, so that the target server can request target registration information corresponding to the target key from the target platform.
[0028] The target registration information returned by the target server through the communication connection is obtained through the baseboard management controller.
[0029] In another aspect, this application also provides a device registration apparatus, comprising:
[0030] The first information acquisition unit is used to obtain target registration information from the target server through the baseboard management controller of the electronic device. The target registration information is the information required for the electronic device to apply for registration with the target platform. The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection.
[0031] The second information acquisition unit is used to obtain the target registration information from the baseboard management controller through the operating system when the electronic device has an operating system;
[0032] The device registration unit is used to apply for device registration with the target platform based on the target registration information.
[0033] In one possible implementation, the device further includes:
[0034] An information storage unit is used to store the target registration information in the internal storage area of the baseboard management controller;
[0035] The second information acquisition unit includes:
[0036] The information acquisition subunit is used to obtain the target registration information from the internal storage area of the baseboard management controller through the operating system.
[0037] In yet another possible implementation, the device further includes:
[0038] An activation request unit is used to send a device activation request to a target server via the baseboard management controller of an electronic device.
[0039] An activation connection unit is used to establish a communication connection between the baseboard management controller and the target server in response to the activation instruction of the target server.
[0040] The second information acquisition unit is specifically used to obtain target registration information from the target server through the baseboard management controller of the electronic device based on the communication connection.
[0041] In yet another possible implementation, the device further includes:
[0042] A software installation unit is used to install an operating system on an electronic device and a connection engine for connecting to the target platform;
[0043] The second information acquisition unit includes:
[0044] An engine operation unit, used to run the connection engine through the operating system;
[0045] A request sending unit is used to send a registration information request to the operating system through the connection engine;
[0046] The information acquisition unit is used to respond to the registration information request through the operating system, obtain the target registration information from the baseboard management controller, and send the target registration information to the connection engine.
[0047] In another possible implementation, the target registration information is the registration information obtained by the target server from the target platform according to the configured registration requirement information, which is required for applying for registration with the target platform. The registration requirement information indicates: at least one candidate platform to which registration needs to be applied for with the help of the target server and the number of devices to be applied for registration with the candidate platform, wherein the target platform belongs to the at least one candidate platform.
[0048] In yet another possible implementation, the device further includes:
[0049] The electronic device's unique target key is determined by the electronic device's baseboard management controller;
[0050] The step of obtaining target registration information from the target server through the baseboard management controller of the electronic device based on the communication connection includes:
[0051] Based on the communication connection, a registration information request is sent to the target server through the baseboard management controller. The registration information request carries the target key, so that the target server can request target registration information corresponding to the target key from the target platform.
[0052] The target registration information returned by the target server through the communication connection is obtained through the baseboard management controller. Attached Figure Description
[0053] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0054] Figure 1 This paper illustrates a flowchart of a device registration method provided in an embodiment of this application.
[0055] Figure 2 This illustration shows another flowchart of the device registration method provided in an embodiment of this application;
[0056] Figure 3 This illustration shows an application scenario architecture diagram applicable to the solution of this application embodiment;
[0057] Figure 4 This illustration shows a flowchart of a device registration method provided in an embodiment of this application.
[0058] Figure 5 This illustration shows another flowchart of the device registration method provided in an embodiment of this application;
[0059] Figure 6 This paper shows a schematic diagram of the composition structure of a device registration apparatus provided in an embodiment of this application;
[0060] Figure 7 A schematic diagram of the component architecture of an electronic device provided in an embodiment of this application is shown. Detailed Implementation
[0061] The technical solutions of 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 of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0062] like Figure 1 The illustration shows a flowchart of a device registration method provided in an embodiment of this application. The method in this embodiment can be applied to an electronic device, which can be an electronic device with a Baseboard Management Controller (BMC), such as a server or a mainframe with a BMC, etc., without limitation.
[0063] The method in this embodiment may include:
[0064] S101, obtain target registration information from the target server through the board management controller of the electronic device.
[0065] The target server can be a server other than an electronic device. It can be a server used to manage and control the board management controllers of different electronic devices; for example, it could be a server maintained by the manufacturer that produces the board management controller. The target server can be a standalone server or a cloud server within a cloud service system.
[0066] The target registration information refers to the information required for an electronic device to register with the target platform. This information may include one or more of the following: a key and a configuration file. The specific details may vary depending on the actual scenario, and there are no restrictions on this.
[0067] A target platform is a server system that an electronic device needs to connect to in order to perform specific functions or services. Registering an electronic device with this target platform essentially means adding it to the target platform's device management list, enabling it to provide corresponding services under the platform's management. For example, a target platform could be a cloud management platform in the Internet of Things (IoT) or edge computing. Depending on the specific application scenario, the target platform that the electronic device needs to register with will vary, and there are no restrictions on this.
[0068] The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection.
[0069] S102, if the electronic device has an operating system, the target registration information is obtained from the board management controller through the operating system.
[0070] Understandably, since the BMC of an electronic device can obtain target registration information from the target server, if the electronic device has an operating system installed, the operating system of the electronic device can directly obtain the target registration information from the board management controller. Therefore, it is not necessary to pre-install files related to registration information in the operating system during the production stage, thus decoupling the operating system from the registration information and avoiding complex operations such as pre-installing registration information during the production stage, which naturally reduces the requirements on the supply chain related to electronic devices.
[0071] The operating system can obtain the target registration information by communicating with the baseboard management controller, and there are no restrictions on the specific method by which the operating system obtains the target registration information from the baseboard management controller.
[0072] In one possible implementation, the baseboard management controller has an internal storage area accessible to the operating system. Based on this, after obtaining target registration information, the baseboard management controller can store the target registration information in its internal storage area. Correspondingly, the operating system can retrieve the target registration information from the baseboard management controller's internal storage area.
[0073] In this implementation, the baseboard management controller has an internal storage area accessible to the operating system. This implementation not only enables the operating system to obtain target registration information from the baseboard management controller, but also improves the security of the target registration information by leveraging the relatively secure data access mechanism of the baseboard management controller itself, reducing the possibility of target registration information being leaked due to pre-installation of target registration information in the operating system.
[0074] There are various ways to make the internal storage area of the baseboard management controller accessible to the operating system, and this application does not impose any restrictions on this. For example, in one possible approach, the internal storage area of the baseboard management controller that is accessible to the operating system corresponds to a directory that the operating system can view. Therefore, after the baseboard management controller stores data in the internal storage area, the operating system can see and access the data information stored in the corresponding directory.
[0075] It is understandable that, after the electronic device is powered on, in order to ensure that the electronic device can perform the relevant processing required for device registration, an operating system can be installed on the electronic device before step S103. The installation of the operating system can be initiated by the electronic device itself, or it can be performed after the user sends an instruction to install the operating system; there are no restrictions on this.
[0076] Since the operating system does not need to pre-install registration information and other data corresponding to the target platform, the operating system installed on the electronic device in this application can be any type of operating system, without being bound to the target platform or having an operating system pre-developed to adapt to the target platform, thus providing greater flexibility.
[0077] S103, apply for device registration with the target platform based on the target registration information.
[0078] Depending on the target platform, the specific implementation of electronic devices using target registration information to apply for device registration with the target platform may vary, and this application does not impose any restrictions on this.
[0079] For example, if the target registration information includes a configuration file and a key, the configuration file may include information such as the account required for electronic device registration. Therefore, the electronic device can configure this configuration file locally and send a registration request carrying the key to the target platform based on the configuration file, so as to establish a key-based encrypted communication channel on the target platform. Alternatively, some target platforms may require the electronic device to send the configuration file and key to the target platform during device registration; in this case, the registration request may need to include the configuration file and key.
[0080] Of course, there are other possible methods for device registration, which will not be elaborated here.
[0081] In one possible implementation, to differentiate the device registration processes across different target platforms, this application allows the electronic device to install a connection engine for establishing a connection with the target platform before applying for device registration. Based on this, the electronic device runs the connection engine and applies for device registration with the target platform using the target registration information.
[0082] As can be seen, in this embodiment, the target server can obtain the target registration information required for the electronic device to register with the target platform through a data connection with the target platform. Furthermore, the electronic device can obtain this target registration information from the target server through the baseboard management controller. Based on this, if the electronic device has an operating system, the operating system can directly obtain the target registration information from the baseboard management controller, thus eliminating the need to pre-install the registration information required for registration with the target platform within the operating system. This avoids the complex operation of pre-installing registration information, reduces the requirements for the factory pre-installation stage, and naturally reduces the complexity of registering the electronic device with the target platform.
[0083] In this application, there are various possibilities regarding when and how the target server obtains the target registration information required for the electronic device to register with the target platform.
[0084] For example, in one possible implementation, when a data connection is established between the target server and the target platform, the target server can request the registration information required to register with the target platform at any time. Based on this, the target server can obtain the target registration information in advance before the electronic device's baseboard management controller requests it.
[0085] In this possible implementation, the target server may be configured with registration requirement information, which may indicate: at least one candidate platform to which registration is required through the target server, and the number of devices to be registered to each candidate platform.
[0086] The candidate platform can be any platform that allows electronic devices to register with it, such as a cloud management platform in edge computing or a management platform in the Internet of Things, without limitation. Accordingly, in this application, the target platform to which the electronic device needs to register belongs to at least one of the candidate platforms indicated in the registration requirement information.
[0087] For example, a target server can support applying for registration information from multiple different candidate platforms. In this case, for each candidate platform, the target server can be configured with the number of electronic devices that need to apply for device registration with that candidate platform through the target server. Based on this, the target server can be used to provide different electronic devices with the registration information required to apply for registration with different candidate platforms.
[0088] For example, the target server may simply be bound to a candidate platform. In this case, the target server can only provide the electronic device with the registration information required to apply for device registration with the candidate platform.
[0089] The target server is configured with registration requirement information. For each candidate platform indicated in the registration requirement information, the target server can obtain the same number of registration information entries as the number of devices that need to register with that candidate platform through a connection established with the candidate platform. For example, the target server can request one registration information entry from the candidate platform each time. Alternatively, to improve efficiency, the target server can request multiple registration information entries from the candidate platform at once.
[0090] The process of the target server requesting registration information from the candidate platform and the candidate platform confirming or constructing the registration information can be implemented in various ways, and can be set as needed. This application does not impose any restrictions on this.
[0091] To make it easier to understand, let's take the example of the target server obtaining registration information from a candidate platform as a simple illustration:
[0092] In one scenario, once a data connection is established between the target server and the candidate platform, the target server can send an information allocation request to the candidate platform. This request requests the registration information required for registration with the candidate platform, and can indicate the target number of registration requests. In this case, the candidate platform, in response to the information allocation request, can determine its acceptable target number of registration information copies and return that target number of registration information copies to the candidate platform.
[0093] For example, taking registration information including keys and configuration files as an example, the candidate platform can generate a new key that is different from the existing key and a configuration file corresponding to the new key, and use the newly generated key and configuration file as a set of registration information.
[0094] In another scenario, where each registration record includes a key and a configuration file, the target server can generate a number of distinct keys based on the number of devices corresponding to the candidate platform as specified in the registration requirements. Then, based on the data connection established with the candidate platform, the target server sends an information allocation request to the candidate platform carrying that number of keys for each device.
[0095] Based on this, the candidate platform responds to the information allocation request by generating a configuration file for each key, resulting in a number of device configuration files. Correspondingly, based on a key and its corresponding configuration file, a set of registration information can be determined, ultimately yielding a number of device registration information files. The candidate platform can then send these device configuration files to the target server.
[0096] Of course, the above are just two examples. In actual applications, the process of the candidate platform generating registration information for the target server can adopt other commonly used methods for generating registration information, without any restrictions.
[0097] Based on the above, when an electronic device requests registration information from the target server for registration with the target platform, the target server can select one piece of registration information from at least one piece of registration information already obtained from the target platform as the target registration information and send it to the electronic device. Therefore, the target registration information obtained by the electronic device from the target server is also the registration information required by the target server to apply for registration with the target platform, according to the configured registration requirement information.
[0098] In the above possible scenarios, the target server can obtain the registration information of each candidate platform in advance before the electronic device requests registration information from it. In this way, when the electronic device requests registration information, the server can return the registration information to the electronic device more efficiently. Moreover, the acquisition of registration information is decoupled from the startup of the electronic device and whether an operating system is installed, making the acquisition of registration information independent of the hardware and operating status of the electronic device, which is more flexible and has wider applicability.
[0099] In another possible scenario, the target server can obtain the target registration information required by the electronic device from the target platform after receiving a registration information request from the electronic device. This registration information request is used to request registration information, and this request can trigger the target server to obtain the target registration information required by the electronic device from the target platform.
[0100] For example, the registration information application may indicate the target platform to which the electronic device needs to be registered, or the target server may be pre-configured with the target platform corresponding to the electronic device or its baseboard management controller. Accordingly, in response to the registration information application, the target server requests target registration information from the target platform.
[0101] The process by which the target server requests target registration information from the target platform in response to the registration information request can adopt the implementation methods mentioned above, which will not be elaborated further.
[0102] In one alternative approach, when the registration information includes a key, to enhance key security and ensure its unclonability, the electronic device can determine a unique target key via a baseboard management controller before requesting target registration information. Since this target key is required for the electronic device to apply for registration information, the baseboard management controller can generate a hardware-bound and unique key specific to the electronic device.
[0103] Based on this, the electronic device can send a registration information request to the target server through the baseboard management controller. This registration information request carries the target key, enabling the target server to request target registration information corresponding to the target key from the target platform.
[0104] For example, if the target server sends an information allocation request carrying a target key to the target platform, the target platform will generate target registration information corresponding to and containing that target key. For instance, the target platform generates a configuration file corresponding to the target key, saves the target key and configuration file as target registration information, and sends the target registration information to the target server.
[0105] Correspondingly, the target registration information returned by the target server can be obtained through the baseboard management controller.
[0106] It is understood that in any of the above embodiments of this application, considering that different platforms have different connection engines, the connection engine can realize the communication connection between the electronic device and the platform and complete the registration-related operations. Based on this, the electronic device in this application can also install the corresponding connection engine according to the platform to be registered. The following is a description of one implementation method.
[0107] like Figure 2 As shown, it illustrates another flowchart of the device registration method provided in this application embodiment, which is applied to electronic devices.
[0108] The method in this embodiment may include:
[0109] S201, obtain target registration information from the target server through the board management controller of the electronic device.
[0110] The target registration information is the information required for the electronic device to apply for registration with the target platform.
[0111] The target server and the target platform have a data connection, through which the target server obtains the target registration information.
[0112] The process by which the target server obtains registration information from the target platform, and the process by which the baseboard management controller of the electronic device obtains the target registration information from the target server, can be found in the relevant descriptions of the embodiments of this application, and will not be repeated here.
[0113] S202, which installs an operating system and a connection engine on electronic devices to connect to target platforms.
[0114] The connection engine is a program or component used to establish communication connections and data interaction with the target platform.
[0115] There are many ways to install an operating system and connect an engine on an electronic device, and this application does not limit them.
[0116] It is understandable that, considering that in some cases, applying for device registration with the target platform requires the electronic device to have a runtime library corresponding to the target platform, such as parameters required for the connection engine to run, the electronic device can also install the runtime library corresponding to the target platform and other related software at the same time as installing the connection engine, without any restrictions.
[0117] S203, through which the connection engine runs the operating system.
[0118] For example, if an electronic device detects a command to start a connection engine after the operating system is started, the electronic device can start the connection engine through the operating system.
[0119] S204 sends a registration information request to the operating system through the connection engine.
[0120] The registration information request is used to request the registration information required for device registration.
[0121] S205, the operating system responds to the registration information request, obtains the target registration information from the baseboard management controller, and sends the target registration information to the connection engine.
[0122] For example, if the baseboard management controller stores the target registration information in the internal storage area of the baseboard management controller that is accessible to the operating system, then the operating system obtains the stored target registration information from the internal storage area of the baseboard management controller.
[0123] S206, The connection engine applies for device registration with the target platform based on the target registration information.
[0124] As can be seen, in this embodiment, when the baseboard management controller of the electronic device is started, the electronic device can obtain the target registration information required for the electronic device to register to the target platform through the baseboard management controller, thereby separating the installation of the operating system from the acquisition of the target registration information, so that the acquisition of the target registration information does not depend on the operating system.
[0125] Based on this, after the electronic device installs an operating system and a connection engine for connecting to the target platform, it can send a registration information request to the operating system through the connection engine. This can trigger the operating system to obtain the target registration information from the baseboard management controller, so that the connection engine can obtain the target registration information through the operating system without the operating system pre-installing the registration information file. This eliminates the need to install a specific operating system for a specific platform in the electronic device, allowing the electronic device to flexibly choose any operating system, and naturally reducing the complex operations such as pre-installing the operating system for device registration.
[0126] It is understood that, in this application, to ensure the security of registration information, the electronic device requesting registration information from the target server can be any electronic device that the target server needs to control. Based on this, before the electronic device's baseboard management controller obtains the target registration information from the target server, it can also send a device activation request to the target server through the baseboard management controller. On this basis, only after receiving an activation instruction returned by the target server can the electronic device establish a communication connection between the baseboard management controller and the target server, so that the baseboard management controller can obtain the target registration information from the target server through this communication connection.
[0127] The activation indication signifies that the target server confirms that the electronic device belongs to the electronic device with activation permissions as determined by the target server.
[0128] To facilitate understanding, the following explanations will focus on two different scenarios where electronic devices obtain target registration information corresponding to the target platform from the target server.
[0129] To facilitate understanding of this solution, we will illustrate it using a scenario architecture that this solution is applicable to, such as... Figure 3 This diagram illustrates an interactive scenario architecture to which the device registration method of this application applies.
[0130] exist Figure 3 The interaction scenario includes the target server, the target platform, and electronic devices.
[0131] The electronic device has a baseboard management controller and a processor architecture. The processor architecture may include a processor and memory, and an operating system, a connection engine for connecting to the target platform, and other software programs can run on the processor architecture.
[0132] exist Figure 3 Based on this, let's first take the example of the target server obtaining registration information from the target platform before the baseboard management controller of the electronic device issues a device activation request.
[0133] exist Figure 3 Based on, combined Figure 4 To explain, Figure 4 This illustration shows an interactive flow diagram provided by an embodiment of this application. The method of this embodiment includes:
[0134] S401, when the target server establishes a data connection with the target platform, the target server obtains at least one set of registration information from the target platform based on the configured registration requirement information.
[0135] For example, the registration requirement information indicates the number of devices to be registered to the target platform. This number of devices can be at least one, and correspondingly, the number of registration information copies obtained by this application is the same as the number of devices.
[0136] It should be noted that, in Figure 3 The scenario only shows one platform, the target platform, for different electronic devices to apply for registration. However, in practical applications, the target server can establish data connections with multiple different candidate platforms. Therefore, by configuring the number of devices to register with different candidate platforms in the registration requirement information, electronic devices under the control of the target server can choose different candidate platforms for device registration. This makes the solution applicable to a variety of different platforms for device registration, thus having wider applicability.
[0137] The specific process by which the target server obtains registration information from the target platform can be found in the previous section on the process by which the target server obtains registration information from the candidate platform, and will not be repeated here.
[0138] S402: After the baseboard management controller of the electronic device is started, a device activation request is sent to the target server through the baseboard management controller of the electronic device.
[0139] S403, in response to the device activation request, the target server, after confirming that the electronic device has activation authority, sends an activation instruction to the electronic device to establish a communication connection between the electronic device's board management controller and the target server.
[0140] Among them, the device activation request is used to request to become a legitimate electronic device under the control of the target server.
[0141] For example, if an electronic device is one that the target server has management authority over, then before the electronic device leaves the factory, it will be configured with activation key and other activation credential information that the target server can recognize. Based on this, the device activation request sent by the electronic device's baseboard management controller can carry the activation credential information of the electronic device. If the target server confirms that the activation credential information is valid credential information in the target server, then it confirms that the electronic device has been added to the target server's list of managed devices, and can naturally send an activation instruction to the electronic device.
[0142] In an alternative approach, the electronic device can be deployed as an edge server for the target server. Therefore, the device activation request can be an edge device activation request. The specific activation process is similar to that described above and will not be repeated here.
[0143] Of course, there are other possibilities in the process of an electronic device requesting activation from the target server, and there are no restrictions on this.
[0144] Combination Figure 3 and Figure 4 It can be seen that the communication connection between the electronic device and the target server is a communication connection established based on the baseboard management controller of the electronic device. In this case, the target server determines the electronic device where the baseboard management controller is located as an electronic device that needs to be registered and controlled.
[0145] S404, based on the communication connection between the electronic device's baseboard management controller and the target server, the electronic device obtains the target registration information required to register with the target platform from the target server through the baseboard management controller, and stores the target registration information in the internal storage area of the baseboard management controller.
[0146] Among them, the target registration information refers to at least one set of registration information obtained by the target server from the target platform.
[0147] For example, the baseboard management controller sends a registration information request to the target server, which can indicate the target platform to which an electronic device has applied for registration. Based on this, the target server can determine the target registration information that has not yet been assigned to other electronic devices from at least one set of registration information obtained from the target platform, and send the target registration information to that electronic device.
[0148] Of course, the registration information application does not specify the target platform. Instead, the target platform that the electronic device can apply to register is pre-configured in the baseboard management controller, so that the target server obtains an unassigned registration information from at least one registration information corresponding to the target platform as the target registration information and sends it to the electronic device.
[0149] The internal storage area of the baseboard management controller is accessible to the operating system.
[0150] S405: Install an operating system and a connection engine for connecting to the target platform on the electronic device, start the operating system, and run the connection engine through the operating system.
[0151] S406, electronic devices send registration information requests to the operating system through the connection engine.
[0152] S407, the electronic device responds to the registration information request through the operating system, obtains the target registration information from the internal storage area of the baseboard management controller, and sends the target registration information to the connection engine.
[0153] S408, electronic devices apply for device registration with the target platform based on the target registration information through the connection engine.
[0154] The specific process by which the connection engine applies for device registration with the target platform can use any device registration method without any restrictions.
[0155] Depend on Figure 3 and Figure 4 As can be seen, unlike the communication connection established between the electronic device and the target server through the baseboard management controller, the connection between the electronic device and the target platform after the electronic device applies for registration with the target platform through the connection engine is based on the connection engine running in the processor of the electronic device and the connection established with the target platform.
[0156] Below Figure 3 Based on this, the process by which the target server requests registration information from the target platform only after receiving the activation request from the electronic device is explained.
[0157] like Figure 5 As shown, this illustration depicts another flow interaction diagram of the device registration method provided in this application embodiment. The method in this embodiment may include:
[0158] S501, after the baseboard management controller of the electronic device is started, sends a device activation request to the target server through the baseboard management controller of the electronic device.
[0159] S502, in response to the device activation request, the target server, after confirming that the electronic device has activation authority, sends an activation instruction to the electronic device to establish a communication connection between the electronic device's board management controller and the target server.
[0160] S503 determines the unique target key of the electronic device through the board management controller of the electronic device.
[0161] The target key can be a key that is bound to the baseboard management controller of the electronic device or other hardware of the electronic device, such as a unique key generated by leveraging the hardware characteristics of the electronic device, so that the target key is bound to the hardware of the electronic device.
[0162] S504, based on the communication connection between the electronic device's baseboard management controller and the target server, the electronic device sends a registration information application to the target server through the baseboard management controller.
[0163] The registration information application carries the target key.
[0164] S505, In response to the registration information request, the target server requests the target registration information corresponding to the target key from the target platform.
[0165] S506, the target platform generates a configuration file corresponding to the target key and sends the target registration information containing the target key and configuration file to the target server.
[0166] In this embodiment, after the baseboard management controller of the electronic device is started, the baseboard management controller of the electronic device requests activation from the target server and sends the target key for registration with the target platform to the target server. Only then will the target server request registration information from the target platform. This is more suitable for scenarios where the key requirements for registering with the target platform are high.
[0167] S507, the target server sends the target registration information to the baseboard management controller of the electronic device.
[0168] S508, the substrate management controller stores the target registration information in the internal storage area.
[0169] S509 installs an operating system and a connection engine for connecting to the target platform on the electronic device, starts the operating system, and runs the connection engine through the operating system.
[0170] In S510, electronic devices send registration information requests to the operating system through the connection engine.
[0171] S511, the electronic device responds to the registration information request through the operating system, obtains the target registration information from the internal storage area of the board management controller, and sends the target registration information to the connection engine.
[0172] S512, electronic devices apply for device registration with the target platform based on the target registration information through the connection engine.
[0173] Corresponding to the device registration method provided in the embodiments of this application, this application also provides a device registration apparatus.
[0174] like Figure 6 The diagram illustrates a possible structural composition of a device registration apparatus provided in this application, which can be applied to electronic devices. The apparatus may include:
[0175] The first information acquisition unit 601 is used to obtain target registration information from the target server through the baseboard management controller of the electronic device. The target registration information is the information required for the electronic device to apply for registration with the target platform. The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection.
[0176] The second information acquisition unit 602 is used to obtain the target registration information from the baseboard management controller through the operating system when the electronic device has an operating system.
[0177] The device registration unit 603 is used to apply for device registration with the target platform based on the target registration information.
[0178] In one possible implementation, the device further includes:
[0179] An information storage unit is used to store the target registration information in the internal storage area of the baseboard management controller;
[0180] The second information acquisition unit includes:
[0181] The information acquisition subunit is used to obtain the target registration information from the internal storage area of the baseboard management controller through the operating system.
[0182] In yet another possible implementation, the device further includes:
[0183] An activation request unit is used to send a device activation request to a target server via the baseboard management controller of an electronic device.
[0184] An activation connection unit is used to establish a communication connection between the baseboard management controller and the target server in response to the activation instruction of the target server.
[0185] The second information acquisition unit is specifically used to obtain target registration information from the target server through the baseboard management controller of the electronic device based on the communication connection.
[0186] In yet another possible implementation, the device further includes:
[0187] A key determination unit is used to determine a unique target key for the electronic device through the baseboard management controller of the electronic device;
[0188] The second information acquisition unit includes:
[0189] An information request unit is used to send a registration information request to a target server through a baseboard management controller based on the communication connection. The registration information request carries the target key, so that the target server requests target registration information corresponding to the target key from the target platform.
[0190] An information receiving unit is used to obtain the target registration information returned by the target server through the communication connection via the baseboard management controller.
[0191] In yet another possible implementation, the device further includes:
[0192] A software installation unit is used to install an operating system on an electronic device and a connection engine for connecting to the target platform;
[0193] The second information acquisition unit includes:
[0194] An engine operation unit, used to run the connection engine through the operating system;
[0195] A request sending unit is used to send a registration information request to the operating system through the connection engine;
[0196] The information acquisition unit is used to respond to the registration information request through the operating system, obtain the target registration information from the baseboard management controller, and send the target registration information to the connection engine.
[0197] In another possible implementation, the target registration information obtained by the first information obtaining unit is the registration information required by the target server to apply for registration with the target platform, obtained from the target platform according to the configured registration requirement information. The registration requirement information indicates at least one candidate platform to which registration needs to be applied for with the help of the target server and the number of devices to be applied for registration with the candidate platform. The target platform belongs to the at least one candidate platform.
[0198] Furthermore, this application also provides an electronic device, such as Figure 7 As shown, it illustrates a schematic diagram of the composition structure of the electronic device. The electronic device can be any type of electronic device, and the electronic device includes at least a baseboard management controller 701, a processor 702, and a memory 703.
[0199] The baseboard management controller 701 is at least used to obtain target registration information from a target server. The target registration information is the information required for the electronic device to apply for registration with the target platform. The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection.
[0200] The processor 702 is at least used to, when the electronic device has an operating system, obtain the target registration information from the baseboard management controller through the operating system; and apply for device registration with the target platform based on the target registration information.
[0201] The memory 703 is used to store the programs required for the processor to perform operations.
[0202] Of course, the electronic device can also have more than Figure 7 There are no restrictions on the number of more or fewer components.
[0203] On the other hand, this application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the device registration method as described in any of the above embodiments.
[0204] This application also proposes a computer program comprising computer instructions stored in a computer-readable storage medium. When executed on an electronic device, the computer program performs the device registration method as described in any of the above embodiments.
[0205] It is understood that in this application, the terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings are used to distinguish similar parts and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that illustrated herein.
[0206] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. Furthermore, the features described in the various embodiments of this specification can be substituted or combined with each other, enabling those skilled in the art to implement or use this application. For apparatus embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.
[0207] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only 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.
[0208] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[0209] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A device registration method, comprising: The electronic device obtains target registration information from the target server through its baseboard management controller. The target registration information is the information required for the electronic device to apply for registration with the target platform. The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection. The target registration information is stored in the internal storage area of the baseboard management controller; When the electronic device has an operating system, the target registration information is obtained from the internal storage area of the baseboard management controller through the operating system. Apply for device registration with the target platform based on the target registration information.
2. The method according to claim 1, further comprising: The device activation request is sent to the target server via the baseboard management controller of the electronic device; In response to the activation instruction of the target server, a communication connection is established between the baseboard management controller and the target server; The process of obtaining target registration information from the target server via the baseboard management controller of the electronic device includes: Based on the communication connection, target registration information is obtained from the target server through the baseboard management controller of the electronic device.
3. The method according to claim 1, further comprising: Install an operating system and a connection engine for connecting to the target platform on the electronic device; The step of obtaining the target registration information from the baseboard management controller through the operating system includes: The connection engine is run through this operating system; The connection engine sends a registration information request to the operating system. The operating system responds to the registration information request, obtains the target registration information from the baseboard management controller, and sends the target registration information to the connection engine.
4. The method according to claim 1 or 2, wherein the target registration information is the registration information required for applying for registration with the target platform obtained by the target server from the target platform according to the configured registration requirement information, and the registration requirement information indicates: at least one candidate platform to which registration needs to be applied for with the help of the target server and the number of devices to be applied for registration with the candidate platform, and the target platform belongs to the at least one candidate platform.
5. The method according to claim 2, further comprising: The electronic device's unique target key is determined by the electronic device's baseboard management controller; The step of obtaining target registration information from the target server through the baseboard management controller of the electronic device based on the communication connection includes: Based on the communication connection, a registration information request is sent to the target server through the baseboard management controller. The registration information request carries the target key, so that the target server can request target registration information corresponding to the target key from the target platform. The target registration information returned by the target server through the communication connection is obtained through the baseboard management controller.
6. A device registration apparatus, comprising: The first information acquisition unit is used to obtain target registration information from the target server through the baseboard management controller of the electronic device. The target registration information is the information required for the electronic device to apply for registration with the target platform. The target server and the target platform have a data connection, and the target server obtains the target registration information through the data connection. An information storage unit is used to store the target registration information in the internal storage area of the baseboard management controller; The second information acquisition unit is configured to, when the electronic device has an operating system, obtain the target registration information from the internal storage area of the baseboard management controller through the operating system. The device registration unit is used to apply for device registration with the target platform based on the target registration information.
7. The apparatus according to claim 6, further comprising: An activation request unit is used to send a device activation request to a target server via the baseboard management controller of an electronic device. An activation connection unit is used to establish a communication connection between the baseboard management controller and the target server in response to the activation instruction of the target server. The second information acquisition unit is specifically used to obtain target registration information from the target server through the baseboard management controller of the electronic device based on the communication connection.
8. The apparatus according to claim 6, further comprising: A software installation unit is used to install an operating system on an electronic device and a connection engine for connecting to the target platform; The second information acquisition unit includes: An engine operation unit, used to run the connection engine through the operating system; A request sending unit is used to send a registration information request to the operating system through the connection engine; The information acquisition unit is used to respond to the registration information request through the operating system, obtain the target registration information from the baseboard management controller, and send the target registration information to the connection engine.
Citation Information
Patent Citations
Cloud service access method and device, equipment and medium
CN111262866A