CN110366194B - Resource calling method, device and system - Google Patents
Resource calling method, device and system Download PDFInfo
- Publication number
- CN110366194B CN110366194B CN201910490823.XA CN201910490823A CN110366194B CN 110366194 B CN110366194 B CN 110366194B CN 201910490823 A CN201910490823 A CN 201910490823A CN 110366194 B CN110366194 B CN 110366194B
- Authority
- CN
- China
- Prior art keywords
- base station
- resource
- idle
- party
- demand
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a resource calling method, a device and a system, wherein the resource calling method comprises the following steps: receiving resource demand information; searching a supplier base station matched with the resource demand information in the idle base station cluster; and establishing a resource calling channel between the requiring base station and the supplying base station so as to enable the requiring base station to call the idle resource of the supplying base station. According to the resource calling method, the device and the system, the resource waste is avoided and the hardware cost is reduced by reasonably utilizing redundant idle resources.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a resource calling method, device, and system.
Background
In recent years, computer networks have become carriers of various industries, and cloud computing platforms provide resources such as computation, storage, software, and services to users through high-speed internet transmission capability.
Although the cloud computing platform has the flexible and flexible characteristic and can provide resource supply on demand and dynamic management, in the actual use process, the situation of resource redundancy or resource insufficiency still happens inevitably at different time intervals. In order to ensure the service quality of the cloud computing platform, the traditional method generally increases hardware equipment for providing resources. Although the problem of insufficient resources during peak periods of resource utilization can be solved, the hardware equipment is expensive, the cost is increased by adding the hardware equipment, and more resource redundancy occurs after the peak periods, so that resource waste is caused.
Disclosure of Invention
Therefore, it is necessary to provide a resource calling method, device and system for solving the problems of a traditional resource allocation method, such as a lot of resource waste and high hardware cost, so as to reasonably utilize redundant idle resources, avoid resource waste, and reduce hardware cost.
A first aspect of an embodiment of the present invention provides a resource calling method, including:
receiving resource demand information;
searching a supplier base station matched with the resource demand information in the idle base station cluster; and
and establishing a resource calling channel between the requiring base station and the supplying base station so that the requiring base station calls the idle resource of the supplying base station.
In one embodiment, the searching for a provider base station matching the resource requirement information in the idle base station cluster includes:
determining target resource characteristics according to the resource demand information;
analyzing the resource characteristics of each idle base station in the idle base station cluster; and
and determining the idle base station with the resource characteristics conforming to the target resource characteristics as a provider base station.
In one embodiment, the searching for a provider base station matching the resource requirement information in an idle base station cluster includes:
determining a target computing capacity grade according to the resource demand information;
acquiring the current computing capacity grade of each idle base station in the idle base station cluster; and
and determining the idle base station with the current computing capacity level reaching the target computing capacity level as the provider base station.
In one embodiment, before the establishing the resource invoking channel between the demanding base station and the supplying base station, the resource invoking method further includes:
judging whether the demand side base station and the supply side base station are mutually trusted base stations;
and if the demand side base station and the supply side base station are mutual communication base stations, establishing a resource calling channel between the demand side base station and the supply side base station.
In an embodiment, before the determining whether the requiring base station and the supplying base station are mutual communication base stations, the resource invoking method further includes:
establishing mutual trust relations between a plurality of base stations and a cloud platform in advance;
the determining whether the demand side base station and the supply side base station are mutually trusted base stations includes:
judging whether a mutual trust relationship between the demand side base station and a cloud platform and a mutual trust relationship between the supply side base station and the cloud platform are established or not; and if so, the requiring party base station and the supplying party base station are mutual trust base stations.
In one embodiment, before the establishing the resource invoking channel between the demanding base station and the supplying base station, the resource invoking method further includes:
sending a resource calling request to the provider base station; and
and receiving the acceptance calling information fed back by the supplier base station.
A second aspect of the present invention provides a resource calling apparatus, including:
the receiving module is used for receiving the resource demand information;
the searching module is used for searching the supplier base station matched with the resource demand information in the idle base station cluster; and
the channel establishing module is used for establishing a resource calling channel between a demand side base station and the supply side base station so as to enable the demand side base station to call the idle resource of the supply side base station.
In one embodiment, the lookup module comprises:
a first determining unit, configured to determine a target resource feature according to the resource demand information;
the analysis unit is used for analyzing the resource characteristics of each idle base station in the idle base station cluster; and
and a second determining unit, configured to determine an idle base station with a resource characteristic that meets the target resource characteristic as a provider base station.
In one embodiment, the lookup module comprises:
a third determining unit, configured to determine a target computing capability level according to the resource demand information;
the acquiring unit is used for acquiring the current computing capacity grade of each idle base station in the idle base station cluster; and
and the fourth determination unit is used for determining the idle base station with the current computing capacity level reaching the target computing capacity level as the provider base station.
In one embodiment, the resource calling device further includes:
the judging module is used for judging whether the requiring party base station and the supplying party base station are mutually trusted base stations or not;
the channel establishing module is used for establishing a resource calling channel between the demand side base station and the supply side base station when the demand side base station and the supply side base station are mutual communication base stations.
In one embodiment, the resource calling device further comprises:
the mutual trust establishing module is used for establishing mutual trust relations between the base stations and the cloud platform in advance;
the judging module is used for judging whether a mutual trust relationship between the demand side base station and the cloud platform and a mutual trust relationship between the supply side base station and the cloud platform are established or not; and if so, the requiring party base station and the supplying party base station are mutual trust base stations.
In one embodiment, the resource calling device further comprises:
a sending module, configured to send a resource invocation request to the provider base station;
the receiving module is further configured to receive the acceptance calling information fed back by the provider base station.
A third aspect of the present invention provides a resource invoking system, which includes a plurality of base stations and the resource invoking device as described in any of the embodiments of the second aspect or the second aspect, wherein the plurality of base stations include the requiring base station and the supplying base station.
According to the resource calling method, the device and the system, the supplier base station is searched according to the resource demand information issued by the demander base station, and the resource calling channel between the demander base station and the supplier base station is established, so that the demander base station can call the idle resource of the supplier base station, and by reasonably utilizing the redundant idle resource, the resource waste is avoided, and the hardware cost is reduced.
Drawings
FIG. 1 is a flowchart illustrating a resource calling method according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a resource calling method according to another embodiment of the present invention;
FIG. 3 is a flowchart illustrating a resource calling method according to another embodiment of the present invention;
FIG. 4 is a flowchart illustrating a resource calling method according to another embodiment of the present invention;
FIG. 5 is a flowchart illustrating a resource calling method according to another embodiment of the present invention;
FIG. 6 is a block diagram of a resource calling device according to an embodiment of the present invention;
FIG. 7 is a block diagram of a lookup module according to an embodiment of the present invention;
FIG. 8 is a block diagram of a lookup module according to an embodiment of the present invention;
FIG. 9 is a block diagram of a resource calling device according to another embodiment of the present invention;
fig. 10 is a schematic block diagram of a resource calling system according to an embodiment of the present invention.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully hereinafter with reference to the accompanying drawings. Preferred embodiments of the present invention are shown in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
Fig. 1 is a flowchart illustrating a resource calling method according to an embodiment of the present invention. As shown in fig. 1, the resource calling method includes:
In this embodiment, the base station refers to a device, such as a server or a smart terminal, registered as a base station on the cloud platform. The base station of the demand party is the base station which has insufficient resources to meet the current service requirement and needs to request other base stations for resource calling.
Specifically, the resource requirement information includes information about resources required by the base station of the demander, for example, usage and call duration, including usage, call duration and some special requirements. For example, the special requirement includes that the distance between the resource provider and the demander base station is within a preset distance; as another example, the special requirements include idle resources and/or processing power of the provider base station, and the like.
It should be appreciated that at different time periods, the same base station may be either a requiring base station or an idle base station, depending on the different conditions to be met for the current service requirements. For example, in a resource utilization peak period, the resource held by the base station a is not enough to meet the current service requirement, and when a resource call needs to be requested from another base station, the base station a is the base station of the demand side. For example, in the resource utilization idle period, the resources held by the base station a are sufficient to meet the current service requirement, and when there are more idle resources, the base station a is an idle base station.
In this embodiment, the idle base station cluster is a set of base stations having a certain idle resource reserve at the current time. For example, the current time is the time for receiving the resource requirement information, for example, having a certain idle resource reservation means that the amount of idle resources reaches a preset threshold, for example, idle resources means unoccupied resources.
Specifically, polling each idle base station in the idle base station cluster, determining whether each idle base station matches the resource demand information, and determining the idle base station matching the resource demand information as a provider base station. For example, a requirement condition may be determined according to the resource requirement information, and if the idle resource condition of the idle base station satisfies the requirement condition, the idle base station matches the resource requirement information.
In some cases, when there are a plurality of idle base stations matching the resource requirement information, one of the plurality of idle base stations matching the resource requirement information is selected as a provider base station. For example, an idle base station closest to the base station of the demand side is selected as the base station of the supply side; for example, an idle base station with the largest amount of idle resources is selected as a provider base station; for example, the idle base station with the highest level of computing power is selected as the provider base station.
For example, the idle resource address of the supplier base station is sent to the demander base station, so that the demander base station invokes the idle resource of the supplier base station according to the idle resource address. For example, the free resources of the supplying base station are called, and the free resources are allocated to the requiring base station.
According to the resource calling method, the supplier base station is searched according to the resource demand information issued by the supplier base station, and the resource calling channel between the supplier base station and the supplier base station is established, so that the supplier base station can call the idle resource of the supplier base station, and the resource waste is avoided and the hardware cost is reduced by reasonably utilizing the redundant idle resource.
As shown in FIG. 2, in one embodiment, step 130 comprises:
In this embodiment, according to the resource demand information, a target resource feature matching the resource demand information is determined. For example, the target resource characteristics are determined according to the use and calling duration of the resource. For example, the target resource characteristics are determined according to the use of the resource, the calling time length and the special requirements of the base station of the demand side. The target resource characteristics are characteristics of resources required by the base station of the demand side. The target resource characteristics may include at least one of an amount of free resources, a distance, a speed, a bandwidth, a reliability, and the like.
And step 134, analyzing the resource characteristics of each idle base station in the idle base station cluster.
In this embodiment, analyzing the resource characteristics of each idle base station includes analyzing at least one of the amount of idle resources, speed, distance, bandwidth, reliability, and the like of the resources of each idle base station.
Judging whether the resource characteristics of each idle base station meet the target resource characteristics, for example, judging whether the idle resource quantity of each idle base station meets the requirements of the target resource characteristics; for example, whether the idle resource amount and the bandwidth of each idle base station meet the requirements of target resource characteristics is judged; for example, whether the amount of idle resources, the bandwidth and the speed of each space base station all meet the requirements of target resource characteristics is judged; for example, it is determined whether the distance, speed and reliability of each idle base station meet the requirements of the target resource characteristics.
And step 136, determining the idle base station with the resource characteristics conforming to the target resource characteristics as a provider base station.
In this embodiment, if there is an idle base station whose resource characteristics match the target resource characteristics, it is determined as the donor base station. And if the number of idle base stations with the resource characteristics meeting the target resource characteristics is more than 1, selecting one of the idle base stations as a provider base station. For example, an idle base station with the largest amount of idle resources is determined as a provider base station; for example, an idle base station closest to the base station of the demand side is determined as the base station of the supply side; for example, the base station with the strongest computing power is determined as the provider base station. For example, after a plurality of idle base stations conforming to the target resource characteristics are found, resource calling requests are sent to the idle base stations conforming to the target resource characteristics, and the idle base station which responds fastest and accepts the resource calling requests is determined as the provider base station.
As shown in FIG. 3, in one embodiment, step 130 includes:
and step 131, determining a target computing capacity grade according to the resource demand information.
In this embodiment, a target computing power level matching the resource demand information is determined based on the resource demand information. For example, the target computing power level is determined according to the usage of the resource and the call duration. For example, the target computing power level may be determined based on the usage of the resource, the duration of the call, and the particular requirements of the requesting base station. Wherein the target computing power level is a computing power level that meets the requirements of the resources required by the demander base station.
And step 133, obtaining the current computing capability level of each idle base station in the idle base station cluster.
In this embodiment, when the server is registered as a base station on the cloud platform, the geographical location information and the hardware resource information of each base station are collected. And evaluating the computing power level of each base station according to the hardware resource information.
As an implementation mode, the resource states of a plurality of base stations in the system can be monitored in real time, and the computing capacity levels of the base stations can be updated in real time according to the resource states of the base stations. For example, the resource status of all base stations in the system is monitored in real time, and the computing power level of all base stations in the system is evaluated/updated. For example, the resource status of base stations meeting specific conditions in the system is monitored in real time, and the computing capability level of the base stations meeting the specific conditions is evaluated/updated, wherein the idle base stations in the idle base station cluster are the cluster of the idle base stations meeting the specific conditions. For example, the specific condition is that the credit/security is high; for example, the specific condition is that a mutual trust agreement has been signed; for example, the particular condition is a signed resource sharing agreement. After determining the target computing capacity level, the current computing capacity level of each idle base station in the idle base station cluster is obtained, and whether the target computing capacity level is reached is judged, for example, whether the target computing capacity level is equal to or higher than the target computing capacity level is judged.
As an implementation manner, after receiving the resource demand information, the resource status of each idle base station in the idle base station cluster is detected, and the computing capability level of each idle base station is evaluated. After the target computing capacity level is determined and the computing capacity level of each idle base station in the idle base station cluster is evaluated, whether the computing capacity level of each idle base station in the idle base station cluster reaches the target computing capacity level is judged.
In this embodiment, if there is an idle base station whose current computing power level reaches the target computing power level, it is determined as the provider base station. And if the number of the idle base stations with the current computing capacity level reaching the target computing capacity level is more than 1, selecting one of the idle base stations as a provider base station. For example, an idle base station with the largest amount of idle resources is determined as a provider base station; for example, an idle base station closest to the base station of the demand side is determined as the base station of the supply side; for example, the base station with the strongest computing power is determined as the provider base station. For example, after a plurality of idle base stations with current computing power levels reaching the target computing power level are found, resource calling requests are sent to the idle base stations with current computing power levels reaching the target computing power level, and the idle base station which responds fastest and accepts the resource calling requests is determined as a provider base station.
As shown in fig. 4, in an embodiment, before step 150, the method for invoking a resource further includes:
and 142, receiving the acceptance calling information fed back by the provider base station.
In one embodiment, before determining a provider base station, broadcasting a resource invocation request to each idle base station in an idle base station cluster, and receiving acceptance invocation information fed back by at least one idle base station, where the at least one idle base station includes the provider base station. For example, the provider base station is the idle base station that most quickly feeds back the acceptance information. For example, the provider base station is an idle base station that receives the call information for feedback and has the largest amount of idle resources. For example, the donor base station calls information for feedback acceptance and the idle base station closest to the donor base station. For example, the provider base station is an idle base station which receives the call information for feedback and has the fastest resource transmission speed. As another example, the provider base station is selected according to the following manner: setting weighted values for the feedback time, the idle resource quantity, the distance and the resource transmission speed in advance, calculating the overall weight of the feedback time, the idle resource quantity, the distance and the resource transmission speed of each idle base station according to the weighted values and the feedback time, the idle resource quantity, the distance and the resource transmission speed of each idle base station, and selecting the idle base station with the highest overall weight as the supplier base station according to the overall weight of each idle base station. The specific weight value setting, adjusting and assigning, and the design and calculation of the feedback time, the idle resource amount, the distance and the resource transmission speed can be set according to experience; for example, the feedback time, the amount of idle resources, the distance, and the resource transmission speed are numerically processed, e.g., quantized to percentage data, to obtain numerical feedback time, amount of idle resources, distance, and resource transmission speed, and an overall weight of the feedback time, amount of idle resources, distance, and resource transmission speed of each idle base station is calculated according to the weight values and the numerical feedback time, amount of idle resources, distance, and resource transmission speed of each idle base station.
After determining the provider base station, the method for implementing the resource scheduling comprises the steps of sending a resource scheduling request to the determined provider base station and receiving the scheduling accepting information fed back by the provider base station. And if the receiving and calling information fed back by the supplier base station is not received within the preset time, determining a supplier base station from the idle base stations matched with the resource demand information again and sending a resource calling request to the supplier base station.
The resource calling request comprises resource demand information issued by the base station of the demand party, so that the base station of the supply party determines whether to accept calling or not according to the resource demand information in the resource calling request and the resource state of the base station of the supply party. If the provider base station decides to accept the call, it will feed back an accept call message. The embodiment of the invention receives the received calling information, and further establishes a resource calling channel between the requiring side base station and the supplying side base station.
In an embodiment, before step 150, the method for invoking a resource further includes: and judging whether the demand side base station and the supply side base station are mutual communication base stations.
Correspondingly, step 150 specifically includes: and if the demand side base station and the supply side base station are mutual communication base stations, establishing a resource calling channel between the demand side base station and the supply side base station.
As an implementation mode, mutual trust relations between a plurality of base stations and a cloud platform are established in advance; for example, when a base station is registered, prompting the base station to establish a mutual trust relationship with a cloud platform; for example, when the base station issues the resource demand information, whether the base station establishes a mutual trust relationship with the cloud platform is judged, and if not, the base station is prompted to establish the mutual trust relationship with the cloud platform.
Specifically, the method for determining whether the demand side base station and the supplier side base station are mutually trusted base stations includes: judging whether a mutual trust relationship between the demand side base station and the cloud platform and a mutual trust relationship between the supply side base station and the cloud platform are established; if yes, a mutual communication base station is between the demand side base station and the supply side base station.
As one embodiment, establishing the mutual trust relationship includes signing a mutual trust agreement. And if the demand side base station and the supply side base station sign mutual trust protocols with the cloud platform, the demand side base station and the supply side base station are mutual trust base stations. In order to improve the security of resource calling, under the condition that the demand side base station and the supply side base station are mutual communication base stations, the two sides are allowed to call the resources.
The following is a specific resource invocation example:
in this embodiment, as shown in fig. 5, when the demander publishes the resource demand information, the resource invoking device searches the idle base station cluster for the supplier base station matching the resource demand information according to the resource demand information, and determines whether the demander base station and the supplier base station are mutually trusted base stations. If the requiring base station and the supplying base station are mutually communicating base stations, the resource calling device sends a resource calling request to the supplying base station, wherein the resource calling request comprises resource requirement information. And the supplier base station judges whether the resource calling can be accepted or not according to the resource demand information in the resource calling request, and if so, feeds back the acceptance calling information to the resource calling device. And after receiving the call receiving information, the resource calling device establishes a resource calling channel between the requiring base station and the supplying base station so that the requiring base station calls the idle resource of the supplying base station.
Fig. 6 is a schematic block diagram of a resource calling device according to an embodiment of the present invention. The resource calling device can be applied to a cloud platform. As shown in fig. 6, the resource calling apparatus includes:
a receiving module 610, configured to receive resource requirement information;
a searching module 630, configured to search, in an idle base station cluster, a provider base station matching the resource demand information; and
a channel establishing module 650, configured to establish a resource invoking channel between the demanding base station and the supplying base station, so that the demanding base station invokes an idle resource of the supplying base station.
As shown in fig. 7, in one embodiment, the lookup module 630 further includes:
a first determining unit 632, configured to determine a target resource characteristic according to the resource demand information;
an analyzing unit 634, configured to analyze resource characteristics of idle base stations in the idle base station cluster; and
a second determining unit 636, configured to determine an idle base station whose resource characteristics conform to the target resource characteristics as a provider base station.
As shown in fig. 8, in one embodiment, the lookup module 630 further includes:
a third determining unit 631 for determining a target computing capacity level according to the resource demand information;
an obtaining unit 633, configured to obtain a current computing capability level of each idle base station in the idle base station cluster; and
a fourth determining unit 635, configured to determine an idle base station whose current computing capability level reaches the target computing capability level as the provider base station.
As shown in fig. 9, in one embodiment, in addition to the receiving module 610, the searching module 630 and the channel establishing module 650, the resource invoking apparatus further includes at least one of a determining module 670, a mutual trust establishing module 680 and a sending module 690, where:
a determining module 670, configured to determine whether the demand side base station and the supply side base station are mutual communication base stations;
the channel establishing module 650 is specifically configured to establish a resource invoking channel between the requesting base station and the supplying base station when the requesting base station and the supplying base station are mutual communication base stations.
A mutual trust establishing module 680, configured to pre-establish mutual trust relationships between the multiple base stations and the cloud platform;
correspondingly, the determining module 670 is specifically configured to determine whether a mutual trust relationship between the demand side base station and the cloud platform and a mutual trust relationship between the supply side base station and the cloud platform have been established; and if so, the requiring party base station and the supplying party base station are mutual trust base stations.
The sending module 690 is configured to send a resource invoking request to the provider base station;
the receiving module 610 is further configured to receive the call accepting information fed back by the provider base station;
accordingly, the channel establishing module 650 is further specifically configured to establish a resource calling channel between the requiring base station and the providing base station after the receiving module 610 receives the receiving and calling information.
According to the resource calling device, the supplier base station is searched according to the resource demand information issued by the demander base station, and the resource calling channel between the demander base station and the supplier base station is established, so that the demander base station can call the idle resource of the supplier base station, and by reasonably utilizing the redundant idle resource, the resource waste is avoided, and the hardware cost is reduced.
Fig. 10 is a schematic block diagram of a resource calling system according to an embodiment of the present invention. As shown in fig. 10, the resource invoking system includes a resource invoking device 1010 and a plurality of base stations 1030, wherein the plurality of base stations 1030 includes a requesting base station 1031 and a providing base station 1033. In some embodiments, the plurality of base stations 1030 may also include one or more other idle base stations 1032 in addition to the donor base station 1033.
In a specific implementation, the resource invoking device 1010 is a resource invoking device described in any one of the embodiments shown in fig. 6-9, and can be used to execute the resource invoking method described in any one of the embodiments shown in fig. 1-4. The resource calling system of the embodiment of the invention can be used for executing the resource calling method of the embodiment shown in FIG. 5.
As can be seen from the description of fig. 1 to fig. 9, the resource invoking system not only avoids resource waste, but also reduces hardware cost by making reasonable use of redundant idle resources.
It should be noted that, in the above system embodiment, each included module is only divided according to functional logic, but is not limited to the above division as long as the corresponding function can be implemented; in addition, the specific names of the functional modules are only for convenience of distinguishing from each other and are not used for limiting the protection scope of the present invention.
In addition, it can be understood by those skilled in the art that all or part of the steps in the method for implementing the embodiments described above may be implemented by instructing the relevant hardware through a program, and the corresponding program may be stored in a readable storage medium.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is specific and detailed, but not to be understood as limiting the scope of the invention. It should be noted that various changes and modifications can be made by those skilled in the art without departing from the spirit of the invention, and these changes and modifications are all within the scope of the invention. Therefore, the protection scope of the present patent should be subject to the appended claims.
Claims (6)
1. A method for resource invocation, comprising:
receiving resource demand information issued by a base station of a demand party;
searching a supplier base station matched with the resource demand information in the idle base station cluster; and
judging whether the requiring side base station and the supplying side base station are mutually trusted base stations or not;
if the demand side base station and the supply side base station are mutual communication base stations, a resource calling channel between the demand side base station and the supply side base station is established, so that the demand side base station calls idle resources of the supply side base station;
the searching for the supplier base station matching the resource demand information in the idle base station cluster comprises:
determining a target computing capacity grade according to the resource demand information;
acquiring the current computing capacity grade of each idle base station in the idle base station cluster; and
and determining the idle base station with the current computing capacity level reaching the target computing capacity level as the provider base station.
2. The method of claim 1, wherein the searching for a provider base station matching the resource requirement information in the idle base station cluster comprises:
determining target resource characteristics according to the resource demand information;
analyzing the resource characteristics of each idle base station in the idle base station cluster; and
and determining the idle base station with the resource characteristics conforming to the target resource characteristics as a provider base station.
3. The method for invoking resources according to claim 1, wherein before the determining whether the requiring base station and the providing base station are mutually trusted base stations, the method for invoking resources further comprises:
establishing mutual trust relationships between a plurality of base stations and a cloud platform in advance;
the determining whether the demand side base station and the supply side base station are mutually trusted base stations includes:
judging whether a mutual trust relationship between the demand side base station and a cloud platform and a mutual trust relationship between the supply side base station and the cloud platform are established; and if so, the requiring party base station and the supplying party base station are mutual trust base stations.
4. A resource invocation apparatus, comprising:
the receiving module is used for receiving the resource demand information issued by the base station of the demand party;
the searching module is used for searching the supplier base station matched with the resource demand information in the idle base station cluster; and
the judging module is used for judging whether the requiring party base station and the supplying party base station are mutually trusted base stations or not;
a channel establishing module, configured to establish a resource invoking channel between the demanding party base station and the supplying party base station when the demanding party base station and the supplying party base station are mutual communication base stations, so that the demanding party base station invokes an idle resource of the supplying party base station;
the searching module comprises:
a third determining unit, configured to determine a target computing capability level according to the resource demand information;
the acquiring unit is used for acquiring the current computing capacity grade of each idle base station in the idle base station cluster; and
a fourth determining unit, configured to determine an idle base station whose current computing capability level reaches the target computing capability level as a provider base station.
5. The resource calling apparatus of claim 4, wherein the lookup module comprises:
the first determining unit is used for determining target resource characteristics according to the resource demand information;
the analysis unit is used for analyzing the resource characteristics of each idle base station in the idle base station cluster; and
and a second determining unit, configured to determine an idle base station with a resource characteristic that meets the target resource characteristic as a provider base station.
6. A resource invoking system, comprising a plurality of base stations and the resource invoking apparatus according to any one of claims 4-5, wherein the plurality of base stations comprise the requiring base station and the supplying base station.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910490823.XA CN110366194B (en) | 2019-06-06 | 2019-06-06 | Resource calling method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910490823.XA CN110366194B (en) | 2019-06-06 | 2019-06-06 | Resource calling method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110366194A CN110366194A (en) | 2019-10-22 |
| CN110366194B true CN110366194B (en) | 2023-04-14 |
Family
ID=68215728
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910490823.XA Active CN110366194B (en) | 2019-06-06 | 2019-06-06 | Resource calling method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110366194B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114677038A (en) * | 2022-04-12 | 2022-06-28 | 杭州锦辉科技有限公司 | Service resource allocation method, system and device |
| CN117499995A (en) * | 2022-07-21 | 2024-02-02 | 中兴通讯股份有限公司 | Base station calculation power arrangement method and device, electronic equipment and storage medium |
| CN117500068A (en) * | 2022-07-21 | 2024-02-02 | 中兴通讯股份有限公司 | Base station calculation power calling method, device, equipment and medium based on federal learning |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101841860A (en) * | 2010-05-28 | 2010-09-22 | 华为技术有限公司 | Load balancing method and base station |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105898754B (en) * | 2011-11-18 | 2019-08-09 | 华为技术有限公司 | A kind of system and BTS management method for BTS management |
| CN102378186B (en) * | 2011-11-21 | 2018-08-07 | 南京中兴软件有限责任公司 | A kind of base station resource sharing system and method |
| WO2013105787A1 (en) * | 2012-01-09 | 2013-07-18 | Samsung Electronics Co., Ltd. | Method and apparatus for providing communication service to mobile station by multiple base stations in cooperation in wireless communication system |
| CN109474681A (en) * | 2018-11-05 | 2019-03-15 | 安徽大学 | Resource allocation methods, system and the server system of mobile edge calculations server |
-
2019
- 2019-06-06 CN CN201910490823.XA patent/CN110366194B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101841860A (en) * | 2010-05-28 | 2010-09-22 | 华为技术有限公司 | Load balancing method and base station |
Non-Patent Citations (1)
| Title |
|---|
| Ahmed Douik ; Hayssam Dahrouj ; Tareq Y. Al-Naffouri ; Mohamed-Slim.《Distributed Hybrid Scheduling in Multi-Cloud Networks Using Conflict Graphs》.《 IEEE Transactions on Communications》.2018, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110366194A (en) | 2019-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110366194B (en) | Resource calling method, device and system | |
| CN108463805B (en) | User equipment selection for mobile edge computing | |
| CN108989061B (en) | Communication system, method, server and storage medium | |
| CN110336848B (en) | Scheduling method, scheduling system and scheduling equipment for access request | |
| CN111885733B (en) | Resource allocation method, device, storage medium and network equipment | |
| US20200041972A1 (en) | Method and system for creating energy demand model | |
| CN107506910A (en) | The method for assessing electrical changing station service ability | |
| JP6449921B2 (en) | Terminal device and D2D resource management method | |
| CN110659863A (en) | Object monitoring method and device, electronic equipment and computer readable storage medium | |
| CN107426109B (en) | Traffic scheduling method, VNF module and traffic scheduling server | |
| CN111381843A (en) | Firmware upgrading scheduling method, firmware upgrading method and related device | |
| CN108702756B (en) | Resource selection method and terminal | |
| CN106162573B (en) | Cluster group call processing method, related equipment and system | |
| CN107645468B (en) | Extension resource allocation method and device | |
| CN109756949B (en) | Resource allocation method and device | |
| CN107835104B (en) | Method, system, equipment and storage medium for sharing NF user permission among network slices | |
| CN112449357B (en) | Information interaction method and related equipment | |
| CN103260221B (en) | Cell accessing method and device | |
| CN111866994B (en) | Method and device for rapidly distributing network at hot spot | |
| CN114374495B (en) | Uplink data transmission method and related products | |
| CN114630391A (en) | Communication method, device and system under network co-construction sharing scene and sharing base station | |
| CN112449301B (en) | Broadcast method of positioning auxiliary information, positioning server and RAN node | |
| CN113254207B (en) | Identification code generation method, device, server and storage medium | |
| US10506001B2 (en) | Method for transmitting data sets to mobile terminals | |
| CN112954744A (en) | Access control method and device for mobile terminal |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |