Demand scheduling method, device, computer readable storage medium and electronic device

Abstract

The present application provides a demand scheduling method, a demand scheduling device, a computer-readable storage medium and an electronic device, which relate to the field of wireless communication technology and are applied to terminal devices, including: receiving demand information sent by a first device; splitting the demand information into multiple unit demands based on a device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device and the relationship between each second device; sending multiple unit demands to the corresponding target second device based on the device capability table, so that the target second device responds to the corresponding unit demands; wherein each second device includes a target second device. In this way, the capability of each second device in the network can be registered according to the registration information of each second device. When there is a demand on the first device, the demand can be split according to the capability of each second device, thereby scheduling multiple second devices to jointly perform computing tasks to improve the efficiency of demand response.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a demand scheduling method, a demand scheduling device, a computer-readable storage medium, and an electronic device. Background Art

[0002] In a network architecture with multiple smart devices, there may be conflicts in the decisions of smart devices for the same request. If a device with smart demand requests business calculation, generally speaking, the idle smart device in the network will perform the business calculation. However, the computing resources of the idle smart device may not be able to meet the business calculation demand. At this time, the business calculation demand needs to be forwarded to other idle smart devices, which easily leads to low demand response efficiency.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The purpose of the present application is to provide a demand scheduling method, a demand scheduling device, a computer-readable storage medium and an electronic device, which can register the capabilities of each second device in the network based on the registration information of each second device. When there is a demand on the first device, the demand can be divided according to the capabilities of each second device, so as to schedule multiple second devices to jointly perform computing tasks to improve the demand response efficiency.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to one aspect of the present application, a demand scheduling method is provided, which is applied to a terminal device, and the method includes:

[0007] Receiving demand information sent by the first device;

[0008] The demand information is split into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capability corresponding to each second device and the relationship between each second device;

[0009] Based on the device capability table, multiple unit demands are respectively sent to corresponding target second devices, so that the target second devices respond to the corresponding unit demands; wherein each second device includes the target second device.

[0010] In an exemplary embodiment of the present application, any second device among the second devices is a core network device, an access network device or a terminal device.

[0011] In an exemplary embodiment of the present application, the representation forms corresponding to the device capability table include at least: a topology diagram form, a table form, a text form, and a character string form.

[0012] In an exemplary embodiment of the present application, before splitting the demand information into multiple unit demands based on the device capability table, the method further includes:

[0013] Receiving registration information sent by each second device; wherein the registration information is used to describe the performance of each second device;

[0014] Generate a device capability table in the form of a topology diagram based on the registration information and network topology information.

[0015] In an exemplary embodiment of the present application, after generating a device capability table in the form of a topology map according to the registration information and the network topology information, the method further includes:

[0016] receiving new registration information sent by a new second device;

[0017] The device capability table in the form of a topology map is updated according to the new registration information and network topology information.

[0018] In an exemplary embodiment of the present application, the demand information is split into multiple unit demands based on the device capability table, including:

[0019] Determine the current resource occupancy corresponding to each second device;

[0020] Determine the performance corresponding to each second device according to the device capability table;

[0021] Extracting required capability characteristics from the demand information; wherein the required capability characteristics include at least one of a computing power value, a storage space, an algorithm, a storage location, a temperature value, and a congestion value;

[0022] The demand information is split into multiple unit demands according to the current resource occupancy and performance and required capability characteristics corresponding to each second device.

[0023] In an exemplary embodiment of the present application, the number of target second devices is greater than 1, and after sending multiple unit demands to corresponding target second devices based on the device capability table so that the target second devices respond to the corresponding unit demands, the method further includes:

[0024] Receiving response results fed back by each target second device to obtain multiple response results;

[0025] Generate a feedback result according to the multiple response results;

[0026] The feedback result is sent to the first device.

[0027] According to one aspect of the present application, a demand scheduling system is provided, characterized in that the system includes a capability registration module, a demand scheduling module, a first device and a second device, wherein:

[0028] The second device is used to send registration information to the capability registration module;

[0029] A capability registration module, used to receive registration information sent by each second device; wherein the registration information is used to describe the performance of each second device; and generate a device capability table in the form of a topology map according to the registration information and the network topology information;

[0030] A first device, used to send demand information to a demand scheduling module;

[0031] A demand scheduling module is used to receive demand information sent by a first device; split the demand information into multiple unit demands based on a device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device and the relationship between each second device; based on the device capability table, the multiple unit demands are respectively sent to the corresponding target second devices, so that the target second device responds to the corresponding unit demands; wherein each second device includes a target second device.

[0032] According to one aspect of the present application, a demand scheduling device is provided, characterized in that it includes:

[0033] A demand receiving unit, configured to receive demand information sent by the first device;

[0034] A demand splitting unit, used to split the demand information into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capability corresponding to each second device and the relationship between each second device;

[0035] The demand scheduling unit is used to send multiple unit demands to the corresponding target second devices based on the device capability table, so that the target second devices respond to the corresponding unit demands; wherein each second device includes the target second device.

[0036] In an exemplary embodiment of the present application, any second device among the second devices is a core network device, an access network device or a terminal device.

[0037] In an exemplary embodiment of the present application, the representation forms corresponding to the device capability table include at least: a topology diagram form, a table form, a text form, and a character string form.

[0038] In an exemplary embodiment of the present application, the above-mentioned device further includes:

[0039] An information receiving unit, used for receiving registration information sent by each second device before the demand splitting unit splits the demand information into multiple unit demands based on the device capability table; wherein the registration information is used to describe the performance of each second device;

[0040] The device capability table generating unit is used to generate a device capability table in the form of a topology diagram according to the registration information and the network topology information.

[0041] In an exemplary embodiment of the present application, wherein:

[0042] The information receiving unit is further configured to receive new registration information sent by the new second device after the device capability table generating unit generates the device capability table in the form of a topology map according to the registration information and the network topology information;

[0043] The device capability table generating unit is further used to update the device capability table in the form of a topology map according to the new registration information and the network topology information.

[0044] In an exemplary embodiment of the present application, the demand splitting unit splits the demand information into multiple unit demands based on the device capability table, including:

[0045] Determine the current resource occupancy corresponding to each second device;

[0046] Determine the performance corresponding to each second device according to the device capability table;

[0047] Extracting required capability characteristics from the demand information; wherein the required capability characteristics include at least one of a computing power value, a storage space, an algorithm, a storage location, a temperature value, and a congestion value;

[0048] The demand information is split into multiple unit demands according to the current resource occupancy and performance and required capability characteristics corresponding to each second device.

[0049] In an exemplary embodiment of the present application, the number of the target second devices is greater than 1, and the apparatus further includes:

[0050] A receiving unit, configured to receive response results fed back by each target second device after the demand scheduling unit sends the multiple unit demands to the corresponding target second device based on the device capability table so that the target second device responds to the corresponding unit demands, and obtain multiple response results;

[0051] A feedback result generating unit, used for generating a feedback result according to a plurality of response results;

[0052] A sending unit is used to send the feedback result to the first device.

[0053] According to one aspect of the present application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any one of the above methods by executing the executable instructions.

[0054] According to one aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, any one of the above methods is implemented.

[0055] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the above-mentioned various optional implementations.

[0056] The exemplary embodiments of the present application may have some or all of the following beneficial effects:

[0057] The demand scheduling method provided by an example implementation of the present application specifically receives demand information sent by a first device; splits the demand information into multiple unit demands based on a device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device and the relationship between each second device; and sends multiple unit demands to the corresponding target second devices based on the device capability table, so that the target second device responds to the corresponding unit demands; wherein each second device includes a target second device. According to the above scheme description, on the one hand, the present application can register the capabilities of each second device in the network based on the registration information of each second device. When there is a demand on the first device, the demand can be divided according to the capabilities of each second device, thereby scheduling multiple second devices to jointly perform computing tasks to improve the efficiency of demand response. On the other hand, the present application can take into account the capabilities of each second device and reasonably divide the demand information into unit demands suitable for different second devices to improve the utilization rate of device resources in the network.

[0058] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0060] Figure 1 A schematic diagram showing the structure of a computer system suitable for implementing a terminal device of an embodiment of the present application is shown;

[0061] Figure 2 A flowchart of a demand scheduling method according to an embodiment of the present application is schematically shown;

[0062] Figure 3 A flowchart of a demand scheduling method according to another embodiment of the present application is schematically shown;

[0063] Figure 4 A schematic diagram of the structure of a demand scheduling system according to an embodiment of the present application is shown;

[0064] Figure 5 A schematic diagram of the structure of a demand scheduling system according to another embodiment of the present application is shown;

[0065] Figure 6 The functional diagram of the IRF and the IMF according to an embodiment of the present application is schematically shown;

[0066] Figure 7 A schematic diagram schematically shows a device capability table in the form of a topology diagram according to an embodiment of the present application;

[0067] Figure 8 A schematic diagram schematically shows an application diagram of a device capability table in the form of a topology diagram according to an embodiment of the present application;

[0068] Fig. 9 A sequence diagram schematically shows a demand scheduling method according to an embodiment of the present application;

[0069] Fig.10 The structural block diagram of a demand scheduling device according to an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0070] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present application will be more comprehensive and complete, and the concept of the example embodiments will be fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical solutions of the present application may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present application.

[0071] In addition, the accompanying drawings are only schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0072] Figure 1 A schematic diagram of the structure of a computer system of a terminal device suitable for implementing an embodiment of the present application is shown.

[0073] It should be noted that Figure 1 The computer system 100 of the terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0074] like Figure 1 As shown, the computer system 100 includes a central processing unit (CPU) 101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 102 or a program loaded from a storage part 108 to a random access memory (RAM) 103. In the RAM 103, various programs and data required for system operation are also stored. The CPU 101, the ROM 102, and the RAM 103 are connected to each other through a bus 104. An input / output (I / O) interface 105 is also connected to the bus 104.

[0075] The following components are connected to the I / O interface 105: an input section 106 including a keyboard, a mouse, etc.; an output section 107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 108 including a hard disk, etc.; and a communication section 109 including a network interface card such as a LAN card, a modem, etc. The communication section 109 performs communication processing via a network such as the Internet. A drive 110 is also connected to the I / O interface 105 as needed. A removable medium 111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 110 as needed, so that a computer program read therefrom is installed into the storage section 108 as needed.

[0076] In particular, according to an embodiment of the present application, the process described below with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 109, and / or installed from a removable medium 111. When the computer program is executed by a central processing unit (CPU) 101, various functions defined in the method and apparatus of the present application are executed.

[0077] Figure 1 The computer system 100 is shown for implementing Figure 2 A demand scheduling method is shown, which can be applied to a terminal device / server. The demand scheduling method includes: steps S210 to S230.

[0078] Step S210: receiving demand information sent by the first device.

[0079] Step S220: split the demand information into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capability corresponding to each second device and the relationship between each second device.

[0080] Step S230: sending the plurality of unit demands to the corresponding target second devices respectively based on the device capability table, so that the target second devices respond to the corresponding unit demands; wherein each second device includes the target second device.

[0081] Steps S210 to S230 disclosed in this application can be applied to 4G networks, 5G networks, and 6G networks, and are not limited in the embodiments of this application. G is used to represent generation, 4G can be called the fourth generation mobile communication system, 5G can be called the fifth generation mobile communication system, and 6G can be called the sixth generation mobile communication system. In addition, this application does not limit the number of the first device and the second device.

[0082] Next, the above steps of this exemplary embodiment are described in more detail.

[0083] In step S210, demand information sent by a first device is received.

[0084] Among them, when there is a demand, any second device among the second devices can send demand information as the first device, that is, the first device can belong to any second device among multiple second devices or can be an external device, which is not limited in the embodiments of the present application. If the first device belongs to any second device among multiple second devices, when the demand information of the first device is responded to, it can continue to provide services as the original second device. The demand information is used to characterize the resources required to complete the user request (100 computing power values), the information that needs to be obtained (such as the degree of network congestion), the architecture / algorithm that needs to be used, etc. The total number of resources and the sum of information of multiple unit demands are consistent with the demand information, and the architecture / algorithm in the multiple unit demands is also consistent with the demand information.

[0085] In step S220, the demand information is split into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capability corresponding to each second device and the relationship between each second device.

[0086] Among them, any second device among the second devices is a core network device, an access network device or a terminal device. The representation form corresponding to the device capability table at least includes: a topology diagram form, a table form, a text form and a character string form.

[0087] Specifically, the demand information is divided into multiple unit demands based on the device capability table, including: determining the current resource occupancy of each second device; determining the performance of each second device according to the device capability table; extracting the required capability characteristics in the demand information; wherein the required capability characteristics include at least one of computing power value, storage space, algorithm, storage location, temperature value and congestion value; dividing the demand information into multiple unit demands according to the current resource occupancy (such as CPU occupancy rate, hard disk remaining space, etc.) and performance and required capability characteristics of each second device. In this way, distributed network intelligent capability management and calling can be realized, which is conducive to improving the efficiency of responding to demands.

[0088] Among them, the computing power value is used to characterize the computing power of the device, the storage space can be the entire storage space of the device or the remaining available storage space, the storage location is used to characterize the location where the device stores information, the temperature value is used to characterize the current temperature of the device, and the congestion value is used to characterize the current busyness of the device. The algorithm used can be: the algorithm of Federated Learning (FedAI), the algorithm in the Convolutional Neural Network (CNN), and the algorithm in the Recurrent Neural Networks (RNN). CNN is a feedforward neural network, consisting of one or more convolutional layers and a fully connected layer at the top, and also includes associated weights and pooling layers. The biggest difference between RNN and traditional neural networks is that each time the output result of the previous time is brought to the hidden layer of the next time and trained together. In addition, the computing power value, storage space, algorithm, storage location, temperature value and congestion value can all be represented by numerical values, identifiers or text, etc., and the embodiments of the present application are not limited.

[0089] Optionally, before the demand information is split into multiple unit demands based on the device capability table in step S220, the method further includes: receiving registration information sent by each second device; wherein the registration information is used to describe the performance of each second device; and generating a device capability table in the form of a topology map according to the registration information and the network topology information. This is conducive to realizing distributed network intelligent capability management and calling according to the device capability table, thereby realizing the change from external network intelligence to endogenous network intelligence.

[0090] Among them, network topology information is used to describe the network topology structure (Network Topology). Network topology refers to the physical layout of various devices interconnected by transmission media. Topology is an abstract representation method that does not consider the physical properties of objects such as size and shape, but only uses points or lines to describe the actual position and relationship of multiple objects. Network topology information can vividly describe the arrangement and configuration of the network and the relationship between each node. In addition, the registration information may include the computing power value, storage space, read and write speed, algorithm, storage location, temperature value, congestion value, etc. of the second device.

[0091] Further optionally, after generating the device capability table in the form of a topology map according to the registration information and the network topology information, the method further includes: receiving new registration information sent by a new second device; and updating the device capability table in the form of a topology map according to the new registration information and the network topology information. In this way, the device capability table can be updated in a timely manner, so that the device capability table is consistent with each second device, so as to ensure the rationality of demand allocation scheduling.

[0092] Among them, the new registration information sent by the new second device can be expressed in a preset format, such as key-value, metadata-value. Updating the device capability table in the form of a topology map according to the new registration information and the network topology information includes: extracting keywords in the new registration information and determining the association relationship between the second device and other second devices, and adding the new registration information to the device capability table in the form of a topology map according to the keywords and the association relationship. In addition, the above method also includes: monitoring each second device according to the registration information corresponding to each second device, and if a second device with performance changes is detected, updating the stored device capability table.

[0093] In step S230, multiple unit demands are sent to corresponding target second devices based on the device capability table, so that the target second devices respond to the corresponding unit demands; wherein each second device includes the target second device. The number of target second devices can be one or more, which is not limited in the embodiment of the present application.

[0094] Optionally, if the number of target second devices is greater than 1, after sending multiple unit demands to the corresponding target second devices based on the device capability table in step S230 so that the target second devices respond to the corresponding unit demands, the method further includes: receiving the response results fed back by each target second device to obtain multiple response results; generating feedback results based on the multiple response results; and sending the feedback results to the first device. In this way, unified coordination and calling of the intelligent capabilities of each device in the network can be achieved, and effective resource utilization of multiple second devices under the same network architecture can be improved.

[0095] Among them, generating feedback results based on multiple response results includes: splicing / integrating multiple response results into feedback results; wherein the feedback results may include the integration result of multiple response results, multiple response results, identifiers (such as, ID) of the second devices corresponding to the multiple response results, etc., which are not limited in the embodiments of the present application.

[0096] It can be seen that the implementation Figure 2 The method shown can register the capabilities of each second device in the network based on the registration information of each second device. When the first device has a demand, the demand can be divided according to the capabilities of each second device, thereby scheduling multiple second devices to jointly perform computing tasks to improve the efficiency of demand response. In addition, since the capabilities of each second device can be taken into account, the demand information can be reasonably divided into unit demands suitable for different second devices to improve the utilization rate of device resources in the network.

[0097] Combination Figure 2 The steps and embodiments shown in the figure disclose another embodiment of a demand scheduling method. Figure 3, specifically including: step S310 to step S380.

[0098] Step S310: receiving registration information sent by each second device; wherein the registration information is used to describe the performance of each second device.

[0099] Step S320: Generate a device capability table in the form of a topology graph according to the registration information and the network topology information.

[0100] Step S330: Receive demand information sent by the first device.

[0101] Step S340: determine the current resource occupancy of each second device, and determine the performance of each second device according to the device capability table.

[0102] Step S350: extracting the required capability characteristics in the demand information; wherein the required capability characteristics include at least one of computing power value, storage space, algorithm, storage location, temperature value and congestion value.

[0103] Step S360: split the demand information into multiple unit demands according to the current resource occupancy and performance and required capability characteristics corresponding to each second device.

[0104] Step S370: sending the plurality of unit demands to the corresponding target second devices respectively based on the device capability table, so that the target second devices respond to the corresponding unit demands; wherein each second device includes the target second device.

[0105] Step S380: receiving the response results fed back by each target second device, obtaining multiple response results, generating a feedback result according to the multiple response results, and sending the feedback result to the first device.

[0106] It should be noted that steps S310 to S380 are Figure 2 The steps and their embodiments shown correspond to each other. For the specific implementation of steps S310 to S380, please refer to Figure 2 The steps and embodiments shown are not described in detail here.

[0107] It can be seen that the implementation Figure 3 The method shown can register the capabilities of each second device in the network based on the registration information of each second device. When the first device has a demand, the demand can be divided according to the capabilities of each second device, thereby scheduling multiple second devices to jointly perform computing tasks to improve the efficiency of demand response. In addition, since the capabilities of each second device can be taken into account, the demand information can be reasonably divided into unit demands suitable for different second devices to improve the utilization rate of device resources in the network.

[0108] For further information, see Figure 4 , the present application also discloses a demand scheduling system 400. The system may include: a capability registration module 401, a demand scheduling module 402, a first device 403 and a second device 404; wherein the capability registration module 401 may be set in an independent device or in the first device 403 / the second device 404, and similarly, the demand scheduling module 402 may be set in an independent device or in the first device 403 / the second device 404. In addition, the capability registration module 401 and the demand scheduling module 402 may be set in the same device or in different devices, which is not limited in the embodiments of the present application.

[0109] Specifically:

[0110] The second device 404 is used to send registration information to the capability registration module 401;

[0111] The capability registration module 401 is used to receive registration information sent by each second device 404; wherein the registration information is used to describe the performance of each second device 404; and generate a device capability table in the form of a topology map according to the registration information and the network topology information;

[0112] The first device 403 is used to send demand information to the demand scheduling module 402;

[0113] The demand scheduling module 402 is used to receive demand information sent by the first device 403; split the demand information into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device 404 and the relationship between each second device 404; based on the device capability table, the multiple unit demands are respectively sent to the corresponding target second device 404, so that the target second device 404 responds to the corresponding unit demands; wherein each second device 404 includes the target second device 404.

[0114] Among them, the capability registration module 401 has an intelligent repository function (Intelligence Repository Function, IRF); the demand scheduling module 402 has an intelligent management function (Intelligence Management Function, IMF); the first device 403 can be an intelligent demand device (such as a user's mobile phone); the second device 404 can be a core network device, an access network device or a terminal device.

[0115] It can be seen that the implementation Figure 4The system shown can register the capabilities of each second device in the network based on the registration information of each second device. When the first device has a demand, the demand can be divided according to the capabilities of each second device, so as to schedule multiple second devices to jointly perform computing tasks to improve the efficiency of demand response. In addition, since the capabilities of each second device can be taken into consideration, the demand information can be reasonably divided into unit demands suitable for different second devices to improve the utilization rate of device resources in the network.

[0116] For further information, see Figure 5 , Figure 5 It can be used to show the node relationship between the above IRF, IMF, core network equipment, access network equipment, terminal equipment, and intelligent demand equipment. Specifically, Figure 5 The demand scheduling system 500 shown may include: core network equipment 511, access network equipment 512, terminal equipment 513, IRF520, IMF530, and intelligent demand equipment 540. The core network equipment 511 may be a cloud server, the access network equipment 512 may be an edge server, and the terminal equipment 513 may be a user terminal equipment.

[0117] Specifically, any of the core network device 511, the access network device 512, and the terminal device 513 may send registration information to the IRF 520. If the core network device 511, the access network device 512, and the terminal device 513 all send registration information to the IRF 520, after the IRF 520 receives the registration information, a device capability table in the form of a topology diagram may be generated according to the registration information and the network topology information. Furthermore, the intelligent demand device 540 can send demand information to IMF530; IMF530 can split the demand information into unit demands for allocation to at least one of the core network device 511, the access network device 512 and the terminal device 513 based on the device capability table, and send multiple unit demands to the corresponding devices (such as the core network device 511, the access network device 512, the terminal device 513) based on the device capability table, so that the device responds to the corresponding unit demand and feeds back the response result to IMF530. IMF530 can integrate the response results to generate a return result corresponding to the above demand information and send the return result to the intelligent demand device 540.

[0118] For further information, see Figure 6 , Figure 6 The functional diagram of IRF and IMF according to an embodiment of the present application is schematically shown. Figure 6As shown, IMF610 can provide scheduling services 611, ..., query services 612, etc., wherein the query service 612 can be used to query the device capability table in the form of a topology map generated by IRF620, and the scheduling service 611 can be used to split the demand information into multiple unit demands based on the device capability table. The core network device 630, the access network device 640, and the terminal device 650 can send registration information to the IRF620.

[0119] Among them, IRF620 can generate a device capability table in the form of a topology diagram based on the registration information. The device capability table may include the computing power value 621, algorithm 622, storage space 623, storage location 624, temperature value 625, congestion value 626 of the core network device 630, access network device 640, and terminal device 650, as well as the topological relationship between the core network device 630, access network device 640, and terminal device 650.

[0120] Among them, since IMF610 can provide scheduling services 611,..., query services 612, etc., service intelligence in the network can be realized; the interaction between IMF610, IRF620, core network equipment 630, access network equipment 640, and terminal equipment 650 can realize network intelligence; IRF620 generates a device capability table in the form of a topology diagram based on registration information, which can realize device intelligence.

[0121] See also Figure 7 , Figure 7 The following schematically shows a schematic diagram of a device capability table in the form of a topology diagram according to an embodiment of the present application. Figure 7 As shown, the device capability table in the form of a topology graph may include multiple nodes, specifically represented as: node 710, node 720, node 730, node 740, node 750, node 760, node 770. The device capability table in the form of a topology graph may also represent the topological relationship between the above nodes.

[0122] Among them, node 710 includes the computing power value of terminal A: 1, storage space: 1, algorithm: FedAI, and information: location, temperature. Node 720 includes the computing power value of terminal B: 2, storage space: 1, and algorithm: FedAI. Node 730 includes the computing power value of terminal C: 1, storage space: 2, and algorithm: FedAI. Node 740 includes the computing power value of base station D: 20, storage space: 10, algorithms: FedAI, CNN, RNN, and information: congestion level. Node 750 includes the computing power value of base station E: 10, storage space: 10, algorithms: FedAI, CNN, RNN. Node 760 includes the computing power value of core network F: 200, storage space: 100, algorithms: FedAI, CNN, RNN. Node 770 includes the computing power value of core network G: 200, storage space: 300, and algorithms: FedAI, CNN, RNN.

[0123] Among them, terminal A, terminal B, and terminal C correspond to Figure 6 The terminal device 650 in the base station D and the base station E correspond to Figure 6 The access network device 640 in the core network F and the core network G correspond to Figure 6 The core network device 630 in.

[0124] See also Figure 8 , Figure 8 The following schematic diagram shows an application diagram of a device capability table in the form of a topology diagram according to an embodiment of the present application. Figure 8 As shown, IMF800 can send the corresponding unit requirements to the devices corresponding to node 810, node 840, and node 860, so that the devices corresponding to node 810, node 840, and node 860 respond to the corresponding unit requirements. Specifically, Figure 8 The device capability table in the form of a topology graph may include multiple nodes, specifically represented as: node 810, node 820, node 830, node 840, node 850, node 860, node 870. The device capability table in the form of a topology graph may also represent the topological relationship between the above nodes.

[0125] Among them, node 810 includes the computing power value of terminal A: 1, storage space: 1, algorithm: FedAI, and information: location, temperature. Node 820 includes the computing power value of terminal B: 2, storage space: 1, algorithm: FedAI. Node 830 includes the computing power value of terminal C: 1, storage space: 2, algorithm: FedAI. Node 840 includes the computing power value of base station D: 20, storage space: 10, algorithm: FedAI, CNN, RNN, and information: congestion level. Node 850 includes the computing power value of base station E: 10, storage space: 10, algorithm: FedAI, CNN, RNN. Node 860 includes the computing power value of core network F: 200, storage space: 100, algorithm: FedAI, CNN, RNN. Node 870 includes the computing power value of core network G: 200, storage space: 300, algorithm: FedAI, CNN, RNN.

[0126] Among them, terminal A, terminal B, and terminal C correspond to Figure 6 The terminal device 650 in the base station D and the base station E correspond to Figure 6 The access network device 640 in the core network F and the core network G correspond to Figure 6 The core network device 630 in.

[0127] When IMF800 receives demand information and the computing resources required by the demand information include computing power 100, storage 50, FedAI algorithm, required location, temperature, and congestion level information, the demand information can be split into three unit demands based on the relationship among nodes 810, 820, 830, 840, 850, 860, and 870 and the specific performance information of each node, and then the three unit demands can be sent to the corresponding nodes 810, 840, and 860. Node 810 can allocate 1 / 1 of the computing power value and 1 / 1 of the storage space and respond to the unit demand based on FedAI, node 840 can allocate 10 / 20 of the computing power value and 5 / 10 of the storage space and respond to the unit demand based on FedAI, and node 860 can allocate 89 / 200 of the computing power value and 44 / 100 of the storage space and respond to the unit demand based on FedAI. Furthermore, IMF800 may also receive response results fed back by node 810, node 840, and node 860 respectively.

[0128] exist Figure 2 For the basis of its examples, please refer to Fig. 9 , Fig. 9 The sequence diagram of the demand scheduling method according to an embodiment of the present application is schematically shown. The sequence diagram includes interaction steps between the IRF, the IMF, the second device, and the first device, and the interaction steps specifically include: step S910 to step S980.

[0129] S910: The second device sends registration information to the IRF.

[0130] S920: The IRF generates a device capability table in the form of a topology map according to the registration information and the network topology information.

[0131] S930: The first device sends demand information to the IMF.

[0132] S940: IMF splits the demand information into multiple unit demands based on the equipment capability table.

[0133] S950: The IMF queries the IRF for a device capability table.

[0134] S960: The IRF returns the query result.

[0135] S970: The IMF sends the multiple unit demands to the corresponding target second devices respectively based on the device capability table.

[0136] S980: The first device provides an intelligent service.

[0137] It can be seen that execution Fig. 9 As shown in the sequence diagram, the capability of each second device in the network can be registered according to the registration information of each second device. When the first device has a demand, the demand can be divided according to the capability of each second device, so as to schedule multiple second devices to jointly perform computing tasks to improve the efficiency of demand response. In addition, since the capability of each second device can be taken into consideration, the demand information can be reasonably divided into unit demands suitable for different second devices to improve the utilization rate of device resources in the network.

[0138] For further information, see Fig.10 , Fig.10 The realization is with Figure 2 A corresponding demand scheduling device. Fig.10 As shown, the demand scheduling device 1000 includes: a demand receiving unit 1001, a demand splitting unit 1002 and a demand scheduling unit 1003.

[0139] The demand receiving unit 1001 is used to receive demand information sent by the first device;

[0140] The demand splitting unit 1002 is used to split the demand information into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capability corresponding to each second device and the relationship between each second device;

[0141] The demand scheduling unit 1003 is used to send multiple unit demands to corresponding target second devices based on the device capability table, so that the target second devices respond to the corresponding unit demands; wherein each second device includes the target second device.

[0142] Among them, any second device among the second devices is a core network device, an access network device or a terminal device. The representation form corresponding to the device capability table at least includes: a topology diagram form, a table form, a text form and a character string form.

[0143] It can be seen that the implementation Fig.10 The device shown can register the capabilities of each second device in the network based on the registration information of each second device. When the first device has a demand, the demand can be divided according to the capabilities of each second device, thereby scheduling multiple second devices to jointly perform computing tasks to improve the efficiency of demand response. In addition, since the capabilities of each second device can be taken into account, the demand information can be reasonably divided into unit demands suitable for different second devices to improve the utilization rate of device resources in the network.

[0144] In an exemplary embodiment of the present application, the above-mentioned device further includes:

[0145] An information receiving unit (not shown) is used to receive registration information sent by each second device before the demand splitting unit 1002 splits the demand information into multiple unit demands based on the device capability table; wherein the registration information is used to describe the performance of each second device;

[0146] The device capability table generating unit (not shown) is used to generate a device capability table in the form of a topology map according to the registration information and the network topology information.

[0147] It can be seen that the implementation of this optional embodiment can be beneficial to realize distributed network intelligence capability management and calling according to the device capability table, thereby realizing the change from external network intelligence to endogenous network intelligence.

[0148] In an exemplary embodiment of the present application, wherein:

[0149] The information receiving unit is further configured to receive new registration information sent by the new second device after the device capability table generating unit generates the device capability table in the form of a topology map according to the registration information and the network topology information;

[0150] The device capability table generating unit is further used to update the device capability table in the form of a topology map according to the new registration information and the network topology information.

[0151] It can be seen that by implementing this optional embodiment, the device capability table can be updated in time, so that the device capability table is consistent with each second device, so as to ensure the rationality of demand allocation scheduling.

[0152] In an exemplary embodiment of the present application, the demand splitting unit 1002 splits the demand information into multiple unit demands based on the device capability table, including:

[0153] Determine the current resource occupancy corresponding to each second device;

[0154] Determine the performance corresponding to each second device according to the device capability table;

[0155] Extracting required capability characteristics from the demand information; wherein the required capability characteristics include at least one of a computing power value, a storage space, an algorithm, a storage location, a temperature value, and a congestion value;

[0156] The demand information is split into multiple unit demands according to the current resource occupancy and performance and required capability characteristics corresponding to each second device.

[0157] It can be seen that the implementation of this optional embodiment can realize distributed network intelligent capability management and invocation, which is conducive to improving the efficiency of responding to needs.

[0158] In an exemplary embodiment of the present application, the number of the target second devices is greater than 1, and the apparatus further includes:

[0159] A receiving unit (not shown) is used for receiving response results fed back by each target second device after the demand scheduling unit 1003 sends the multiple unit demands to the corresponding target second devices based on the device capability table so that the target second devices respond to the corresponding unit demands, and obtaining multiple response results;

[0160] A feedback result generating unit (not shown), configured to generate a feedback result according to a plurality of response results;

[0161] The sending unit (not shown) is used to send the feedback result to the first device.

[0162] It can be seen that the implementation of this optional embodiment can achieve unified coordination and invocation of the intelligent capabilities of each device in the network, and improve the effective resource utilization of multiple second devices under the same network architecture.

[0163] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0164] Since the various functional modules of the demand scheduling device of the example embodiment of the present application correspond to the steps of the example embodiment of the demand scheduling method described above, for details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the demand scheduling method described above in the present application.

[0165] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method described in the above embodiment.

[0166] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0167] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0168] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0169] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0170] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A demand scheduling method, characterized in that: include: Receiving demand information sent by the first device; Splitting the demand information into multiple unit demands based on a device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device and the relationship between each second device; Based on the device capability table, the plurality of unit requirements are respectively sent to corresponding target second devices, so that the target second devices respond to the corresponding unit requirements; wherein the second devices include the target second device; The step of dividing the demand information into multiple unit demands based on the device capability table includes: Determine the current resource occupancy corresponding to each second device; Determine the performance corresponding to each of the second devices according to the device capability table; Extracting required capability characteristics from the demand information; wherein the required capability characteristics include at least one of a computing power value, a storage space, an algorithm, a storage location, a temperature value, and a congestion value; The demand information is split into a plurality of unit demands according to the current resource occupancy and performance corresponding to each second device and the required capability characteristics.

2. The method according to claim 1, characterized in that Any of the second devices is a core network device, an access network device or a terminal device.

3. The method according to claim 1, characterized in that The representation forms corresponding to the device capability table include at least: topology map form, table form, text form and character string form.

4. The method according to claim 3, characterized in that Before splitting the demand information into a plurality of unit demands based on the equipment capability table, the method further includes: Receiving registration information sent by each second device; wherein the registration information is used to describe the performance of each second device; A device capability table in the form of a topology graph is generated according to the registration information and the network topology information.

5. The method according to claim 4, characterized in that After generating a device capability table in the form of a topology map according to the registration information and the network topology information, the method further includes: receiving new registration information sent by a new second device; The device capability table in the form of a topology map is updated according to the new registration information and the network topology information.

6. The method according to claim 1, characterized in that The number of the target second devices is greater than 1, and after the plurality of unit demands are respectively sent to the corresponding target second devices based on the device capability table so that the target second devices respond to the corresponding unit demands, the method further includes: receiving a response result fed back by each of the target second devices to obtain a plurality of response results; Generate a feedback result according to the multiple response results; The feedback result is sent to the first device.

7. A demand scheduling system, characterized in that: The system includes a capability registration module, a demand scheduling module, a first device and a second device, wherein: The second device is used to send registration information to the capability registration module; The capability registration module is used to receive registration information sent by each second device; wherein the registration information is used to describe the performance of each second device; and generate a device capability table in the form of a topology map according to the registration information and the network topology information; The first device is used to send demand information to the demand scheduling module; The demand scheduling module is used to receive demand information sent by the first device; split the demand information into multiple unit demands based on the device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device and the relationship between each second device; based on the device capability table, the multiple unit demands are respectively sent to the corresponding target second devices, so that the target second device responds to the corresponding unit demands; wherein each second device includes the target second device; the demand information is split into multiple unit demands based on the device capability table, including: determining the current resource occupancy corresponding to each second device; determining the performance corresponding to each second device according to the device capability table; extracting the required capability characteristics in the demand information; wherein the required capability characteristics include at least one of computing power value, storage space, algorithm, storage location, temperature value and congestion value; splitting the demand information into multiple unit demands according to the current resource occupancy and performance corresponding to each second device and the required capability characteristics.

8. A demand scheduling device, characterized in that: include: A demand receiving unit, configured to receive demand information sent by the first device; A demand splitting unit, used to split the demand information into multiple unit demands based on a device capability table; wherein the device capability table is used to characterize the device capabilities corresponding to each second device and the relationship between each second device; A demand scheduling unit, configured to send the plurality of unit demands to corresponding target second devices respectively based on the device capability table, so that the target second devices respond to the corresponding unit demands; wherein the second devices include the target second device; Wherein, the demand splitting unit is specifically used for: Determine the current resource occupancy corresponding to each second device; Determine the performance corresponding to each of the second devices according to the device capability table; Extracting required capability characteristics from the demand information; wherein the required capability characteristics include at least one of a computing power value, a storage space, an algorithm, a storage location, a temperature value, and a congestion value; The demand information is split into a plurality of unit demands according to the current resource occupancy and performance corresponding to each second device and the required capability characteristics.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 6 by executing the executable instructions.

Images