CN116010103A - Device management method and electronic device - Google Patents

Device management method and electronic device Download PDF

Info

Publication number
CN116010103A
CN116010103A CN202310098922.XA CN202310098922A CN116010103A CN 116010103 A CN116010103 A CN 116010103A CN 202310098922 A CN202310098922 A CN 202310098922A CN 116010103 A CN116010103 A CN 116010103A
Authority
CN
China
Prior art keywords
target
parameters
devices
task
current
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310098922.XA
Other languages
Chinese (zh)
Inventor
郝伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Priority to CN202310098922.XA priority Critical patent/CN116010103A/en
Publication of CN116010103A publication Critical patent/CN116010103A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Debugging And Monitoring (AREA)

Abstract

The application provides a device management method and electronic equipment, and relates to the technical field of Internet of things. The device management method comprises the following steps: firstly, acquiring target parameters according to a set period, wherein the target parameters are the device parameters of each current target device or the resource demand parameters of each current task. The device parameters comprise device types and device states, wherein the device states comprise an idle state and an occupied state; the resource demand parameter includes the number of occupancy for each type of target device. And then, determining the number of idle devices in various target devices according to the target parameters. And finally, obtaining the bearing capacity of each type of target equipment at the current node according to the number of the idle equipment in each type of target equipment. Through the technical scheme, the automatic management and evaluation of the occupied state of the laboratory resources and the bearing capacity of the resources can be realized.

Description

Device management method and electronic device
[ field of technology ]
The application relates to the technical field of the internet of things, in particular to a device management method and electronic equipment.
[ background Art ]
The research laboratory is a place dedicated to supporting smart device research and development work. The equipment resources used for assisting the research and development work in the research and development laboratory are numerous, such as computers, power supplies, charging equipment, SIM cards and the like. In order to meet the requirements of various research and development tasks on equipment resources and ensure the smooth progress of the research and development tasks, various equipment resources of a research laboratory are required to be managed so as to determine the resource occupation condition, the bearing capacity surplus and the like of each time node. In the prior art, the management process is realized mainly by manual mode, which is time-consuming and labor-consuming and has poor instantaneity.
[ invention ]
The embodiment of the application provides a device management method and electronic equipment, which can be used for realizing automatic management and evaluation of a laboratory resource occupation state and a resource bearing capacity based on the technology of the Internet of things.
In a first aspect, an embodiment of the present application provides a device management method, including: acquiring target parameters according to a set period, wherein the target parameters are equipment parameters of current target equipment or resource demand parameters of current tasks; the device parameters comprise device types and device states, wherein the device states comprise an idle state and an occupied state; the resource demand parameters comprise the occupation quantity of various target devices; determining the number of idle devices in various target devices according to the target parameters; and obtaining the bearing capacity of each type of target equipment at the current node according to the number of the idle equipment in each type of target equipment.
According to the technical scheme, the number of idle devices in various devices can be automatically calculated by acquiring the parameters of the devices or the task parameters in the laboratory in the process of using the research laboratory. Therefore, the management of the occupied state of the laboratory resources and the evaluation of the bearing capacity of the resources can be realized.
In one possible implementation manner, each target device is configured with an identification card, and device parameters are stored in the identification card; acquiring the device parameters of each current target device according to a set period, wherein the method comprises the following steps: and receiving the device parameters read and sent by each target device from the identity card according to the set period.
In the implementation mode, each device in the laboratory can update the device parameters in the personal identification card according to the change condition of the self state, and actively send the device parameters to the device for executing the device management method. Thereby improving the acquisition efficiency of the equipment parameters and being beneficial to improving the equipment management efficiency.
In one possible implementation manner, determining the number of idle devices in each type of target device according to the resource demand parameters of each task at present includes: determining the occupied quantity of each current task to the N-type target equipment according to the resource demand parameters of each current task; determining the number of idle devices in the N-th type target devices according to the occupied number of each task to the N-th type target devices; the N-type target equipment is any type of target equipment in various types of target equipment.
In one possible implementation manner, after determining the number of hollow devices in each type of target device according to the target parameter, the method further includes: before a new task is started, the load capacity of the current various target devices to the new task is determined.
In the implementation manner, the obtained number of hollow devices in various devices can be used for evaluating the load capacity of the current various devices before a new task is started. Therefore, the automatic comprehensive assessment of the bearing capacity of the laboratory can be realized, and the utilization rate maximization of the bearing capacity of the laboratory is improved.
In one possible implementation manner, before starting a new task, determining the load capacity of the current various target devices to the new task includes: before a new task is started, determining estimated resource demand parameters of the new task; and determining the load capacity of the current various target devices to the new task according to the estimated resource demand parameters.
In one possible implementation, determining the estimated resource requirement parameter of the new task includes: acquiring each historical resource demand parameter of a historical task; determining a plurality of target values from each historical resource demand parameter; and determining the estimated resource demand parameters of the new task according to the weighted results of the target values.
In the implementation manner, the resource demand parameters of the new task can be predicted based on the resource demand parameters of the previous tasks, so that the assessment accuracy of the load capacity is improved.
In one possible implementation manner, under the condition that it is determined that the current various target devices cannot load new tasks according to the estimated resource demand parameters, the method further includes: the shortage amount of each type of target device is determined.
In the implementation mode, the shortage quantity of various target devices is calculated, so that resource shortage early warning is formed, and a user is assisted to timely supplement the target devices or reduce the target devices.
In one possible implementation manner, the method further includes: and updating the shortage quantity of each type of target equipment in response to the completion of the current at least one task.
In a second aspect, an embodiment of the present application provides an electronic device, including: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method according to the first aspect.
In a third aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a data interface, where the processor reads an instruction stored on a memory through the data interface, and is capable of performing the method according to the first aspect.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing computer instructions that cause the computer to perform the method according to the first aspect.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a device management method provided in an embodiment of the present application;
FIG. 2 is a flowchart of another device management method according to an embodiment of the present application;
FIG. 3 is a flowchart of another device management method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an apparatus management device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
[ detailed description ] of the invention
For a better understanding of the technical solutions of the present application, embodiments of the present application are described in detail below with reference to the accompanying drawings.
It should be understood that the described embodiments are merely some, but not all, of the embodiments of the present application. All other embodiments, based on the embodiments herein, which would be apparent to one of ordinary skill in the art without making any inventive effort, are intended to be within the scope of the present application.
The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
A large amount of equipment resources are generally configured in a research laboratory to assist in research and development of various intelligent products. After a development task is started, multiple device resources are usually required, and if the free resources are insufficient, the development task cannot be supported. Therefore, in order to ensure that various research and development tasks are smoothly carried out, the application provides an equipment management method which is used for overall management of equipment resources in a research and development laboratory so as to determine resource occupation conditions and bearing capacity surplus of each time node. The device management method provided by the application can be executed on any device, such as a device management server and the like.
Fig. 1 is a flowchart of a device management method according to an embodiment of the present application, where, as shown in fig. 1, the device management method may include:
step 101, obtaining device parameters of each current target device.
In the embodiment of the application, the target device refers to resource devices used for assisting in completing research and development tasks in any research and development laboratory. The kinds of the target devices may be plural, for example, a mobile phone, a charger, a power source, etc., and the number of each target device may be plural.
In the embodiment of the application, an identity identification card can be configured for each target device. The identification card may be a non-physical card based on software or a physical card based on hardware. The identification card may have device parameters stored therein. The device parameters may include, in particular, device placement location, device category, device number, device status, associated tasks, etc. Where the device placement position may be represented by a number of the rack, for example, assuming that the target device 1 is placed on the rack 100, the device placement position of the target device 1 may be 100. The device state may be used to indicate whether the device is used in association with a task, and the device state may include both an idle state and an occupied state. The associated task may be used to represent a development task currently occupying the target device.
The device parameters stored in each target device identification card can be initialized by the user. In the using process of the target equipment, the target equipment can also update the equipment parameters in the identity card in real time according to the condition that the target equipment is used by being associated with the task. For example, the device state can be updated in real time according to the situation that the target device is used in a task association, and when the target device is used in the task association, the device state is updated to be an occupied state; and when the task is completed, the target equipment is released and updated to an idle state.
Based on the above description, in the embodiment of the application, the device parameters of each target device in the research and development laboratory can be obtained according to the set period, so as to realize the automatic management of the resource state in the laboratory area. Specifically, the device parameters read and sent from the self identity card by each target device in a set period can be received. The manner in which the respective target devices send the device parameters may be wireless or wired, which is not limited in this application.
Step 102, determining the number of idle devices in each type of target device according to the device parameters of each current target device.
Because the device parameters of the target devices comprise the device types and the device states, the number of the hollow devices in each type of target device can be obtained according to the device types and the device states of each target device after the device parameters of each target device are received.
After the number of hollow devices in various target devices is obtained, the bearing capacity of various target devices at the current node can be obtained based on the number of hollow devices in various target devices. The greater the number of idle devices, the greater the bearer capability and vice versa.
Through the technical scheme, the equipment parameters of each target equipment can be periodically acquired, so that the automatic management of equipment resources is realized, the resource occupation condition and the bearing capacity surplus of each time node are obtained, and the load capacity assessment of the newly added task can be conveniently realized when the new task is added.
Fig. 2 is a flowchart of another device management method provided in the embodiment of the present application, and as shown in fig. 2, the device management method provided in the embodiment of the present application may include:
step 201, obtaining the resource demand parameters of each current task.
In the embodiment of the application, each research and development task in operation has specific resource demand parameters, and the resource demand parameters comprise the occupation quantity, the occupation duration and the like of various target devices. Taking a mobile phone call test task as an example, the resource requirement parameters may include: 10 mobile phone prototype resources are occupied, and each mobile phone prototype resource needs to complete making calls 500 times. Taking power supply test as an example, the resource requirement parameters may include: and occupies 100 power resources, and each power resource needs to be charged for 60 minutes.
Based on the above description, in the embodiment of the present application, the resource demand parameters of each task that is being operated may be obtained according to the set period.
Step 202, determining the number of idle devices in various target devices according to the resource demand parameters of the current tasks.
In a practical scenario, there may be multiple types of target devices that each task needs to occupy, and there may also be multiple numbers of occupied target devices of each type. Based on this, in the embodiment of the present application, after the resource demand parameters of each task are obtained, a polling manner may be adopted to count the target devices occupied by each task in turn, so as to obtain the number of idle devices in each type of target device.
Specifically, first, the number of occupied N-th target devices by each task can be determined according to the resource demand parameters of each task. Then, the number of empty devices in the N-th type of target devices can be determined according to the occupied number of the N-th type of target devices by each task. The N-type target equipment is any type of target equipment in various types of target equipment.
For ease of understanding, the following description will be given by taking the first type of target device Resource (1) as an example.
Firstly, each task can be polled currently to obtain the occupation quantity of each task to the first class target device Resource (1).
Specifically, the occupation number of Task one Task (1) to the first type of target device Resource (1) can be calculated sequentially: task (1) ×resource (1) ×requ i request (1) ×re l at i on (1), and Task two Task (2) occupy a number of first class target devices Resource (1): task (2) Resource (1) Requ i request (1) Re l at i on (1) until Task n Task (n) occupies a number of target devices Resource (1) of the first type: task (n) Resource (1) Requ i request (1) Re l at i on (1).
The Task (n) is used for representing tasks, re l at on (n) is used for representing the occupied quantity of various target equipment resources (n), requ i segment (n) is used for representing whether the target equipment resources (n) are occupied or not, the value of the Requ i segment (n) comprises 0 or 1, the occupied quantity is 1, and the unoccupied quantity is 0.
Then, the total occupied amount of each task to the first type target device Resource (1) is obtained by performing accumulated weighted calculation on the occupied amount of each task to the first type target device Resource (1), so as to obtain the total occupied amount Requ i redNumberResource (1) of each task to the first type target device Resource (1).
Further, the number of idle devices of the first type of target device Resource (1) may be calculated according to the total occupied amount Requ i redNumberResource (1) of the first type of target device Resource (1) and the total number Tota l NumberResource (1) of the first type of target device Resource (1):
I d l eNumberResource(1)=Tota l NumberResource(1)-
Requ i redNumberResource(1)。
with such a push, the number I d l eNumberResource (n) of idle devices of each type of target device can be calculated one by one.
After the number of hollow devices in various target devices is obtained, the bearing capacity of various target devices at the current node can be obtained based on the number of hollow devices in various target devices. The greater the number of idle devices, the greater the bearer capability and vice versa.
Through the technical scheme, the resource demand parameters of each task in operation can be periodically acquired, and the number of idle devices in each type of target device can be calculated based on the resource demand parameters. Therefore, the management of equipment resources is realized, the resource occupation condition and the bearing capacity surplus of each time node are obtained, and the load capacity assessment result of the newly added task is conveniently determined when the new task is added.
In another embodiment of the present application, after determining the number of idle devices in each type of target device, the load capability of the current target device to the new task may be determined based on the number of idle devices in each type of target device before the new task is started.
Fig. 3 is a flowchart of another device management method provided in the embodiment of the present application, and as shown in fig. 3, the device management method provided in the embodiment of the present application may include:
step 301, determining estimated resource requirement parameters of a new task before the new task is started.
In an actual scenario, before a new task is started, the number of various target devices which need to be occupied, the occupied time length and the like are often not determined. Therefore, to evaluate the load capacity of the existing device resources on the new task, it is necessary to obtain the estimated resource demand parameters of the new task.
In the embodiment of the application, the resource demand parameters of the new task can be estimated based on the historical resource demand parameters of each historical task in a previous period of time.
Specifically, first, each historical resource demand parameter of the historical task may be obtained. The history task may be a plurality of history tasks of the same type as the new task, or may be a plurality of history tasks of various types. Then, a number of target values may be determined from each of the historical resource demand parameters. The number of target values may include any one or more of a maximum value, a minimum value, and an average value of the respective historical resource demand parameters. Finally, the estimated resource demand parameters of the new task can be determined according to the weighted results of the target values.
Step 302, determining the load capacity of the current various target devices to the new task according to the estimated resource demand parameters.
According to the estimated resource demand parameters, if the number of the idle devices in the current various target devices is larger than the estimated resource demand parameters, determining that the current various target devices can load new tasks; otherwise, determining that the current various target devices cannot load new tasks.
Further, in the embodiment of the application, under the condition that the current various target devices cannot load new tasks, the shortage number of the various target devices can be further determined. And after at least one task is executed and the occupied target equipment is released, the shortage quantity of various target equipment can be updated.
In the embodiment of the application, the shortage quantity of various target devices can reflect the type of the devices to be supplemented in the laboratory. For various kinds of target devices whose shortage amount is continuously high, a new configuration can be made to cope with the risk of resource shortage. For various target devices which do not have shortage and the quantity of which continuously has surplus, the resource transfer can be carried out or the utilization rate of the target devices can be improved.
Fig. 4 is a schematic structural diagram of an apparatus management device according to an embodiment of the present application. As shown in fig. 4, the above apparatus may include: an acquisition module 41 and a determination module 42.
The obtaining module 41 is configured to obtain, according to a set period, a target parameter, where the target parameter is a device parameter of each current target device or a resource requirement parameter of each current task. The device parameters comprise device types and device states, wherein the device states comprise an idle state and an occupied state; the resource demand parameter includes the number of occupancy for each type of target device.
A determining module 42, configured to determine the number of hollow devices in each type of target device according to the target parameters.
And the evaluation module 43 is configured to obtain the bearing capacity of each type of target device at the current node according to the number of idle devices in each type of target device.
In a specific implementation manner, each target device is configured with an identity card, and the identity card stores device parameters; the obtaining module 41 is specifically configured to: and receiving the device parameters read and sent by each target device from the identity card.
In a specific implementation manner, the determining module 42 is specifically configured to determine, according to a resource requirement parameter of each current task, an occupied number of each current task on the nth class target device; determining the number of idle devices in the N-th type target devices according to the occupied number of each task to the N-th type target devices; the N-type target equipment is any type of target equipment in various types of target equipment.
In a specific implementation, the determining module 42 is further configured to determine, before the new task is started, a loading capability of the current various target devices on the new task.
In a specific implementation, the determining module 42 is specifically configured to determine, before the new task is started, an estimated resource requirement parameter of the new task; and determining the load capacity of the current various target devices to the new task according to the estimated resource demand parameters.
In a specific implementation manner, the determining module 42 is specifically configured to obtain each historical resource requirement parameter of the historical task; determining a plurality of target values from each historical resource demand parameter; and determining the estimated resource demand parameters of the new task according to the weighted results of the target values.
In a specific implementation manner, the determining module 42 is further configured to determine the number of shortages of each type of target device when it is determined that the current each type of target device cannot load a new task according to the estimated resource demand parameter.
In one particular implementation, the determination module 42 is further configured to update the number of shortages of each type of target device in response to the current completion of the at least one task.
By the technical scheme, management of the occupied state of the laboratory resources and evaluation of the bearing capacity of the resources can be automatically realized.
Fig. 5 is a schematic structural diagram of another electronic device according to an embodiment of the present application. As shown in fig. 5, the electronic device may include at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to execute the device management method provided in the embodiment of the present application.
The embodiment is not limited to the specific form of the electronic device.
Fig. 5 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present application. The electronic device shown in fig. 5 is only an example and should not be construed as limiting the functionality and scope of use of the embodiments herein.
As shown in fig. 5, the electronic device is in the form of a general purpose computing device. Components of an electronic device may include, but are not limited to: one or more processors 410, a memory 430, and a communication bus 440 that connects the different system components (including the memory 430 and the processor 410).
The communication bus 440 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. For example, these architectures include, but are not limited to, industry standard architecture (I ndustry Standard Arch I tecture; below: isa) bus, micro channel architecture (M I cro Channe l Arch I tecture; below: MAC) bus, enhanced isa bus, video electronics standards association (Vi deo E l ectron I cs Standards Assoc I at I on; below: VESA) local bus, and peripheral component interconnect (Per I phera l Component I nterconnect I on; below: PC I) bus.
Electronic devices typically include a variety of computer system readable media. Such media can be any available media that can be accessed by the electronic device and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 430 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) and/or cache memory. The electronic device may further include other removable/non-removable, volatile/nonvolatile computer system storage media. Although not shown in fig. 5, a magnetic disk drive for reading from and writing to a removable nonvolatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable nonvolatile optical disk (e.g., optical disk read only memory (Compact D i sc Read On l y Memory; hereinafter CD-ROM), digital versatile disk (D i g i ta l Vi deo D i sc Read On l y Memory; hereinafter DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to communication bus 440 by one or more data medium interfaces. Memory 430 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments of the present application.
A program/utility having a set (at least one) of program modules may be stored in the memory 430, such program modules including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules generally perform the functions and/or methods in the embodiments described herein.
The electronic device may also communicate with one or more external devices (e.g., keyboard, pointing device, display, etc.), with one or more devices that enable a user to interact with the electronic device, and/or with any device (e.g., network card, modem, etc.) that enables the electronic device to communicate with one or more other computing devices. Such communication may occur through communication interface 420. Moreover, the electronic device may also communicate with one or more networks (e.g., local area network (Loca l Area Network; hereinafter: LAN), wide area network (W i de Area Network; hereinafter: WAN) and/or a public network, such as the Internet) via a network adapter (not shown in FIG. 5) that may communicate with other modules of the electronic device via the communication bus 440. It should be appreciated that although not shown in fig. 5, other hardware and/or software modules may be used in connection with an electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk arrays (Redundant Ar rays of I ndependent Dr I ves; hereinafter referred to as RA ID) systems, tape drives, data backup storage systems, and the like.
The processor 410 executes various functional applications and device management by running programs stored in the memory 430, for example, implementing the device management method provided in the embodiment of the present application.
The embodiment of the application also provides a computer readable storage medium, which stores computer instructions for causing the computer to execute the device management method provided by the embodiment of the application.
Any combination of one or more computer readable media may be utilized as the above-described computer readable storage media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (Read On l y Memory; hereinafter ROM), an erasable programmable read-only memory (Erasab l e Programmab l e Read On l y Memory; hereinafter EPROM) or flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "plurality" is at least two, such as two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims (11)

1. A device management method, comprising:
acquiring target parameters according to a set period, wherein the target parameters are equipment parameters of current target equipment or resource demand parameters of current tasks; the device parameters comprise a device class and a device state, wherein the device state comprises an idle state and an occupied state; the resource demand parameters comprise the occupation quantity of various target devices;
determining the number of idle devices in various target devices according to the target parameters;
and obtaining the bearing capacity of the various target devices at the current node according to the number of the hollow devices in the various target devices.
2. The method of claim 1, wherein each of the target devices is configured with an identification card, and wherein the identification card stores the device parameters;
acquiring the device parameters of each current target device according to a set period, wherein the method comprises the following steps:
and receiving the device parameters read and sent by each target device from the identity card according to a set period.
3. The method of claim 1, wherein determining the number of hollow devices in each type of target device based on the resource demand parameters of each current task comprises:
determining the occupied quantity of each current task to the N-type target equipment according to the resource demand parameters of each current task;
determining the number of idle devices in the N-th type target devices according to the occupied number of each task to the N-th type target devices;
the N-th target device is any type of target device in the various types of target devices.
4. The method of claim 1, wherein after determining the number of hollow devices in each type of target device based on the target parameter, the method further comprises:
before a new task is started, the load capacity of the current various target devices on the new task is determined.
5. The method of claim 4, wherein determining the load capacity of the current classes of target devices for a new task prior to initiation of the new task comprises:
before a new task is started, determining estimated resource demand parameters of the new task;
and determining the load capacity of the current various target devices to the new task according to the estimated resource demand parameters.
6. The method of claim 5, wherein determining the estimated resource requirement parameter for the new task comprises:
acquiring each historical resource demand parameter of a historical task;
determining a plurality of target values from the historical resource demand parameters;
and determining the estimated resource demand parameters of the new task according to the weighted results of the target values.
7. The method of claim 5, wherein in the case where it is determined that the current target devices cannot load the new task according to the estimated resource requirement parameter, the method further comprises:
and determining the shortage quantity of the various target devices.
8. The method of claim 7, wherein the method further comprises:
and updating the shortage quantity of the various target devices in response to the completion of the current at least one task.
9. An electronic device, comprising:
at least one processor; and
at least one memory communicatively coupled to the processor, wherein:
the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-8.
10. A computer readable storage medium storing computer instructions for causing a computer to perform the method of any one of claims 1 to 8.
11. A chip comprising a processor and a data interface, the processor being capable of executing the method of any one of claims 1 to 8 by reading instructions stored on a memory via the data interface.
CN202310098922.XA 2023-02-08 2023-02-08 Device management method and electronic device Pending CN116010103A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310098922.XA CN116010103A (en) 2023-02-08 2023-02-08 Device management method and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310098922.XA CN116010103A (en) 2023-02-08 2023-02-08 Device management method and electronic device

Publications (1)

Publication Number Publication Date
CN116010103A true CN116010103A (en) 2023-04-25

Family

ID=86021133

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310098922.XA Pending CN116010103A (en) 2023-02-08 2023-02-08 Device management method and electronic device

Country Status (1)

Country Link
CN (1) CN116010103A (en)

Similar Documents

Publication Publication Date Title
CN110389816B (en) Method, apparatus and computer readable medium for resource scheduling
CN109840142A (en) Thread control method, device, electronic equipment and storage medium based on cloud monitoring
CN109144658A (en) Load-balancing method, device and the electronic equipment of limited resources
CN111800462A (en) Micro-service instance processing method and device, computer equipment and storage medium
CN112101602A (en) Robot charging distribution method, device, equipment, system and storage medium
CN113890712A (en) Data transmission method and device, electronic equipment and readable storage medium
CN111565216A (en) Back-end load balancing method, device, system and storage medium
CN111813517A (en) Task queue allocation method and device, computer equipment and medium
CN117032937B (en) Task scheduling method based on GPU, electronic device and storage medium
CN115373826B (en) Task scheduling method and device based on cloud computing
CN116010103A (en) Device management method and electronic device
CN111209333A (en) Data updating method, device, terminal and storage medium
CN114662804B (en) Resource configuration method, device, equipment and medium for power swapping station
CN113407322B (en) Multi-terminal task allocation method and device, electronic equipment and readable storage medium
CN115952054A (en) Simulation task resource management method, device, equipment and medium
CN109445863A (en) A kind of data processing method based on FPGA, device, equipment and medium
CN111078405B (en) Memory allocation method and device, storage medium and electronic equipment
CN115061895A (en) Business process arranging method and device, electronic equipment and storage medium
CN114781903A (en) Battery replacement place load determination method and device, electronic equipment and storage medium
CN112988383A (en) Resource allocation method, device, equipment and storage medium
CN111667411A (en) Image transmission method and device, electronic equipment and storage medium
CN115276762B (en) Satellite network connection method, system, electronic equipment and storage medium
CN114598705B (en) Message load balancing method, device, equipment and medium
CN108959517A (en) File management method, device and electronic equipment
CN117891618B (en) Resource task processing method and device of artificial intelligent model training platform

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination