Slice service processing method, device, network device and readable storage medium

Abstract

The present application provides a method, apparatus, network device, and readable storage medium for slice service processing. The method includes: obtaining, from the received slice service request, the service requirements of the specified service carried in the slice service request; obtaining slice resource usage information from the data analysis server, and obtaining the resource capacity information of the relevant slice instance of the slice service request from the slice manager; determining the current available resource information of the relevant slice instance according to the obtained slice resource usage information and the resource capacity information of the relevant slice instance; performing a requirement matching between the service requirements and the current available resource information of the relevant slice instance, so as to process the slice service request according to the requirement matching result.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to a method, apparatus, network device, and readable storage medium for slice service processing. Background Art

[0002] The network slice instance (NSI) of the 5th Generation Wireless Systems (5G) can be understood as cutting a physical network into multiple virtual end-to-end networks according to different service-level agreement (SLA) requirements such as bandwidth and latency. The networks are logically independent of each other, and any failure or abnormality in one virtual network will not affect other virtual networks.

[0003] For a set of physical networks, the capabilities are fixed. Within the limited capabilities, unreasonable service segmentation of slice instances will lead to a large waste of resources and relatively high operating costs. Summary of the Invention

[0004] This application provides a method, apparatus, network device, and readable storage medium for slice service processing.

[0005] An embodiment of this application provides a method for slice service processing, including: obtaining the service requirements of a specified service carried in a received slice service request from the slice service request; obtaining slice resource usage information from a data analysis server, and obtaining the resource capability information of a relevant slice instance of the slice service request from a slice manager; determining the current available resource information of the relevant slice instance according to the obtained slice resource usage information and the resource capability information of the relevant slice instance; and performing a demand match between the service requirements and the current available resource information of the relevant slice instance, so as to process the slice service request according to the demand match result.

[0006] An embodiment of this application provides a slice service processing apparatus, including: a service requirement obtaining module, configured to obtain the service requirements of a specified service carried in a received slice service request from the slice service request; a resource information obtaining module, configured to obtain slice resource usage information from a data analysis server, and obtain the resource capability information of a relevant slice instance of the slice service request from a slice manager; an available resource calculation module, configured to determine the current available resource information of the relevant slice instance according to the obtained slice resource usage information and the resource capability information of the relevant slice instance; and a match result processing module, configured to perform a demand match between the service requirements and the current available resource information of the relevant slice instance, so as to process the slice service request according to the demand match result.

[0007] An embodiment of the present application provides a network device, including: one or more processors; a memory storing one or more programs, which when executed by the one or more processors, cause the one or more processors to implement any one of the slice service processing methods in the embodiments of the present application.

[0008] An embodiment of the present application provides a readable storage medium storing a computer program, which when executed by a processor, implements any one of the slice service processing methods in the embodiments of the present application.

[0009] According to the slice service processing method, device, network device, and readable storage medium of the embodiments of the present application, according to the service requirements in the received slice service request, obtain slice resource usage information from the data analysis server, and obtain the resource capacity information of the slice instance related to the slice service request from the slice manager, so as to determine the current available resource information of the relevant slice instance. When processing the slice service request, after matching the service requirements with the current available resources, process the slice service request according to the result of the requirement matching, thereby helping the operator solve the waste of physical network resources under unreasonable service opening and deployment, and assisting the operator to achieve the goal of the most reasonable utilization of physical network resources.

[0010] More descriptions are provided in the accompanying drawings, specific implementation manners, and claims regarding the above embodiments and other aspects of the present application and their implementation manners. Description of the Drawings

[0011] Figure 1 A schematic network architecture diagram showing the slice model association relationship of the embodiments of the present application.

[0012] Figure 2 A schematic diagram showing the bandwidth requirements of different users in an exemplary embodiment of the present application.

[0013] Figure 3 A schematic diagram showing the services and functions that the management data analysis MDA service can provide.

[0014] Figure 4 A schematic flowchart showing the slice service processing method of the embodiments of the present application.

[0015] Figure 5 A detailed flowchart showing the slice service processing method of another embodiment of the present application.

[0016] Figure 6 A schematic diagram showing the processing timing of the service opening feasibility check request in the embodiments of the present application

[0017] Figure 7 A schematic diagram showing the processing timing of the slice service opening request in the embodiments of the present application.

[0018] Figure 8 The structural schematic diagram of the slice service processing device provided by an embodiment of the present invention is shown.

[0019] Figure 9 It is a structural diagram showing an exemplary hardware architecture of a computing device capable of implementing the methods and devices according to the embodiments of the present invention. Detailed implementation manners

[0020] To make the objectives, technical solutions and advantages of the present application clearer and more understandable, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments may be combined arbitrarily with each other.

[0021] In the embodiments of the present application, a network slice instance may be a logically running network that can meet certain network characteristics or service requirements. A network slice instance may provide one or more network services (NS). A network slice instance may be created by a network management system. A network management system may create multiple network slice instances and manage them simultaneously, including performance monitoring, fault management, modification, etc. during the running process of the network slice instance. A complete network slice instance may provide a complete end-to-end network service. What composes a network slice instance may be at least one of a network slice subnet instance (NSSI) and a network function (NF).

[0022] The 3rd Generation Partnerships Project (3GPP) standardization organization has also put forward requirements and specifications for 5G communication networks. In terms of the management domain, three new logical management units are added in the standard: the Communication Service Management Function (CSMF), the Network Slice Management Function (NSMF), and the Network Slice Subnet (abbreviated as sub-slice) Management Function (NSSMF).

[0023] Figure 1 The schematic diagram of the network architecture showing the correlation relationship of the slice model in the embodiments of the present application. In Figure 1Among them, the network architecture includes a CSMF entity 10, an NSMF entity 11, and an NSSMF entity 12. The CSMF entity 10 is located at the communication service provider (Network Operator, NOP), and the NSMF entity 11 and the NSSMF entity 12 are located at the network operator (Network Operator, NOP).

[0024] It should be noted that the number of CSMF entities, NSMF entities, and NSSMF entities included in the network architecture is not limited to Figure 1 As shown, in actual applications, there may be multiple CSMF entities, multiple NSMF entities, and multiple NSSMF entities. It should be noted that the above three management entities may be described by other names, and the embodiments of this application do not make any limitations in this regard.

[0025] In Figure 1 Among them, the CSMF entity 10 can be used to convert the communication service requirements of the operator and / or third-party customers into requirements for the network or network slices; send requests for network slices (such as create, terminate, modify network slice instance requests, etc.) to the NSMF 11 entity through the interface with the NSMF 11 entity; obtain management data of the network slice (such as performance, fault data, etc.) from the NSMF 11 entity; generate management data of the communication services running on the network slice instance; receive subscription requirements of the operator and / or third-party customers for the management data of the network slice and / or the management data of the communication services, etc.

[0026] The NSMF 11 entity can be used to receive the network slice requirements sent by the CSMF entity 10; manage the life cycle, performance, faults, etc. of the network slice instance; orchestrate the composition of the network slice instance; decompose the requirements of the network slice instance into the requirements of each network slice subnet instance and / or network function; send network slice subnet instance management requests to each NSSMF entity 12, etc.

[0027] The NSSMF entity 12 can be used to receive the network slice subnet requirements sent by the NSMF 11 entity; manage the network slice subnet instance; orchestrate the composition of the sub-network slice instance; decompose the requirements of the network slice subnet instance into the requirements of each network function and / or nested network slice subnet instance; may send nested network slice subnet instance management requests to other NSSMF entities 12, etc.

[0028] In Figure 1In this context, a network slice, as a complete logical network, can provide a set of network functions (NFs) and corresponding resources necessary for certain network capabilities and network characteristics. A network slice includes an access network (AN) and a core network (CN). Correspondingly, the network functions provided by the network slice 13 can include: core network functions (CNFs) 1301 and access network functions (ANFs) 1302. That is to say, a network slice instance can be defined as the instantiation of a network slice, namely a set of deployed network functions that provide the expected network slice services.

[0029] Continuing to refer to Figure 1 , in Figure 1 the relationship between the slice management system and the corresponding management objects is also shown. As an example, the management object of the CSMF entity 10 is a communication service (not shown in the figure), and each communication service is completed by one or more network slice functions. As Figure 1 shown in "Managed Network Slice" in Figure 1 , the management object of the NSMF entity 11 is a network slice, and each network slice can be composed of zero or one or more network slice subnets. As Figure 1 shown in "Managed Network Slice Subnet" in

[0030] In the embodiment of the present application, 5G network application scenarios are divided into three categories: Ultra Reliable & Low Latency Communication (uRLLC) network, Enhanced Mobile Broadband (eMBB) network, Massive Machine Type of Communication (mMTC) network, etc. With the gradual construction and commercial use of 5G, each scenario gradually has its own commercial industry applications. Visible applications include virtual reality (VR), augmented reality (AR), ultra-high-definition video, Internet of Vehicles, networked drones, and so on.

[0031] Different business needs have different requirements for resources. On a physical network, it is divided into different isolated virtual networks. For operators, building a physical network is a process that requires a lot of investment and continuous investment, including subsequent operating costs. The country has also clearly put forward energy-saving and emission-reduction requirements for operators. For a physical network, the capacity is fixed. Within the limited capacity range, unreasonable business segmentation of slice instances will lead to a large waste of resources.

[0032] Figure 2 FIG. 2 is a schematic diagram showing bandwidth requirements of different users in an exemplary embodiment of the present application. Figure 2 As shown, for example, if a park is preparing to build and launch end-to-end eMBB 5G services, three users in the park need to use it to support their own services. Figure 2 For example, the bandwidth requirements of three users are 900M, 800M, and 800M, respectively. The current requirement only takes bandwidth as an example, and the maximum bandwidth capability of the end-to-end eMBB service is 1G.

[0033] To meet peak demand, the park needs to create three physical networks for these three services to meet everyone's needs at the same time. Figure 2 It can be seen that services have different real needs at different time points. Although the needs during peak hours are met, there is a lot of resource waste during non-peak hours. Therefore, to avoid resource waste, a more reasonable service provisioning method is that service 1 occupies one physical network exclusively, but because the peak and trough times are inconsistent, services 2 and 3 can share one physical network. In fact, only two physical networks need to be built, which can save one set of resources and avoid resource waste.

[0034] In 3GPP's 28.809 protocol, for slice operation and maintenance, it is proposed to utilize the services and functions of Management Data Analytics (MDA). MDA plays the role of Analytics in the management cycle.

[0035] Figure 3 The figure shows the schematic diagram of the services and functions that the Management Data Analytics (MDA) service can provide. As Figure 3 shown, the MDA service can classify and correlate data such as current resource usage data and historical resource usage data based on SLA, learn and identify data patterns, and perform data Observation, Analytics to obtain inferences, insights and predictions, so as to make decisions (Decision) and execute (Execution).

[0036] The embodiment of this application proposes a way to improve the utilization rate of slice resources. By leveraging the capabilities of MDA and through more refined analysis of resources, when slice services are launched or during the integrated governance after launch, existing resources are maximally utilized. Avoiding fragmentation and waste of slice resources helps operators reduce the construction of physical networks and lower operating costs. At the same time, it achieves the goal of energy conservation and emission reduction.

[0037] Figure 4 The figure shows the schematic flow diagram of the slice service processing method according to the embodiment of this application. As Figure 1 shown, the slice service processing method in the embodiment of this application may include the following steps.

[0038] S110, obtain the service requirements of the specified service carried in the slice service request from the received slice service request.

[0039] S120, obtain the slice resource usage information from the data analysis server, and obtain the resource capacity information of the relevant slice instance of the slice service request from the slice manager.

[0040] S130, determine the current available resource information of the relevant slice instance according to the obtained slice resource usage information and the resource capacity information of the relevant slice instance.

[0041] S140, perform demand matching between the service requirements and the current available resource information of the relevant slice instance, so as to process the slice service request according to the demand matching result.

[0042] According to the slice service processing method of the embodiments of the present application, when a slice service request is received, according to the service requirements carried in the service operation request, obtain slice resource usage information from the data analysis server, and obtain resource capability information of relevant slice instances from the slice manager, calculate the current available resource information of the relevant slice instances, and thus process the slice service request according to the matching result of the service requirements and the current available resource information of the relevant slice instances. This method can combine the analysis ability of MDA, and according to the matching result of the service requirements and the current available resource information of the relevant slice instances, perform the processing of slice services, thereby helping the operator to solve the waste of physical network resources under unreasonable service opening and deployment, and assisting the operator to achieve the goal of the most reasonable utilization of physical network resources.

[0043] In one embodiment, the slice service request in step S110 may include a slice service feasibility check request and a slice service activation request.

[0044] In one embodiment, the data analysis server in step S120 can be understood as a network element capable of providing Management Data Analytics Service (MDAS). The slice resource usage information obtained from the data analysis server is the network data model information of the resource usage situation of the services carried by multiple slice instances managed by the slice manager according to the predetermined resource usage performance indicators; and the obtained slice resource usage information includes: the network data model information of the actual resources used by each running service in the corresponding slice instance, and the network data model information includes but is not limited to the resource usage period, resource usage amount, and stickiness value.

[0045] In one embodiment, the data analysis server can collect and analyze two types of resources. One type is to collect the usage situation of the actual resource indicators on the slice instance, and the other type is to collect the usage situation of the actual resource indicators of each running service.

[0046] Among them, the resource information collected on the slice instance according to the actual resource indicators includes but is not limited to bandwidth, the number of access users, etc. The collected resource data can be used to extract the total service actual resource usage model information carried by the resources periodically; the resource information collected according to the actual resource indicators of each running service includes but is not limited to bandwidth, the number of access users, etc. The collected data is used to extract the periodic actual resource usage model information of specific services. As an example, the above periodic resource usage model information can be resource usage model information with time periods such as hours, days, weeks, and holidays.

[0047] In this embodiment, the data analysis server can utilize the collected data to perform big data analysis on the data, and extract the overall resource model of the services carried by the slice instances and the actual resource models used by each service. Therefore, the in-use network model data corresponding to each slice instance and the unused network model data corresponding to each slice instance can be obtained from the data analysis server.

[0048] In one embodiment, if the slice service request is a slice service feasibility check request, the slice service request further carries the identification information of the specified slice instance, and the relevant slice instance is the specified slice instance.

[0049] In this embodiment, step S140 may specifically include: S11, if the matching result is that the current available resource information of the specified slice instance can meet the service requirements, generate an authentication success response message as the processing result of the slice service feasibility check request; S12, if the matching result is that the current available resource information cannot meet the service requirements, generate an authentication failure response message as the processing result of the slice service feasibility check request.

[0050] Through the above steps S11 - S12, it is possible to perform service authentication in the service activation scenario of the specified slice instance when processing the slice service feasibility check request.

[0051] In one embodiment, after step S12, the method further includes: S13, send an authentication success response message to the slice manager, and carry the instance information of the specified slice instance in the authentication success response message.

[0052] In this embodiment, when the authentication is successful, an authentication success response message can be returned to the slice management server, and when the resources are satisfied, the instance information that currently meets the requirements can also be returned in this response message.

[0053] In one embodiment, if the slice service request is a slice service activation request, the relevant slice instances are multiple slice instances managed by the slice manager.

[0054] In this embodiment, step S140 may specifically include: S21, perform requirement matching between the service requirements and the current available resource information of multiple slice instances to obtain the slice instances that can meet the service requirements; S22, select the slice instances that meet the predetermined preference conditions from the slice instances that can meet the service requirements as the processing result of the slice service activation request.

[0055] In one embodiment, the slice instances that meet the predetermined preference conditions include: the slice instances that can meet the service requirements and whose current available resource information is closest to the service requirements.

[0056] In this embodiment, it is possible to perform requirement matching according to the specified slice example and service requirements in the received slice service activation request, and optimize the instances that meet the service requirements.

[0057] In one embodiment, after step S22, the slice service processing method may further include: S23, sending the instance information of the slice instance that meets the predetermined optimization conditions to the slice manager.

[0058] In one embodiment, if there is no slice instance that can meet the service requirements, or no slice instance that meets the predetermined optimization conditions is selected, the slice service processing method further includes: S24, sending a selection failure indication message to indicate that there is currently no slice instance that can carry the service requirements of the specified service.

[0059] In this embodiment, when there is an optimal instance, the slice instance information can be returned to the slice manager; when no instance that can meet the requirements is matched, a selection failure indication message is returned.

[0060] Figure 5 The detailed flowchart of the slice service processing method showing another embodiment of the present application is as follows Figure 5 As shown, the service intelligent selection system can be used to implement the slice service processing method of the embodiments of the present application. In some embodiments, the slice service processing method may include the following steps.

[0061] S201, the data analysis server collects and analyzes the total service actual resource usage information and each service actual resource usage information on the slice instance.

[0062] In this step, the data analysis server can collect the resource usage corresponding to the actual resource metrics on the slice instance, and extract the periodic actual resource usage model information of the total service carried on the slice instance from it; the data analysis server can also collect the resource usage corresponding to the actual resource metrics of each running service, and extract the periodic actual resource usage model information of each service carried on the slice instance from it.

[0063] S202, the slice manager receives a slice service request, and this request carries the service requirement information of this service.

[0064] In this step, the received slice service request includes a slice service activation request or an instance availability check request received from other systems, and the request carries the requirement information of this service. For example, the slice service activation request or the instance availability check request received from other systems can be requests initiated by users or external systems.

[0065] In S203, the service intelligence selection system obtains the actual resource usage model information on each slice instance from the data analysis server, and obtains the capability information of this slice instance from the slice manager.

[0066] In this step, obtain the actual used resource model information from the data analysis server, such as the MDAS service. Table 1 below shows the currently obtained actual used resource model information table with the resource type being bandwidth as an example in the embodiments of the present application.

[0067] Table 1 Current actual used bandwidth resource model information table corresponding to the slice instance

[0068] Actual Used Bandwidth (bits / second) Period Viscosity Value Actual Used Bandwidth Upstream: 50M 9:00～18:00 10M Actual Used Bandwidth Upstream: 10M 18:00～9:00 2M Actual Used Bandwidth Downstream: 350M 9:00～18:00 50M Actual Used Bandwidth Downstream: 600M 18:00～23:00 100M Actual Used Bandwidth Downstream: 200M 23:00～9:00 10M

[0069] In this step, as an example, obtain the capability information of this slice instance from the slice manager. Currently, taking bandwidth as an example, for example, it is obtained that the bandwidth capacity carried by the slice instance (physical network) is 1G.

[0070] In S204, the service intelligence selection system calculates the actual remaining resources according to the resource capabilities that the slice example can carry.

[0071] Table 2 below shows the actually remaining resource model information table calculated with the resource type being bandwidth as an example in the embodiments of the present application.

[0072] Table 2 Current actually remaining bandwidth resource model information table corresponding to the slice example

[0073] Available Bandwidth Resource (bits / second) Period Available Bandwidth Upstream: 950M 9:00～18:00 Available Bandwidth Upstream: 990M 18:00～9:00 Available Bandwidth Downstream: 650M 9:00～18:00 Available Bandwidth Downstream: 400M 18:00～23:00 Available Bandwidth Downstream: 800M 23:00～9:00

[0074] In S205, the service intelligence selection system calculates whether the currently available resources can meet the existing service requirements according to the requirement information of this service.

[0075] In the above example, in the requirement of this service, the available bandwidth downlink peak period is from 20:00 to 22:00, and the service requirement bandwidth is 700M. Then the calculation result is that the current slice instance cannot meet the service requirements of this service; if the available bandwidth downlink peak period is from 00:00 to 08:00 and the required bandwidth is 700M, then the current slice instance can meet the service requirements of this service.

[0076] In S206, the service intelligence selection system returns the selection result to the request initiator.

[0077] Through the slice service processing method of the embodiments of the present application, through the analysis and modeling capabilities of MDAS for the actual used resources, the service intelligence selection module provides service intelligence matching calculation capabilities, combines with service requirements, performs availability checks on the instances, and calculates and selects available slice instances that meet the requirements, thereby effectively solving the problems of slice instance resource fragmentation and insufficient resource utilization.

[0078] In order to better understand this application, Figure 6 and Figure 7 , describes the processing process of a slice service feasibility check request for a specified slice instance in an embodiment of the present application, and the processing process of a slice service network request for a slice service activation request for an unspecified slice instance.

[0079] Figure 6 FIG. 2 is a schematic diagram showing a processing sequence of a request for checking the feasibility of provisioning according to an embodiment of the present application. Figure 6 As shown, in one embodiment, the processing of the provisioning feasibility check request may include the following steps.

[0080] S301, the user or external system specifies the slice instance through the slice manager and enters the business requirements to perform a feasibility check on the slice service activation.

[0081] S302, the slice manager sends a request to the business intelligent selection module, carrying the slice instance and detailed business requirement information.

[0082] S303-01, after receiving the request, the business intelligent selection system initiates a request to the data analysis server to obtain detailed information about the network data models in use and the network data models not in use.

[0083] S303-02, the data analysis server returns detailed information about the network data models in use and the network data models that are not in use.

[0084] S303-03, the business intelligent selection system sends a request to the slice manager to obtain the corresponding slice instance capability information based on the slice instance information carried.

[0085] S303-04, the business intelligence selection system receives the capability data supported by the current slice instance sent by the slice manager.

[0086] S304, the business intelligent selection system calculates the current available resources, and performs an availability check on the slice instance based on the business demand information in the previously received request to determine whether the resources of the slice instance meet the business demand.

[0087] S305-01, when the resources of the slice instance meet the business requirements, an authentication success response message is returned.

[0088] In this step, the instance information that currently meets the requirements may also be carried in the authentication success response message.

[0089] S305-02: When the resources of the slice instance do not meet the business requirements, an authentication failure response message is returned.

[0090] In S306, after the slicing manager receives the authentication success response message, it can continue to activate services on the specified slice instance.

[0091] In S307, after the slicing manager receives the authentication failure response message, it prompts the user that the corresponding service cannot be activated on the specified slice instance.

[0092] Through the processing of the activation feasibility check request in this embodiment, service authentication can be performed in the service activation scenario of the specified slice instance in combination with the actual resource usage situation.

[0093] Figure 7 The timing diagram of the processing of the slice service activation request according to the embodiment of the present application is shown. As Figure 7 shown, in one embodiment, the processing of the slice service activation request may include the following steps.

[0094] In S401, the slicing manager receives a slice service activation request from a user or an external system, and service requirement information is carried in the slice service activation request.

[0095] In S402, the slicing manager sends the slice service activation request to the service intelligent selection system and carries the service requirement information.

[0096] In S403-01, after receiving the slice service activation request, the service intelligent selection system sends a request to the MDAS to obtain the detailed network data model in use and the unused network data model.

[0097] In S403-02, the data analysis server returns the detailed network data model information in use and the unused network data model information.

[0098] In S403-03, the service intelligent selection system sends a request for slice instance capability information to the slicing manager.

[0099] In S403-04, the service intelligent selection system receives the capability data supported by the current slice instance sent by the slicing manager.

[0100] In S404, the service intelligent selection system calculates the current available resource situation, and based on the service requirement information in the previously received request, optimally selects the slice instances that meet the service requirements.

[0101] In this step, the conditions for optimal selection include: being able to meet the service requirements and the current available resource information being closest to the specified service requirements.

[0102] In S405-01, when there is an optimal instance, the slice instance information is returned;

[0103] S405-02, when no instance that can meet the requirements is matched, return a slice instance failure message.

[0104] S406, after the slice manager receives the slice instance information, initiate service creation, activation, and configuration distribution for the slice instance.

[0105] S407, after the slice manager receives the selection failure information, prompt the user that there is currently no instance that can carry the current service requirements, and a complete end-to-end slice instance needs to be newly created.

[0106] Through the processing of the slice service activation request in this embodiment, in combination with the actual resource usage situation, in the case of not specifying a slice instance, intelligent selection of slice instances for service activation in a multi-slice instance scenario can be achieved.

[0107] According to the slice service processing method of the embodiment of the present application, in combination with the actual resource usage situation, as many services as possible can be deployed under limited resources. During the process of slice instance feasibility check or intelligent selection of slice instances, high resource utilization can be ensured, effectively solving the problems of slice instance resource fragmentation and insufficient resource utilization, and assisting the operator to achieve the goal of the most reasonable utilization of physical network resources.

[0108] Next, in combination with the accompanying drawings, the slice service processing device according to the embodiment of the present invention will be introduced in detail. Figure 8 The structural schematic diagram of the slice service processing device provided by an embodiment of the present invention is shown. As Figure 8 shown, the slice service processing device may include the following modules.

[0109] The service requirement acquisition module 510 is used to acquire the service requirements of the specified service carried in the slice service request from the received slice service request.

[0110] The resource information acquisition module 520 is used to acquire slice resource usage information from the data analysis server and acquire the resource capacity information of the relevant slice instance of the slice service request from the slice manager.

[0111] The available resource calculation module 530 is used to determine the current available resource information of the relevant slice instance according to the acquired slice resource usage information and the resource capacity information of the relevant slice instance.

[0112] The matching result processing module 540 is used to perform requirement matching between the service requirements and the current available resource information of the relevant slice instance, so as to process the slice service request according to the requirement matching result.

[0113] The slice service processing device according to the embodiment of the present application can obtain slice resource usage information from the data analysis server according to the service requirements in the received slice service request, and obtain the resource capability information of the slice instance related to the slice service request from the slice manager, so as to determine the current available resource information of the relevant slice instance. When processing the slice service request, after matching the service requirements with the current available resources, the slice service request is processed according to the result of the requirement matching, thereby helping the operator solve the waste of physical network resources under unreasonable service opening and deployment, and assisting the operator to achieve the goal of the most reasonable utilization of physical network resources.

[0114] In one embodiment, if the slice service request is a slice service feasibility check request, the slice service request further carries the identification information of the specified slice instance, and the relevant slice instance is the specified slice instance.

[0115] In this embodiment, the matching result processing module 540 may specifically include: an authentication success response generation module, configured to generate an authentication success response message as the processing result of the slice service feasibility check request if the matching result is that the current available resource information of the specified slice instance can meet the service requirements; an authentication failure response generation module, configured to generate an authentication failure response message as the processing result of the slice service feasibility check request if the matching result is that the current available resource information cannot meet the service requirements.

[0116] In one embodiment, the slice service processing device may further include: an authentication success response sending module, configured to send an authentication success response message to the slice manager and carry the instance information of the specified slice instance in the authentication success response message.

[0117] In one embodiment, if the slice service request is a slice service opening request, the relevant slice instances are multiple slice instances managed by the slice manager. In this embodiment, the matching result processing module 540 may specifically include: a slice instance determination module, configured to perform requirement matching between the service requirements and the current available resource information of the multiple slice instances to obtain a slice instance that can meet the service requirements; a slice instance preference module, configured to select a slice instance that meets the predetermined preference conditions from the slice instances that can meet the service requirements as the processing result of the slice service opening request.

[0118] In one embodiment, the slice service processing device may further include: an instance information sending module, configured to send the instance information of the slice instance that meets the predetermined preference conditions to the slice manager.

[0119] In one embodiment, if there is no slice instance that can meet the service requirements, or no slice instance that meets the predetermined preferred conditions is selected, the slice service processing device may further include: a selection failure indication sending module, configured to send a selection failure indication message to indicate that there is currently no slice instance that can carry the service requirements of the specified service.

[0120] In one embodiment, the slice instances that meet the predetermined preferred conditions include: slice instances that can meet the service requirements and whose current available resource information is closest to the service requirements.

[0121] In one embodiment, the obtained slice resource usage information is the network data model information of the resource usage situation of the services carried by multiple slice instances managed by the slice manager collected by the data analysis server according to the predetermined resource usage performance metrics; and the obtained slice resource usage information includes: the network data model information of the actual resources used by each running service in the corresponding slice instance, and the network data model information includes but is not limited to: resource usage cycle, resource usage amount, and stickiness value.

[0122] The slice service processing device according to the embodiments of the present application can intelligently select a slice instance that can carry the specified service requirements for a slice manager and other systems. Specifically, it can obtain the capability information of the slice instance from the slice manager, and with the existing analysis capabilities of MDAS, through message interaction, obtain the actual resource usage model of the running services. By calculation, it is determined whether the existing slices can meet the service requirements. If there are multiple slice instances that meet the conditions, the slice instance with the highest resource utilization rate is selected, and a notification is returned to the corresponding system, so as to deploy the new service on the existing slice instance as much as possible and ensure the maximum utilization of the slice instance resources.

[0123] It should be clear that the present invention is not limited to the specific configurations and processes described in the above embodiments and shown in the figures. For the convenience and brevity of description, the detailed description of known methods is omitted here, and the specific working processes of the systems, modules, and units described above can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0124] Figure 9 It is a structural diagram showing an exemplary hardware architecture of a computing device capable of implementing the slice service processing method and device according to the embodiments of the present invention.

[0125] Such as Figure 9As shown in the figure, the computing device 600 includes an input device 601, an input interface 602, a central processing unit 603, a memory 604, an output interface 605, and an output device 606. Among them, the input interface 602, the central processing unit 603, the memory 604, and the output interface 605 are interconnected through a bus 610. The input device 601 and the output device 606 are respectively connected to the bus 610 through the input interface 602 and the output interface 605, and then connected to other components of the computing device 600.

[0126] Specifically, the input device 601 receives input information from the outside and transmits the input information to the central processing unit 603 through the input interface 602; the central processing unit 603 processes the input information based on computer-executable instructions stored in the memory 604 to generate output information, stores the output information temporarily or permanently in the memory 604, and then transmits the output information to the output device 606 through the output interface 605; the output device 606 outputs the output information to the outside of the computing device 600 for the user to use.

[0127] In one embodiment, Figure 9 the computing device shown can be implemented as a network device, and the network device may include: a memory configured to store a program; a processor configured to run the program stored in the memory to execute the slice service processing method described in the above embodiment.

[0128] In one embodiment, Figure 9 the computing device shown can be implemented as a service intelligent selection system, and the service intelligent selection system may include: a memory configured to store a program; a processor configured to run the program stored in the memory to execute the slice service processing method described in the above embodiment.

[0129] As described above, it is only an exemplary embodiment of the present application and is not used to limit the protection scope of the present application. Generally, various embodiments of the present application can be implemented in hardware or special circuits, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, a microprocessor, or other computing devices, although the present application is not limited thereto.

[0130] Embodiments of the present application can be implemented by a data processor of a mobile device executing computer program instructions, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0131] Any block diagram of a logical process in the accompanying drawings of the present application may represent a program step, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions. A computer program may be stored in a memory. The memory may have any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory devices and systems (Digital Versatile Disc DVD or CD disc), etc. The computer-readable medium may include a non-transitory storage medium. The data processor may be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0132] By way of illustrative and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adaptations of the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and the claims, without departing from the scope of the invention. Accordingly, the proper scope of the invention will be determined in accordance with the claims.

Claims

1. A method for processing slice services, characterized in that, the method includes: Obtain the service requirements of the specified service carried in the received slice service request from the received slice service request; Obtain slice resource usage information from the data analysis server, and obtain the resource capacity information of the relevant slice instance of the slice service request from the slice manager; Determine the current available resource information of the relevant slice instance according to the obtained slice resource usage information and the resource capacity information of the relevant slice instance; Perform requirement matching between the service requirements and the current available resource information of the relevant slice instance to process the slice service request according to the requirement matching result; The slice resource usage information includes: network data model information of the actual resources used by each running service in the corresponding slice instance, and the network data model information at least includes: resource usage period, resource usage amount, and stickiness value.

2. The method according to claim 1, characterized in that, If the slice service request is a slice service feasibility check request, the slice service request also carries the identification information of the specified slice instance, and the relevant slice instance is the specified slice instance; The performing requirement matching between the service requirements and the current available resource information of the relevant slice instance to process the slice service request according to the requirement matching result includes: If the matching result is that the current available resource information of the specified slice instance can meet the service requirements, generate an authentication success response message as the processing result of the slice service feasibility check request; If the matching result is that the current available resource information cannot meet the service requirements, generate an authentication failure response message as the processing result of the slice service feasibility check request.

3. The method according to claim 2, characterized in that, After generating the authentication success response message, the method further includes: Send the authentication success response message to the slice manager, and carry the instance information of the specified slice instance in the authentication success response message.

4. The method according to any one of claim 1, characterized in that, If the slice service request is a slice service activation request, the relevant slice instance is multiple slice instances managed by the slice manager; The performing requirement matching between the service requirements and the current available resource information of the relevant slice instance to process the slice service request according to the requirement matching result includes: Perform requirement matching between the service requirements and the current available resource information of the multiple slice instances to obtain a slice instance that can meet the service requirements; Select a slice instance that meets the predetermined preferred conditions from the slice instances that can meet the service requirements as the processing result of the slice service activation request.

5. The method according to claim 4, characterized in that, After selecting a slice instance that meets the predetermined preferred conditions as the processing result of the slice service activation request, the method further includes: Send the instance information of the slice instance that meets the predetermined preferred conditions to the slice manager.

6. The method according to claim 4, It is characterized in that if there is no slice instance that can meet the service requirements, or no slice instance that meets the predetermined preferred conditions is selected, the method further includes: sending a selection failure indication message to indicate that there is currently no slice instance that can carry the service requirements of the specified service.

7. The method according to any one of claims 4 to 6, It is characterized in that the slice instance that meets the predetermined preferred conditions includes: a slice instance that can meet the service requirements and the current available resource information is closest to the service requirements.

8. The method according to any one of claims 1 to 6, It is characterized in that the obtained slice resource usage information is the network data model information of the resource usage situation of the services carried by multiple slice instances managed by the slice manager by the data analysis server according to predetermined resource usage performance indicators, and is the resource usage situation of each slice instance carried by the service.

9. A slice service processing device, It is characterized in that the device includes: a service requirement acquisition module, configured to acquire the service requirements of the specified service carried by the slice service request from the received slice service request; a resource information acquisition module, configured to acquire slice resource usage information from the data analysis server and acquire the resource capability information of the relevant slice instance of the slice service request from the slice manager; an available resource calculation module, configured to determine the current available resource information of the relevant slice instance according to the obtained slice resource usage information and the resource capability information of the relevant slice instance; a matching result processing module, configured to perform demand matching between the service requirements and the current available resource information of the relevant slice instance, and process the slice service request according to the demand matching result; the slice resource usage information includes: the network data model information of the actual resources used by each running service in the corresponding slice instance, and the network data model information at least includes: resource usage period, resource usage amount, and stickiness value.

10. A network device, including: one or more processors; a memory, on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the slice service processing method according to any one of claims 1-8.

11. A computer-readable storage medium, It is characterized in that the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the slice service processing method according to any one of claims 1-8.

Images