CN111885185A

CN111885185A - Resource scheduling method and device

Info

Publication number: CN111885185A
Application number: CN202010744618.4A
Authority: CN
Inventors: 李铭轩; 陈淑平; 常培; 刘秋妍
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2020-07-29
Filing date: 2020-07-29
Publication date: 2020-11-03

Abstract

The embodiment of the application provides a resource scheduling method and device, relates to the technical field of communication, and solves the technical problem that the existing resource scheduling method is single. The resource scheduling method is applied to a resource scheduling system comprising a first server, a second server, a bearing network device and a network slice cooperative device. The bearer network device firstly sends a resource request to the first server through a network slice established in advance by the network slice cooperative device. And when receiving that the resource provided by the first server does not meet the preset condition, the bearing network equipment schedules the resource provided by the second server through the network slice. The network slice comprises a bearing network subslice, a first network subslice and a second network subslice. The first network subslice correspond to a first server. The second network subslice correspond to a second server. The network slice also includes service requirement information for the traffic.

Description

Resource scheduling method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a resource scheduling method and apparatus.

Background

At present, with the development of network technology, more and more terminals adopt cloud computing to realize data processing.

Cloud computing is one of distributed computing, and is used for decomposing a huge data computing processing program into a plurality of small programs, then processing the small programs through a server cluster consisting of a plurality of servers to determine a processing result, and returning the processing result to a terminal. In cloud computing, resources such as a Central Processing Unit (CPU), a memory, and a hard disk of each server in a server cluster form a pooled cloud resource pool to provide resources for a terminal.

When a network includes multiple cloud resource pools, a Cloud Management Platform (CMP) is generally required to uniformly manage network resources in the multiple cloud resource pools. However, when scheduling network resources, the existing cloud management platform generally schedules resources according to network bandwidth only. With the development of network diversification, the existing resource scheduling method is single and cannot meet the requirement of a more refined network.

Disclosure of Invention

The application provides a resource scheduling method and device, and solves the technical problem that the existing resource scheduling method is single.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, a resource scheduling method is provided, which is applied to a resource scheduling system including a first server, a second server, a bearer network device, and a network slice cooperative device. Here, the network slice cooperative device is connected to the first server, the second server, and the bearer network device, respectively. The first server and the second server are used for providing different resources for the service carried by the carrying network equipment.

Specifically, the bearer network device first sends a resource request to the first server through a network slice established in advance by the network slice cooperating device. And when receiving that the resource provided by the first server does not meet the preset condition, the bearing network equipment schedules the resource provided by the second server through the network slice. The network slice comprises a bearing network subslice, a first network subslice and a second network subslice. The first network subslice correspond to a first server. The second network subslice correspond to a second server. The network slice also includes service requirement information for the traffic.

It can be seen that, when the bearer network device performs resource scheduling, the resource provided by the first server or the second server may be scheduled through the network slice. Because the network slice includes service requirement information (such as geographical position requirement, bandwidth requirement, time delay requirement, transmission quality requirement, etc.) of the service, the bearer network device can schedule resources required by the service according to service requirements in various aspects of the service, thereby solving the technical problem that the existing resource scheduling method is single, and increasing the diversity of resource scheduling.

In a second aspect, a resource scheduling method is provided, which is applied to a resource scheduling system including a first server, a second server, a bearer network device, and a network slice cooperative device. Here, the network slice cooperative device is connected to the first server, the second server, and the bearer network device, respectively. The first server and the second server are used for providing different resources for the service carried by the carrying network equipment.

Specifically, the network slice coordination device first obtains a first network sub-slice established by the first server, a second network sub-slice established by the second server, and a bearer network sub-slice established by the bearer network device, and then establishes a network slice according to the first network sub-slice, the second network sub-slice, and the bearer network sub-slice. The network slice is used for cooperatively communicating the first server, the second server and the bearing network device.

As can be seen from the above, the network slice cooperative apparatus may establish a network slice in which the first server, the second server, and the bearer network apparatus cooperatively communicate according to the first network sub-slice, the second network sub-slice, and the bearer network sub-slice, and implement resource scheduling through the network slice. Because the network slice can represent the service requirement information of the service from multiple aspects, the network slice is established by the network slice cooperation equipment, so that the bearing network equipment can schedule the resources required by the service according to the service requirements from multiple aspects of the service, the technical problem that the conventional resource scheduling method is single is solved, and the diversity of resource scheduling is increased.

In a third aspect, a resource scheduling apparatus is provided, where the resource scheduling apparatus is applied to a bearer network device, and the bearer network device belongs to a resource scheduling system including a first server, a second server, a bearer network device, and a network slice coordination device; the network slice cooperative equipment is respectively connected with the first server, the second server and the bearing network equipment; the first server and the second server are used for providing different resources for the service carried by the carrying network equipment; the resource scheduling device comprises: a transmitting unit and a scheduling unit.

Specifically, the sending unit is configured to send the resource request to the first server through a network slice established in advance by the network slice coordination device; the network slices comprise a bearing network sub-slice, a first network sub-slice and a second network sub-slice; the first network subslice corresponding to a first server; the second network subslice corresponding to a second server; the network slice also comprises service requirement information of the service; and if the received resource provided by the first server does not meet the preset condition, the scheduling unit is used for scheduling the resource provided by the second server through the network slice.

In a fourth aspect, a resource scheduling apparatus is provided, which is applied to a network slice cooperative device belonging to a resource scheduling system including a first server, a second server, a bearer network device, and a network slice cooperative device; the network slice cooperative equipment is respectively connected with the first server, the second server and the bearing network equipment; the first server and the second server are used for providing different resources for the service carried by the carrying network equipment; the resource scheduling device comprises: the device comprises an acquisition unit and a building unit.

Specifically, the acquiring unit is configured to acquire a first network sub-slice established by a first server, a second network sub-slice established by a second server, and a bearer network sub-slice established by bearer network equipment; the establishing unit is used for establishing a network slice according to the first network sub-slice, the second network sub-slice and the bearing network sub-slice acquired by the acquiring unit; the network slice is used for cooperatively penetrating the first server, the second server and the bearing network equipment.

In a fifth aspect, an apparatus for scheduling resources is provided and includes a memory and a processor. The memory is used for storing computer execution instructions, and the processor is connected with the memory through a bus. When the resource scheduling apparatus is operated, the processor executes computer-executable instructions stored in the memory, so as to cause the resource scheduling apparatus to execute the resource scheduling method according to the first aspect or the second aspect.

The resource scheduling apparatus may be a network device, or may be a part of an apparatus in the network device, such as a system on chip in the network device. The system on chip is configured to support the network device to implement the functions involved in the first aspect or the second aspect and any one of the possible implementations thereof, for example, to receive, determine, and offload data and/or information involved in the resource scheduling method. The chip system includes a chip and may also include other discrete devices or circuit structures.

In a sixth aspect, a computer-readable storage medium is provided, which comprises computer-executable instructions, which, when executed on a computer, cause the computer to perform the resource scheduling method of the first or second aspect.

In a seventh aspect, a computer program product is provided, which comprises computer instructions that, when run on a computer, cause the computer to perform the resource scheduling method as described in the first aspect and its various possible implementations.

It should be noted that all or part of the above computer instructions may be stored on the first computer readable storage medium. The first computer readable storage medium may be packaged together with the processor of the resource scheduling apparatus, or may be packaged separately from the processor of the resource scheduling apparatus, which is not limited in this application.

For the description of the third, fourth, fifth, sixth and seventh aspects of the present invention, reference may be made to the detailed description of the first or second aspect; in addition, for the beneficial effects described in the third aspect, the fourth aspect, the fifth aspect, the sixth aspect and the seventh aspect, reference may be made to beneficial effect analysis of the first aspect or the second aspect, and details are not repeated here.

In the present application, the names of the resource scheduling devices do not limit the devices or the functional modules themselves, and in practical implementations, the devices or the functional modules may appear by other names. Insofar as the functions of the respective devices or functional blocks are similar to those of the present invention, they are within the scope of the claims of the present invention and their equivalents.

These and other aspects of the invention will be more readily apparent from the following description.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic hardware structure diagram of a resource scheduling apparatus according to an embodiment of the present disclosure;

fig. 3 is a schematic hardware structure diagram of another resource scheduling apparatus according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a resource scheduling method according to an embodiment of the present application;

fig. 5 is a schematic flowchart of another resource scheduling method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of another resource scheduling method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a resource scheduling apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of another resource scheduling apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another resource scheduling apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

For the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first" and "second" are used to distinguish the same items or similar items with basically the same functions and actions, and those skilled in the art can understand that the terms "first" and "second" are not used to limit the quantity and execution order.

To facilitate an understanding of the present application, the relevant elements referred to in the present application will now be described.

Network slicing

Network slicing is a logical concept that mainly combines different application scenarios and requirements to provide specific network capabilities and network characteristics. The network slicing essentially divides a physical network of an operator into a plurality of virtual networks, and each virtual network is divided according to different service requirements, such as delay, bandwidth, security, reliability and the like, so as to flexibly cope with different network application scenarios.

The earliest concept of network slicing can be traced back to infrastructure as a service in a cloud computing model, and different tenants realize network, computing and storage resource sharing by creating mutually isolated virtual networks on a common underlying physical infrastructure. The method comprises the steps of performing differentiation processing according to the request of each client, dividing the client into different service types by a network operator through slicing, enabling each service to have different service requests, and managing the slice type and network service distributed and used by each service according to a Service Level Agreement (SLA).

At present, technologies such as a Software Defined Network (SDN) and a Network Function Virtualization (NFV) are main implementation manners of network slicing. On this basis, virtualization of topology resources (such as links, nodes, ports, and the like) of the bearer network slice is realized based on virtualization technologies such as Virtual Private Networks (VPNs), Virtual Local Area Networks (VLANs), and the like, and a plurality of virtual networks (i.e., slice networks) are organized as required.

The whole network slice architecture is divided into a service layer, a slice network layer and a physical layer. According to the overall architecture of the network slice, around three application scenarios commonly used by the network slice, a virtual network controller is created by an SDN controller according to the requirements of the network slice, and management of the slice topology and the physical network topology is realized by realizing network resource topology, slice arrangement, pipeline control and the like through virtual network virtualization.

In this embodiment, the network slice cooperative device may establish a network slice in which the first server, the second server, and the bearer network device cooperatively communicate according to the first network sub-slice established by the first server and the configuration information thereof, and implement resource scheduling by using the network slice.

As described in the background, existing cloud management platforms generally schedule resources based only on network bandwidth when scheduling network resources. With the development of network diversification, the existing resource scheduling method is single and cannot meet the requirement of a more refined network.

In view of the foregoing problems, an embodiment of the present application provides a resource scheduling method, where a bearer network device first sends a resource request to a first server through a network slice established in advance by a network slice coordination device. And when receiving that the resource provided by the first server does not meet the preset condition, the bearing network equipment schedules the resource provided by the second server through the network slice. Because the network slice includes service requirement information (such as geographical position requirement, bandwidth requirement, time delay requirement, transmission quality requirement, etc.) of the service, the bearer network device can schedule resources required by the service according to service requirements in various aspects of the service, thereby solving the technical problem that the existing resource scheduling method is single, and increasing the diversity of resource scheduling.

The resource scheduling method provided by the embodiment of the application is suitable for the resource scheduling system 10. Fig. 1 shows a structure of the resource scheduling system 10. As shown in fig. 1, the resource scheduling system 10 includes: the system comprises a terminal 11, a bearer network device 12, a first server 13, a second server 14 and a network slicing coordination device 15.

Wherein, the terminal 11 is connected with the carrying network device 12 in a communication way. The network slicing coordination apparatus 15 is connected to the first server 13, the second server 14, and the carrier network apparatus 12, respectively. The bearer network device 12 is connected to the first server 13 and the second server 14 through the network slice determined by the network slice coordination device 15.

The terminal 11 in this embodiment of the present application may be various handheld devices, vehicle-mounted devices, wearable devices, computers, smart home devices, or smart office devices having a communication function, which is not limited in this embodiment of the present application. For example, the handheld device may be a smartphone. The in-vehicle device may be an in-vehicle navigation system. The wearable device may be a smart bracelet. The computer may be a Personal Digital Assistant (PDA) computer, a tablet computer, and a laptop computer. The intelligent household equipment can be an intelligent curtain and an intelligent water meter. The intelligent office equipment may be an intelligent printer.

Optionally, when the terminal 11 is a mobile terminal, the terminal 11 may be connected to the bearer network device through a wireless access manner, such as a Customer Premise Equipment (CPE) and an access network device (not shown in fig. 1). When the terminal 11 is a fixed terminal, the terminal 11 may be connected to the bearer network device through a wired access manner such as an optical fiber, a broadband, and the like.

The bearer network device 12 in this embodiment may be a Packet Transport Network (PTN) device, an Optical Transport Network (OTN) device, or a network device such as an SDN controller that is responsible for carrying and aggregating data, which is not limited in this embodiment.

The first server 13 and the second server 14 in this embodiment of the application are configured to provide different resources to services carried by the carrying network device 12.

Specifically, the first server 13 is one server in a cloud computing server cluster (composed of a plurality of servers) corresponding to the server, may also be a chip in the server, may also be a system on chip in the server, and may also be implemented by a Virtual Machine (VM) deployed on a physical machine, which is not limited in this embodiment of the present application.

Correspondingly, the second server 14 is one server in a cloud computing server cluster (composed of a plurality of servers) corresponding to the server, may also be a chip in the server, may also be a system on chip in the server, and may also be implemented by a virtual machine deployed on a physical machine, which is not limited in this embodiment of the present application.

It should be noted that, the first server 13 forms resources, such as a central processing unit, a memory, and a hard disk, of each server in the server cluster corresponding to the server into a pooled first cloud resource pool, so as to provide resources for the terminal.

Correspondingly, the second server 14 forms resources such as a central processing unit, a memory, and a hard disk of each server in the server cluster corresponding to the server into a pooled second cloud resource pool, so as to provide resources for the terminal.

The network slice cooperative apparatus 15 in this embodiment is used to establish a network slice where the first server, the second server, and the bearer network apparatus are cooperatively communicated. The network slice cooperative device 15 may be a server, or may be one server in a server cluster (composed of a plurality of servers), or may be a chip in the server, or may be a system on chip in the server, or may be implemented by a virtual machine deployed on a physical machine, which is not limited in this embodiment of the present application.

The terminal 11, the bearer network device 12, the first server 13, the second server 14 and the network slice coordination device 15 in fig. 1 include elements included in the resource scheduling apparatus shown in fig. 2. The hardware structures of the terminal 11, the bearer network device 12, the first server 13, the second server 14 and the network slice coordination device 15 in fig. 1 will be described below by taking the resource scheduling apparatus shown in fig. 2 as an example.

Fig. 2 shows a hardware structure diagram of a resource scheduling apparatus according to an embodiment of the present application. As shown in fig. 2, the resource scheduling apparatus includes a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, the memory 22 and the communication interface 23 may be connected by a bus 24.

The processor 21 is a control center of the resource scheduling apparatus, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 21 may be a Central Processing Unit (CPU), other general-purpose processors, or the like. Wherein a general purpose processor may be a microprocessor or any conventional processor or the like.

For one embodiment, processor 21 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG. 2.

The memory 22 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In a possible implementation, the memory 22 may exist separately from the processor 21, and the memory 22 may be connected to the processor 21 via a bus 24 for storing instructions or program codes. The processor 21 can implement the resource scheduling method provided by the embodiment of the present invention when calling and executing the instructions or program codes stored in the memory 22.

In another possible implementation, the memory 22 may also be integrated with the processor 21.

And a communication interface 23 for connecting with other devices through a communication network. The communication network may be an ethernet network, a radio access network, a Wireless Local Area Network (WLAN), or the like. The communication interface 23 may include a receiving unit for receiving data, and a transmitting unit for transmitting data.

The bus 24 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 2, but it is not intended that there be only one bus or one type of bus.

It should be noted that the structure shown in fig. 2 does not constitute a limitation to the resource scheduling apparatus. The resource scheduler may comprise more or fewer components than shown in fig. 2, or some components may be combined, or a different arrangement of components than shown.

Fig. 3 shows another hardware structure of the resource scheduling apparatus in the embodiment of the present application. As shown in fig. 3, the resource scheduling means may comprise a processor 31 and a communication interface 32. The processor 31 is coupled to a communication interface 32.

The function of the processor 31 may refer to the description of the processor 21 above. The processor 31 also has a memory function, and the function of the memory 22 can be referred to.

The communication interface 32 is used to provide data to the processor 31. The communication interface 32 may be an internal interface of the resource scheduling apparatus, or may be an external interface (corresponding to the communication interface 23) of the resource scheduling apparatus.

It is noted that the structure shown in fig. 2 (or fig. 3) does not constitute a limitation of the resource scheduling apparatus, which may comprise more or less components than those shown in fig. 2 (or fig. 3), or combine some components, or a different arrangement of components, in addition to the components shown in fig. 2 (or fig. 3).

The following describes in detail a resource scheduling method provided in the embodiment of the present application with reference to the communication system shown in fig. 1 and the resource scheduling apparatus shown in fig. 2 (or fig. 3).

The resource scheduling method provided by the embodiment of the application comprises the following steps: the network slice cooperative device establishes a network slice flow (referred to as a "network slice establishing flow") for cooperatively communicating the first server, the second server and the bearer network device, and the bearer network device performs resource scheduling according to the established network slice (referred to as a "resource scheduling flow").

The "network slicing establishment procedure" will be described first.

As shown in fig. 4, the "network slice establishment procedure" includes: S401-S402.

S401, the network slice cooperative device obtains a first network sub-slice established by the first server, a second network sub-slice established by the second server and a bearer network sub-slice established by the bearer network device.

Specifically, as can be seen from the above description of the network slice, in the cloud computing technology, when the first cloud resource pool and the second cloud resource pool implement cooperative communication of resources, the SDN controller is required to create a virtual network controller, and management of the slice topology and the physical network topology is implemented by implementing network resource topology, slice arrangement, pipeline control, and the like through virtual network virtualization. Therefore, the temperature of the molten metal is controlled,

the first cloud resource pool of the first server firstly establishes a template of the virtual network, and then sends the template of the virtual network to the SDN controller of the first server. The SDN controller establishes a first sub-network according to a template of the virtual network, and sends a first network sub-slice and configuration information thereof to the first cloud resource pool according to the first sub-network. In this case, the first server may obtain the first network sub-slice and its configuration information received by the first cloud resource pool.

After the first server acquires the first network subslice and the configuration information thereof, the network slice cooperation device acquires the first network subslice and the configuration information thereof established by the first server, and carries out information record and request encapsulation on the first network subslice and the configuration information thereof.

And then, when the network slice cooperative equipment establishes the network slice according to the first network subslice and the configuration information thereof, the network slice cooperative equipment sends the configuration information of the first network subslice to the second server.

After the second server receives the configuration information of the first network sub-slice sent by the network slice cooperative device, a second cloud resource pool of the second server firstly establishes a template of the virtual network according to the configuration information of the first network sub-slice, and then sends the template of the virtual network to an SDN controller of the second server. And the SDN controller establishes a second sub-network according to the template of the virtual network and sends a second network sub-slice to a second cloud resource pool according to the second sub-network. In this case, the second server may retrieve the second network sub-slice received by the second cloud resource pool.

After the second server obtains the second network sub-slice, the network slice cooperative device obtains the second network sub-slice and the configuration information thereof established by the second server, and carries out information record and request encapsulation on the second network sub-slice and the configuration information thereof.

After the configuration information of the first network sub-slice and the configuration information of the second network sub-slice are obtained, the network slice cooperation device sends the configuration information of the first network sub-slice and the configuration information of the second network sub-slice to the bearer network device.

After receiving the first network sub-slice and the configuration information thereof, and the second network sub-slice and the configuration information thereof, the SDN controller of the bearer network device establishes a template of a virtual network according to the first network sub-slice and the configuration information thereof, and the second network sub-slice and the configuration information thereof, and establishes a bearer network sub-network and a bearer network sub-slice according to the template of the virtual network.

After the bearer network device establishes a bearer network sub-network and a bearer network sub-slice, the network slice coordination device obtains the bearer network sub-slice established by the bearer network device and configuration information thereof, and performs information filing and request encapsulation on the bearer network sub-slice and the configuration information thereof.

S402, the network slice cooperative equipment establishes a network slice according to the first network sub-slice, the second network sub-slice and the bearing network sub-slice.

The network slice is used for cooperatively communicating the first server, the second server and the bearing network device.

After the first network sub-slice, the second network sub-slice and the carrier network sub-slice are obtained, the network slice cooperation device establishes the network slice according to the first network sub-slice, the second network sub-slice and the carrier network sub-slice, so that cooperation and communication of the first server, the second server and the carrier network device are achieved.

Optionally, in conjunction with fig. 4, as shown in fig. 5, S401 may be replaced by S501-S508.

S501, establishing a first network sub-slice by the first server.

S502, the network slice cooperative equipment acquires a first network sub-slice established by the first server and configuration information thereof.

S503, the network slice cooperative device sends the configuration information of the first network subslice to the second server.

And S504, the second server establishes a second network sub-slice according to the configuration information of the first network sub-slice.

And S505, the network slice cooperative device acquires a second network sub-slice established by the second server according to the configuration information of the first network sub-slice.

S506, the network slice cooperative equipment sends the configuration information of the first network sub-slice and the configuration information of the second network sub-slice to the carrying network equipment.

Namely, the bearer network device receives the network slice configuration information sent by the network slice coordination device.

And S507, the bearer network device establishes the bearer network sub-slice according to the configuration information of the first network sub-slice and the configuration information of the second network sub-slice.

Namely, the bearer network device establishes the bearer network sub-slice according to the configuration information of the network slice.

And S508, the network slice cooperative equipment acquires the bearer network sub-slice established by the bearer network equipment according to the configuration information of the first network sub-slice and the configuration information of the second network sub-slice.

The resource scheduling process is described below.

As shown in fig. 6, the "resource scheduling flow" includes: S601-S605.

S601, the bearing network device sends a resource request to the first server through a network slice established in advance by the network slice cooperative device.

The network slice comprises a bearing network subslice, a first network subslice and a second network subslice. The first network subslice correspond to a first server. The second network subslice correspond to a second server. The network slice also includes service requirement information of the traffic, such as: geographical location requirements, bandwidth requirements, latency requirements, transmission quality requirements, and the like.

As can be seen from the above description of network slices, a network slice may provide specific network capabilities and network characteristics in connection with different application scenarios and requirements. Therefore, after the network slice is pre-established by the network slice coordination device, the bearer network device may send the resource request to the first server through the network slice pre-established by the network slice coordination device, so that the first server processes the service borne by the bearer network device according to the resources in the first cloud resource pool.

S602, the bearing network equipment receives the resource provided by the first server.

After receiving a resource request sent by a bearer network device to a first server through a network slice, the first server establishes resources of a service borne by the bearer network device and sends corresponding resources to the bearer network device.

S603, the bearing network equipment judges whether the received resource provided by the first server meets a preset condition.

After receiving the resource provided by the first server, the network loading equipment judges whether the received resource provided by the first server meets a preset condition. If it is received that the resource provided by the first server satisfies the predetermined condition, S604 is executed. If it is received that the resource provided by the first server does not satisfy the preset condition, S605 is executed.

Optionally, the preset condition may be that the bandwidth meets a preset threshold, or that the time delay meets a preset threshold, or that the geographic location meets a preset distance, or other preset conditions, which is not limited in this embodiment of the present application.

S604, the bearer network device processes the service borne by the bearer network device according to the resource provided by the first server.

S605, the bearing network equipment schedules the resource provided by the second server through network slicing.

Because the first server and the second server are used for providing different resources for the service borne by the bearer network device, if the received resource provided by the first server does not meet the preset condition, the bearer network device schedules the resource provided by the second server through network slicing.

The embodiment of the application provides a resource scheduling method, which is applied to a resource scheduling system comprising a first server, a second server, a bearing network device and a network slice cooperative device. Here, the network slice cooperative device is connected to the first server, the second server, and the bearer network device, respectively. The first server and the second server are used for providing different resources for the service carried by the carrying network equipment.

The scheme provided by the embodiment of the application is mainly introduced from the perspective of a method. To implement the above functions, it includes hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiment of the present application, the resource scheduling apparatus may be divided into the functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. Optionally, the division of the modules in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 7 is a schematic structural diagram of a resource scheduling apparatus 70 according to an embodiment of the present application. The resource scheduling apparatus 70 is used to solve the technical problem that the continuity of the service of the terminal cannot be guaranteed in the prior art, for example, to execute the resource scheduling method shown in fig. 5 or fig. 6. The resource scheduling apparatus 70 is applied to a bearer network device, and the bearer network device belongs to a resource scheduling system including a first server, a second server, a bearer network device, and a network slice coordination device. The network slice cooperative device is respectively connected with the first server, the second server and the bearing network device. The first server and the second server are used for providing different resources for the service carried by the carrying network equipment. The resource scheduling device comprises: a transmitting unit 701 and a scheduling unit 702.

A sending unit 701, configured to send a resource request to a first server through a network slice established in advance by a network slice coordination device; the network slices comprise a bearing network sub-slice, a first network sub-slice and a second network sub-slice; the first network subslice corresponding to a first server; the second network subslice corresponding to a second server; the network slice also includes service requirement information for the traffic. For example, in conjunction with fig. 6, the transmitting unit 701 is configured to execute S601.

If it is received that the resource provided by the first server does not satisfy the preset condition, the scheduling unit 702 is configured to schedule the resource provided by the second server through the network slice. For example, in connection with fig. 6, the scheduling unit 702 is configured to execute S605.

Optionally, as shown in fig. 8, the resource scheduling apparatus further includes: a receiving unit 703 and a processing unit 704.

A receiving unit 703 is configured to receive network slice configuration information sent by the network slice coordination device. For example, in conjunction with fig. 5, the receiving unit 703 is configured to perform S506.

A processing unit 704, configured to establish a bearer network subslice according to the configuration information of the network slice received by the receiving unit 703. For example, in conjunction with fig. 5, the processing unit 704 is configured to execute S507.

Fig. 9 is a schematic structural diagram of another resource scheduling apparatus 90 according to an embodiment of the present application. The resource scheduling apparatus 90 is used to solve the technical problem that the continuity of the service of the terminal cannot be guaranteed in the prior art, for example, to execute the resource scheduling method shown in fig. 4 or fig. 5. The resource scheduling apparatus 90 is applied to a network slice cooperative device, and the network slice cooperative device belongs to a resource scheduling system including a first server, a second server, a bearer network device, and a network slice cooperative device. The network slice cooperative device is respectively connected with the first server, the second server and the bearing network device. The first server and the second server are used for providing different resources for the service carried by the carrying network equipment. The resource scheduling device comprises: an acquisition unit 901 and a setup unit 902.

An obtaining unit 901, configured to obtain a first network sub-slice established by a first server, a second network sub-slice established by a second server, and a bearer network sub-slice established by a bearer network device. For example, in conjunction with fig. 4, the acquisition unit 901 is configured to execute S401.

An establishing unit 902, configured to establish a network slice according to the first network sub-slice, the second network sub-slice, and the bearer network sub-slice acquired by the acquiring unit 901; the network slice is used for cooperatively penetrating the first server, the second server and the bearing network equipment. For example, in conjunction with fig. 4 or fig. 5, the establishing unit 902 is configured to execute S402.

Optionally, the obtaining unit 901 is specifically configured to:

and acquiring a first network sub-slice established by the first server and configuration information thereof. For example, in conjunction with fig. 5, the obtaining unit 901 is further configured to execute S502.

Configuration information for the first network subslice is sent to a second server. For example, in conjunction with fig. 5, the obtaining unit 901 is further configured to execute S503.

And acquiring a second network sub-slice established by the second server according to the configuration information of the first network sub-slice. For example, in conjunction with fig. 5, the obtaining unit 901 is further configured to execute S505.

And sending the configuration information of the first network sub-slice and the configuration information of the second network sub-slice to the bearer network equipment. For example, in conjunction with fig. 5, the obtaining unit 901 is further configured to execute S506.

And acquiring the bearer network sub-slice established by the bearer network equipment according to the configuration information of the first network sub-slice and the configuration information of the second network sub-slice. For example, in conjunction with fig. 5, the obtaining unit 901 is further configured to execute S508.

Embodiments of the present application also provide a computer-readable storage medium, which includes computer-executable instructions. When the computer executes the instructions to run on the computer, the computer is enabled to execute the steps executed by the resource scheduling device in the resource scheduling method provided by the embodiment.

The embodiments of the present application further provide a computer program product, where the computer program product may be directly loaded into the memory and contains software codes, and after the computer program product is loaded and executed by the computer, the computer program product can implement each step executed by the resource scheduling device in the resource scheduling method provided in the foregoing embodiments.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The processes or functions according to the embodiments of the present application are generated in whole or in part when the computer-executable instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). Computer-readable storage media can be any available media that can be accessed by a computer or can comprise one or more data storage devices, such as servers, data centers, and the like, that can be integrated with the media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical function division, and there may be other division ways in actual implementation. For example, various elements or components may be combined or may be integrated into another device, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. Units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A resource scheduling method is characterized in that the method is applied to a resource scheduling system comprising a first server, a second server, a bearing network device and a network slice cooperative device; the network slice cooperative equipment is respectively connected with the first server, the second server and the bearing network equipment; the first server and the second server are used for providing different resources for the service carried by the carrying network equipment; the resource scheduling method comprises the following steps:

the bearing network equipment sends a resource request to the first server through a network slice which is established in advance by the network slice cooperative equipment; the network slices comprise a bearing network subslice, a first network subslice and a second network subslice; the first network sub-slice corresponds to the first server; the second network subslice corresponding to the second server; the network slice also comprises service requirement information of the service;

and if the received resource provided by the first server does not meet the preset condition, the bearing network equipment schedules the resource provided by the second server through the network slice.

2. The method for scheduling resources according to claim 1, wherein the method for scheduling resources further comprises:

the bearing network equipment receives the network slice configuration information sent by the network slice cooperative equipment;

and the bearing network equipment establishes the bearing network sub-slice according to the configuration information of the network slice.

3. A resource scheduling method is characterized in that the method is applied to a resource scheduling system comprising a first server, a second server, a bearing network device and a network slice cooperative device; the network slice cooperative equipment is respectively connected with the first server, the second server and the bearing network equipment; the first server and the second server are used for providing different resources for the service carried by the carrying network equipment; the resource scheduling method comprises the following steps:

the network slice cooperative device acquires a first network sub-slice established by the first server, a second network sub-slice established by the second server and a bearer network sub-slice established by the bearer network device;

the network slice cooperative equipment establishes a network slice according to the first network sub-slice, the second network sub-slice and the bearer network sub-slice; the network slice is used for cooperatively communicating the first server, the second server and the bearing network device.

4. The method according to claim 3, wherein the acquiring, by the network slice coordination device, the first network sub-slice sent by the first server, the second network sub-slice sent by the second server, and the bearer network sub-slice sent by the bearer network device includes:

the network slice cooperative equipment acquires a first network sub-slice established by the first server and configuration information thereof;

the network slice cooperative device sends configuration information of the first network sub-slice to the second server;

the network slice cooperative equipment acquires a second network sub-slice established by the second server according to the configuration information of the first network sub-slice;

the network slice cooperative device sends the configuration information of the first network sub-slice and the configuration information of the second network sub-slice to the bearer network device;

and the network slice cooperation device acquires the bearer network sub-slice established by the bearer network device according to the configuration information of the first network sub-slice and the configuration information of the second network sub-slice.

5. A resource scheduling device is characterized in that the resource scheduling device is applied to a bearing network device, and the bearing network device belongs to a resource scheduling system comprising a first server, a second server, the bearing network device and a network slicing cooperative device; the network slice cooperative equipment is respectively connected with the first server, the second server and the bearing network equipment; the first server and the second server are used for providing different resources for the service carried by the carrying network equipment; the resource scheduling apparatus includes: a transmitting unit and a scheduling unit;

the sending unit is configured to send a resource request to the first server through a network slice established in advance by the network slice coordination device; the network slices comprise a bearing network subslice, a first network subslice and a second network subslice; the first network sub-slice corresponds to the first server; the second network subslice corresponding to the second server; the network slice also comprises service requirement information of the service;

and if the received resource provided by the first server does not meet the preset condition, the scheduling unit is used for scheduling the resource provided by the second server through the network slice.

6. The apparatus for scheduling resources according to claim 5, wherein the apparatus for scheduling resources further comprises: a receiving unit and a processing unit;

the receiving unit is configured to receive network slice configuration information sent by the network slice coordination device;

the processing unit is configured to establish the bearer network sub-slice according to the configuration information of the network slice received by the receiving unit.

7. A resource scheduling device is applied to network slice cooperative equipment, wherein the network slice cooperative equipment belongs to a resource scheduling system comprising a first server, a second server, bearing network equipment and the network slice cooperative equipment; the network slice cooperative equipment is respectively connected with the first server, the second server and the bearing network equipment; the first server and the second server are used for providing different resources for the service carried by the carrying network equipment; the resource scheduling apparatus includes: an acquisition unit and an establishment unit;

the acquiring unit is configured to acquire a first network sub-slice established by the first server, a second network sub-slice established by the second server, and a bearer network sub-slice established by the bearer network device;

the establishing unit is configured to establish a network slice according to the first network sub-slice, the second network sub-slice and the carrier network sub-slice acquired by the acquiring unit; the network slice is used for cooperatively communicating the first server, the second server and the bearing network device.

8. The resource scheduling apparatus according to claim 7, wherein the obtaining unit is specifically configured to:

acquiring a first network sub-slice established by the first server and configuration information thereof;

sending configuration information of the first network subslice to the second server;

acquiring a second network sub-slice established by the second server according to the configuration information of the first network sub-slice;

sending the configuration information of the first network sub-slice and the configuration information of the second network sub-slice to the bearer network device;

and acquiring the bearer network sub-slice established by the bearer network equipment according to the configuration information of the first network sub-slice and the configuration information of the second network sub-slice.

9. A resource scheduling apparatus, comprising a memory and a processor; the memory is used for storing computer execution instructions, and the processor is connected with the memory through a bus;

the processor executes the computer-executable instructions stored by the memory when the resource scheduling apparatus is running to cause the resource scheduling apparatus to perform the resource scheduling method of any one of claims 1-2 or 3-4.

10. A computer-readable storage medium, comprising computer-executable instructions that, when executed on a computer, cause the computer to perform the method of resource scheduling of any of claims 1-2 or 3-4.