5G slice network management method, device, system, equipment and product

Abstract

The invention provides a 5G slice network management method, device, system, equipment and product, and belongs to the technical field of network communication, and the method comprises the steps: determining a resource distribution strategy of a network slice; respectively sending corresponding slice configuration parameters to an access network, a core network and a bearer network through an application programming interface docking module; and coordinating the access network, the core network and the bearer network to open and configure slices based on a preset workflow template. The access network, the core network and the bearer network are comprehensively managed through the operation and maintenance management module, the slicing strategy is issued and executed through a unified interface, slice opening and configuration are carried out based on the preset standardized workflow template, delay caused by manual configuration is avoided, the slice opening time is greatly shortened, and the slice opening efficiency is improved. The configuration error rate is reduced, the business service is timely and accurately delivered to the user, the satisfaction degree of the user is improved, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a 5G slicing network management method, apparatus, system, equipment and product. Background Technology

[0002] With the rapid development of 5G technology, the application prospects of 5G ToB (To Business) fully automated slicing, commissioning, and operation and maintenance management software systems in intelligent transportation systems have shown unprecedented breadth. Through highly dynamic resource allocation and automated management, this system provides robust network support for intelligent transportation systems, ensuring that various transportation application scenarios can obtain optimized network resource configurations according to actual needs. In the field of intelligent transportation, from real-time data transmission from autonomous vehicles and smooth playback of high-definition video surveillance to precise synchronization of intelligent traffic signal control, every link places extremely high demands on network bandwidth, latency, and reliability.

[0003] Traditional 5G slicing technology relies heavily on manual slicing configuration, resulting in long activation cycles and delays in service delivery to users, impacting user satisfaction and experience. Summary of the Invention

[0004] This application provides a 5G slicing network management method, apparatus, system, equipment, and product, aiming to solve the problem that the long cycle of manual slicing configuration affects user satisfaction and experience.

[0005] Firstly, this application provides a 5G slicing network management method, applied to an operation and maintenance management module, including: Determine the resource allocation strategy for network slices, which includes slice configuration parameters corresponding to the access network, core network, and bearer network; The application programming interface (API) interface module sends the corresponding slice configuration parameters to the access network, core network, and bearer network respectively. The API interface interface module is used to perform protocol conversion between the operation and maintenance management module, access network, core network, and bearer network, and to complete data transmission between the operation and maintenance management module and the access network, core network, and bearer network respectively. Based on a preset workflow template, the access network, core network, and bearer network are coordinated to enable and configure network slices.

[0006] In one embodiment, the slice management method further includes: The application programming interface module receives real-time slice operation data uploaded from the access network, core network, and bearer network. Perform performance analysis on the real-time running data of the slices, and adjust the resource allocation strategy based on the performance analysis results.

[0007] In one embodiment, the slice management method further includes: Perform security analysis on real-time slice operation data and adjust slice security management strategies based on the analysis results.

[0008] In one embodiment, determining the resource allocation strategy for network slices specifically includes: Receive the user's initial business requirements and configuration requirements for managing the slices; The resource allocation strategy is determined based on the primary business requirements, configuration requirements, and the current network operating status.

[0009] In one embodiment, the slice management method further includes: Receive current event information and / or preset information within a preset time period in the future; Retrieve historical data corresponding to a preset future time period; Predict the second business demand based on preset information and historical data; Determine resource pre-allocation strategies based on the second business requirements; Furthermore, the resource allocation strategy is determined based on the primary business requirements, network slicing service level instructions, the current network operating status, and the resource pre-allocation strategy corresponding to the current time.

[0010] Secondly, this application also provides a 5G slicing network management device, applied to an operation and maintenance management module, including: The strategy determination module is used to determine the resource allocation strategy for network slices. The resource allocation strategy includes slice configuration parameters corresponding to the access network, core network, and bearer network. The policy distribution module is used to send the corresponding slice configuration parameters to the access network, core network and bearer network respectively through the application programming interface interface module. The application programming interface interface module is used to perform protocol conversion between the operation and maintenance management module, access network, core network and bearer network, and to complete the data transmission between the operation and maintenance management module and the access network, core network and bearer network respectively. The workflow execution module is used to coordinate the activation and configuration of slices in the access network, core network, and bearer network based on a preset workflow template.

[0011] Thirdly, this application also provides a 5G slicing network management system, including an operation and maintenance management module and an application programming interface (API) interface module; The operation and maintenance management module is used to execute the above-mentioned 5G slice network management methods; The application programming interface (API) module is used to perform protocol conversion between the operation and maintenance management module, access network, core network, and bearer network, and to complete data transmission between the operation and maintenance management module and the access network, core network, and bearer network, respectively.

[0012] In one embodiment, the slice management system further includes a user interface module, which has a self-service module for setting network slice service level instructions.

[0013] Fourthly, this application also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the above-mentioned 5G slicing network management methods.

[0014] Fifthly, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements any of the above-described 5G slicing network management methods. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is one of the structural diagrams of the 5G slicing network management system provided in this application; Figure 2 This is one of the flowcharts illustrating the 5G slicing network management method provided in this application; Figure 3 This is the second flowchart of the 5G slicing network management method provided in this application; Figure 4 This is the third flowchart of the 5G slicing network management method provided in this application; Figure 5 This is one of the structural schematic diagrams of the 5G slicing network management device provided in this application; Figure 6 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0019] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0020] The following is combined Figures 1 to 6 This application describes the 5G slicing network management methods, apparatus, systems, equipment, and products provided.

[0021] like Figure 1 As shown, the 5G slicing network management system provided in this application includes an operation and maintenance management module and an application programming interface (API) interface module.

[0022] The operation and maintenance management module is used to create preset workflow templates; determine the resource allocation strategy for network slices; send the resource allocation strategy to the access network, core network, and bearer network through the application programming interface interface module; and coordinate the access network, core network, and bearer network to enable and configure slices based on the preset workflow templates.

[0023] Specifically, the operation and maintenance management module uses a relational database (such as MySQL) or a non-relational database (such as MongoDB) to store data such as slice configuration and real-time slice operation data.

[0024] As the core of 5G network management, the Operations and Maintenance (O&M) module takes a holistic approach, comprehensively considering the characteristics, business processes, and interactions of the three heterogeneous network domains: access network, core network, and bearer network. Based on the equipment types, technical standards, and business requirements of different network domains, it develops universal and standardized workflow templates that meet overall network operation requirements. This ensures that operations such as slice activation, configuration, and adjustment follow a consistent process across different business scenarios and network environments, improving work efficiency and quality. The O&M module pre-configures workflow templates for centralized management, updating, and maintenance. When network technology upgrades, business requirements change, or new standards emerge, the O&M module can easily modify and improve the workflow templates and promptly push them to each network domain.

[0025] The preset workflow template is pre-designed and stored in the operation and maintenance management module. It is a set of standardized process steps that guide the automated configuration and operation of 5G network slices in multiple different network domains. It specifies the order, content, and conditions of operations to be performed in each network domain when creating, modifying, or deleting slices, and serves as a standardized operation process blueprint.

[0026] In one possible implementation, the workflow template includes operation steps, operation sequence, parameter configuration, condition judgment, etc.

[0027] The operation steps clearly define the specific operations that need to be performed in each network domain. For example, in the execution network, configure radio resource parameters (such as bandwidth, frequency band, antenna configuration, etc.), in the core network, set up slice quality of service (QoS) flow mapping, session management rules, etc., and in the bearer network, configure FlexE slices, routing policies, etc.

[0028] The operation sequence specifies the order in which each operation step is executed to ensure that the network slicing configuration process conforms to logical and network protocol requirements. For example, the core network can only perform the corresponding QoS configuration after the access network completes the basic radio resource configuration, and the bearer network then allocates routing and transmission resources according to the upper-layer configuration. Parameter configuration defines the required parameters and their value ranges for each operation step. These parameters can be fixed default values ​​or dynamically adjusted according to user needs or network environment. For example, the wireless bandwidth parameter in the access network can be set to different values ​​according to different service requirements. Conditional checks include logic that determines subsequent steps based on different situations. For example, if a device in a network domain does not support a specific function, the relevant configuration steps are skipped or an alternative is adopted.

[0029] With this pre-defined workflow template, the system can quickly execute operations according to the pre-defined workflow, greatly shortening the slice activation time and avoiding the need to manually write complex configuration processes each time a slice is activated or managed. This reduces the activation speed from the traditional "days" or even "weeks" to "minutes." Furthermore, the pre-defined workflow template ensures that the slice configuration process follows a unified standard and specification under different network environments and business requirements, reducing configuration errors and discrepancies caused by human factors and improving the quality and reliability of network slices.

[0030] The operation and maintenance management module includes a workflow execution module. Based on a preset workflow template, the workflow execution module automatically coordinates the access network, core network, and bearer network to ensure that each network domain executes its corresponding tasks in the correct order and steps when slicing and configuring.

[0031] For example, when a 5G slice is activated, the workflow execution module first triggers the access network to configure radio resources. After the access network configuration is completed, it automatically notifies the core network to perform session management and QoS configuration. Finally, the bearer network domain configures transmission resources, realizing automated collaboration of cross-domain operations. This can complete a large number of configuration operations in a short time and avoid errors caused by human factors, thus improving work efficiency and accuracy.

[0032] The application programming interface (API) module is used to perform protocol conversions between the operation and maintenance management module, access network, core network, and bearer network, and to complete data transmission between the operation and maintenance management module and the access network, core network, and bearer network, respectively. The transmitted data includes slice configuration parameters and the real-time operating status of the slices.

[0033] The Application Programming Interface (API) module serves as a crucial bridge connecting the operations and maintenance (O&M) module with the Operations & Maintenance Center (OMC) of the access network, core network, and bearer network, providing a unified and standardized interface. These interfaces abstract and encapsulate the proprietary protocols and interfaces of devices in different network domains, shielding them from underlying protocol differences and enabling the O&M module to interact with devices across various network domains in a unified manner. For example, the API calls for radio resource configuration of access network devices from different vendors are standardized into a single API call format, allowing configuration through this unified interface regardless of the wireless communication standard (such as LTE-Advanced Pro or 5G NR) or vendor-specific protocol used by the device. The application programming interface (API) module internally performs protocol conversion between the operations and maintenance (O&M) management module and various network domains, resolving the protocol adaptation issue for heterogeneous devices. It uses middleware technology to convert general configuration commands issued by the O&M management module into proprietary protocol commands that can be understood by devices in each network domain. For example, it converts general slice bandwidth configuration commands into radio resource block allocation commands supported by access network devices, QoS flow configuration commands recognizable by core network devices, and bandwidth adjustment commands acceptable to bearer network devices. Conversely, the API module can also convert information returned by devices in various network domains into a unified format for analysis and processing by the O&M management module.

[0034] Specifically, the application programming interface (API) module pre-configures protocol adaptation rules for multiple network domains, including various protocol adaptation rules for interactions between devices in the access network, core network, and bearer network. These rules are formulated based on the technical standards and actual interaction requirements of devices in each network domain. For example, the rule base specifies the establishment order and parameter passing rules for user plane and control plane connections between access network devices and core network devices when creating 5G slices, as well as rules for how bearer network devices perform routing configuration and bandwidth allocation according to the needs of the core network. When new devices are accessed or device version upgrades cause protocol changes, the rule base can be updated to adapt to the new protocol adaptation requirements, ensuring that the system can continuously and stably interact with heterogeneous devices in various domains. During the slicing activation and operation and maintenance process, the application programming interface (API) interface module system dynamically calls the pre-set protocol adaptation rules according to the actual device type and business needs.

[0035] This application embodiment uses an operation and maintenance management module to manage the access network, core network, and bearer network in a unified manner, and uses a unified interface to distribute and execute slicing policies. Based on a preset standardized workflow template, slicing is enabled and configured, avoiding delays caused by manual configuration, greatly improving slicing enablement time, reducing configuration error rate, and enabling timely and accurate delivery of business services to users, thereby improving user satisfaction and user experience.

[0036] In traditional slicing configuration strategies, enterprise users need to apply indirectly through operator account managers, resulting in a long service activation cycle.

[0037] Based on these considerations, in one possible implementation, such as Figure 1 As shown, the slice management system also includes a user interface module.

[0038] The user interface module is used for human-computer interaction. It provides a user-friendly interface and self-service functions. Users can use the self-service module to apply for configuration requirements for managing slices, such as setting QoS parameters by dragging and dropping or selecting templates for network slice service level agreements (SLAs) by themselves.

[0039] This application embodiment enables quick selection of configuration requirements by providing a self-service function in the user interface module, thereby quickly activating and configuring slices. Compared with manual activation, the self-service function can help improve the efficiency of slice activation.

[0040] The 5G slicing network management method and apparatus provided in this application are described in detail below.

[0041] It should be noted that the 5G slice network management method provided in this application embodiment is implemented based on a 5G slice network management device. The 5G slice network management method can automatically enable and configure slices in the network based on the resource allocation strategy of network slices, thereby improving the speed of slice activation.

[0042] This application describes the 5G slice network management method using a 5G slice network management device as the execution subject as an example.

[0043] Figure 2 This is one of the flowcharts illustrating the 5G slicing network management method provided in this application. For example... Figure 2 As shown, the 5G slicing network management method provided in this application is applied to the operation and maintenance management module, including: S210: Determine the resource allocation strategy for network slices. The resource allocation strategy includes slice configuration parameters corresponding to the access network, core network, and bearer network.

[0044] The operation and maintenance management module takes a global perspective and formulates resource allocation strategies for network slices based on business needs and network domain configuration requirements.

[0045] S220: Sends the corresponding slice configuration parameters to the access network, core network, and bearer network respectively through the application programming interface module.

[0046] S230: Based on a preset workflow template, coordinates the access network, core network, and bearer network to enable and configure slices.

[0047] This application embodiment uses an operation and maintenance management module to comprehensively manage the access network, core network, and bearer network, and utilizes a unified interface to distribute and execute slicing policies. Slice activation and configuration are based on preset standardized workflow templates, avoiding delays caused by manual configuration, significantly improving slice activation time, reducing configuration error rates, and ensuring timely and accurate delivery of services to users, thereby increasing user satisfaction and improving user experience. Furthermore, this application embodiment ensures that various application scenarios (such as transportation application scenarios) can obtain optimized network resource configuration according to actual needs.

[0048] In one possible implementation, such as Figure 3 As shown, the slice management method also includes: S240: Receives real-time slice operation data from the access network, core network, and bearer network via an application programming interface (API) interface module.

[0049] S250: Performs performance analysis on real-time slice operation data and adjusts resource allocation strategies based on the performance analysis results.

[0050] This step is used to monitor the slice performance of each network domain in real time, analyze key indicators such as slice bandwidth utilization, latency, and packet loss, obtain real-time analysis data, and generate automatic feedback reports based on the real-time analysis data to provide decision support and help operation and maintenance personnel adjust and optimize network configurations in a timely manner.

[0051] In one possible implementation, dynamic resource scheduling is performed using a dynamic scaling algorithm based on reinforcement learning.

[0052] Understandably, other dynamic adjustment algorithms can also be used to achieve dynamic resource scheduling of slices, and this application does not impose any restrictions on this.

[0053] This application embodiment dynamically adjusts the resource allocation strategy of the slice by using real-time operation data of the slice, so that the resource allocation changes with the dynamic changes of business needs, ensuring a high degree of matching between needs and services.

[0054] In one possible implementation, such as Figure 3 As shown, after step S240, the following steps are also included: S260: Perform security analysis on real-time slice operation data and adjust slice security management strategies based on the security analysis results.

[0055] In one possible implementation, abnormal traffic patterns are identified through machine learning, then analyzed to assess their impact, and based on that impact, a decision is made on how to adjust the slice security management strategy.

[0056] Analyzing abnormal traffic patterns allows for the identification of source and destination addresses, port numbers, protocol types, traffic volume, and traffic trends. By comparing these abnormal traffic patterns with historical normal traffic patterns, the degree of deviation and potential risk level can be determined. This helps assess whether the abnormal traffic will affect slice performance metrics and threaten service availability, integrity, and confidentiality. Slice security management strategies can be adjusted by restricting or blocking traffic from IP addresses generating abnormal traffic, or by isolating areas affected by abnormal traffic.

[0057] In one possible implementation, the slice security management strategy also includes: Each slice uses an independent root key. The root key is a core component of the hierarchical key management system, responsible for generating and protecting the next-level keys, but it does not directly participate in data encryption or decryption operations. As the root of trust in hierarchical key management, even if the upper-level keys are leaked, the security of the root key cannot be directly threatened. Protecting the root key through physical isolation and encryption algorithms reduces the risk of data being cracked.

[0058] This application embodiment monitors the security of video slices in real time and identifies potential security threats through security analysis of real-time operational data. Furthermore, it adjusts the security management strategy for video slices based on security threats to ensure the security of user data and network resources.

[0059] In one possible implementation, step S210, determining the resource allocation strategy for network slices, specifically includes: S2101: Receive the user's initial business requirements and configuration requirements for managing slices; Specifically, users input their primary business requirements and configuration needs through the user interface module. The user interface module provides a user-friendly interface and self-service functionality, allowing users to apply for and manage service slices independently, such as setting QoS parameters through drag-and-drop or selecting SLA templates.

[0060] S2102: Determine the resource allocation strategy based on the primary service requirements, configuration requirements, and the current network operating status.

[0061] This application embodiment enables quick selection of configuration requirements by providing a self-service function in the user interface module, thereby quickly activating and configuring slices. Compared with manual activation, the self-service function can help improve the efficiency of slice activation.

[0062] In one possible implementation, step S230 involves coordinating the access network, core network, and bearer network to enable and configure network slices based on a preset workflow template, specifically including: S2301: Determine the workflow and flowchart for slice activation based on the workflow template to guide slice activation, configuration, and management. The workflow includes automated scripts for each step.

[0063] Among them, the flowchart is a visual workflow that helps to understand the overall picture and operating mechanism of the workflow more intuitively.

[0064] Specifically, the workflow template defines the automated scripts that need to be executed at each stage of the workflow, as well as the execution order of the scripts. The operations and maintenance management module calls the corresponding workflow template according to the resource allocation strategy and generates the corresponding workflow according to the order and logic defined in the workflow template.

[0065] S2302: Create a script based on the workflow to execute the task.

[0066] S2303: Invoke the automated script corresponding to the script execution task, execute the script execution task, and send the execution result of the script execution task to the access network, core network, or bearer network.

[0067] The automated scripts ultimately operate on devices across various network domains, configuring and manipulating these devices. For example, they might send radio resource configuration parameters to access network devices, configure QoS flow mapping rules to core network devices, and allocate bandwidth to bearer network devices. The devices will respond to the execution requests of the automated scripts and provide feedback on the execution results.

[0068] Specifically, automated scripts are used to execute the slice activation process, including slice configuration, verification, and monitoring. The automated scripts also have error handling mechanisms to handle unexpected situations and reduce human intervention.

[0069] This application embodiment improves the accuracy of slice activation by decomposing the workflow template and controlling the execution order of script execution tasks to achieve cross-domain slice activation and configuration.

[0070] In one possible implementation, such as Figure 4 As shown, the slice management method also includes: S410: Receive current event information and / or preset information within a preset time period in the future.

[0071] The preset information can be weather forecasts, publicly announced events (such as concerts, sporting events, etc.), etc. This preset information has a clear time and location of occurrence.

[0072] S420: Retrieve historical data corresponding to a preset future time period. For example, retrieve historical network traffic data for locations and times where weather forecasts indicate rainfall, snowfall, or wind.

[0073] S430: Predicts second business needs based on preset information and historical data.

[0074] For example, network demand in the transportation sector may surge at the location and time of public events, making it possible to predict business needs.

[0075] S440: Determine resource pre-allocation strategies based on secondary business needs. For example, reserve bandwidth for vehicle-to-everything (V2X) communication during heavy rain.

[0076] Furthermore, based on the first service requirement, the network slicing service level instruction, the current network operating status, and the resource pre-allocation policy corresponding to the current time, a resource allocation policy is determined (corresponding to step S210). Then, steps S220-S260 are executed.

[0077] This application embodiment predicts slice demand based on spatiotemporal information and combines pre-allocated resources with real-time demand to ensure the smooth allocation of network resources and avoid network anomalies caused by sudden changes in network demand.

[0078] Based on the above, this application provides the following specific application examples to illustrate the 5G slicing network management method provided in this application.

[0079] A city plans to build an intelligent transportation system to improve traffic flow management, real-time monitoring, and emergency response capabilities. This system requires multiple network slices to meet different quality of service (QoS) requirements. The slice requirements are as follows: a. eMBB (Enhanced Mobile Broadband) slice: Function: Used for real-time video surveillance; Bandwidth requirement: ≥200Mbps; Latency requirement: ≤20ms; Number of users: 500; b. uRLLC (Ultra Reliable Low Latency Communications) slice: Function: Used for real-time traffic signal control; Bandwidth requirement: ≥100Mbps; Latency requirement: ≤10ms; Number of users: 100; c. mMTC (Massive Machine Type Communications) slicing: used for vehicle-to-everything (V2X) devices; Bandwidth requirement: ≥50Mbps; Latency requirement: ≤100ms; Number of users: 1000; Resource allocation: eMBB slice: 300Mbps; uRLLC slice: 200Mbps; mMTC slice: 500Mbps; With a total bandwidth of 1Gbps in a 5G network, the slice management process is as follows: Strategy Determination: Generate a resource allocation strategy based on the above slicing requirements; Policy distribution: The slice configuration parameters in the resource allocation policy are distributed to the corresponding access network, core network, and bearer network devices through the application programming interface module, and the slices are automatically deployed based on the workflow template.

[0080] Slice verification: Perform latency and bandwidth tests on the slices to ensure that the slice performance meets the preset standards.

[0081] The test results are as follows: eMBB slice: latency 18ms, bandwidth 220Mbps; uRLLC slice: 9ms latency, 110Mbps bandwidth; mMTC slice: 80ms latency, 55Mbps bandwidth; Real-time monitoring of slice performance data: eMBB: 75% utilization, 0.5% packet loss rate; uRLLC: Utilization rate 60%, packet loss rate 0%; mMTC: Utilization rate 85%, packet loss rate 1%; Troubleshooting: During a peak period, the utilization rate of eMBB slices reached 85%, triggering an alarm.

[0082] The automated processing flow is initiated, resource allocation is adjusted, and the bandwidth of the mMTC slice is reduced to 450Mbps to ensure that the eMBB slice receives sufficient resources.

[0083] Performance Evaluation: After the intelligent transportation system went live, the average delay of traffic flow decreased by 15%, and the response time of traffic signals improved by 30%. Overall user satisfaction increased by 20%, and traffic management efficiency was significantly improved.

[0084] As can be seen from the above, the 5G slicing network management method described above ensures the resource requirements and performance requirements of different types of slices in practical applications, and realizes the efficient operation of intelligent transportation systems.

[0085] Based on the above, this application also provides a 5G slicing network management device. The 5G slicing network management device and the aforementioned 5G slicing network management method can be referred to and correspond to each other.

[0086] As an example, such as Figure 5 As shown, the 5G slicing network management device provided in this application includes: The strategy determination module 510 is used to determine the resource allocation strategy for network slices. The resource allocation strategy includes slice configuration parameters corresponding to the access network, core network, and bearer network.

[0087] The policy distribution module 520 is used to send the corresponding slice configuration parameters to the access network, core network and bearer network respectively through the application programming interface interface module.

[0088] The workflow execution module 530 is used to coordinate the activation and configuration of slices in the access network, core network and bearer network based on a preset workflow template.

[0089] This application embodiment uses an operation and maintenance management module to manage the access network, core network, and bearer network in a unified manner, and uses a unified interface to distribute and execute slicing policies. Based on a preset standardized workflow template, slicing is enabled and configured, avoiding delays caused by manual configuration, greatly improving slicing enablement time, reducing configuration error rate, and enabling timely and accurate delivery of business services to users, thereby improving user satisfaction and user experience.

[0090] In one possible implementation, the slice management device further includes: The receiving module 540 is used to receive real-time slice operation data uploaded from the access network, core network and bearer network in real time through the application programming interface interface. The performance analysis module 550 is used to perform performance analysis on the real-time running data of the slice and adjust the resource allocation strategy based on the performance analysis results.

[0091] This application embodiment dynamically adjusts the resource allocation strategy of the slice by using real-time operation data of the slice, so that the resource allocation changes with the dynamic changes of business needs, ensuring a high degree of matching between needs and services.

[0092] In one possible implementation, the slice management device further includes: The security analysis module 560 is used to perform security analysis on the real-time running data of the slice and adjust the slice security management strategy based on the security analysis results.

[0093] This application embodiment monitors the security of video slices in real time and identifies potential security threats through security analysis of real-time operational data. Furthermore, it adjusts the security management strategy for video slices based on security threats to ensure the security of user data and network resources.

[0094] In one possible implementation, the strategy determination module 510 is specifically used for: Receive the user's initial business requirements and configuration requirements for managing the slices; The resource allocation strategy is determined based on the primary business requirements, configuration requirements, and the current network operating status.

[0095] This application embodiment enables quick selection of configuration requirements by providing a self-service function in the user interface module, thereby quickly activating and configuring slices. Compared with manual activation, the self-service function can help improve the efficiency of slice activation.

[0096] In one possible implementation, the workflow execution module 530 is specifically used for: Determine the workflow to be activated for the slice based on the workflow template; Create scripts based on the workflow to execute tasks; Invoke the automated script corresponding to the script execution task, execute the script execution task, and send the execution result of the script execution task to the access network, core network, or bearer network.

[0097] This application embodiment improves the accuracy of slice activation by decomposing the workflow template and controlling the execution order of script execution tasks to achieve cross-domain slice activation and configuration.

[0098] In one possible implementation, the slice management device is also used for: Receive current event information and / or preset information within a preset time period in the future; Retrieve historical data corresponding to a preset future time period; Predict the second business demand based on preset information and historical data; Determine resource pre-allocation strategies based on the second business requirements; Furthermore, the resource allocation strategy is determined based on the primary business requirements, network slicing service level instructions, the current network operating status, and the resource pre-allocation strategy corresponding to the current time.

[0099] This application embodiment predicts slice demand based on spatiotemporal information and combines pre-allocated resources with real-time demand to ensure the smooth allocation of network resources and avoid network anomalies caused by sudden changes in network demand.

[0100] Figure 6 This is a schematic diagram of the structure of the electronic device provided in this application, such as... Figure 6As shown, the electronic device may include: a processor 610, a communications interface 620, a memory 630, and a communication bus 640, wherein the processor 610, the communications interface 620, and the memory 630 communicate with each other via the communication bus 640. The processor 610 can call logical instructions in the memory 630 to execute a 5G slicing network management method, which includes: Determine the resource allocation strategy for network slices, which includes slice configuration parameters corresponding to the access network, core network, and bearer network; The application programming interface (API) interface module sends the corresponding slice configuration parameters to the access network, core network, and bearer network respectively. The API interface interface module is used to perform protocol conversion between the operation and maintenance management module, access network, core network, and bearer network, and to complete data transmission between the operation and maintenance management module and the access network, core network, and bearer network respectively. Based on a preset workflow template, the access network, core network, and bearer network are coordinated to enable and configure network slices.

[0101] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0102] On the other hand, this application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer is able to execute the 5G slicing network management method provided in the above embodiments. The method includes: Determine the resource allocation strategy for network slices, which includes slice configuration parameters corresponding to the access network, core network, and bearer network; The application programming interface (API) interface module sends the corresponding slice configuration parameters to the access network, core network, and bearer network respectively. The API interface interface module is used to perform protocol conversion between the operation and maintenance management module, access network, core network, and bearer network, and to complete data transmission between the operation and maintenance management module and the access network, core network, and bearer network respectively. Based on a preset workflow template, the access network, core network, and bearer network are coordinated to enable and configure network slices.

[0103] In another aspect, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is implemented to perform the 5G slicing network management method provided in the above embodiments, the method comprising: Determine the resource allocation strategy for network slices, which includes slice configuration parameters corresponding to the access network, core network, and bearer network; The application programming interface (API) interface module sends the corresponding slice configuration parameters to the access network, core network, and bearer network respectively. The API interface interface module is used to perform protocol conversion between the operation and maintenance management module, access network, core network, and bearer network, and to complete data transmission between the operation and maintenance management module and the access network, core network, and bearer network respectively. Based on a preset workflow template, the access network, core network, and bearer network are coordinated to enable and configure network slices.

[0104] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0105] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence 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 ROM / RAM, magnetic disk, optical disk, etc., and includes 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 or some parts of the embodiments.

[0106] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A 5G slicing network management method, characterized in that, Applied to the operation and maintenance management module, including: Determine the resource allocation strategy for network slices, the resource allocation strategy including slice configuration parameters corresponding to the access network, core network and bearer network; The application programming interface (API) interface module sends corresponding slice configuration parameters to the access network, the core network, and the bearer network respectively. The API interface interface module is used to perform protocol conversion between each pair of the operation and maintenance management module, the access network, the core network, and the bearer network, and to complete data transmission between the operation and maintenance management module and the access network, the core network, and the bearer network respectively. Based on a preset workflow template, the access network, the core network, and the bearer network are coordinated to enable and configure slices.

2. The 5G slicing network management method according to claim 1, characterized in that, The slice management method also includes: The application programming interface module receives real-time slice operation data uploaded by the access network, the core network, and the bearer network. The real-time running data of the slice is analyzed for performance, and the resource allocation strategy is adjusted based on the performance analysis results.

3. The 5G slicing network management method according to claim 2, characterized in that, The slice management method also includes: The real-time running data of the slice is subjected to security analysis, and the slice security management strategy is adjusted based on the security analysis results.

4. The 5G slice network management method according to claim 1, characterized in that, The resource allocation strategy for determining network slices specifically includes: Receive the user's initial business requirements and configuration requirements for managing the slices; The resource allocation strategy is determined based on the first service requirement, the configuration requirement, and the current network operating status.

5. The 5G slicing network management method according to claim 4, characterized in that, The slice management method also includes: Receive current event information and / or preset information within a preset time period in the future; Retrieve historical data corresponding to the preset future time period; Predict the second business demand based on the preset information and the historical data; Determine the resource pre-allocation strategy based on the second business requirement; Furthermore, the resource allocation strategy is determined based on the first service requirement, the network slicing service level instruction, the current network operating status, and the resource pre-allocation strategy corresponding to the current time.

6. A 5G slicing network management device, characterized in that, Applied to the operation and maintenance management module, including: The strategy determination module is used to determine the resource allocation strategy for network slices, wherein the resource allocation strategy includes slice configuration parameters corresponding to the access network, core network and bearer network; The policy distribution module is used to send corresponding slice configuration parameters to the access network, the core network, and the bearer network respectively through the application programming interface interface module. The application programming interface interface module is used to perform protocol conversion between each pair of the operation and maintenance management module, the access network, the core network, and the bearer network, and to complete data transmission between the operation and maintenance management module and the access network, the core network, and the bearer network respectively. The workflow execution module is used to coordinate the activation and configuration of slices in the access network, the core network, and the bearer network based on a preset workflow template.

7. A 5G slicing network management system, characterized in that, This includes an operations and maintenance management module and an application programming interface (API) integration module. The operation and maintenance management module is used to execute the 5G slice network management method according to any one of claims 1 to 5; The application programming interface (API) module is used to perform protocol conversion between the operation and maintenance management module, the access network, the core network, and the bearer network, and to complete data transmission between the operation and maintenance management module and the access network, the core network, and the bearer network, respectively.

8. The 5G slicing network management system method according to claim 7, characterized in that, The slice management system also includes a user interface module, which has a self-service module for setting network slice service level instructions.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the 5G slice network management method as described in any one of claims 1 to 5.

10. A computer program product, the computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the 5G slice network management method as described in any one of claims 1 to 5.

Images