CN114024855B - Fusion method and device of network slice and edge cloud - Google Patents
Fusion method and device of network slice and edge cloud Download PDFInfo
- Publication number
- CN114024855B CN114024855B CN202010689176.8A CN202010689176A CN114024855B CN 114024855 B CN114024855 B CN 114024855B CN 202010689176 A CN202010689176 A CN 202010689176A CN 114024855 B CN114024855 B CN 114024855B
- Authority
- CN
- China
- Prior art keywords
- network
- service
- edge cloud
- network slice
- service provider
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
Abstract
The application provides a method and a device for fusing network slice and edge cloud, relates to the technical field of communication, and solves the problem of unsafe network caused by sinking network resources and edge cloud to a user side. The method comprises the following steps: the fusion device of the network slice and the edge cloud receives the network request and determines an initial service provider according to the service type of the service. And then, determining the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator, and determining a target service provider corresponding to the network request according to the initial service provider, the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator. Finally, the fusion device of the network slice and the edge cloud sends a network request to the target service provider. The embodiment of the application is applied to fusing network slices and edge clouds.
Description
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a fusion method and device of network slices and edge clouds.
Background
Network slicing can provide a fast, secure, efficient network environment for users. The mobile edge computation (mobile edge computing, MEC) of the edge cloud can provide low-latency, efficient services to users. Therefore, the integration of the network slice and the edge cloud can greatly improve the experience of the user.
Currently, the convergence scheme of network slicing and edge cloud is generally to sink network resources and cloud computing capabilities to the network edge. When there is a network request, the edge software defined network (software defined network, SDN) controller (edge SDN controller, ESC) reports the network request and network resources to the radio access network (radio access network, RAN) slice orchestrator (RAN slicing orehestrator, RSO). Then, the RSO realizes the instantiation of the network slice according to the global view of the access network, the network resource and the network request. However, this manner of sinking network resources and cloud computing capabilities of the edge cloud to the user side is vulnerable to attacks, which would be detrimental to the security of the overall network.
Disclosure of Invention
The application provides a method and a device for fusing network slices and edge clouds, which solve the problem of unsafe network caused by sinking network resources and edge clouds to a user side.
In a first aspect, the present application provides a method for fusing a network slice and an edge cloud, which is applied to a device for fusing a network slice and an edge cloud, and the method includes: the fusion device of the network slice and the edge cloud receives the network request and determines an initial service provider according to the service type of the service. And then, determining the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator, and determining a target service provider corresponding to the network request according to the initial service provider, the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator. Finally, the fusion device of the network slice and the edge cloud sends a network request to the target service provider.
Wherein the initial service provider is an edge cloud server or a network slice orchestrator. The target service provider is an edge cloud server or a network slice orchestrator. The network request is for requesting the target service provider to allocate network resources for the service.
In the above scheme, the fusion device of the network slice and the edge cloud acquires the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator, and then determines the target service provider according to the first value, the second value and the initial service provider. Thus, the fusion device of the network slice and the edge cloud only acquires the size of the network resource and has no authority of the network resource. Network resources of the edge network corresponding to the edge cloud server are governed by the edge cloud server, network resources of the access network corresponding to the network slice orchestrator are governed by the network slice orchestrator, and the situation that the network resources are totally sunk to a user side to be distributed is avoided, so that the safety of the network is improved.
Further, the network slice and edge cloud fusion device determines an initial service provider corresponding to the service according to the service type in the network request, and then determines a target service provider according to the first numerical value, the second numerical value and the initial service provider. In this way, the problem that network resources are difficult to be coordinated due to excessive quantity of edge clouds when the network resources are totally sunk to a user side and the edge clouds are utilized for distribution can be avoided.
In a second aspect, the present application provides a fusion device of a network slice and an edge cloud, including: and the acquisition module is used for receiving the network request. And the determining module is used for determining the initial service provider according to the service type of the service. The acquisition module is further used for acquiring the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator. And the determining module is also used for determining a target service provider corresponding to the network request according to the initial service provider, the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator. And the sending module is used for sending the network request to the target service provider.
Wherein the initial service provider is an edge cloud server or a network slice orchestrator. The target service provider is an edge cloud server or a network slice orchestrator. The network request is for requesting the target service provider to allocate network resources for the service.
In a third aspect, the present application provides a fusion device of a network slice and an edge cloud, including a processor, where when the fusion device of a network slice and an edge cloud is running, the processor executes computer-executable instructions to cause the fusion device of a network slice and an edge cloud to perform a fusion method of a network slice and an edge cloud as described above.
In a fourth aspect, the present application provides a computer readable storage medium comprising instructions that when run on a computer cause the computer to perform a method of fusion of network slices and edge clouds as described above.
In a fifth aspect, the present application provides a computer program product comprising instruction code for performing a network slice and edge cloud fusion method as described above.
It should be appreciated that any of the above-mentioned fusion apparatus, computer-readable storage medium or computer program product of network slice and edge cloud is used to perform the above-mentioned method, and thus, the advantages achieved by the method can be referred to as the advantages of the above method and the corresponding solution in the following detailed description, which are not repeated herein.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a prior art fusion system;
FIG. 2 is a schematic diagram of a fusion system according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a fusion system according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram III of a fusion system according to an embodiment of the present application;
fig. 5 is a schematic hardware structure diagram of a fusion device of a network slice and an edge cloud according to an embodiment of the present application;
fig. 6 is a flow chart of a method for fusing network slice and edge cloud according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a fusion device of network slice and edge cloud according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.
Application scenarios of the fifth generation mobile communication technology (5 th-generation, 5G) include strong mobile broadband (enhance mobile broadband, emmbb), mass machine type communication (massive machine type communication, mctc), ultra-high reliability and ultra-low latency communication (ultra-low 1atency communications,uRLLC). The requirements of different application scenarios on network performance are different, and if only a quality of service (quality of service, qoS) scheme for mobile broadband service used in the third generation mobile communication technology (3 rd-generation, 3G)/fourth generation mobile communication technology (4 th-generation, 4G) is adopted, it is difficult to meet the requirements of 5G service on network performance. Therefore, a network slicing technology is introduced into the 5G system, unified management of network resources can be realized, and network resources which are isolated from each other and meet service requirements are allocated for different services. For example, the third generation partnership project (3rd generation partnership project,3GPP) proposes that 5G network slices be divided longitudinally into access network slices, carrier network slices, core network slices, and laterally into eMBB, mMTC, uRLLC slices.
In a conventional network structure, the processing of information is usually located in a data center room at the core network side, that is, service information of a user is transmitted from a network edge to the core network for processing, and then returned to the network edge. This results in an unsecured delay of the traffic. In a 5G system of a multi-application scene, an edge computing technology of edge cloud is introduced in order to adapt to diversified network requirements of different services. The edge computing technology is to deploy equipment such as a gateway, a server and the like in an edge machine room close to a user side, increase computing capacity, process and transmit low-delay service, local data, low-value data and the like in the edge machine room, and return to a core network through a transmission network is not needed. Therefore, the time delay of the service is greatly reduced, the broadband pressure of a transmission network is reduced, the transmission cost is reduced, the content distribution efficiency is improved, and the user experience is improved.
In the 5G intelligent logistics warehouse scenario, there are many services that require a 5G network to ensure the communication quality. For example, in addition to requiring high-definition video, unlike the common video monitoring service, the video monitoring service in the intelligent logistics scene needs low time delay to ensure that the video analysis result is fed back to the scene in time, and meanwhile, the video of the illegal operation part needs to be transmitted to the cloud for storage, so that the edge cloud and the network slice are required to work cooperatively. For another example, large-scale collaborative services of large-scale automated guided vehicles (automated guided vehicles, AGVs) require network slicing to ensure low latency and communication security when planning and scheduling algorithms from the cloud. From the above, it can be seen that the network slice can provide a fast, safe and effective network environment for users. The mobile edge computation (mobile edge computing, MEC) of the edge cloud can provide low-latency, efficient services to users. Therefore, the fusion of the network slice and the edge cloud will greatly improve the user experience.
Currently, the convergence scheme of network slicing and edge cloud is generally to sink network resources and cloud computing capabilities to the network edge. For example, FIG. 1 is a prior art fusion system. As shown in fig. 1, the fusion system includes a cloud server 101, a central cloud 102, a base station 103, a terminal 104, an RSO 105, and an ESC 106. The terminal 104 is in communication connection with the base station 103, the base station 103 is in communication connection with the central cloud 102, the central cloud 102 is composed of cloud servers 101, the RSO 105 is in communication connection with the central cloud 102, cloud servers 101 in the central cloud 102 are managed, the ESC 106 is in communication connection with the base station 103, and the base station 103 is managed. The base station 103 side adds an edge cloud server to compose an edge cloud (not shown in the figure). In this converged system, network resources and cloud computing capabilities are sunk to the network edge so that when there is a network request, ESC 106 reports the network request and network resources to RSO 105. Then, instantiation of the network slice is implemented by the RSO 105 based on the global view of the access network, the network resources, and the network request. However, this manner of sinking network resources and cloud computing capabilities of the edge cloud to the user side is vulnerable to attacks, which would be detrimental to the security of the overall network. In addition, when the number of edge clouds is too large, this fusion scheme will create a problem that network resource allocation is difficult to coordinate.
Aiming at the problems, the application provides a fusion method and device of network slice and edge cloud, which are applied to a 5G intelligent logistics storage scene, wherein the fusion method comprises the following steps: the fusion device of the network slice and the edge cloud receives the network request and determines an initial service provider of the service according to the service type in the network request. And then, according to the obtained residual network resource quantity of the edge cloud server, the residual network resource quantity of the network slice orchestrator and the initial service provider target service provider, sending a network request to the target service provider so as to facilitate the target service to provide network resources for service allocation. The network resource is prevented from being totally sunk to the user side for distribution, and the security of the network is improved.
The fusion device of the network slice and the edge cloud in the embodiment of the application can be a part of devices in an edge cloud server, for example, a chip system in the edge cloud server; or may be a stand-alone device communicatively coupled to the edge cloud server.
Fig. 2 is a fusion system provided herein. Referring to fig. 2, the fusion system includes a cloud server 101, a central cloud 102, a base station 103, a terminal 104, a network slice orchestrator 201, and an edge cloud server 202. The terminal 104 is in communication connection with the base station 103, the base station 103 is in communication connection with the center cloud 102, and the edge cloud server 202 is in communication connection with the base station 103 to form an edge cloud. The network slice orchestrator 201 is communicatively connected to the central cloud 102, managing cloud servers 101 in the central cloud 102.
The fusion method of the network slice and the edge cloud provided by the embodiment of the application is applied to a fusion system shown in fig. 2, and the fusion system comprises a fusion device of the network slice and the edge cloud and an edge cloud server.
Optionally, in combination with the foregoing description, if the fusion device of the network slice and the edge cloud is a part of the device in the edge cloud server, a structure of a fusion system applied by the fusion method of the network slice and the edge cloud provided in the embodiment of the present application is shown in fig. 3. Referring to fig. 3, the fusion system includes a cloud server 101, a central cloud 102, a base station 103, a terminal 104, a network slice orchestrator 201, and an edge cloud server 301 that contains a fusion device of network slices and edge clouds. The terminal 104 is in communication connection with the base station 103, the base station 103 is in communication connection with the central cloud 102, the edge cloud server 301 including the fusion device of the network slice and the edge cloud is in communication connection with the base station 103, and the edge cloud server 301 including the fusion device of the network slice and the edge cloud is in communication connection with the network slice orchestrator 201.
Optionally, in combination with the foregoing description, if the fusion device of the network slice and the edge cloud is an independent device that establishes a communication connection with the edge cloud server, a structure of a fusion system applied by the fusion method of the network slice and the edge cloud provided in the embodiment of the present application is shown in fig. 4. Referring to fig. 4, the fusion system includes a cloud server 101, a central cloud 102, a base station 103, a terminal 104, a network slice orchestrator 201, an edge cloud server 202, and a fusion device 401 of network slices and edge clouds. The terminal 104 is in communication connection with the base station 103, the base station 103 is in communication connection with the central cloud 102, the base station 103 is in communication connection with the network slice and edge cloud fusion device 401, the network slice and edge cloud fusion device 401 is in communication connection with the edge cloud server 202, and the network slice and edge cloud fusion device 401 is in communication connection with the network slice orchestrator 201.
In particular implementations, the fusion device of the network slice and the edge cloud has components as shown in fig. 5. Fig. 5 is a network slice and edge cloud fusion apparatus provided in an embodiment of the present application, which may include at least one processor 502, where the processor 502 is configured to execute application program codes, so as to implement a network slice and edge cloud fusion method in the present application.
The processor 502 may be a central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in accordance with aspects of the present application.
As shown in fig. 5, the fusion device of the network slice and the edge cloud may further include a memory 503. The memory 503 is used for storing application codes for executing the present application, and is controlled by the processor 502 to execute the present application.
The memory 503 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 (randomaccess memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 503 may be stand alone and coupled to the processor 502 via a bus. Memory 503 may also be integrated with processor 502.
As shown in fig. 5, the network slice and edge cloud fusion device may further comprise a communication interface 501, wherein the communication interface 501, the processor 502, and the memory 503 may be coupled to each other, for example, by a bus 504. The communication interface 501 is used for information interaction with other devices, for example, a fusion device supporting network slicing and edge cloud.
It should be noted that the apparatus structure shown in fig. 5 does not constitute a limitation of the network slice and edge cloud fusion apparatus, and the network slice and edge cloud fusion apparatus may include more or less components than those shown in fig. 5, or may combine some components, or may be a different arrangement of components.
The following describes a method for fusing a network slice and an edge cloud according to an embodiment of the present application with reference to fig. 6 by using the fusion system shown in fig. 2 to fig. 4 and the fusion device for a network slice and an edge cloud shown in fig. 5.
Fig. 6 is a flow chart of a method for fusing network slice and edge cloud according to an embodiment of the present application. Referring to fig. 6, the fusion method of the network slice and the edge cloud comprises the following steps.
601. The fusion device of the network slice and the edge cloud receives the network request.
Wherein the network request is for requesting allocation of network resources for the service. The network request includes a service type of the service.
Specifically, the fusion device of the network slice and the edge cloud is arranged on the edge cloud server side close to the network edge, and can acquire the network request sent by the terminal. The network request also comprises QoS parameters of the service, such as time delay, speed, jitter, packet loss rate and the like, and is used for indicating the minimum quality index of the service; capacity parameters of the service, e.g., number of users, user density, etc., for indicating a maximum capacity limit of the service; parameters of the service, such as service type, security index, etc., are used to indicate network selection of the service.
602. The fusion device of the network slice and the edge cloud determines an initial service provider according to the service type of the service, and acquires a first value and a second value.
Wherein the initial service provider is an edge cloud server or a network slice orchestrator. The first value is a remaining network resource amount of the edge cloud server. The second value is the amount of network resources remaining by the network slice orchestrator.
First, the fusion device of the network slice and the edge cloud determines an initial service provider of the service according to the service type of the service.
Specifically, if it is determined that the data of the service needs to be transmitted across domains according to the service type of the service, the network slice orchestrator is determined to be an initial service provider. For example, in a large-scale collaborative service of an AGV with a service being an intelligent logistics scene, data of a path planning and scheduling algorithm is transmitted from a cloud, the service type is a cross-domain type service, and at the moment, a network slice is determined to be needed to ensure low time delay and communication safety of the service, so that a network slice orchestrator is determined to be an initial service provider.
If the data of the service need to be uploaded to the cloud server according to the service type of the service, the network slice orchestrator is determined to be an initial service provider. For example, in a video monitoring service in which the service is an intelligent logistics scene, uploading data of a part of video subjected to illegal operation to a cloud server, and determining that the service type is a service of a cloud type, and determining that network slicing is required to ensure low time delay of the service at the moment, so that a network slicing orchestrator is determined to be an initial service provider.
If the data of the service do not need to be transmitted in a cross-domain mode and the cloud server does not need to be uploaded according to the service type of the service, the edge cloud server is determined to be an initial service provider. For example, in a video monitoring service in which the service is an intelligent logistics scene, a video analysis result is fed back to the site, the service type is a service of a non-cloud and non-cross-domain type, and at the moment, the mobile edge calculation of the edge cloud is required to ensure the low time delay and high efficiency of the service, so that the edge cloud server is determined to be an initial service provider.
Then, the fusion device of the network slice and the edge cloud acquires a first value and a second value. Specifically, the fusion device of the network slice and the edge cloud receives a first value sent by the edge cloud server and a second value sent by the network slice orchestrator.
Optionally, the service provider of the service, namely the edge cloud server or the network slice orchestrator, periodically counts the own residual network resource amount and feeds back to the fusion device of the network slice and the edge cloud.
603. The fusion device of the network slice and the edge cloud determines a target service provider according to the initial service provider, the first numerical value, the second numerical value and a preset algorithm.
Wherein the target service provider is an edge cloud server or a network slice orchestrator.
Specifically, if the first value is greater than the first threshold and the second value is greater than the second threshold, it is determined that the target service provider is the same as the initial service provider. The first threshold is preset, for example, a default value, or a value rewritten by a manager according to a network resource of the edge cloud server. Similarly, the second threshold is preset, for example, a default value, or a value rewritten by the administrator according to the network resources of the network slice orchestrator. Further specifically, if the first value is greater than the first threshold and the second value is greater than the second threshold, the network resources of the edge cloud server and the network slice orchestrator are considered to be sufficient, and at this time, the initial service provider is determined to be the target service provider, so that services are provided for users, and the service quality is ensured.
And if the first value is smaller than or equal to the first threshold value, or if the second value is smaller than or equal to the second threshold value, determining the target service provider according to a greedy algorithm.
Further specifically, when the first value is less than or equal to the first threshold, determining that the amount of remaining network resources of the edge cloud server is insufficient. At this time, the service applied by a part of the edge cloud server can be transferred to the network slice orchestrator side for adjustment, so that sufficient network resource space is provided for the service, and the service quality is ensured. For example, greedy algorithms may be used to determine which applications of traffic to transfer to the network slice orchestrator side to achieve the best service results.
Similarly, when the second value is less than or equal to the second threshold, then the remaining amount of network resources of the network slice orchestrator is determined to be insufficient. At this time, the service applied by a part of the network slice orchestrator can be transferred to the edge cloud server side for adjustment, so that sufficient network resource space is provided for the service, and the service quality is ensured. For example, a greedy algorithm may be used to determine which application services are to be transferred to the edge cloud server side, so that the best service effect can be achieved.
604. The fusion device of the network slice and the edge cloud sends a network request to the target service provider.
Specifically, the fusion device of the network slice and the edge cloud sends a network request to the target service provider according to the result analyzed in step 603.
Optionally, after receiving the network request, the target service provider, i.e. the edge cloud server or the network slice orchestrator, allocates network resources for the service according to parameters included in the network request, and then counts the amount of remaining network resources of the target service provider, and feeds back to the fusion device of the network slice and the edge cloud.
In the above scheme, the fusion device of the network slice and the edge cloud acquires the residual network resource quantity of the edge cloud server and the residual network resource quantity of the network slice orchestrator, and then determines the target service provider according to the first value, the second value and the initial service provider. Thus, the fusion device of the network slice and the edge cloud only acquires the size of the network resource and has no authority of the network resource. Network resources of the edge network corresponding to the edge cloud server are governed by the edge cloud server, network resources of the access network corresponding to the network slice orchestrator are governed by the network slice orchestrator, and the situation that the network resources are totally sunk to a user side to be distributed is avoided, so that the safety of the network is improved.
Further, the network slice and edge cloud fusion device determines an initial service provider corresponding to the service according to the service type in the network request, and then determines a target service provider according to the first numerical value, the second numerical value and the initial service provider. In this way, the problem that network resources are difficult to be coordinated due to excessive quantity of edge clouds when the network resources are totally sunk to a user side and the edge clouds are utilized for distribution can be avoided.
According to the embodiment of the application, the function modules of the fusion device of the network slice and the edge cloud can be divided according to the embodiment of the method, for example, each function module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.
Fig. 7 shows a possible structural diagram of the fusion device of the network slice and the edge cloud, in the case of dividing the individual functional modules with the corresponding individual functions. As shown in fig. 7, the fusion device of the network slice and the edge cloud includes an acquisition module 71, a determination module 72, and a transmission module 73.
The obtaining module 71 is configured to receive a network request. The network request is for requesting allocation of network resources for the service. The network request includes a service type of the service. For example, referring to fig. 6, the acquisition module 71 is configured to perform step 601. A determining module 72 is configured to determine an initial service provider according to the service type of the service. The initial service provider is an edge cloud server or a network slice orchestrator. For example, referring to FIG. 6, the determination module 72 is configured to perform step 602. The obtaining module 71 is further configured to obtain the first value and the second value. The first value is a remaining network resource amount of the edge cloud server. The second value is the amount of network resources remaining by the network slice orchestrator. The determining module 72 is further configured to determine the target service provider according to the initial service provider, the first value, the second value, and a preset algorithm. The target service provider is an edge cloud server or a network slice orchestrator. For example, referring to FIG. 6, the determination module 72 is also configured to perform step 603. A sending module 73, configured to send a network request to the target service provider determined by the determining module 72. For example, referring to fig. 6, the transmitting module 73 is configured to perform step 604.
Optionally, the determining module 72 is specifically configured to: if the data of the service need to be transmitted in a cross-domain mode according to the service type of the service, the network slice composer is determined to be an initial service provider. Or if the cloud server is required to be uploaded according to the service type of the service, determining that the network slice orchestrator is an initial service provider. Or if the data of the service do not need to be transmitted in a cross-domain mode according to the service type of the service and the cloud server does not need to be uploaded, determining the edge cloud server as an initial service provider.
Optionally, the acquiring module 71 is specifically configured to: and receiving the first numerical value sent by the edge cloud server. A second value sent by the network slice orchestrator is received.
Optionally, the determining module 72 is specifically configured to: if the first value is greater than the first threshold and the second value is greater than the second threshold, then the target service provider is determined to be the same as the initial service provider. And if the first value is smaller than or equal to the first threshold value, or if the second value is smaller than or equal to the second threshold value, determining the target service provider according to a greedy algorithm.
Another embodiment of the present application also provides a computer readable storage medium having instructions stored therein that, when executed on a network slice and edge cloud fusion device, perform the steps in the network slice and edge cloud fusion method of the embodiment shown in fig. 6.
In another embodiment of the present application, there is also provided a computer program product comprising computer-executable instructions stored in a computer-readable storage medium; the processor of the network slice and edge cloud fusion device may read the computer-executable instructions from the computer-readable storage medium, the processor executing the computer-executable instructions causing the network slice and edge cloud fusion device to perform steps in the network slice and edge cloud fusion method of the embodiment shown in fig. 6.
All relevant contents of each step related to the above method embodiment may be cited to the functional descriptions of the corresponding functional modules, and their effects are not described herein.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
Those of ordinary skill in the art will appreciate that the various illustrative modules, units, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software 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 application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative, and for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory), a magnetic disk or an optical disk, etc., which can store program codes.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (8)
1. A method for fusing network slice and edge cloud, comprising:
receiving a network request; the network request is used for requesting to allocate network resources for the service; the network request includes a service type of the service;
determining an initial service provider according to the service type of the service; the initial service provider is an edge cloud server or a network slice orchestrator;
acquiring a first numerical value and a second numerical value; the first value is the residual network resource quantity of the edge cloud server; the second value is the remaining network resource amount of the network slice orchestrator;
if the first value is greater than a first threshold and the second value is greater than a second threshold, determining that the target service provider is the same as the initial service provider; the target service provider is the edge cloud server or the network slice orchestrator;
if the first value is smaller than or equal to a first threshold value, or if the second value is smaller than or equal to a second threshold value, determining the target service provider according to a greedy algorithm;
and sending the network request to the target service provider.
2. The fusion method of claim 1, wherein the determining an initial service provider based on the service type of the service comprises:
if the data of the service need to be transmitted in a cross-domain mode according to the service type of the service, determining that the network slice composer is the initial service provider;
or alternatively, the process may be performed,
if the data of the service need to be uploaded to a cloud server according to the service type of the service, determining that the network slice orchestrator is the initial service provider;
or alternatively, the process may be performed,
and if the data of the service do not need to be transmitted in a cross-domain mode and the cloud server does not need to be uploaded according to the service type of the service, determining the edge cloud server as the initial service provider.
3. The fusion method of claim 1, wherein the obtaining the first value and the second value comprises:
receiving a first numerical value sent by the edge cloud server;
and receiving a second value sent by the network slice orchestrator.
4. A fusion device of a network slice and an edge cloud, comprising:
the acquisition module is used for receiving the network request; the network request is used for requesting to allocate network resources for the service; the network request includes a service type of the service;
a determining module, configured to determine an initial service provider according to a service type of the service; the initial service provider is an edge cloud server or a network slice orchestrator;
the acquisition module is also used for acquiring a first numerical value and a second numerical value; the first value is the residual network resource quantity of the edge cloud server; the second value is the remaining network resource amount of the network slice orchestrator;
the determining module is further configured to determine that the target service provider is the same as the initial service provider if the first value is greater than a first threshold and the second value is greater than a second threshold; the target service provider is the edge cloud server or the network slice orchestrator;
the determining module is further configured to determine, according to a greedy algorithm, the target service provider if the first value is less than or equal to a first threshold value, or if the second value is less than or equal to a second threshold value;
and the sending module is used for sending the network request to the target service provider determined by the determining module.
5. The fusion device of claim 4, wherein the determination module is specifically configured to:
if the data of the service need to be transmitted in a cross-domain mode according to the service type of the service, determining that the network slice composer is the initial service provider;
or alternatively, the process may be performed,
if the data of the service need to be uploaded to a cloud server according to the service type of the service, determining that the network slice orchestrator is the initial service provider;
or alternatively, the process may be performed,
and if the data of the service do not need to be transmitted in a cross-domain mode and the cloud server does not need to be uploaded according to the service type of the service, determining the edge cloud server as the initial service provider.
6. The fusion device of claim 4, wherein the acquisition module is specifically configured to:
receiving a first numerical value sent by the edge cloud server;
and receiving a second value sent by the network slice orchestrator.
7. A network slice and edge cloud fusion device comprising a processor that, when run, executes computer-executable instructions to cause the network slice and edge cloud fusion device to perform the network slice and edge cloud fusion method of any of claims 1-3.
8. A computer-readable storage medium comprising instructions that, when run on a computer, cause the computer to perform the network slice and edge cloud fusion method of any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010689176.8A CN114024855B (en) | 2020-07-16 | 2020-07-16 | Fusion method and device of network slice and edge cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010689176.8A CN114024855B (en) | 2020-07-16 | 2020-07-16 | Fusion method and device of network slice and edge cloud |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114024855A CN114024855A (en) | 2022-02-08 |
| CN114024855B true CN114024855B (en) | 2023-05-30 |
Family
ID=80053988
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010689176.8A Active CN114024855B (en) | 2020-07-16 | 2020-07-16 | Fusion method and device of network slice and edge cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114024855B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114900860B (en) * | 2022-05-05 | 2024-04-02 | 中国联合网络通信集团有限公司 | Edge computing method and device for mobile terminal, edge computing server and medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9471391B1 (en) * | 2013-11-20 | 2016-10-18 | Google Inc. | Aggregating resource requests |
| CN107404733A (en) * | 2017-08-22 | 2017-11-28 | 山东省计算中心（国家超级计算济南中心） | A kind of 5G method of mobile communication and system based on MEC and layering SDN |
| CN108770016A (en) * | 2018-06-04 | 2018-11-06 | 北京邮电大学 | 5G end to end network slice generation method based on template and device |
| CN109219020A (en) * | 2018-09-14 | 2019-01-15 | 云迅智能科技南京有限公司 | A kind of network dicing method and system |
| CN109644143A (en) * | 2016-09-09 | 2019-04-16 | 华为技术有限公司 | Method and apparatus for network slice |
| CN109640348A (en) * | 2019-01-08 | 2019-04-16 | 中国联合网络通信集团有限公司 | The multi-service MEC network architecture, the processing method and processing device of multi-service data flow |
| CN110198555A (en) * | 2019-05-21 | 2019-09-03 | 中国联合网络通信集团有限公司 | A kind of configuration method and device of network slice |
| CN110401572A (en) * | 2019-09-04 | 2019-11-01 | 中国联合网络通信集团有限公司 | Network end-to-end arranging service system and method |
| CN111083744A (en) * | 2019-12-31 | 2020-04-28 | 北京思特奇信息技术股份有限公司 | Network slicing method, device, storage medium and equipment |
| CN111082997A (en) * | 2019-12-30 | 2020-04-28 | 西安电子科技大学 | Network function arrangement method based on service identification in mobile edge computing platform |
-
2020
- 2020-07-16 CN CN202010689176.8A patent/CN114024855B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9471391B1 (en) * | 2013-11-20 | 2016-10-18 | Google Inc. | Aggregating resource requests |
| CN109644143A (en) * | 2016-09-09 | 2019-04-16 | 华为技术有限公司 | Method and apparatus for network slice |
| CN109743893A (en) * | 2016-09-09 | 2019-05-10 | 华为技术有限公司 | Method and apparatus for network slice |
| CN107404733A (en) * | 2017-08-22 | 2017-11-28 | 山东省计算中心（国家超级计算济南中心） | A kind of 5G method of mobile communication and system based on MEC and layering SDN |
| CN108770016A (en) * | 2018-06-04 | 2018-11-06 | 北京邮电大学 | 5G end to end network slice generation method based on template and device |
| CN109219020A (en) * | 2018-09-14 | 2019-01-15 | 云迅智能科技南京有限公司 | A kind of network dicing method and system |
| CN109640348A (en) * | 2019-01-08 | 2019-04-16 | 中国联合网络通信集团有限公司 | The multi-service MEC network architecture, the processing method and processing device of multi-service data flow |
| CN110198555A (en) * | 2019-05-21 | 2019-09-03 | 中国联合网络通信集团有限公司 | A kind of configuration method and device of network slice |
| CN110401572A (en) * | 2019-09-04 | 2019-11-01 | 中国联合网络通信集团有限公司 | Network end-to-end arranging service system and method |
| CN111082997A (en) * | 2019-12-30 | 2020-04-28 | 西安电子科技大学 | Network function arrangement method based on service identification in mobile edge computing platform |
| CN111083744A (en) * | 2019-12-31 | 2020-04-28 | 北京思特奇信息技术股份有限公司 | Network slicing method, device, storage medium and equipment |
Non-Patent Citations (2)
| Title |
|---|
| 5G边缘计算和网络切片技术;项弘禹;肖扬文;张贤;朴竹颖;彭木根;;电信科学(第06期);全文 * |
| 基于SDN的网络切片资源映射与编排技术研究;王睿;《中国优秀硕士论文电子期刊网》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114024855A (en) | 2022-02-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11272569B2 (en) | System and method for sharing multi-access edge computing resources in a wireless network | |
| Brik et al. | Service-oriented MEC applications placement in a federated edge cloud architecture | |
| US11894992B2 (en) | Network component management method and network device | |
| US20200213937A1 (en) | Network Slice Instance Processing Method and Apparatus, and System | |
| CN107911850B (en) | Transport network service establishing method and equipment | |
| US20140379928A1 (en) | Method for implementing network using distributed virtual switch, apparatus for performing the same, and network system based on distributed virtual switch | |
| US11902108B2 (en) | Dynamic adaptive network | |
| CN110769468B (en) | Processing method of network slice, access network element and user terminal | |
| EP4247050A1 (en) | Network slice connection method and apparatus, storage medium, and electronic apparatus | |
| CN112543508A (en) | Wireless resource allocation method and network architecture for 5G network slice | |
| CN110912722B (en) | Service resource management method, device, network equipment and readable storage medium | |
| CN110708708A (en) | Wireless resource optimization method and device | |
| CN109379208B (en) | Network object management method and device | |
| CN114024855B (en) | Fusion method and device of network slice and edge cloud | |
| EP3499818B9 (en) | Method and device for load processing | |
| CN107171976B (en) | Method and device for realizing resource reservation | |
| KR102389334B1 (en) | Virtual machine provisioning system and method for cloud service | |
| CN108777857A (en) | A kind of connection control method under URLLC and mMTC coexistence scenarios and system | |
| CN115211159A (en) | Allocation resources of network slices | |
| CN109526032B (en) | Method and device for modifying network slice example | |
| CN113453285B (en) | Resource adjusting method, device and storage medium | |
| CN115176452B (en) | Method and system for data management in a communication network | |
| CN117918013A (en) | Side channel attack against 5G network slices | |
| CN116074784A (en) | Vehicle-mounted data transmission method and device and storage medium | |
| US11432292B2 (en) | Resource allocation method, and network device, terminal device and computer storage medium |
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 |