Service deployment method and device, equipment, storage medium and computer program product

Abstract

The invention provides a service deployment method and device, equipment, a storage medium and a computer program product, and the method comprises the steps: obtaining virtual function configuration corresponding to at least one network card and container mirror image configuration for a service-oriented radio access network RAN; according to the virtual function configuration and the container mirror image configuration, updating container configuration information; and deploying a target RAN service corresponding to the target demand according to the updated container configuration information. According to the scheme, the RAN service based on the target demand can be automatically deployed, so that automatic deployment of the service RAN and dynamic resource allocation and optimization are realized, the complexity of the RAN service deployment scheme is reduced, the resource management efficiency is improved, the intelligent level and the operation efficiency of the RAN are improved, support is provided for intelligent deployment of a 6G network and the like, and the user experience is improved. At least one of the problems of high complexity and low resource management efficiency of the RAN service deployment scheme in the prior art is well solved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a service deployment method, apparatus, device, storage medium, and computer program product. Background Technology

[0002] In today's information age, with the evolution from 5G to 6G, Service-based Radio Access Network (RAN) has gradually become a key research direction for future network architecture. RAN, through its modular and flexible orchestration design, enables on-demand customization and free combination of communication network functions, significantly improving the scalability and adaptability of communication networks. However, existing RAN platforms still face the following challenges during deployment: 1. High deployment complexity: Traditional service-oriented RAN deployment relies on manual configuration or static resource allocation. The basic hardware and software environment requires manual intervention, the process is complex and cumbersome, the deployment cycle is long and prone to errors.

[0003] 2. Inefficient resource management: The startup of business Pods (containerized units / minimum deployment units), loading of image repositories, and configuration of environment parameters need to be manually modified, making it difficult to achieve dynamic resource allocation and optimization.

[0004] As shown above, existing RAN service deployment solutions suffer from problems such as high complexity and low management efficiency. Summary of the Invention

[0005] The purpose of this application is to provide a service deployment method, apparatus, device, storage medium, and computer program product to solve at least one of the problems of high complexity and low resource management efficiency in existing RAN service deployment schemes.

[0006] To address the aforementioned technical problems, embodiments of this application provide a service deployment method, including: Obtain the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN); Update the container configuration information based on the virtual function configuration and container image configuration; Based on the updated container configuration information, deploy the target RAN service corresponding to the target requirements.

[0007] Optionally, deploying the target RAN service corresponding to the target requirement based on the updated container configuration information includes: Based on the updated container configuration information, create a container runtime environment for the service-oriented RAN; In the container runtime environment, launch the container for the service-oriented RAN; The service-oriented platform application runs within the container to obtain runtime data. Based on the operational data, deploy the target RAN service corresponding to the target requirements.

[0008] Optionally, deploying the target RAN service corresponding to the target requirement based on the operational data includes: Based on the orchestration information, determine the target RAN service corresponding to the target demand; Download the corresponding RAN service configuration based on the target RAN service; Based on the operational data, the target RAN service is deployed according to the RAN service configuration.

[0009] Optionally, obtaining the virtual function configuration corresponding to at least one network interface card includes: Obtain the required number of ports corresponding to the network card; Create a corresponding number of virtual functions based on the required number of ports; Bind the created virtual functionality to the Data Plane Development Kit (DPDK); Each of the bound virtual functions is assigned a Media Access Control (MAC) address, with different virtual functions corresponding to different MAC addresses. The virtual function configuration corresponding to the network card is obtained based on the MAC address assigned to the virtual function.

[0010] Optionally, obtain the container image configuration for the service-oriented RAN, including: Update the image configuration file for the service-oriented RAN according to user needs; Based on the updated image configuration file, obtain the container image configuration for the service-oriented RAN.

[0011] Optional, also includes: Monitor the operational status of services; the operational status of services includes at least one of the following: the operational status of the target RAN service, the operational status of the container corresponding to the target RAN service, and the operational status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform; If the indicator data of the business operation status meets the triggering conditions, a business recovery strategy is executed; the business recovery strategy includes at least one of the following: Restart or reconfigure the target RAN service; Restart or reconfigure the container corresponding to the target RAN service; Restart or reconfigure the service Pod corresponding to the target RAN service; Business migration across resource nodes.

[0012] This application embodiment also provides a service deployment apparatus, including: The first acquisition module is used to acquire the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN). The first update module is used to update the container configuration information based on the virtual function configuration and container image configuration; The first deployment module is used to deploy the target RAN service corresponding to the target requirements based on the updated container configuration information.

[0013] Optionally, deploying the target RAN service corresponding to the target requirement based on the updated container configuration information includes: Based on the updated container configuration information, create a container runtime environment for the service-oriented RAN; In the container runtime environment, launch the container for the service-oriented RAN; The service-oriented platform application runs within the container to obtain runtime data. Based on the operational data, deploy the target RAN service corresponding to the target requirements.

[0014] Optionally, deploying the target RAN service corresponding to the target requirement based on the operational data includes: Based on the orchestration information, determine the target RAN service corresponding to the target demand; Download the corresponding RAN service configuration based on the target RAN service; Based on the operational data, the target RAN service is deployed according to the RAN service configuration.

[0015] Optionally, obtaining the virtual function configuration corresponding to at least one network interface card includes: Obtain the required number of ports corresponding to the network card; Create a corresponding number of virtual functions based on the required number of ports; Bind the created virtual functionality to the Data Plane Development Kit (DPDK); Each of the bound virtual functions is assigned a Media Access Control (MAC) address, with different virtual functions corresponding to different MAC addresses. The virtual function configuration corresponding to the network card is obtained based on the MAC address assigned to the virtual function.

[0016] Optionally, obtain the container image configuration for the service-oriented RAN, including: Update the image configuration file for the service-oriented RAN according to user needs; Based on the updated image configuration file, obtain the container image configuration for the service-oriented RAN.

[0017] Optional, also includes: The first monitoring module is used to monitor the service operation status; the service operation status includes at least one of the following: the operation status of the target RAN service, the operation status of the container corresponding to the target RAN service, and the operation status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform; The first execution module is configured to execute a service recovery strategy when the indicator data of the service operation status meets the triggering conditions; the service recovery strategy includes at least one of the following: Restart or reconfigure the target RAN service; Restart or reconfigure the container corresponding to the target RAN service; Restart or reconfigure the service Pod corresponding to the target RAN service; Business migration across resource nodes.

[0018] This application embodiment also provides a service deployment device, including: a processor; The processor is used to obtain the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN). Update the container configuration information based on the virtual function configuration and container image configuration; Based on the updated container configuration information, deploy the target RAN service corresponding to the target requirements.

[0019] Optionally, deploying the target RAN service corresponding to the target requirement based on the updated container configuration information includes: Based on the updated container configuration information, create a container runtime environment for the service-oriented RAN; In the container runtime environment, launch the container for the service-oriented RAN; The service-oriented platform application runs within the container to obtain runtime data. Based on the operational data, deploy the target RAN service corresponding to the target requirements.

[0020] Optionally, deploying the target RAN service corresponding to the target requirement based on the operational data includes: Based on the orchestration information, determine the target RAN service corresponding to the target demand; Download the corresponding RAN service configuration based on the target RAN service; Based on the operational data, the target RAN service is deployed according to the RAN service configuration.

[0021] Optionally, obtaining the virtual function configuration corresponding to at least one network interface card includes: Obtain the required number of ports corresponding to the network card; Create a corresponding number of virtual functions based on the required number of ports; Bind the created virtual functionality to the Data Plane Development Kit (DPDK); Each of the bound virtual functions is assigned a Media Access Control (MAC) address, with different virtual functions corresponding to different MAC addresses. The virtual function configuration corresponding to the network card is obtained based on the MAC address assigned to the virtual function.

[0022] Optionally, obtain the container image configuration for the service-oriented RAN, including: Update the image configuration file for the service-oriented RAN according to user needs; Based on the updated image configuration file, obtain the container image configuration for the service-oriented RAN.

[0023] Optionally, the processor is further configured to: Monitor the operational status of services; the operational status of services includes at least one of the following: the operational status of the target RAN service, the operational status of the container corresponding to the target RAN service, and the operational status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform; If the indicator data of the business operation status meets the triggering conditions, a business recovery strategy is executed; the business recovery strategy includes at least one of the following: Restart or reconfigure the target RAN service; Restart or reconfigure the container corresponding to the target RAN service; Restart or reconfigure the service Pod corresponding to the target RAN service; Business migration across resource nodes.

[0024] This application also provides a service deployment device, including a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, it implements the service deployment method described above.

[0025] This application also provides a readable storage medium storing a program that, when executed by a processor, implements the steps in the service deployment method described above.

[0026] This application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the service deployment method described above.

[0027] The beneficial effects of the above technical solution in this application are as follows: In the above scheme, the service deployment method obtains the virtual function configuration corresponding to at least one network card and the container image configuration for the service-oriented radio access network (RAN); updates the container configuration information according to the virtual function configuration and the container image configuration; and deploys the target RAN service corresponding to the target requirement according to the updated container configuration information. This supports the automatic deployment of RAN services based on target requirements, thereby realizing the automatic deployment, dynamic resource allocation and optimization of service-oriented RAN, reducing the complexity of RAN service deployment schemes and improving resource management efficiency, enhancing the intelligence level and operational efficiency of RAN, and providing support for intelligent deployment such as 6G networks. It effectively solves at least one of the problems of high complexity and low resource management efficiency in existing RAN service deployment schemes. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the service deployment method according to an embodiment of this application; Figure 2 This is a schematic diagram illustrating the specific implementation process of the service deployment method in this application embodiment; Figure 3 This is a schematic diagram of the service deployment device structure according to an embodiment of this application; Figure 4 This is a schematic diagram of the service deployment device structure according to an embodiment of this application. Detailed Implementation

[0029] To make the technical problems, technical solutions and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0030] The following is a brief introduction to the relevant content of this plan.

[0031] Service-oriented RAN is based on cloud-native technologies and uses Kubernetes (K8s, an open-source system) to manage multiple host nodes within the cloud platform, achieving functional decoupling through containerization. In the service-oriented approach, the single-base station functionality of traditional radio access networks is broken down, allowing each functional module to be developed, deployed, and extended independently. Currently, K8s is used to decompose and deploy RAN functional modules in different containers, further improving network flexibility, scalability, and resource utilization. Specifically, the current solution mainly involves the following: 1. The service-oriented architecture based on Kubernetes is used as a container orchestration platform, utilizing core components such as Pods (the smallest deployment unit) and Deployments to achieve containerized deployment and management of RAN functional modules. Hardware resources (such as CPU (Central Processing Unit), memory, and large page memory) are dynamically allocated by Kubernetes to improve system resource utilization efficiency.

[0032] 2. The atomic design of the service-oriented RAN breaks down the traditional monolithic RAN architecture into multiple atomic services. This design allows for dynamic parameter adjustments based on business needs without restarting the entire base station. Standardized interfaces are used for interaction between the various RAN functional modules, which can be combined as needed to form a complete RAN functional chain.

[0033] 3. Deeply integrated with cloud-native technologies, the RAN function is encapsulated into a lightweight image through Docker container technology, and supports dynamic adjustment of the number of Pods based on the regional user density to achieve elastic scaling.

[0034] The current solution has the following drawbacks: 1. Weak Fault Recovery Capabilities: If anomalies occur during business operations (such as service failures or log accumulation), there is a lack of automatic recovery mechanisms, requiring manual intervention to restart or clean up, impacting business continuity. In the event of a single module failure, maintenance personnel must be relied upon to repair configurations or switch nodes. Business Pods lack automatic recovery mechanisms after failures. Although reconstruction and scheduling can be achieved using external controllers (such as Deployments and StatefulSets), their recovery behavior is relatively generic and lacks the stringent requirements and fine-grained control needed for complex scenarios in service-oriented RANs, such as low latency, high reliability, and continuous service requirements.

[0035] 2. Lack of standardization: The interfaces of service-oriented RAN components from different vendors are not uniform, resulting in poor compatibility when deployed across platforms and increasing operation and maintenance costs.

[0036] Based on the above, this application addresses the problems of high complexity and low resource management efficiency in existing RAN service deployment schemes, and provides a service deployment method, such as... Figure 1 As shown, it includes: Step 11: Obtain the virtual function configuration for at least one network interface card and the container image configuration for the service-oriented radio access network (RAN); Step 12: Update the container configuration information according to the virtual function configuration and container image configuration; Step 13: Deploy the target RAN service corresponding to the target requirements based on the updated container configuration information.

[0037] The container configuration information can correspond to YAML; and / or, steps 12+13 can also be understood as: determining the target container configuration based on the virtual function configuration and container image configuration; deploying the target RAN service corresponding to the target requirements based on the target container configuration, but not limited to this. Target requirements include, for example, real-time service load, user requirements, etc., which are not limited here.

[0038] The service deployment method provided in this application embodiment obtains the virtual function configuration corresponding to at least one network interface card (NIC) and the container image configuration for the service-oriented radio access network (RAN); updates the container configuration information according to the virtual function configuration and the container image configuration; and deploys the target RAN service corresponding to the target requirement according to the updated container configuration information. This method supports the automatic deployment of RAN services based on target requirements, thereby achieving automatic deployment, dynamic resource allocation and optimization of service-oriented RAN, reducing the complexity of RAN service deployment schemes, improving resource management efficiency, enhancing the intelligence level and operational efficiency of RAN, and providing support for intelligent deployments such as 6G networks. It effectively solves the problems of high complexity and low resource management efficiency in existing RAN service deployment schemes.

[0039] The step of deploying the target RAN service corresponding to the target requirement based on the updated container configuration information includes: creating a container runtime environment for the service-oriented RAN based on the updated container configuration information; launching a container for the service-oriented RAN within the container runtime environment; running the service-oriented platform application within the container to obtain runtime data; and deploying the target RAN service corresponding to the target requirement based on the runtime data. This ensures accurate deployment of the target RAN service.

[0040] In this embodiment of the application, the step of deploying the target RAN service corresponding to the target requirement based on the operational data includes: determining the target RAN service corresponding to the target requirement based on orchestration information; downloading the corresponding RAN service configuration based on the target RAN service; and deploying the target RAN service based on the operational data and the RAN service configuration. This can specifically realize the deployment of the target RAN service.

[0041] The step of obtaining the virtual function configuration corresponding to at least one network interface card (NIC) includes: obtaining the required number of ports corresponding to the NIC; creating a corresponding number of virtual functions based on the required number of ports; binding the created virtual functions to the Data Plane Development Kit (DPDK); assigning a Media Access Control (MAC) address to each bound virtual function, with different virtual functions corresponding to different MAC addresses; and obtaining the virtual function configuration corresponding to the NIC based on the MAC addresses assigned to the virtual functions. This ensures accurate acquisition of the virtual function configuration. The phrase "obtaining the virtual function configuration corresponding to the NIC based on the MAC addresses assigned to the virtual functions" may include: obtaining the virtual function configuration corresponding to the NIC based on the MAC addresses assigned to the virtual functions and other information besides the MAC addresses, which is not limited here.

[0042] In this embodiment, obtaining the container image configuration for the Service-Oriented RAN includes: updating the image configuration file for the Service-Oriented RAN according to user requirements; and obtaining the container image configuration for the Service-Oriented RAN based on the updated image configuration file. This ensures accurate acquisition of the container image configuration. The image configuration file may correspond to a Dockerfile, and / or the image configuration file may support tagging each built image. Furthermore, this solution may also include: sending the container image configuration to an image server for storage and management, facilitating centralized storage and management of the container image configuration.

[0043] Furthermore, the service deployment method further includes: monitoring the service operation status; the service operation status includes at least one of the following: the operation status of the target RAN service, the operation status of the container corresponding to the target RAN service, and the operation status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform; and executing a service recovery strategy when the indicator data of the service operation status meets the triggering conditions; the service recovery strategy includes at least one of the following: restarting or reconfiguring the target RAN service; restarting or reconfiguring the container corresponding to the target RAN service; restarting or reconfiguring the service Pod corresponding to the target RAN service; and service migration across resource nodes. This can ensure the normal operation of the service as much as possible. The "indicator data of the target RAN service's operation status" may include at least one of the following: channel quality, user plane data packet loss rate, processing latency, etc., and correspondingly, the "triggering conditions" may include at least one of the following: channel quality below a corresponding threshold, user plane data packet loss rate above a corresponding threshold, processing latency above a corresponding threshold, etc., which are not limited here.

[0044] The following provides an example illustrating the service deployment method provided in the embodiments of this application.

[0045] To address the aforementioned technical issues, this application provides a service deployment method, specifically an automated deployment scheme based on a service-oriented RAN (Radio Access Network) platform. This scheme overcomes the obstacles to service-oriented RAN deployment by developing automated plugin scripts, enabling automated deployment of the service-oriented RAN platform. This includes at least one of the following deployment-related operations: automatic application and binding of VFs (Virtual Functions); automatic creation, uploading, and downloading of pod container images; automatic configuration of runtime parameters and automatic loading of service dynamic link libraries; automatic execution of the main program within the container; and automatic fault recovery functionality. Based on this, the scheme can achieve automated deployment of service-oriented RAN, improving the intelligence level and operational efficiency of the RAN, and providing support for the intelligent deployment of 6G networks.

[0046] Specifically, to improve the deployment efficiency of the service-oriented RAN operating environment, simplify the tedious and error-prone configuration operations in traditional deployments, and minimize configuration errors caused by manual intervention, this application provides a complete automated deployment solution, such as... Figure 2 As shown, this solution can achieve intelligent deployment and management based on the following four modules.

[0047] Module 1 can be used for automated network deployment (such as automated deployment of service-oriented RAN networks): This module can be implemented as an executable script that can automatically identify network card model and other parameter information; in addition, this solution also supports manually inputting the network card model to be bound to the Data Plane Development Kit (DPDK); based on this, subsequent automated deployment of the corresponding network card can be supported. This module can automatically create a corresponding number of Virtual Functions (VFs / Virtual Network Interfaces) based on the required number of ports corresponding to the aforementioned network interface cards (NICs). It then calls the dpdk-devbind.py tool to bind the VFs to the Data Plane Development Kit (DPDK) and assigns Media Access Control (MAC) addresses to the bound VFs. Different VFs can have different MAC addresses. This operation corresponds to obtaining the required number of ports for the NIC; creating a corresponding number of Virtual Functions based on the required number of ports; binding the created Virtual Functions to the DPDK; assigning Media Access Control (MAC) addresses to each bound Virtual Function, with different Virtual Functions corresponding to different MAC addresses; and obtaining the Virtual Function configuration corresponding to the NIC based on the assigned MAC addresses. This allows for the determination of the Virtual Function configuration corresponding to the NIC, supporting real-time network resource request and binding (i.e., creating VFs for the NIC and binding VFs).

[0048] The above deployment process can be completed without manual intervention, which not only significantly improves the efficiency and consistency of network configuration, but also avoids problems such as binding errors or resource conflicts caused by manual operation.

[0049] In addition, the automated deployment of this module can also be used similarly for other network deployments besides RAN services, and is not limited here.

[0050] Module 2 is used for automated container image building (i.e., container image building and deployment): This module provides end-to-end container image management from build to deployment, supporting automatic image building based on user needs. Specifically, this module provides Dockerfile build templates and build scripts. Users can modify the Dockerfile (corresponding to the image configuration file mentioned above) in advance according to their needs, adding or deleting lib libraries (i.e., dependency libraries used for image building), installing or uninstalling program components, and then executing the build script tool to create a new service-oriented RAN image based on the modified Dockerfile; it can also update the image configuration file for service-oriented RAN according to user needs; and obtain the container image configuration for service-oriented RAN based on the updated image configuration file. In addition, the script tool can support tagging each built image, such as user-named tags, which are then entered into the script, and the script tool uses these tags for subsequent tagging. Based on the above, this module supports user customization of the image base environment (i.e., modifying the Dockerfile mentioned above), dependency library integration, application installation, and version tag management (i.e., tagging).

[0051] Furthermore, after the image is built, users can choose whether to push it to the Harbor image server for centralized storage and management. During image deployment, each service-oriented RAN node can pull specified versions and types of images from Harbor as needed (e.g., based on business requirements), ensuring environment consistency and deployment repeatability.

[0052] Module 3 can be used for automated configuration and operation management within containers (such as running service-oriented RAN applications, which can correspond to the aforementioned service-oriented platform applications): for example, modifying the network configuration of the yaml (configuration file) based on the network interface (such as VF) generated in Module 1 during the previous network deployment phase; modifying the image configuration of the yaml based on the image generated in Module 2 during the image building process; and updating container configuration information based on the virtual function configuration and container image configuration mentioned above.

[0053] Next, use YAML (corresponding to the updated container configuration information mentioned above) to launch the POD and multiple containers. During container startup, the supervisord tool can be used to launch the configuration script (i.e., build the container application's runtime environment) before starting the container application. The script configures runtime parameters, which may include environment variables such as the VF port selection created during network deployment. This effectively avoids deployment errors caused by missing dependencies. The VF port selection can be based on business requirements; environment variables can be pre-configured parameters (such as the POD name), which are parameters of the application's runtime environment. This part of the operation corresponds to the above steps: creating a container runtime environment for the service-oriented RAN based on the updated container configuration information; and launching containers for the service-oriented RAN within that container runtime environment.

[0054] The script can include a built-in automatic RAN service download mechanism, including parsing the RAN service list and downloading the corresponding RAN services. Specifically, after creating the container, it can call the MinIO (open-source object storage service) client to download dynamic link library services (i.e., RAN services) from the MinIO server on demand. Specifically, after the script (i.e., the configuration script mentioned above) is configured, the supervisord tool can automatically run service-oriented platform applications such as OMA (Operation and Maintenance Agent), SPU (Service Processing Unit), OMOC (Operation and Maintenance Orchestration Center), and OMU (Operation and Maintenance Unit) (which can correspond to the aforementioned RAN applications) and record logs (which can correspond to the aforementioned runtime data). Subsequently, based on this, the required dynamic libraries (i.e., RAN services) can be loaded according to the orchestrated service list (i.e., the aforementioned RAN service list, which can correspond to the aforementioned target RAN services), enabling services to be used immediately upon startup. This part of the operation can correspond to the above-mentioned running of the service platform application within the container to obtain runtime data; determining the target RAN service corresponding to the target requirement based on the orchestration information; downloading the corresponding RAN service configuration based on the target RAN service; and deploying the target RAN service based on the runtime data and the RAN service configuration.

[0055] In this solution, "automatic RAN service download" can be performed on demand within the container, but is not limited to this. Furthermore, the download of RAN services can be understood as the deployment of RAN services, or as the download of RAN service configuration and the deployment of RAN services; no further limitations are imposed here.

[0056] Furthermore, this module also possesses runtime anomaly monitoring and self-healing capabilities, enabling real-time detection of service operation status. Upon detecting a fault or performance anomaly, it automatically triggers repair strategies, such as service restart, configuration reset, and container restart. This corresponds to the aforementioned monitoring of service operation status. The service operation status includes at least one of the following: the operation status of the target RAN service and the operation status of the container corresponding to the target RAN service. When the indicator data of the service operation status meets the triggering conditions, a service recovery strategy is executed. The service recovery strategy includes at least one of the following: restarting or reconfiguring the target RAN service; restarting or reconfiguring the container corresponding to the target RAN service.

[0057] Module 4 can be used for business Pod self-healing assurance: In existing Kubernetes, Pods do not have fault self-recovery capabilities; when a native Pod fails, Kubernetes does not automatically attempt to restart or repair the Pod, but only records the event and maintains the final state of the Pod (e.g., CrashLoopBackOff or Error). In this module, the Pod self-healing mechanism can integrate the specific needs of RAN services, providing fault awareness and recovery strategies; for example, if the monitoring program detects an abnormal Pod state, it can call a pre-written script to restart or reload the configuration and redeploy the Pod; in addition, the monitoring program can also make intelligent decisions (such as restarting or reconfiguring the Pod) based on the real-time operating indicators of RAN services (such as channel quality, user plane data packet loss rate, processing latency, etc.). In this solution, once the performance degradation or crash of the RAN service within a Pod is detected, the module can not only automatically attempt a local restart, but also combine the cluster resource status (for server nodes) to perform rapid cross-node Pod reconstruction and lossless business migration, thereby providing an additional layer of high availability assurance. In a service-oriented RAN scenario, any service interruption can directly impact the communication quality of end users. This module can significantly reduce the risk of single points of failure by customizing health management of the Pod lifecycle, ensuring that the RAN service can maintain stable operation even when encountering anomalies, thereby improving the robustness and service continuity of the entire network architecture. The self-healing guarantee mechanism executed by this module corresponds to the monitoring of the service operation status mentioned above. The service operation status includes at least one of the following: the operation status of the target RAN service and the operation status of the service Pod corresponding to the target RAN service. The Pod represents the smallest deployment unit of the container orchestration platform. When the indicator data of the service operation status meets the triggering conditions, a service recovery strategy is executed. The service recovery strategy includes at least one of the following: restarting or reconfiguring the target RAN service; restarting or reconfiguring the service Pod corresponding to the target RAN service; and service migration across resource nodes.

[0058] In this solution, after running the service-oriented RAN application, it can monitor whether the Pod operation or service is abnormal. If not, the process can be terminated. If so, it can enter the POD self-healing module for service-oriented RAN (i.e., module four above).

[0059] To clarify, the operations performed in Modules 1 and 2 above can be used to prepare for the operation of the APP involved in Module 3. For example, Module 1 provides a network interface for operation, enabling DPDK and VPP (Vector Packet Processing) to have a network port for efficient data transmission; the container image creation process involved in Module 2 can support the encapsulation of the APP and various dependent libraries and software into an image, and then use this image as the basis for container startup, which is finally started by Kubernetes when the POD is launched. The operations performed in Module 4 can support the implementation of a crash recovery mechanism.

[0060] Based on the above, the solutions provided in this application involve the following: 1. Based on automated network deployment, VF configuration and container image configuration for service-oriented RAN are obtained; specifically involving: (1) Network automated deployment method: This solution employs an automated network deployment approach, encompassing automated NIC identification, VF configuration, and dynamic DPDK driver binding based on service-oriented RAN. This enables automatic VF resource identification, driver binding, and MAC address allocation based on predefined policies and real-time service load status.

[0061] (2) Container image end-to-end automated management mechanism: This solution supports automatic on-demand image building, completing environment customization, dependency integration, and version management during the pre-configuration phase. After the build is complete, the image can be automatically pushed to the image server for unified storage. When deploying nodes, the image can be pulled on demand, realizing full-link automated management of container image building, storage, and distribution.

[0062] 2. Automated management of container configuration and operation: This solution supports RAN service resolution and automatic download. During container startup, it can automatically inject configuration parameters, environment variables, and dependent service information, and download service dynamic libraries on demand according to the service-oriented RAN business requirements. After container startup, the container main program can run automatically, avoiding deployment interruptions. Specifically, it involves: (1) Based on the obtained VF configuration and container image configuration, update the yaml (i.e., container configuration information); before starting the container, you can first create the container runtime environment (including VF selection, etc.) according to the yaml, and then the container is started by k8s; (2) After the container starts, it runs the service platform application (such as OMA, SPU, OMOC, OMU, etc.) and obtains runtime data. Then, based on the runtime data and the RAN service list generated by orchestration, it can call the MinIO tool to download the corresponding RAN service, or, based on the RAN service list generated by orchestration, it can call the MinIO tool to download the configuration of the corresponding RAN service, and deploy the RAN service based on the configuration and the aforementioned runtime data. Both the RAN service and its configuration are stored on the MinIO server and can be downloaded automatically.

[0063] 3. Pod self-healing mechanism for service-oriented RAN: To address the issue that native Kubernetes Pods lack business awareness and cannot self-recover, this solution provides a Pod fault awareness and recovery method that deeply integrates with RAN service requirements. It can enhance the stability of RAN deployment by intelligently performing local Pod restarts or cross-node reconstruction and migration through real-time monitoring of key RAN indicators.

[0064] In summary, this solution supports the automatic deployment of Kubernetes-based service-oriented RAN, containerized decomposition of RAN functions, and features automated network configuration, image building, adaptive recovery, and migration based on base station services. For example, it can dynamically adjust deployment parameters and recovery timing based on RAN performance metrics.

[0065] Based on the above, compared with existing technologies, this solution can support the automated construction of service-oriented RAN runtime networks, container images, and runtime configurations, and has the ability to recover from runtime anomalies, thus enhancing the accuracy and stability of service-oriented RAN deployment: 1. Currently, most service-oriented RAN deployments are done manually, which is prone to errors. This solution proposes an automated deployment strategy for the runtime environment based on the service-oriented RAN platform, greatly improving deployment efficiency.

[0066] 2. The proposal for an automatic container image creation mechanism and an automatic configuration and execution mechanism within containers enables first-time users of service-oriented platforms to correctly build and run containers, greatly saving learning and time costs.

[0067] 3. Since native Pods do not have recovery capabilities, this solution proposes a local self-healing or cross-node migration strategy for Pods by combining service-oriented RAN platform business metrics and Pod status monitoring, thereby reducing the risk of service-oriented RAN platform operation interruption and error.

[0068] This application also provides a service deployment apparatus, such as... Figure 3 As shown, it includes: The first acquisition module 31 is used to acquire the virtual function configuration corresponding to at least one network card and the container image configuration for the service-oriented radio access network (RAN). The first update module 32 is used to update the container configuration information according to the virtual function configuration and the container image configuration; The first deployment module 33 is used to deploy the target RAN service corresponding to the target requirements based on the updated container configuration information.

[0069] The service deployment apparatus provided in this application embodiment obtains the virtual function configuration corresponding to at least one network interface card (NIC) and the container image configuration for the service-oriented radio access network (RAN); updates the container configuration information according to the virtual function configuration and the container image configuration; and deploys the target RAN service corresponding to the target requirement according to the updated container configuration information. This supports the automatic deployment of RAN services based on target requirements, thereby achieving automatic deployment, dynamic resource allocation and optimization of service-oriented RAN, reducing the complexity of RAN service deployment schemes and improving resource management efficiency, enhancing the intelligence level and operational efficiency of RAN, and providing support for intelligent deployments such as 6G networks. It effectively solves the problems of high complexity and low resource management efficiency in existing RAN service deployment schemes.

[0070] The step of deploying the target RAN service corresponding to the target requirement based on the updated container configuration information includes: creating a container runtime environment for the service-oriented RAN based on the updated container configuration information; launching a container for the service-oriented RAN in the container runtime environment; running the service-oriented platform application in the container to obtain runtime data; and deploying the target RAN service corresponding to the target requirement based on the runtime data.

[0071] In this embodiment of the application, the step of deploying the target RAN service corresponding to the target requirement based on the operational data includes: determining the target RAN service corresponding to the target requirement based on the orchestration information; downloading the corresponding RAN service configuration based on the target RAN service; and deploying the target RAN service based on the operational data and the RAN service configuration.

[0072] The step of obtaining the virtual function configuration corresponding to at least one network interface card (NIC) includes: obtaining the required number of ports corresponding to the NIC; creating a corresponding number of virtual functions based on the required number of ports; binding the created virtual functions to the Data Plane Development Kit (DPDK); assigning a Media Access Control (MAC) address to each of the bound virtual functions, with different virtual functions corresponding to different MAC addresses; and obtaining the virtual function configuration corresponding to the NIC based on the MAC addresses assigned to the virtual functions.

[0073] In this embodiment of the application, obtaining the container image configuration for the service-oriented RAN includes: updating the image configuration file for the service-oriented RAN according to user requirements; and obtaining the container image configuration for the service-oriented RAN based on the updated image configuration file.

[0074] Furthermore, the service deployment device further includes: a first monitoring module, used to monitor the service operation status; the service operation status includes at least one of the following: the operation status of the target RAN service, the operation status of the container corresponding to the target RAN service, and the operation status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform; a first execution module, used to execute a service recovery strategy when the indicator data of the service operation status meets the triggering conditions; the service recovery strategy includes at least one of the following: restarting or reconfiguring the target RAN service; restarting or reconfiguring the container corresponding to the target RAN service; restarting or reconfiguring the service Pod corresponding to the target RAN service; and service migration across resource nodes.

[0075] The implementation embodiments of the above service deployment method are all applicable to the embodiments of the service deployment device, and can achieve the same technical effect.

[0076] This application also provides a service deployment device, such as... Figure 4 As shown, it includes: processor 41; The processor 41 is used to obtain the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN). Update the container configuration information based on the virtual function configuration and container image configuration; Based on the updated container configuration information, deploy the target RAN service corresponding to the target requirements.

[0077] The service deployment device provided in this application embodiment obtains the virtual function configuration corresponding to at least one network card and the container image configuration for the service-oriented radio access network (RAN); updates the container configuration information according to the virtual function configuration and the container image configuration; and deploys the target RAN service corresponding to the target requirement according to the updated container configuration information. It can support the automatic deployment of RAN services based on target requirements, thereby realizing the automatic deployment, dynamic resource allocation and optimization of service-oriented RAN, reducing the complexity of RAN service deployment schemes and improving resource management efficiency, enhancing the intelligence level and operational efficiency of RAN, and providing support for intelligent deployment such as 6G networks. It effectively solves the problems of high complexity and low resource management efficiency in existing RAN service deployment schemes.

[0078] The step of deploying the target RAN service corresponding to the target requirement based on the updated container configuration information includes: creating a container runtime environment for the service-oriented RAN based on the updated container configuration information; launching a container for the service-oriented RAN in the container runtime environment; running the service-oriented platform application in the container to obtain runtime data; and deploying the target RAN service corresponding to the target requirement based on the runtime data.

[0079] In this embodiment of the application, the step of deploying the target RAN service corresponding to the target requirement based on the operational data includes: determining the target RAN service corresponding to the target requirement based on the orchestration information; downloading the corresponding RAN service configuration based on the target RAN service; and deploying the target RAN service based on the operational data and the RAN service configuration.

[0080] The step of obtaining the virtual function configuration corresponding to at least one network interface card (NIC) includes: obtaining the required number of ports corresponding to the NIC; creating a corresponding number of virtual functions based on the required number of ports; binding the created virtual functions to the Data Plane Development Kit (DPDK); assigning a Media Access Control (MAC) address to each of the bound virtual functions, with different virtual functions corresponding to different MAC addresses; and obtaining the virtual function configuration corresponding to the NIC based on the MAC addresses assigned to the virtual functions.

[0081] In this embodiment of the application, obtaining the container image configuration for the service-oriented RAN includes: updating the image configuration file for the service-oriented RAN according to user requirements; and obtaining the container image configuration for the service-oriented RAN based on the updated image configuration file.

[0082] Furthermore, the processor is also configured to: monitor the service operation status; the service operation status includes at least one of the following: the operation status of the target RAN service, the operation status of the container corresponding to the target RAN service, and the operation status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform; and execute a service recovery strategy when the indicator data of the service operation status meets the triggering conditions; the service recovery strategy includes at least one of the following: restarting or reconfiguring the target RAN service; restarting or reconfiguring the container corresponding to the target RAN service; restarting or reconfiguring the service Pod corresponding to the target RAN service; and service migration across resource nodes.

[0083] The implementation embodiments of the above service deployment method are all applicable to the embodiments of the service deployment device and can achieve the same technical effect.

[0084] This application also provides a service deployment device, including a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, it implements the service deployment method described above.

[0085] The implementation embodiments of the above service deployment method are all applicable to the embodiments of the service deployment device and can achieve the same technical effect.

[0086] This application also provides a readable storage medium storing a program that, when executed by a processor, implements the steps in the service deployment method described above.

[0087] The implementation embodiments of the above service deployment methods are all applicable to the embodiments of the readable storage medium and can achieve the same technical effect.

[0088] This application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes of the above-described service deployment method and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0089] It should be noted that many of the functional components described in this specification are referred to as modules in order to more specifically emphasize the independence of their implementation.

[0090] In this embodiment, the module can be implemented in software so that it can be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but may include different instructions stored in different bits, which, when logically combined, constitute the module and achieve the module's intended purpose.

[0091] In practice, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified within the module and can be implemented in any suitable form and organized within any suitable data structure. This operational data can be collected as a single dataset or distributed across different locations (including different storage devices), and can exist, at least in part, solely as electronic signals within the system or network.

[0092] When a module can be implemented using software, considering the current level of hardware technology, modules that can be implemented in software can be implemented using hardware circuits by those skilled in the art to achieve the corresponding functions, without considering cost. These hardware circuits include conventional very-large-scale integrated circuits (VLSI) or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules can also be implemented using programmable hardware devices, such as field-programmable gate arrays, programmable array logic, and programmable logic devices.

[0093] The above describes the preferred embodiments of this application. It should be noted that those skilled in the art can make several improvements and modifications without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A service deployment method, characterized in that, include: Obtain the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN); Update the container configuration information based on the virtual function configuration and container image configuration; Based on the updated container configuration information, deploy the target RAN service corresponding to the target requirements.

2. The service deployment method according to claim 1, characterized in that, The step of deploying the target RAN service corresponding to the target requirements based on the updated container configuration information includes: Based on the updated container configuration information, create a container runtime environment for the service-oriented RAN; In the container runtime environment, launch the container for the service-oriented RAN; The service-oriented platform application runs within the container to obtain runtime data. Based on the operational data, deploy the target RAN service corresponding to the target requirements.

3. The service deployment method according to claim 2, characterized in that, The step of deploying the target RAN service corresponding to the target requirement based on the operational data includes: Based on the orchestration information, determine the target RAN service corresponding to the target demand; Download the corresponding RAN service configuration based on the target RAN service; Based on the operational data, the target RAN service is deployed according to the RAN service configuration.

4. The service deployment method according to claim 1, characterized in that, The step of obtaining the virtual function configuration corresponding to at least one network interface card includes: Obtain the required number of ports corresponding to the network card; Create a corresponding number of virtual functions based on the required number of ports; Bind the created virtual functionality to the Data Plane Development Kit (DPDK); Each of the bound virtual functions is assigned a Media Access Control (MAC) address, with different virtual functions corresponding to different MAC addresses. The virtual function configuration corresponding to the network card is obtained based on the MAC address assigned to the virtual function.

5. The service deployment method according to claim 1, characterized in that, Obtain the container image configuration for the service-oriented RAN, including: Update the image configuration file for the service-oriented RAN according to user needs; Based on the updated image configuration file, obtain the container image configuration for the service-oriented RAN.

6. The service deployment method according to claim 1, characterized in that, Also includes: Monitor the operational status of services; The service operation status includes at least one of the following: the operation status of the target RAN service, the operation status of the container corresponding to the target RAN service, and the operation status of the service Pod corresponding to the target RAN service; the Pod represents the smallest deployment unit of the container orchestration platform. If the indicator data of the business operation status meets the triggering conditions, a business recovery strategy is executed; the business recovery strategy includes at least one of the following: Restart or reconfigure the target RAN service; Restart or reconfigure the container corresponding to the target RAN service; Restart or reconfigure the service Pod corresponding to the target RAN service; Business migration across resource nodes.

7. A service deployment device, characterized in that, include: The first acquisition module is used to acquire the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN). The first update module is used to update the container configuration information based on the virtual function configuration and container image configuration; The first deployment module is used to deploy the target RAN service corresponding to the target requirements based on the updated container configuration information.

8. A service deployment device, characterized in that, include: processor; The processor is used to obtain the virtual function configuration corresponding to at least one network interface card and the container image configuration for the service-oriented radio access network (RAN). Update the container configuration information based on the virtual function configuration and container image configuration; Based on the updated container configuration information, deploy the target RAN service corresponding to the target requirements.

9. A service deployment device, comprising a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that, When the processor executes the program, it implements the service deployment method as described in any one of claims 1 to 6.

10. A readable storage medium having a program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the service deployment method as described in any one of claims 1 to 6.

11. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the steps of the service deployment method as described in any one of claims 1 to 6.

Images