Network slice operation and maintenance method, device, system and storage medium

Abstract

The embodiment of the application provides a network slice operation and maintenance method, device, system and storage medium, wherein the method comprises the following steps: selecting a pre-deployed network slice according to a communication service request; allocating functions and resources of the network slice based on communication state information and communication process information in a network domain, wherein the network domain comprises at least one network; collecting performance indicators of the network slice, and guaranteeing a service level agreement of the network slice according to the performance indicators. The embodiment of the application realizes real-time monitoring of the quality of service of the network slice by uniformly managing the network slice through information across the network domain, and adjusts the network slice to meet the corresponding service level agreement based on the running performance indicators of the network slice, thereby improving the security of the network slice operation.

Description

Technical Field

[0001] This invention relates to the field of communications, and more particularly to a method, apparatus, system, and storage medium for the operation and maintenance of network slicing. Background Technology

[0002] 5G network slicing can be deployed and divided according to vertical industries, regions, and virtual operators. However, network slicing orchestration involves radio networks, bearer networks, and core networks. Network slicing technology includes four key technologies: radio, bearer, and core network domain slicing enabling technology; network slice identification and access technology; network slice end-to-end management technology; and network slice end-to-end Service Level Agreement (SLA) guarantee technology. Among these, radio, bearer, and core network domain slicing enabling technology serves as the foundational support, enabling network sub-slice instances in the radio, bearer, and core networks; network slice identification and access technology maps network slice instances to terminal service types and registers terminals to the desired network slice instances; network slice end-to-end management technology enables end-to-end network slice orchestration and management; and network slice end-to-end SLA guarantee technology collects, analyzes, and processes network performance indicators for each domain in near real-time, ensuring that system performance meets user SLA requirements. Existing 3GPP standards only subscribe to the overall architecture of network slicing, providing a certain degree of satisfaction regarding resource guarantees, security, reliability, and availability. However, specific technical requirements include: a unified air interface, support for differentiated slice needs, flexible slice allocation and deployment, and support for integration with the core network. Flexible slice networking, rapid slice construction based on microservices, intelligent slice selection, open slice capabilities, and slice roaming are also crucial. Furthermore, current technologies cannot adequately meet the requirements for multi-layered slicing based on SDN architecture, support for various slice isolation technologies, network element node virtualization, and secure isolation technology for bearer network sub-slices. Network slicing involves multiple networks, each with network equipment provided by different vendors, making secure, reliable, and unified management and maintenance of 5G network slices impossible. Summary of the Invention

[0003] The main objective of this application is to propose a network slicing operation and maintenance method, apparatus, system, and storage medium, aiming to achieve unified operation and maintenance of network slices across network domains, realize real-time monitoring of network slice service quality, and improve the security of network slice operation.

[0004] To achieve the above objectives, this application provides a network slicing operation and maintenance method, which includes:

[0005] Select a pre-deployed network slice based on the communication service request; allocate the functions and resources of the network slice based on the communication status information and communication process information within the network domain, wherein the network domain includes at least one network; collect the performance indicators of the network slice, and manage the service level agreement of the network slice according to the performance indicators.

[0006] To achieve the above objectives, this application also provides a network slicing operation and maintenance device, which includes:

[0007] The slice selection module is used to select pre-deployed network slices based on communication service requests;

[0008] The slice management module is used to allocate the functions and resources of the network slice based on the communication status information and communication process information within the network domain, wherein the network domain includes at least one network;

[0009] The quality assurance module is used to collect performance metrics of the network slices and manage the service level agreements of the network slices based on the performance metrics.

[0010] To achieve the above objectives, this application also provides a network slicing operation and maintenance system, which includes:

[0011] One or more processors;

[0012] Memory, used to store one or more programs;

[0013] When the one or more programs are executed by the one or more processors, the one or more processors implement the network slice operation and maintenance method as described in any of the embodiments of this application.

[0014] To achieve the above objectives, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the network slice operation and maintenance method as described in any of the embodiments of this application.

[0015] In this embodiment, a pre-deployed network slice is selected through a communication service request. Communication status information and communication process information of different network domains are obtained to allocate the functions and resources of the network slice. Performance indicators during the operation of the network slice are collected, and the service level protocol of the network slice is guaranteed according to the performance quality. This enables real-time monitoring of the service quality of the network slice and improves the security of the network slice operation. Attached Figure Description

[0016] Figure 1 This is a flowchart of a network slicing operation and maintenance method provided in an embodiment of this application;

[0017] Figure 2 This is an example diagram of a network slice deployment provided in an embodiment of this application;

[0018] Figure 3 This is an example diagram of another network slice deployment provided in the embodiments of this application;

[0019] Figure 4 This is an example diagram of an end-to-end network slice mapping provided in an embodiment of this application;

[0020] Figure 5 This is an example diagram of another end-to-end network slice mapping provided in the embodiments of this application;

[0021] Figure 6 This is a flowchart of a network slicing operation and maintenance method provided in an embodiment of this application;

[0022] Figure 7 This is a schematic diagram of the structure of a network slicing operation and maintenance device provided in an embodiment of this application;

[0023] Figure 8 This is a schematic diagram of the structure of a network slicing operation and maintenance system provided in an embodiment of this application. Detailed Implementation

[0024] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0025] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no inherent meaning. Therefore, "module," "part," or "unit" may be used interchangeably.

[0026] Figure 1 This is a flowchart illustrating a network slice operation and maintenance method provided in this application embodiment. This embodiment is applicable to network slice operation and maintenance across network domains. The method can be executed by the network slice operation and maintenance device described in this embodiment, which can be implemented using software and / or hardware methods. See [link to relevant documentation]. Figure 1 The method provided in this application embodiment may specifically include the following steps:

[0027] Step 110: Select a pre-deployed network slice based on the communication service request.

[0028] The communication service request can be a request from a network slicing tenant or enterprise to subscribe to a network slice from an operator. This request may include the type of network slice requested and the service level agreement (SLA) requirements for that network slice. A network slice can be a collection of resources for different purposes, divided into segments for different application scenarios. Network slices can include high-definition video slices, mobile phone slices, massive IoT slices, and mission-critical IoT slices.

[0029] Specifically, the operation and maintenance system can obtain communication service requests for subscribed network slices, extract information such as the requested network slice type and service level agreement from the communication service request, and select network slices according to the network slice type and service level agreement to provide communication services to users.

[0030] Step 120: Allocate network slice functions and resources based on communication status information and communication process information within the network domain, wherein the network domain includes at least one network.

[0031] The network domain can be the actual network carrying the network slice, including wireless networks, core networks, and bearer networks. Communication status information and communication process information can be information reflecting the network operation status within the network domain. Since network slices are implemented based on different network domains, such as core networks, wireless networks, and bearer networks, changes in network status will affect the service quality of the network slice.

[0032] In this embodiment of the application, the network slice can correspond to one or more network domains. The communication status information and communication process information in different network domains can be collected to determine the status of each network domain. The functions and resources of the network slice can be allocated according to the status of each network domain, so that the network slice has higher operating efficiency.

[0033] Step 130: Collect performance metrics of network slices and guarantee the service level agreement of network slices based on performance metrics.

[0034] Performance metrics can reflect the operational quality of a network slice, including information such as current average user speed, current latency, and current load. These metrics can be acquired in real-time during network slice operation to improve the accuracy of network slice monitoring. Service Level Agreements (SLAs) are the service quality requirements agreed upon between the subscriber and the operator, and can include the number of communication users, communication speed, and latency that the network slice needs to meet.

[0035] Specifically, the operational status of network slices can be monitored, and information such as the current average user speed, current latency, and current load can be collected as performance indicators. Based on this performance quality, adjustments can be made to the network slices to ensure that the corresponding service level protocol is followed during operation. Adjustments can include allocating higher bandwidth or reducing latency.

[0036] In this embodiment, a pre-deployed network slice is selected through a communication service request. Communication status information and communication process information of different network domains are obtained to allocate the functions and resources of the network slice. Performance indicators during the operation of the network slice are collected, and the service level protocol of the network slice is guaranteed according to the performance quality. This enables real-time monitoring of the service quality of the network slice and improves the security of the network slice operation.

[0037] Furthermore, based on the above-mentioned application embodiments, network slicing is deployed according to application scenarios.

[0038] In the embodiments of this application, application scenarios may include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (uRLLC), etc. See also... Figure 2 Centralized units (DU) and distributed units (CU) can be deployed together, such as... Figure 1 As shown, core network cloudification elements can be deployed in data centers, such as National Data Centers (DCs) and Regional Data Centers (DCs). For services with low latency, UPFs can be deployed in edge data centers to improve communication response speed and reduce access to the core data center. In scenarios where centralized units (DUs) and distributed units (CUs) are deployed separately, network slices for enhanced mobile bandwidth (eMBB) and massive machine-type communications (mMTC) deploy CU-C and CU-U in a cloud-based manner in the Local Data Center. For low-latency communication uRLLC, CU-C is deployed in the Local Data Center, while CU-U can be deployed in conjunction with DUs using a PNF (Power-Only Network Provider Interface), such as... Figure 3 As shown.

[0039] Furthermore, based on the above-mentioned application embodiments, the mapping of network slices and network devices in the network domain includes at least one of physical port mapping, VLAN mapping, DSCP mapping, and VxLAN mapping.

[0040] In this embodiment of the application, network slicing can be implemented by network devices in a network domain. There can be a mapping relationship between network slices and network devices to realize the utilization of network device resources. The mapping method can include at least one of physical port mapping, VLAN mapping, DSCP mapping, and VxLAN mapping. Figure 4 This is an example diagram of an end-to-end network slice mapping provided in an embodiment of this application. See also... Figure 4 Network slices can be mapped to the bearer network using VLANs. Within a network slice, DSCP and IP / POPT can be used for quality of service control of service flows. See also Figure 5 When the network slice corresponds to a unified network topology of centralized unit (CU) and distributed unit (DU) deployed under PNF, each network slice of the centralized unit CU / distributed unit DU can correspond to one VLAN. Within the same Layer 2 access ring, the VLAN IDs of different distributed units DU / centralized units CU cannot be duplicated. If the access ring is a Layer 3 network, then the VLAN IDs of different distributed units DU / centralized units CU can be duplicated. The distributed unit DU / centralized unit CU is an access device that directly accesses the bearer network without going through other switches or routers; that is, the bearer network can directly see the VLAN ID to which the distributed unit DU / centralized unit CU belongs. Different VLAN IDs, received by the bearer PE device, are mapped to different VPN tunnels. Internally, the bearer determines whether the VPN is built on a hard slice (such as FlexE) or vNET based on the required level of isolation. Furthermore, for NFs specific to network slices, such as UPF, VLANs can also be used for isolation. The VLAN IDs for UPF services need to be configured on the ROSNG protocol stack, such as VLAN31 and VLAN41. NFVI platforms, such as TECS, automatically assign VLAN IDs, such as VLAN 101 and VLAN 202, when creating the external network plane. This network plane corresponds to the external network plane orchestrated by MANO. When UPF sends packets, the NFVI platform uses QinQ to transmit the VLAN ID, that is, the platform's VLAN is nested on top of the service's VLAN. The VLAN ID assigned by NFVI and the VLAN ID of the service protocol stack will be stripped at the CE. New VLAN IDs need to be configured at the CE to correspond to them, such as VLAN 102 and VLAN 202, and mapped to the VPN carried by the VLAN based on the newly assigned VLAN IDs.

[0041] Figure 6 This is a flowchart illustrating a network slicing operation and maintenance method provided in this application embodiment. This application embodiment is a specific embodiment based on the above application embodiment. See also... Figure 6 The method provided in this application specifically includes the following steps:

[0042] Step 210: Obtain the expected slice type set and the user-subscribed slice type set corresponding to the communication service request.

[0043] The expected slice type set can be the set of network slice types requested by the user when ordering network slices, and the user-subscribed slice type set can be the set of network slice types agreed upon by the user when signing the contract.

[0044] In this application embodiment, the expected slice type set Requested-NSSAI carried by the user's client UE and the subscribed slice type set Subscribed NSSAI can be obtained respectively to achieve the acquisition of the expected slice type set and the user's subscribed slice type set.

[0045] Step 220: Select network slices based on the slice selection strategy, the desired slice type set, and the user-subscribed slice type set.

[0046] The slice selection strategy can be a strategy for selecting network slices for communication service requests, and can include selection based on network slice availability, selection based on the current region TA, etc.

[0047] Specifically, the network slice can be selected as the network slice requested for communication service based on the expected slice type set, the user-subscribed slice type set, the availability of the network slice, and the current area TA.

[0048] Step 230: Obtain the communication status information and communication process information corresponding to the wireless network domain, bearer network domain, and core network domain, respectively.

[0049] Specifically, communication status information and communication process information can be collected for the wireless network domain, the bearer network domain, and the core network domain respectively, so as to obtain status information for different network domains.

[0050] Step 240: Use communication status information and communication process information to find the corresponding network slice management policy. The network slice management policy includes at least one of the following: network slice lifecycle management policy, cross-domain resource allocation management policy, overall network slice policy, and network slice isolation policy.

[0051] Network slice management policies, which can be pre-configured, manage the lifecycle of network slices. Based on different functions, they can be categorized into network slice lifecycle management policies, cross-domain resource allocation management policies, overall network slice policies, and network slice isolation policies. Network slice lifecycle management policies can include policies for creating, updating, activating, deactivating, and terminating network slices. Cross-domain resource allocation management policies can include resource allocation policies for network slices in different domains. Overall network slice policies can include overall control policies for network slices, and network slice isolation policies include security and hierarchical isolation policies for domain network topologies.

[0052] In this embodiment of the application, the communication status information and communication process information of each network slice in its respective domain can be used to manage the lifecycle of the network slice, manage cross-domain resource allocation, manage the overall control of the network slice, and manage the security isolation mechanism of the network slice.

[0053] Step 250: Allocate the functions and resources of network slices according to the network slice management strategy.

[0054] Specifically, the functions and resources of network slices can be adjusted according to the found network slice management policies to improve the performance of network slices. For example, the resource ratio of network slices in wireless networks, bearer networks, and core networks can be changed, and the life cycle of network slices can also be included to reduce the resource consumption of network slices and improve the quality of user communication services.

[0055] Step 260: Collect the performance metrics of the network slice corresponding to the user in real time.

[0056] Specifically, by collecting network slice performance metrics in real time at the user level, performance metrics can be monitored, statistically analyzed, and reported.

[0057] Step 270: Obtain the comparison results of performance indicators and the service quality corresponding to the network slicing service level protocol, and adjust the network slice according to the comparison results.

[0058] Among them, Quality of Service (QoS) can refer to the communication quality provided by network slicing, and QoS can correspond to Service Level Agreements (SLAs).

[0059] In this embodiment, the collected performance indicators can be compared with the quality of service. If the performance indicators meet the quality of service requirements, no adjustment needs to be made to the network slices. If they do not meet the requirements, the network slices can be reconfigured to improve the operating efficiency of the network slices.

[0060] This application embodiment obtains the expected slice type set and user-subscribed slice type set corresponding to the communication service, selects network slices according to the slice selection strategy, obtains network status information and network process information in different network domains, finds the network slice management strategy corresponding to the network status information and network process information, processes the network slices according to the network slice management strategy, collects the performance indicators of the network slices, and adjusts the network slices based on the comparison results of the performance indicators and service quality. This achieves unified management of network slices, adjusts network slices based on the operational performance indicators to meet the corresponding service level agreement, realizes real-time monitoring of network slice service quality, and improves the security of network slice operation.

[0061] Furthermore, based on the above-described application embodiments, the service level agreement includes at least one of the following: number of online users, average user rate, and latency requirements.

[0062] In this embodiment of the application, the service level agreement corresponding to the network slice can stipulate the number of online users, the average user rate, and the usage requirements. The number of online users can be the maximum number of users that can be served when providing services to the network slice subscriber. The average user rate can be the average rate provided to each communication user when providing services to the network slice subscriber. The latency can be the latency of the network slice providing communication services.

[0063] Figure 7 This is a schematic diagram of a network slicing operation and maintenance device provided in an embodiment of this application. It can execute the network slicing operation and maintenance method provided in any embodiment of this invention, and possesses the corresponding functional modules and beneficial effects of the method. The device can be implemented by software and / or hardware, and specifically includes: a slice selection module 301, a slice management module 302, and a quality assurance module 303.

[0064] The slice selection module 301 is used to select a pre-deployed network slice based on a communication service request.

[0065] The slice management module 302 is used to allocate the functions and resources of the network slice based on the communication status information and communication process information within the network domain, wherein the network domain includes at least one network.

[0066] The quality assurance module 303 is used to collect the performance indicators of the network slice and manage the service level agreement of the network slice according to the performance indicators.

[0067] In this embodiment, the slice selection module selects a pre-deployed network slice according to the communication service request. The slice management module obtains communication status information and communication process information of different network domains to allocate the functions and resources of the network slice and collects performance indicators during the operation of the network slice. The quality assurance module guarantees the service level protocol of the network slice according to the performance quality, thereby realizing real-time monitoring of the service quality of the network slice and improving the security of the network slice operation.

[0068] Furthermore, based on the above-described embodiments, the slice selection module 301 includes:

[0069] The type set unit is used to obtain the expected slice type set and the user-subscribed slice type set corresponding to the communication service request.

[0070] The selection execution unit is used to select network slices based on the slice selection strategy, the desired slice type set, and the user-subscribed slice type set.

[0071] Furthermore, based on the above-mentioned application embodiments, the network slices in the device are deployed according to the application scenario.

[0072] Furthermore, based on the above-described embodiments, the service level agreement in the device includes at least one of the following: number of online users, average user rate, and latency requirements.

[0073] Furthermore, based on the above-mentioned application embodiments, the mapping between network slices and network devices in the device includes at least one of physical port mapping, VLAN mapping, DSCP mapping, and VxLAN mapping.

[0074] Furthermore, based on the above-described embodiments, the slice management module 302 includes:

[0075] The information acquisition unit is used to acquire communication status information and communication process information corresponding to the wireless network domain, bearer network domain, and core network domain, respectively.

[0076] The strategy determination unit is used to use the communication status information and the communication process information to find the corresponding network slice management strategy, wherein the network slice management strategy includes at least one of the following: network slice lifecycle management strategy, cross-domain resource allocation management strategy, overall network slice strategy, and network slice isolation strategy.

[0077] The policy execution unit is used to allocate the functions and resources of the network slice according to the network slice management policy.

[0078] Furthermore, based on the above-described embodiments, the quality assurance module 303 includes:

[0079] The metrics acquisition unit is used to collect the performance metrics of the network slice for the corresponding user in real time.

[0080] The quality assurance unit is used to obtain the comparison results between the performance indicators and the service quality corresponding to the network slice service level protocol, and adjust the network slice according to the comparison results.

[0081] In an exemplary real-time approach, 5G slice operation and maintenance is introduced into the 3GPP protocol to realize end-to-end orchestration, deployment, and management functions of network slices. The 5G slice management system includes functional entities such as Communication Service Management Function (CSMF), Network Slice Management Function (NSMF), and Network Slice Subnet Management Function (NSSMF). End-to-end slice orchestration and management are realized through the interaction of CSMF, NSMF, NSMF, Management and Orchestration (MANO), and EMS, including slice design, slice lifecycle management, slice configuration and activation, and SLA monitoring and assurance.

[0082] In CSMF (Service Provider Facilitation), tenants or enterprises can order network slices from operators and submit relevant SLA (Service Level Agreement) requirements (such as the number of online users, average user speed, latency requirements, etc.). CSMF then translates the user's communication service requirements into network slice requests for NSMF (Service Provider Facilitation) and forwards them to NSMF. CSMF manages communication services, each of which is implemented by one or more network slice functions. Since CSMF primarily implements functions such as slice purchasing, it is generally deployed in the Business Support System (BSS) domain.

[0083] NSMF is the network slice management function, responsible for the orchestration, deployment, and maintenance of slices. It interfaces with CSMF and NSMMF in the Operations Support System (OSS), receiving network slice deployment requests from CSMF, decomposing the end-to-end SLA requirements of a network slice into SLA requirements for network sub-slices, and then sending network sub-slice deployment requests to NSMMF. NSMF manages network slices, each of which can consist of zero, one, or more network slice subnets.

[0084] NSSMF is the network slice subnet management function, responsible for the orchestration, deployment, and maintenance of subslices. It interfaces with NSMF in the OSS system, receiving network slice subnet deployment requests from NSMF, mapping the SLA requirements of the network slice subnet to the QoS requirements of network services, and issuing deployment requests for network services to the NFVO system in the ETSI NFV domain to achieve subslice deployment. It also configures network element service data through EMS. The NSSMF manages network slice subnets, each of which can be a basic subslice or a combination of multiple basic subslices. Each subslice can contain one or more network functions.

[0085] NSMF manages Network Slice Templates (NSTs) and Network Slice Instances (NSIs) for lifecycle and FCAPS management, working in conjunction with NSMF to achieve end-to-end network slicing functionality. Its features include: providing blueprint design capabilities, enabling the design, publication, and management of NST templates through a visual interface; NSI instance lifecycle management, such as creation, update, activation, deactivation, and termination; FCAPS management of NSIs, including resource viewing, topology visualization, alarm monitoring, and performance analysis; NSI policy management, such as NSI updates triggered by NSI operation and maintenance monitoring; and support for interface interaction with NSMF.

[0086] NSSMF manages network slice subnet templates (NSSTs), as well as network slice subnet instances (NSSIs) and their lifecycle and FCAPS management. Its features include: providing blueprint design capabilities, enabling the design, publication, and management of NSST templates through a visual interface; NSSI instance lifecycle management, such as creation, updating, activation, deactivation, and termination; NSSI FCAPS management, such as viewing network slice subnet resources, topology display, alarm monitoring, and performance management; and NSSI policy management, such as NSSI updates triggered by NSSI operation and maintenance monitoring.

[0087] Figure 8 This is a schematic diagram of the structure of a network slicing operation and maintenance system provided in an embodiment of this application, as shown below. Figure 8 As shown, the system includes a processor 40, a memory 41, an input device 42, and an output device 43; the number of processors 40 in the device can be one or more. Figure 8 Taking a processor 40 as an example; in the system, the processor 40, memory 41, input device 42, and output device 43 can be connected via a bus or other means. Figure 8 Taking the example of a connection between China and Israel via a bus.

[0088] The memory 41, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the modules corresponding to the network slicing operation and maintenance device in this embodiment (slice selection module 301, slice management module 302, and quality assurance module 303). The processor 40 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 41, thereby realizing the above-described network slicing operation and maintenance method.

[0089] The memory 41 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on terminal usage. Furthermore, the memory 41 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some instances, the memory 41 may further include memory remotely located relative to the processor 40, which can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0090] Input device 42 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 43 may include display devices such as a display screen.

[0091] This application embodiment also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a network slice operation and maintenance method, the method comprising:

[0092] Select a pre-deployed network slice based on the communication service request;

[0093] The functions and resources of the network slice are allocated based on communication status information and communication process information within the network domain, wherein the network domain includes at least one network;

[0094] Collect the performance metrics of the network slices and guarantee the service level agreement of the network slices based on the performance metrics.

[0095] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the operation of the method described above, but can also perform related operations in the network slice operation and maintenance method provided in any embodiment of this application.

[0096] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0097] It is worth noting that in the embodiments of the search device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0098] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0099] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0100] The preferred embodiments of the present invention have been described above with reference to the accompanying drawings, but this does not limit the scope of the invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of the present invention should be within the scope of the present invention.

Claims

1. A method for operating and maintaining network slices, characterized in that, The method includes: Select a pre-deployed network slice based on the communication service request; Acquire communication status information and communication process information corresponding to the wireless network domain, bearer network domain, and core network domain, respectively; the communication status information and communication process information are information reflecting the network operation status within the network domain. The corresponding network slice management strategy is found using the communication status information and the communication process information. The network slice management strategy includes a cross-domain resource allocation management strategy; the cross-domain resource allocation management strategy includes a resource allocation strategy for network slices in different domains. The functions and resources of the network slices are allocated according to the network slice management strategy. Collect the performance metrics of the network slices and guarantee the service level agreement of the network slices based on the performance metrics.

2. The method according to claim 1, characterized in that, The step of selecting a pre-deployed network slice based on a communication service request includes: Obtain the expected slice type set and the user-subscribed slice type set corresponding to the communication service request; Network slices are selected based on the slice selection strategy, the desired slice type set, and the user-subscribed slice type set.

3. The method according to claim 1, characterized in that, The network slices are deployed according to the application scenario.

4. The method according to claim 1, characterized in that, The service level agreement includes at least one of the following: number of online users, average user speed, and latency requirements.

5. The method according to claim 1, characterized in that, The mapping of network slices to network devices in a domain includes at least one of the following: physical port mapping, VLAN mapping, DSCP mapping, and VxLAN mapping.

6. The method according to claim 1, characterized in that, The process of collecting performance metrics of the network slices and ensuring the service level agreement of the network slices based on the performance metrics includes: Real-time collection of performance metrics for the network slices corresponding to the user; Obtain the comparison results between the performance indicators and the service quality corresponding to the network slicing service level protocol, and adjust the network slice according to the comparison results.

7. A network slicing operation and maintenance device, characterized in that, The device includes: The slice selection module is used to select pre-deployed network slices based on communication service requests; The slice management module includes: The information acquisition unit is used to acquire communication status information and communication process information corresponding to the wireless network domain, the bearer network domain, and the core network domain, respectively; the communication status information and communication process information are information reflecting the network operation status within the network domain. The strategy determination unit is used to use the communication status information and the communication process information to find the corresponding network slice management strategy, wherein the network slice management strategy includes a cross-domain resource allocation management strategy; the cross-domain resource allocation management strategy includes a resource allocation strategy for network slices in different domains; The policy execution unit is used to allocate the functions and resources of the network slice according to the network slice management policy; The quality assurance module is used to collect performance metrics of the network slices and manage the service level agreements of the network slices based on the performance metrics.

8. A network slicing operation and maintenance system, characterized in that, The system includes: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the network slice operation and maintenance method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the network slice operation and maintenance method as described in any one of claims 1-6.

Images