VBF-based operator industry customer self-service system and method

Abstract

The invention discloses a VBF-based operator industry customer self-service system and method, and relates to the technical field of operation management, in the system, a VBF packaging module is used for packaging a plurality of existing support capabilities of an operator into independent virtualized service function units and publishing the independent virtualized service function units to an online shopping mall; the portal module is used for displaying a plurality of virtualized service function units published in the online shopping mall to industry customers; the VBF arrangement module is used for generating a service capability combination scheme; the scheme processing module is used for generating a standardized business order; and the service opening module is used for generating an opening instruction according to the standardized service order, and issuing the opening instruction to the corresponding support system, so that the support system completes service opening of the service capability combination scheme. According to the invention, the quick and automatic opening of the business capability combination scheme is realized, so that the response speed, the operation efficiency and the customer satisfaction of government and enterprise businesses are remarkably improved on the whole.

Description

Technical Field

[0001] This invention relates to the field of operations management technology, and in particular to a VBF-based customer self-service system and method for the telecom operator industry. Background Technology

[0002] A common technical problem in the current product design process for industry clients is that they cannot independently complete the combined ordering of government and enterprise products. When industry clients need to combine multiple products to meet their complex IT needs, manual intervention is often required, involving operations across multiple independent business support systems. This process is lengthy and time-consuming; completing a single product combination design typically requires multiple rounds of repeated communication between the industry client and the operator's account manager, resulting in low efficiency and a poor user experience.

[0003] To address the aforementioned issues, current industry solutions primarily rely on traditional business support system architectures and manual service processes. Operators typically possess multiple independent support systems, each managing different product capabilities. Customer needs are manually understood and relayed by account managers. Internally, account managers must manually coordinate different systems to conduct product feasibility checks, resource confirmations, and pricing combinations before finalizing a solution and providing it to the customer for confirmation. This model heavily relies on manual operation and cross-system manual integration in the product portfolio design, verification, and ordering processes.

[0004] These existing technologies have significant drawbacks. Due to their heavy reliance on manual labor and the involvement of multiple heterogeneous systems, product delivery cycles are long, making it difficult to quickly respond to market changes and immediate customer needs. Throughout the process, industry customers lack autonomy and visibility, and cannot directly participate in the design phase, resulting in final solutions that may not accurately match their actual business scenarios. Furthermore, this model also means high operating costs and limited service scalability for operators, hindering the flexible development and value enhancement of government and enterprise businesses.

[0005] Therefore, in order to overcome the problems of low process efficiency, insufficient customer participation and poor business flexibility in existing technologies, it is necessary and urgent to design a new service system that enables industry customers to complete the ordering and activation of government and enterprise business products on their own. Summary of the Invention

[0006] The technical problem to be solved by this invention is to address the shortcomings of existing technologies, and the following technical solution is provided: 1) In a first aspect, the present invention provides a self-service system for telecom operator customers based on VBF, the specific technical solution of which is as follows: It includes a VBF encapsulation module, a portal module, a VBF orchestration module, a solution processing module, and a service activation module; The VBF encapsulation module is used to: encapsulate multiple existing support capabilities of the operator into independent virtualized service function units, and publish the encapsulated virtualized service function units to the online store; The portal module is used to: showcase multiple virtualized business function units that have been published in the online marketplace to industry clients; The VBF orchestration module is used to: receive at least two target virtualization service function units selected by industry customers from multiple virtualization service function units, and orchestrate the at least two target virtualization service function units according to the combination logic defined by the industry customers to generate a service capability combination scheme. The solution processing module is used to: validate and standardize business capability combination solutions, and generate standardized business orders; The service activation module is used to generate activation instructions based on standardized business orders and send the activation instructions to the corresponding support system so that the support system can complete the service activation of the business capability combination scheme.

[0007] The beneficial effects of the VBF-based self-service system for telecom operators provided by this invention are as follows: This invention encapsulates existing operator support capabilities into independent virtualized service function units (VNFs) through a VBF encapsulation module and publishes them to an online marketplace. This allows industry customers to directly browse and select these VNFs through a portal module, improving the visibility and accessibility of product capabilities. The VBF orchestration module allows industry customers to independently select at least two target VNFs and define their combination logic to generate VNF combinations that meet their specific needs, significantly shortening the product combination design cycle and improving solution accuracy. The solution processing module automatically verifies and standardizes the VNF combination solutions, generating standardized service orders and reducing errors and inconsistencies that may arise from manual intervention. The service activation module automatically generates and sends activation instructions to the corresponding support system based on the standardized service orders, achieving rapid and automated activation of VNF combination solutions. This significantly improves the overall response speed, operational efficiency, and customer satisfaction of government and enterprise services.

[0008] Based on the above solution, the VBF-based self-service system for operator industry customers of the present invention can be further improved as follows.

[0009] Furthermore, the VBF encapsulation module configures parameter templates for each virtualization service function unit, and each parameter template is used to configure the configurable attributes of the corresponding virtualization service function unit.

[0010] The beneficial effects of adopting the above-mentioned further solution are as follows: By configuring parameter templates for each virtualized business function unit, industry customers can flexibly set configurable attributes according to their actual needs, thereby achieving personalized customization of encapsulation support capabilities. This design improves the adaptability and reusability of virtualized business function units, enabling the same unit to serve different business scenarios through parameter adjustments. At the same time, standardized parameter templates provide clear guidance for industry customers' configuration operations, reducing configuration errors and misunderstandings, and ensuring the accuracy and reliability of subsequent business capability combination schemes and standardized business order generation.

[0011] Furthermore, the portal module includes a customer authentication unit, which is used to verify the identity information of industry customers and grant them access to the online marketplace.

[0012] The beneficial effects of adopting the above-mentioned further solution are as follows: The customer authentication unit verifies the identity information of industry customers and grants them access to the online mall, providing necessary security access control for the entire self-service system. This feature ensures that only authenticated and legitimate industry customers can browse and select virtualized business function units in the online mall, effectively preventing unauthorized access and information leakage. Simultaneously, the authentication-based permission granting allows customers from different industries to access a range of products and services that match their identity and contracts, ensuring the standardization and accuracy of business management and establishing a reliable foundation for subsequent online orchestration and ordering.

[0013] Furthermore, the combinational logic provided by the VBF orchestration module includes at least one of sequential execution logic, parallel execution logic, and conditional execution logic. The VBF orchestration module orchestrates the process of at least two target virtualization business function units according to the combinational logic selected by the industry customer.

[0014] The beneficial effects of adopting the above-mentioned further solutions are as follows: The sequential execution logic, parallel execution logic, and conditional execution logic provided by the VBF orchestration module enable industry customers to build flexible and complex business processes for selected virtualized business function units. Sequential execution logic ensures strict dependencies and order in business steps; parallel execution logic supports the simultaneous execution of multiple units to improve efficiency; and conditional execution logic allows for dynamic selection of execution paths based on runtime data. This graphical and diverse process orchestration capability enables the generated business capability combinations to accurately match the ever-changing actual business scenarios of industry customers, greatly enhancing the flexibility of self-service design and the adaptability of business support.

[0015] 2) Secondly, the present invention also provides a self-service method for telecom operator customers based on VBF, the specific technical solution of which is as follows: The operator's existing multiple support capabilities are encapsulated into independent virtualized service function units, and the encapsulated virtualized service function units are published to the online store. Showcase to industry clients the various virtualized business functionalities already released in the online marketplace; Receive at least two target virtualization service function units selected by industry customers from multiple virtualization service function units, and orchestrate the at least two target virtualization service function units according to the combination logic defined by the industry customers to generate a service capability combination scheme; The business capability combination scheme is validated and standardized to generate standardized business orders; Activation instructions are generated based on standardized business orders and sent to the corresponding support systems so that the support systems can complete the activation of the business capability combination scheme.

[0016] Based on the above solution, the self-service method for operator industry customers based on VBF of the present invention can be further improved as follows.

[0017] Furthermore, the VBF encapsulation module configures parameter templates for each virtualization service function unit, and each parameter template is used to configure the configurable attributes of the corresponding virtualization service function unit.

[0018] Furthermore, it also includes: verifying the identity information of industry customers and granting them access to the online marketplace.

[0019] Furthermore, the combinational logic includes at least one of sequential execution logic, parallel execution logic, and conditional execution logic, and the process orchestration is performed on at least two target virtualization business function units according to the combinational logic selected by the industry customer.

[0020] 3) In a third aspect, the present invention also provides an electronic device, the electronic device including a processor coupled to a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor, so as to enable the electronic device to implement any of the above-mentioned VBF-based operator industry customer self-service methods.

[0021] 4) In a fourth aspect, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-mentioned VBF-based operator industry customer self-service methods.

[0022] It should be noted that the beneficial effects of the technical solutions of the second to fourth aspects of the present invention and their corresponding possible implementations can be found in the above description of the technical effects of the first aspect and its corresponding possible implementations, and will not be repeated here. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments of the present invention will be briefly introduced below: Figure 1 This is a schematic diagram of the structure of a VBF-based customer self-service system for the telecom operator industry, according to an embodiment of the present invention. Figure 2 A product category diagram for operations targeting industry clients; Figure 3 This is a schematic diagram illustrating the complete architecture and data flow process of a self-service system for telecom operators based on virtualized business function units. Figure 4 This is a schematic diagram of a self-service method for telecom operator customers based on VBF, according to an embodiment of the present invention. Detailed Implementation

[0024] The principles and features of the present invention are described below. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0025] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0026] like Figure 1 As shown in the figure, an embodiment of the present invention provides a VBF-based self-service system for operators' customers, including a VBF encapsulation module, a portal module, a VBF orchestration module, a solution processing module, and a service activation module. The VBF encapsulation module is used to encapsulate multiple existing support capabilities of the operator into independent virtualized service function units, and to publish the encapsulated virtualized service function units to the online marketplace. The specific implementation process is as follows: 1) Existing business support systems of the operator, such as billing systems, customer relationship management systems, service activation systems, and network resource management systems, each provide specific business processing functions. Technical personnel need to thoroughly analyze the application programming interfaces (APIs) or service interfaces of these systems to identify each functional unit that can be independently called and managed. These functional units constitute the original support capabilities to be encapsulated; they may exist in the form of software code modules, application programming interfaces (APIs), or microservices. This step requires a comprehensive review and definition of the input parameters, output results, processing logic, and dependencies on external systems of the support capabilities.

[0027] 2) Based on the analysis of the original supporting capabilities, a unified abstract model needs to be established. This model describes each supporting capability as a self-contained, independently deployable and manageable software entity. The definition process includes assigning a globally unique identifier to each virtualization business function unit, setting a clear function name, and writing detailed function description documents. More importantly, it is necessary to accurately define the technical interface specifications of the virtualization business function units, including calling protocols, data formats, and response specifications in success and exception situations. Through this abstraction, supporting capabilities from different technical backgrounds and physical systems are standardized into virtualization business function units with a consistent interaction method.

[0028] 3) To enable virtualization service function units to flexibly adapt to the diverse needs of industry clients, a parameter template needs to be designed for each unit. The parameter template is a structured definition file that lists and describes all attributes of the virtualization service function unit that can be configured by industry clients at the time of subscription. For example, for a "Corporate SMS Notification" virtualization service function unit, its parameter template might include configurable items such as "Daily Sending Limit," "Signature Content," and "Whether to Enable Status Reporting." Technical personnel need to define the data type, value range, default value, and whether each configurable attribute is required. This parameter template will then be integrated into the metadata of the virtualization service function unit.

[0029] 4) Once the virtualized service function unit (SFMU) has been packaged and its parameter templates configured, it needs to be deployed to the operator's trusted operating environment. The deployment process typically utilizes cloud-native technologies, such as building the SFMU into a container image and deploying it on a container management platform. After deployment, the SFMU's specific access endpoint information, functional description, and associated parameter template information need to be registered in a centralized capability directory or registry. This registry records a list of all available SFMUs and their technical metadata, providing a foundation for discovery and addressing for subsequent orchestration and invocation.

[0030] 5) The information of successfully registered virtualized business function units needs to be synchronized to the backend of the online marketplace for industry clients. In the product management interface of the online marketplace, operators can call the registration center's API to obtain a list of publishable virtualized business function units. Operators configure market attributes for the selected virtualized business function units, such as setting the display name, category tags, pricing strategy, service level agreement description, and user documentation. After configuration, operators execute the publishing operation, and the virtualized business function unit will appear as a sellable and selectable "product" on the online marketplace page for industry clients to browse and choose from.

[0031] Among them, operators refer to corporate entities that provide communication services and related businesses within telecommunications networks. These companies possess communication network infrastructure covering a wide area and have obtained operating licenses in accordance with the law, providing individual users, households, and various enterprises, governments, and other organizations with a variety of services such as voice calls, SMS, mobile data access, leased lines, cloud computing, and information applications. China Mobile, China Telecom, and China Unicom are typical examples of operators.

[0032] Support capabilities refer to the specific business processing or resource management functions possessed by various business and operational support systems within an operator. These functions are fundamental for operators to conduct business, serve customers, and manage the network. Examples include real-time billing capabilities generated from the billing system, customer information query and update capabilities generated from the customer relationship management system, automatic broadband service activation capabilities generated from the service activation system, and bandwidth adjustment capabilities generated from the network management system. Support capabilities typically exist in the operator's back-end systems in the form of software code, service interfaces, or automated processes.

[0033] A virtualization business function unit (VFU) is a software entity formed by standardizing and encapsulating a discrete yet complete supporting capability. Through abstraction and encapsulation techniques, it hides the implementation details of the underlying supporting capabilities, exposing a unified and standardized interface. A VFU contains executable functional code, a clear technical interface specification, and a parameter template defining adjustable options. Its design goal is to achieve loose coupling and reusability, allowing multiple different VFUs to be flexibly combined like building blocks to construct complex composite business solutions.

[0034] The online marketplace is a digital self-service portal platform provided by operators to industry customers. Presented as a webpage or application, this platform offers a centralized online space for showcasing and selling virtualization service functionalities and other digital products. Industry customers can browse product catalogs, view feature details, configure product options based on parameter templates, combine multiple virtualization service functionalities into solutions, and complete online ordering and payment. The online marketplace serves as a direct bridge connecting the operator's packaged capabilities with the needs of industry customers.

[0035] The portal module is used to showcase multiple virtualized business function units that have been published in the online marketplace to industry clients. The specific implementation process is as follows: 1) Industry clients access the unified resource locator (URL) of the government and enterprise portal website provided by the operator via a web browser or dedicated client. The portal module loads the login page, and the client enters valid corporate account and password credentials. The portal module sends the credentials information to the client authentication unit in the backend for verification. The verification process includes verifying the correctness of the account and password, checking whether the account status is normal, and confirming the client category and permissions of the account. After successful verification, the client authentication unit generates a secure session token and returns it to the portal module. The portal module uses this token to establish a secure access session for the current industry client and, based on the permission policy, determines that the client has the right to access the corresponding virtualized business function unit product catalog and functions in the online marketplace.

[0036] 2) After an industry customer successfully logs in and enters the main interface of the online marketplace, the portal module needs to obtain the latest information on displayable products. The portal module's backend service will initiate a query request to the online marketplace's product management backend or unified capability directory service. This request typically carries the industry customer's session token and possible customer tag information for filtering and personalized display. Upon receiving the request, the online marketplace backend queries the database for all virtualized business function unit records with a status of "Published" and visible to that industry customer. The query results include basic metadata for each virtualized business function unit, such as the unit's unique identifier, display name, function description, product category icon, basic price information, and associated parameter template identifier.

[0037] 3) After receiving the list of virtualization business function units' metadata from the backend, the portal module's front-end application begins organizing a visual display. The front-end application renders the list of virtualization business function units according to a pre-defined page layout template. A common display method is a grid view or list view, where each virtualization business function unit is presented as an independent "product card." The product card clearly displays the virtualization business function unit's icon, display name, and a concise description of its function. Simultaneously, the page typically provides a category navigation sidebar or top tabs. This category information comes from the "Product Category" field in the virtualization business function unit's metadata, such as "Communication Capabilities," "Cloud Computing," and "Internet of Things." Industry customers can quickly browse a collection of virtualization business function units in a specific field by clicking on categories.

[0038] 4) To help industry clients quickly locate virtualization business function units among a vast array of options, the portal module integrates search and filtering components. A search box is prominently displayed on the page, allowing clients to enter keywords such as "SMS" or "video conferencing." The portal module's front-end or back-end services perform fuzzy matching on metadata such as the virtualization business function unit's display name, function description, and keyword tags, and return a list of matching results in real time. In addition to searching, the page also provides an advanced filtering panel. Industry clients can filter based on certain attributes of the virtualization business function units, such as selecting those that "support on-demand billing." The portal module dynamically refreshes the list, displaying only virtualization business function units that meet all selected filter criteria.

[0039] 5) When an industry customer shows interest in a specific virtualization service function unit, they can click on the corresponding product card. The portal module will navigate to the dedicated details page for that virtualization service function unit. The details page retrieves and displays complete and detailed information about the virtualization service function unit by again calling the backend service. This includes detailed functional documentation, application scenario introductions, technical specifications, service level agreement terms, pricing details, and user reviews. Most importantly, the details page integrates a parameter configuration preview area. The portal module dynamically generates a configuration form based on the parameter template definition associated with the virtualization service function unit. For example, if the parameter template defines a configurable attribute for "storage capacity," the details page will render a dropdown selection box labeled "storage capacity" and fill in predefined options from the template such as "50GB," "100GB," and "200GB." Industry customers can learn about and try configuring the virtualization service function unit through this preview area without immediately placing an order, thus making a more accurate selection decision.

[0040] Industry clients refer to enterprises, government agencies, and other organizational clients who purchase and use communication services and IT solutions from telecom operators on a long-term basis. Unlike individual consumers, industry clients have larger-scale and more complex business needs, typically involving deep integration of the operator's communication network capabilities, cloud computing resources, platform services, and their own business processes. For example, a chain retail enterprise might simultaneously need an operator's IoT SIM card to connect the sensing devices in all its stores, a dedicated enterprise line to ensure secure and stable data communication between headquarters and branches, and cloud call center services to handle massive customer inquiries. A typical characteristic of industry clients is that their needs have clear industry attributes, and they expect customizable, integrable, manageable, and service-assured overall solutions.

[0041] The VBF orchestration module is used to: receive at least two target virtualization service function units selected by industry customers from multiple virtualization service function units, and orchestrate the at least two target virtualization service function units according to the combination logic defined by the industry customers to generate a service capability combination scheme. The specific implementation process is as follows: 1) After browsing the online marketplace in the portal module, industry clients can enter the visual orchestration workspace provided by the VBF orchestration module by clicking the "Start Orchestration" button or a similar function. The workspace is typically divided into two main panels: a library panel of available virtualization business function units (VBUs) and an orchestration canvas panel. The VBU library panel dynamically loads and displays a list of all VBUs that the industry client has access to and can order. Industry clients drag and drop at least two target VBUs from the VBU library onto the orchestration canvas on the right. Each VBU placed on the canvas is represented by a graphical node, displaying the unit's abbreviated name and icon.

[0042] 2) After at least two target virtualization functional units (VFUs) are placed on the orchestration canvas, industry customers need to define the execution order and data transfer relationships of these units. The VBF orchestration module provides a connection line drawing tool. Industry customers use the mouse to drag from the output anchor point of one VFU node to the input anchor point of another VFU node to draw a directed connection line. This connection line represents a data dependency, indicating that the output data of the previous VFU can be used as the input data of the subsequent VFU. Customers can define specific data fields to be transferred for each connection line, for example, specifying that the "verification result" field output by unit A is transferred to the "input status" field of unit B. By drawing multiple connection lines, industry customers can construct a directional data flow graph and initially determine the execution chain of multiple VFUs.

[0043] 3) Beyond linear sequential execution, the VBF orchestration module allows industry clients to define more complex combinational logic to control business flows. The module provides pre-defined logic control nodes, such as "parallel branches," "conditional statements," and "loops." Industry clients drag these logic control nodes from the component library into the orchestration canvas. Then, they connect virtualized business function unit nodes to the logic control nodes via connectors, thereby constructing a flowchart with branching, parallel, or looping structures. For example, an industry client can place a "conditional statement" node, leading to two branches: one connecting to the "send SMS notification" virtualized business function unit, and the other to the "send email notification" virtualized business function unit, and configure the condition to determine which path to execute. The VBF orchestration module guides clients through the construction of the entire process structure via a graphical interface and performs real-time logic validation to prevent unexecutable infinite loops or dead ends.

[0044] 4) Each virtualized business function unit has its own independent parameter template to define the configuration required for its operation. In the orchestration context, industry clients need to specify specific values ​​for the runtime parameters of each virtualized business function unit node in the flowchart. The VBF orchestration module provides a parameter configuration panel for each virtualized business function unit node on the canvas. Clients can manually enter fixed values, or choose to dynamically bind parameter values ​​to the output values ​​of other nodes in the process, or to the initial input variables of the entire business process. For example, clients can directly map the "Report Receiving Email" parameter of the "Generate Report" unit to the "Administrator Email" variable entered by the client at the beginning of the process. This dynamic parameter mapping capability makes the orchestrated business process no longer an isolated collection of units, but an executable whole with interconnected parameters and data.

[0045] 6) Once the industry client completes and confirms the visual orchestration, the "Generate Solution" operation is triggered. The background service of the VBF orchestration module begins working, parsing and compiling the entire orchestration model on the canvas. The module traverses all nodes and connections, extracting the execution sequence, data dependencies, control logic, and parameter mapping relationships of the virtualization business function units. This information is organized according to a predetermined structured data format, such as converting it into a JSON or YAML configuration file. This configuration file fully defines the composite business model composed of multiple virtualization business function units combined according to specific logic; it is the final generated business capability combination solution. The solution not only contains the identifiers of all target virtualization business function units that constitute the solution but also precisely describes their calling relationships, execution conditions, and data interaction specifications, forming a blueprint that can be verified and executed by subsequent solution processing modules.

[0046] A business capability combination solution refers to a complete and executable composite business solution formed by integrating multiple independent virtualized business function units according to specific business logic and data flow relationships through the VBF orchestration module. It transcends the atomic capabilities provided by a single virtualized business function unit, achieving comprehensive functionality to meet the complex scenario needs of industry customers through orderly combination and collaboration. A business capability combination solution is essentially a structured process definition document that clearly specifies which virtualized business function units are included in the solution, the order or conditions in which these units are executed, how data is transferred between units, and the specific operating parameters of each unit in this combination. This solution is a direct result of the industry customer self-service design and also the authoritative technical basis driving subsequent automated order generation and business activation.

[0047] The solution processing module is used to verify and standardize business capability combination solutions, and generate standardized business orders. The specific implementation process is as follows: 1) The solution processing module receives business capability combination solution data packets submitted by the VBF orchestration module through an internal system interface. This data packet is typically a structured file describing the composition, orchestration logic, and parameters of virtualized business function units. The solution processing module starts a parsing engine to parse the data packet. The parsing engine reads the solution's global metadata, such as the solution identifier, creation customer information, and timestamp. Next, the engine traverses each virtualized business function unit node defined in the solution, extracting its unique identifier, version number, and instantiation parameter configuration within the solution. Simultaneously, the parsing engine reconstructs the inter-unit connections and composition logic defined in the solution, transforming them into an internally processable flowchart object model, laying the data structure foundation for subsequent deep validation.

[0048] 2) Based on the parsed internal model, the solution processing module initiates the first round of verification. This round of verification primarily focuses on the feasibility of technical implementation. The module queries the virtualization business function unit capability catalog to verify whether each virtualization business function unit identifier referenced in the solution actually exists, whether its current status is "available," and whether its version is supported. Next, the module verifies the data dependencies between units, checking whether the output data type of the upstream virtualization business function unit matches the input data type requirements of the downstream unit. For example, if a unit outputs "image file," and its downstream connection requires "text data," a type mismatch error will occur. The module also checks for logical errors in the flowchart, such as undefined start nodes, unreachable orphaned nodes, or illegal circular dependencies. Any verification failure will generate a clear error code and description, which will be fed back to the front end to guide industry customers in modifying the business capability combination solution.

[0049] 3) After passing the technical verification, the solution processing module initiates a second round of verification based on business rules. The module calls the customer management system and product policy rule base. It verifies, based on the industry customer's identity, whether the customer is permitted to order specific categories of virtualization service function units included in the solution, and whether their corporate credit limit is sufficient to support the estimated cost of the solution. Simultaneously, the module applies preset business policy rules, such as checking whether the combination of virtualization service function units in the solution conforms to the product sales strategy, whether mutually exclusive products are incorrectly combined, or whether the overall configuration of the solution exceeds the maximum resource quota allowed for that customer level. This step ensures that the service capability combination solution is not only technically feasible but also fully complies with the operator's business rules and customer contract constraints.

[0050] 4) For virtualized business function units involving specific physical or virtual resources such as computing, storage, and networking, the solution processing module needs to perform a resource availability check. Based on the instantiation parameters of each virtualized business function unit in the solution, such as the specified data center region, the required number of CPU cores, memory size, or network bandwidth, the module generates an aggregated resource requirement list. Subsequently, the module queries the resource management system or inventory system to verify whether there are sufficient idle resources in the target resource pool to meet the requirements of the list. If resources are sufficient, in some implementations, the module may trigger a brief resource pre-allocation operation to prevent resources from being occupied by other requests before final order confirmation. Resource verification failure means that immediate activation is not possible; this information needs to be explicitly communicated to the customer.

[0051] 5) Once the business capability combination scheme passes all validations, the scheme processing module begins converting it into a standardized order format. The module has a standardized order template that defines all the fields an order must contain. The module maps and populates this template with information obtained during parsing and validation. This includes order header information, such as order number, customer number, and submission time; and order details, i.e., the ordering information for each virtualized business function unit in the scheme, including unit identifier, sales item code, specific values ​​of instantiation parameters, and position number within the scheme's workflow. Simultaneously, the logical relationships between units defined in the scheme are converted into standardized process description language fragments, serving as the order's "installation script" or "activation blueprint" attachment. Finally, the scheme processing module serializes all the populated data into a complete, structured data entity—the standardized business order—and persistently stores it in the order database, marking its status as "pending activation." This order is also associated with the original business capability combination scheme for subsequent traceability.

[0052] The standardized business order is an authoritative, structured data entity output by the solution processing module. It comprehensively and accurately records all key information of a purchase request initiated by an industry customer for a specific combination of service capabilities. This order follows the operator's unified internal order data model definition and includes a standard order header, customer information, order item details, tariff plan, service parameters, and activation instruction blueprint. The significance of the standardized business order lies in transforming the flexible, graphical service capability combination scheme from the front end into a unified language that can be unambiguously understood and executed by various backend support systems. It serves as a crucial conversion interface between customer needs and production system instructions, ensuring the accuracy of information transmission and the feasibility of automated processing from sales to delivery, and is the single source of fact driving the subsequent service activation process.

[0053] The service activation module is used to: generate activation instructions based on standardized business orders, and send the activation instructions to the corresponding support system, so that the support system can complete the service activation of the business capability combination scheme. The specific implementation process is as follows: 1) The business activation module acquires standardized business orders with a status of "Pending Activation" by monitoring changes in the order database or receiving direct notifications from the solution processing module. The module loads the complete standardized business order data and starts the order parsing engine. The parsing engine first reads the order header information to confirm the order number, associated industry customer identifier, and global priority of the order. Next, the engine deeply parses the order details, identifying each virtualized business function unit order item included in this business capability combination solution, extracting the unique sales item code, specific values ​​of instantiation parameters, and the logical position identifier of the unit in the combination solution process for each unit. Simultaneously, the engine parses the standardized process description attached to the order, reconstructing the execution dependency graph between virtualized business function units, clarifying which units need to be activated in parallel and which units must wait for the successful activation of the preceding unit before starting.

[0054] 2) Based on the parsed dependency graph, the service activation module performs topology sorting and plans one or more sequentially executable instruction batches. For each virtualized business function unit order item, the module needs to generate its corresponding atomic activation instruction. The generation process relies on an instruction template library. The module matches a predefined instruction generation template in the template library according to the sales item code of the virtualized business function unit. This template defines the instruction actions, parameter mapping rules, and the interface address of the target support system that the activation instruction must include for this type of unit. The module fills the parameter slots of the instruction template with the instantiation parameter values ​​of the unit in the order, according to the rules defined in the template, thereby generating a specific, executable atomic activation instruction. This instruction contains all the information needed to instruct a specific support system to perform a specific activation operation.

[0055] 3) Because different support systems may use different communication protocols and data formats, the service activation module needs to perform command adaptation. The module maintains a support system adapter library. After generating an atomic activation command, the module calls the corresponding adapter based on the target support system type specified in the command. The adapter is responsible for converting the internally unified command data model into a specific format that the target support system can recognize. For example, for a Web Service-based support system, the adapter encapsulates the command into a specific SOAP message; for a RESTful API-based support system, the adapter assembles it into an HTTP request and sets the correct request headers, request body, and authentication token. The adaptation process ensures that each command is delivered accurately in the way the support system expects.

[0056] 4) The service activation module asynchronously distributes encapsulated activation instructions to the corresponding supporting systems via the enterprise service bus or dedicated message middleware, according to the planned instruction batches and sequence. The module creates an execution tracing task for each issued atomic instruction and records information such as instruction identifier, issuance time, and target system. Subsequently, the module enters monitoring mode. It listens for callback notifications from each supporting system or actively polls the execution status interface of the supporting systems. When it receives feedback on the execution result of an instruction, the module updates the status of the corresponding tracing task, recording it as "success," "failure," or "in execution." The module's logic control unit makes judgments based on the dependency graph: if an instruction on a critical path fails to execute, the module will stop issuing subsequent batches of instructions and attempt to retry or trigger an exception handling process according to a preset strategy; if an instruction executes successfully, the module checks whether its subsequent dependent instructions have met the execution conditions and drives the triggering of the next batch of instructions.

[0057] 5) Once all atomic activation commands have been issued and executed, meaning all involved virtualization business function units have completed resource allocation, configuration activation, or service deployment in their respective supporting systems, the business activation module performs final result aggregation. The module collects the final execution status of all atomic commands. If all are successful, the module determines the activation status of the entire business capability combination solution as "activated successfully." The module generates an activation completion report, recording the activation process, timestamps of each stage, and resource instance identifiers. Subsequently, the module synchronizes the overall success status back to the order database, updating the status of standardized business orders to "activated." Simultaneously, the module may need to send notifications to the customer relationship management system to update the customer product list and to the billing system to trigger billing. If partial failures occur, the module decides, based on its policy, whether to automatically roll back or mark the order as "partially activated but failed," recording detailed error information and notifying operations personnel for manual intervention.

[0058] Support systems are a collective term for the backend professional software systems within an operator used to implement specific business functions, manage network resources, or provide operational services. These systems are typically deployed in the operator's core data center and form the technological foundation for the operation of various telecommunications services. Each support system is responsible for a relatively independent professional area. For example, the billing system handles user accounts, fee calculations, and billing; the service activation system issues configuration commands to network devices to enable broadband or leased line access; the customer relationship management system stores and manages customer information and service agreements; and the resource management system is responsible for scheduling and allocating physical and virtual network devices, servers, ports, and other resources. In a VBF-based self-service scenario, the underlying capabilities of a pre-packaged virtualized business function unit ultimately depend on the collaborative work of one or more support systems. The activation commands generated by the service activation module are ultimately received and executed by these support systems.

[0059] Optionally, in the above technical solution, the VBF encapsulation module configures parameter templates for each virtualization service function unit. Each parameter template is used to configure the configurable attributes of the corresponding virtualization service function unit. The specific implementation process is as follows: 1) For a specific support capability to be packaged, developers and business experts need to conduct collaborative analysis. The analysis focuses on which operational parameters of this support capability can and are suitable for industry customers to select and set during ordering when providing services externally. These parameters originate from the underlying business logic and technical implementation of the support capability. For example, for a "cloud host" support capability, its configurable attributes might include "operating system image type," "number of CPU cores," "memory capacity," "system disk size," "number of data disks," and "virtual private cloud to which it belongs." For a "bulk SMS" capability, its configurable attributes might include "default signature," "sending speed limit," and "whether to enable retry on failure." The analysis process needs to exhaustively list all possible adjustable items and determine a clear business name and internal code for each attribute.

[0060] 2) After defining the attribute set, detailed technical specifications need to be defined for each attribute in the parameter template. This includes determining the data type of the attribute, such as string, integer, boolean, enumeration list, or date. For enumeration type attributes, all valid optional values ​​need to be explicitly listed; for example, the optional values ​​for the "Operating System Image Type" attribute might be "CentOS 7.9", "Ubuntu 20.04", or "Windows Server 2019". Furthermore, constraint rules must be defined for each attribute, including the value range for numeric attributes, length limits or regular expression format requirements for string attributes, and whether the attribute is required. Simultaneously, a reasonable default value needs to be set for each attribute, which the system will automatically adopt when the industry customer does not explicitly configure it. These specifications and constraints will be encoded into the parameter template definition to ensure the validity of the data collected by the front end and the correctness of the back end execution.

[0061] 3) Based on the analysis and design results of the first two steps, the VBF encapsulation module needs to generate a machine-readable parameter template definition file. This file is described using a structured schema language such as JSON Schema or XML Schema. In this definition file, all configurable properties of the virtualization business function unit are organized into a hierarchical structure. Each property is an independent node, and the node contains multiple fields describing the property, such as "property identifier," "display label," "data type," "constraints," "default value," and "help message." The template definition may also support conditional dependencies between properties; for example, the "data disk size" property only needs to be displayed and validated when the "enable data disk" property is set to "yes" by the customer. This structured parameter template metadata is the authoritative source for all subsequent system components to understand the configuration method of this virtualization business function unit.

[0062] 4) During the encapsulation and deployment of virtualized business function units, the VBF encapsulation module calls the template management service to strongly associate the created parameter template metadata definition file with the unique identifier of the virtualized business function unit. This binding relationship is recorded in the metadata repository or capability directory of the virtualized business function unit. The binding operation signifies that the standardized description of the virtualized business function unit is complete. It not only includes executable code or service interfaces but also a clear "user manual," namely the parameter template, which specifies how to personalize its capabilities. Subsequently, when the online marketplace displays the unit or the VBF orchestration module processes the unit, it can retrieve its parameter template by querying this binding relationship and dynamically generate a configuration interface based on the template.

[0063] 5) VBF encapsulation modules typically provide a management interface that allows operations personnel or authorized developers to maintain published parameter templates. Maintenance operations include updating existing template versions, such as adding a new configurable property, modifying the constraint scope of a property, or updating help prompts. When a template changes, the module needs to manage the template's version number and assess the impact of the change on subscribed services, deciding whether to allow online hot updates or to create a new version of the virtualized business function unit. This management functionality ensures that parameter templates can be continuously optimized as business needs and support capabilities evolve.

[0064] The parameter template is a structured metadata definition file specifically designed to describe a series of attributes that industry customers can customize when ordering or using a particular virtualization business function unit. The parameter template details the business meaning, technical data type, input validation rules, selectable value range, default value, and display labels and prompts on the user interface for each configurable attribute. It serves as part of the standardized description of the virtualization business function unit, acting as a crucial bridge between underlying fixed functions and flexible, configurable products on the front end. Both the online marketplace and the VBF orchestration module rely on parameter templates to dynamically generate correct configuration forms, guiding industry customers through service customization.

[0065] The configurable attributes of a virtualization service function unit refer to the parameters or options that external users can adjust and set according to their own needs during the implementation of its core business functions. These attributes are variable control points abstracted and exposed from the underlying original support capabilities when the virtualization service function unit is encapsulated. By changing the values ​​of these attributes, the behavior, performance, capacity, or presentation of the virtualization service function unit can be customized without changing its basic functions. For example, for a load balancing virtualization service function unit, its configurable attributes may include "balancing algorithm," "health check cycle," and "maximum number of connections." The existence of configurable attributes is the foundation for the flexible combination and on-demand service of virtualization service function units.

[0066] Optionally, in the above technical solution, the portal module includes a customer authentication unit, which is used to verify the identity information of industry customers and grant them access to the online marketplace. The specific implementation process is as follows: 1) Industry customers access the unified login page of the operator's enterprise portal via a web browser. On the login page, customers need to fill in their identity information in designated input boxes, typically including at least a corporate account and password. The corporate account is usually a unique identifier assigned by the operator when the customer conducts business, such as a corporate customer code or registered mobile phone number. The password is a key set by the customer or initially assigned. After filling in the information, the industry customer clicks the "Login" button on the login page. At this time, the front-end code of the portal module collects the account and password data from the form and, for security reasons, submits the credential information to the service interface of the back-end customer authentication unit through a secure socket layer encrypted channel.

[0067] 2) The client authentication unit's backend service interface receives the login request data packet from the frontend. The service interface first performs basic parsing of the data packet, extracting the username and password fields. Next, the service interface performs necessary input cleaning and security filtering to prevent malicious injection attacks. For the password field, the client authentication unit immediately calls a hash algorithm to convert the password transmitted from the frontend (which may have been encrypted by the frontend) into an irreversible hash value. This hash value will be used for subsequent comparisons, rather than directly using or storing the plaintext password; this is a crucial step in ensuring password security. After preprocessing, the client authentication unit prepares to perform substantive identity verification.

[0068] 3) The customer authentication unit initiates a query to the operator's core customer relationship management system or unified customer data database based on the extracted enterprise account. The query request carries the enterprise account information to obtain the unique customer identifier, status, and stored password hash value registered in the system. The customer authentication unit compares the received database return results with the login information. The comparison mainly includes three aspects: first, checking if the account exists; second, checking if the customer status corresponding to the account is "normal," rather than "cancelled," "frozen," or "suspended due to unpaid fees"; and third, and most importantly, comparing the hash value calculated using the same hash algorithm for the password submitted during this login with the correct password hash value stored in the database for that account. Only when the account exists, the status is normal, and the password hash value is completely consistent can the credential validity verification be passed.

[0069] 4) After successful identity verification, the customer authentication unit needs to determine which resources the industry customer is authorized to access. The customer authentication unit then queries the customer relationship management system or access control system to obtain the permission policies associated with the customer's identifier. These policies define the product catalogs the customer can access, the categories of virtualized business function units they can operate, and the related data scope. For example, an education industry customer might be authorized to access virtualized business function units related to "online education cloud resources," but not related to "industrial IoT platform." Permission determination is based on preset roles and access control lists, ensuring that industry customers can only see and operate the content they are authorized to access after logging in.

[0070] 5) After successful authentication and authorization verification, the client authentication unit needs to create a secure session context for this login. The client authentication unit generates a globally unique, high-strength session token, typically a long random string. This session token is associated with the industry client's unique identifier, login time, validity period, and the list of permissions obtained, and this session data is persistently stored in a distributed cache server with a reasonable expiration time. Simultaneously, the client authentication unit returns the generated session token to the industry client's browser via a secure HTTP response, either by setting a secure cookie or by including it in the response body. The browser will then carry this session token when subsequently accessing any page on the online marketplace to prove its authentication status.

[0071] 6) Upon receiving the successful response and session token from the client authentication unit, the portal module's front-end application securely stores the token. Based on any basic client information or permission prompts that may be included in the response, the front-end application updates the user interface, for example, displaying "Welcome, XX Company." Subsequently, the front-end application automatically redirects the browser page navigation to the online store's homepage or default view. After this, all requests from industry clients within the online store will have their session tokens validated by the portal module's back-end service. The back-end service verifies the token's validity and expiration by querying cached session data and dynamically filters the virtualized business function unit content displayed in the online store based on the permission list bound to the session, thus completing a full closed loop from authentication to authorized access.

[0072] The identity information of industry customers refers to a set of key data used to uniquely identify and verify the legitimate identity of an enterprise, government agency, or other organizational customer within the operator's system. This data is typically collected and allocated by the operator when a customer registers for network access or signs a service agreement, serving as the digital key for the customer to access the operator's dedicated service platform. The most crucial identity information consists of the enterprise account and its corresponding password. The enterprise account can be an enterprise code assigned by the account manager, a unified social credit code registered in the operator's system, or a bound administrator's mobile phone number. The paired password is an authentication key known only to the customer. Furthermore, to enhance security verification, identity information may also include auxiliary elements such as dynamic SMS verification codes, digital certificates, or biometrics. After rigorous verification by the customer authentication unit, this identity information is the sole basis for determining whether access to the online marketplace is permitted and the scope of the customer's access permissions.

[0073] Optionally, in the above technical solution, the combinational logic provided by the VBF orchestration module includes at least one of sequential execution logic, parallel execution logic, and conditional execution logic. The VBF orchestration module orchestrates the process of at least two target virtualization business function units according to the combinational logic selected by the industry customer. The specific implementation process is as follows: 1) After entering the visual orchestration workspace of the VBF orchestration module, industry clients can not only drag and drop target virtualized business function units from the unit library, but also select the required composite logic nodes from a dedicated "Logic Components" panel. The panel clearly provides icon nodes representing different logic types; for example, a straight line icon with an arrow represents "sequential execution logic," an icon with multiple lines extending simultaneously represents "parallel execution logic," and a diamond-shaped decision box icon represents "conditional execution logic." Industry clients can drag and drop these logic control nodes to appropriate positions on the orchestration canvas according to their envisioned business process structure. Each logic control node is an independent graphical element that can be moved and connected like virtualized business function unit nodes.

[0074] 2) When industry clients need to run multiple virtualization functional units (VFUs) sequentially, sequential execution logic is used. The client connects the "start" node to the first VFU node using a connecting line. Then, a connecting line is drawn from the output anchor point of the first VFU node to the input anchor point of the second VFU node. This process is repeated to chain multiple target VFUs together. This chain-like path formed by the connecting lines embodies the sequential execution logic. The VBF orchestration module's backend model records this connection relationship and interprets it as a specific execution sequence. The generated business capability combination scheme stipulates that the execution of the next VFU can only be triggered after the previous VFU has successfully completed its execution.

[0075] 3) When industry customers need multiple virtualization business function units to start simultaneously and execute independently, parallel execution logic will be used. The customer places a "Parallel Start" logic control node on the canvas. Multiple connection lines extend from this "Parallel Start" node, connecting to different target virtualization business function unit nodes. These virtualization business function unit nodes are not directly connected; they all depend solely on the "Parallel Start" node. Similarly, at the end of these parallel branches, a "Parallel End" node can be placed to converge all branches. During parsing, the VBF orchestration module recognizes this fan-shaped branch structure and generates a parallel execution definition in the business capability composition scheme, indicating that all virtualization business function units connected from the "Parallel Start" node can be triggered and executed simultaneously without waiting for each other.

[0076] 4) When a business process requires executing different virtualized business function units based on different situations, conditional execution logic will be used. The customer places a "conditional judgment" logic control node at a decision point in the process. At this node, the customer needs to configure specific judgment condition expressions. For example, the condition expression might reference the output variable of the previous virtualized business function unit, such as "order amount > 10000". After configuration, two or more connection lines will emerge from the "conditional judgment" node, each representing a judgment result branch. The customer needs to specify the condition value that each branch line must satisfy. Then, different branch lines are connected to different target virtualized business function unit nodes. The VBF orchestration module ensures the correctness of the condition expression syntax and precisely describes this branch logic in the generated scheme, specifying that at runtime, the corresponding unique branch path will be selected for execution based on the actual calculation result of the condition expression.

[0077] 5) Industry clients can comprehensively utilize the above-mentioned multiple combination logics on a single orchestration canvas to construct complex flowcharts. For example, a step in a sequential process can be a parallel execution logic, and a conditional judgment logic can be connected at the end of a branch in the parallel execution. The graphical interface of the VBF orchestration module allows for such nested and mixed connections. After the client completes the orchestration, a generation command is triggered. The background engine of the VBF orchestration module scans and parses the entire canvas, identifies all node types and connections, and converts the graphical process into a structured process description language. This description language explicitly records each virtualized business function unit node, each logical control node, and the complete topology structure formed by their sequential, parallel, or conditional relationships. This structured description, containing rich definitions of combination logic, is the core part of the business capability combination solution that can ultimately be delivered to the solution processing module.

[0078] Sequential execution logic is a basic type of compositional logic that specifies the execution of multiple virtualized business function units in a strict sequential order. Under this logic, the business process forms a single, linear chain. Only after the previous virtualized business function unit completes its task and outputs a result will the next virtualized business function unit be started and executed. Sequential execution logic is suitable for business scenarios where there are strong dependencies between steps; for example, the "customer authentication" virtualized business function unit must be completed before the "query account information" virtualized business function unit can be executed. It ensures that the steps of the business process are well-ordered.

[0079] Parallel execution logic is a type of compositional logic that allows two or more virtualized service function units to be triggered at the same time and execute independently. These virtualized service function units have no dependency on execution order, and their execution processes overlap in time. Parallel execution logic is typically used to handle subtasks that can be performed simultaneously without interference, thereby shortening the overall business process execution time. For example, when activating a service plan, the "assign IP address" virtualized service function unit and the "configure firewall rules" virtualized service function unit can be executed in parallel.

[0080] Conditional execution logic is a type of compositional logic that determines which virtualized business function unit(s) to execute next based on the judgment results of one or more data conditions generated during the process. This logic introduces branching judgments into the process, enabling the business process to dynamically select and adapt. Conditional execution logic relies on a clear conditional expression, typically yielding a true or false result, used to select different branch paths. For example, based on the condition "whether the user level is VIP," it determines whether to execute the "priority customer service access" virtualized business function unit or the "normal queue queuing" virtualized business function unit.

[0081] In the field of mobile communications, the operation of a VBF-based operator customer self-service system can be illustrated through a specific scenario. Suppose a national hotel chain needs to quickly deploy a standardized communication and information service package for all newly opened branches. This package includes providing guests with secure and convenient Wi-Fi access and a stable office network for internal hotel operations. The specific steps include: 1) Operators standardize and encapsulate multiple independent supporting capabilities in the mobile communication network. For example, the "user mobile phone number SMS verification" capability is encapsulated as a virtualized service function unit (VNF) with a configured parameter template containing configurable attributes such as "SMS signature" and "verification code template ID". The "enterprise internet leased line activation" capability is encapsulated as another VNF, with its parameter template containing attributes such as "access bandwidth", "service level protocol level", and "installation address". Similarly, capabilities such as "bulk data package recharge" and "cloud firewall policy configuration" are also encapsulated as independent VNFs. The VBF encapsulation module publishes these encapsulated VNFs to the operator's enterprise online marketplace.

[0082] 2) The IT administrator of the hotel chain logs into the operator's portal website. The portal module includes a customer authentication unit that verifies the corporate account and password submitted by the administrator. After confirming that the hotel group is a legitimate industry customer of the operator, it grants the administrator access to the online marketplace. After successful login, the IT administrator enters the online marketplace interface. The portal module clearly displays all the virtualization service functional units published in the marketplace, such as "SMS Verification," "Enterprise Dedicated Line," "Data Top-up," and "Firewall Configuration," along with detailed function descriptions and parameter specifications.

[0083] 3) Based on the new hotel opening process, the hotel IT administrator selected at least two target virtualized business function units from the unit library and combined them in the visual orchestration interface of the VBF orchestration module. The administrator dragged and dropped the "SMS Verification" unit, "Enterprise Leased Line" unit, "Firewall Configuration" unit, and "Data Top-up" unit onto the orchestration canvas. The administrator then applied composition logic to orchestrate the process: defining sequential execution logic to execute the "SMS Verification" unit first to collect guest information; defining parallel execution logic to activate the "Enterprise Leased Line" unit and the "Firewall Configuration" unit simultaneously after successful verification; and finally defining conditional execution logic to determine whether the leased line activation is completed within 24 hours. If "yes," the "Data Top-up" unit is executed to provide a welcome data package to the first batch of guests; otherwise, the gifting step is skipped. The VBF orchestration module generates a complete "Hotel New Store Communication Service Package" business capability combination scheme based on these graphical definitions.

[0084] 4) After receiving the proposed business capability combination solution, the solution processing module initiates multiple rounds of verification. The module verifies the existence and availability of all virtualized business function units referenced in the solution; verifies whether the hotel group has the authority to order enterprise dedicated line services; verifies whether there are sufficient resources to open a dedicated line for the new store address; and verifies whether the package fee is within the hotel group's credit limit. Once all verifications pass, the solution processing module converts the graphical solution into structured data containing all technical parameters, execution order, and pricing details, thus generating a standardized business order.

[0085] 5) After receiving the standardized service order, the service activation module parses and generates atomic activation instructions. For the "SMS Verification" unit, instructions are generated and sent to the SMS gateway support system; for the "Enterprise Leased Line" unit, instructions are generated and sent to the transmission network management support system; for the "Firewall Configuration" unit, instructions are generated and sent to the cloud management platform support system. The service activation module executes the logic sequentially and in parallel according to the order defined in the order, sending these instructions in an orderly manner and monitoring the execution feedback from each support system. After all instructions are successfully executed, the service activation module confirms that the entire "Hotel New Store Communication Service Package" service capability combination scheme is activated and updates the order status. Ultimately, the hotel new store obtains a customized communication service scheme that is flexibly combined from multiple mobile communication basic capabilities and can be activated with one click.

[0086] The technical solution of the present invention will be further described through another embodiment, as follows: Referring to the ETSI specification (ETSI. Network functions virtualization (NFV) release 2), Network Functions Virtualization (NFV) is a concept related to network architecture. The x86 servers we commonly use are manufactured by hardware vendors and implement various functions after installing different operating systems and software. Traditional network devices do not adopt this model; routers, switches, firewalls, load balancers, and other devices each have their own independent hardware and software systems. NFV borrows from the x86 server architecture, encapsulating different network functions such as routers, switches, firewalls, and load balancers into independent modular software. By running different modular software on hardware devices, diverse network functions can be implemented on a single hardware device.

[0087] In the BSS (Business Support Service) domain, industry customers typically have complex IT needs, encompassing product combinations from multiple fields such as CT (Computer-Driven Systems), DT (Data Technology), and IT. The required support capabilities also span multiple systems and data centers. How to quickly combine, deploy, and sell these existing capabilities has always been a challenge for operators. This invention introduces the design concept of network virtualization into the business support domain. Combining the mature concepts of cloud-native, microservices, and containerization in current IT support development, it proposes the concept of virtualized business function units (VNUs). Each operator's support capability can be encapsulated as a separate VNU. This invention constructs a self-service system for operator industry customers based on VNUs. This system specifically includes a VBF (Virtualized Business Function) encapsulation module, a portal module, a VBF orchestration module, a solution processing module, and a service activation module. Through the VBF encapsulation module, multiple existing operator support capabilities are encapsulated as independent VNUs and published to an online marketplace. The portal module displays the multiple VNUs published in the online marketplace to industry customers. Industry clients, through the VBF orchestration module, select at least two target virtualization business function units (VFs) from multiple VFs, and orchestrate these units according to defined combination logic to generate a business capability combination scheme. The scheme processing module verifies and standardizes the business capability combination scheme, generating a standardized business order. The business activation module generates activation instructions based on the standardized business order and sends the instructions to the corresponding support system to complete the business activation of the business capability combination scheme. In this way, the support capabilities are encapsulated and placed in the government and enterprise online marketplace, facilitating orchestration and ordering for industry clients and enabling the rapid formation of support capability combinations.

[0088] At the system architecture level, the design and implementation of the operator industry customer self-service system based on virtualized service function units (BSS) references the framework concept of Network Function Virtualization (NFV). The main modules in the architecture framework correspond to the system functional components. Service virtualization corresponds to the virtualized service function unit in the system; it is the entity that encapsulates and presents capabilities. The service function virtualization infrastructure provides basic cloud and containerized environment support for the encapsulation, deployment, and operation of the virtualized service function unit. The service function orchestrator corresponds to the VBF orchestration module in the system, responsible for the self-service process combination and orchestration for industry customers. Concepts such as microservice management and elastic computing controllers are specifically reflected in the microservice encapsulation of supporting capabilities by the VBF encapsulation module, and the elastic management and control capabilities required by the service activation module during resource scheduling and command issuance. Through the collaboration of various modules, the entire system achieves standardized, commercialized, and self-service combination and delivery of supporting capabilities for the complex and heterogeneous BSS domain.

[0089] like Figure 2As shown, corresponding to the content structure and data flow logic displayed by the online mall carried by the portal module in this embodiment of the invention, the online mall provides government and enterprise customers with solutions and product browsing and sales functions, and collects operational feedback and realizes related recommendations during the product use, maintenance and operation phase. Its top-level design reflects a unified entry point and brand value proposition. The full range of products displayed in the online mall are systematically classified according to their characteristics, including traditional products such as basic communication services such as voice, data traffic, broadband, and IoT, digital intelligence products, and platform products. Furthermore, these products are organized into two paths that are easy for government and enterprise customers to understand and choose. The first is standard government and enterprise products that directly meet standardized needs, which include BO domain products such as insight, location, management, risk control, and marketing products, as well as M domain products such as office products. The second is non-standard government and enterprise product path that is oriented towards customization and deep integration. Its core is industry capability products, such as big data product sets, cloud-native product sets, and China Mobile Chain. The system integrates various capabilities, generated from big data development and DevOps systems built on production platforms such as Wutong Big Data and Panzhou Jiapanji Platform. Whether standard products or industry capabilities, they can all be packaged into independent virtualized business function units through the VBF encapsulation module in this invention and listed on the online marketplace. After browsing through the portal module, government and enterprise customers can flexibly arrange one or more selected virtualized business function units using the VBF orchestration module to form solutions that meet the needs of specific scenarios, such as trust and anti-fraud solutions for the financial industry or 5G industry solutions. They can then complete product orders or participate in bidding processes. Specific business examples include video network for elderly and asset care, and 5G e-signature. These solutions generate standardized business orders through the solution processing module, and are ultimately driven by the business activation module to complete business activation and delivery, entering the usage and operation phase. This achieves end-to-end support from product capability encapsulation, display, self-service combination to activation and maintenance.

[0090] Figure 3This paper describes the complete architecture and data flow process of a self-service system for telecom operators' industry customers based on virtualized business function units (BFUs). The top layer of this architecture provides scenario-based industry services to customers, which are composed of lower-layer business services. Each business service corresponds to a virtualized business function unit generated by a VBF encapsulation module. Each virtualized business function unit has a standardized VBF description defining its functional interfaces and parameter templates, and a container description defining its microservice deployment specifications. The core of the architecture is the Business Functions Unitization (BFUO) orchestrator. The Orchestrator, corresponding to the VBF orchestration module in the final technical solution, receives orchestration instructions from industry clients and orchestrates multiple virtualized business function units to combine them into a business capability combination solution. Virtualized business function units provide unified and secure service access capabilities to the outside world through the API gateway, and industry clients interact with the API gateway through the portal module. Each virtualized business function unit, such as Service 1, Service 2, and Service 3, is composed of multiple fine-grained microservices. These microservices run on a unified microservice runtime framework and are subject to full lifecycle management by the microservice management component. The underlying layer is the business function virtualization infrastructure, which provides resource-pooled computing, storage, and networking capabilities for the entire system and is built on a container cloud platform. The single-plane elastic computing controller, as the unified resource management brain, is responsible for dynamically scaling and scheduling the resource pool in the business function virtualization infrastructure based on the scheduling requirements of the business function orchestrator and the status information of microservice management, thereby supporting the automated process from the encapsulation and orchestration of virtualized business function units to the final service activation.

[0091] To optimize existing government and enterprise business support processes, this invention aims to make government and enterprise product support more flexible and better suited to the needs of industry clients, meeting the demands of account managers for quickly designing relevant elements of government and enterprise support for industry clients. This goal is achieved through the system constructed using embodiments of this invention. Specifically, the virtualized business function unit encapsulation module in the system encapsulates multiple existing support capabilities of operators into independent virtualized business function units, and configures parameter templates for each unit, making the presentation and invocation of support capabilities highly standardized and configurable. Industry clients can access the online marketplace through the portal module, allowing them to intuitively browse and compare multiple published virtualized business function units. Using the virtualized business function unit orchestration module, industry clients can independently select at least two target virtualized business function units from multiple units and use sequential execution logic, parallel execution logic, or conditional execution logic to orchestrate the process, generating a business capability combination solution tailored to their own business processes. Subsequently, the solution processing module performs automated verification and standardization processing on the solution, generating standardized business orders, and the business activation module drives the automatic execution of the orders. This complete process enables solutions that design and combine virtualized business function unit templates based on industry customer needs to more accurately meet customer requirements, more effectively utilize the capabilities of existing business support systems, thereby improving customer satisfaction, bringing more industry customers to operators, and enhancing the business value of government and enterprise services.

[0092] like Figure 4 As shown in the figure, a self-service method for telecom operator customers based on VBF according to an embodiment of the present invention includes the following steps: S1. Encapsulate the operator's existing multiple support capabilities into independent virtualized service function units, and publish the encapsulated virtualized service function units to the online store. S2. Showcase the multiple virtualization business function units that have been released in the online mall to industry clients; S3. Receive at least two target virtualization service function units selected by the industry customer from multiple virtualization service function units, and orchestrate the at least two target virtualization service function units according to the combination logic defined by the industry customer to generate a service capability combination scheme. S4. Verify and standardize the business capability combination scheme to generate standardized business orders; S5. Generate activation instructions based on standardized business orders and send the activation instructions to the corresponding support system so that the support system can complete the activation of the business capability combination scheme.

[0093] Optionally, in the above technical solution, the VBF encapsulation module configures a parameter template for each virtualization service function unit, and each parameter template is used to configure the configurable attributes of the corresponding virtualization service function unit.

[0094] Optionally, the above technical solution also includes: verifying the identity information of industry customers and granting them access to the online mall.

[0095] Optionally, in the above technical solution, the combinational logic includes at least one of sequential execution logic, parallel execution logic, and conditional execution logic, and the process orchestration is performed on at least two target virtualization business function units according to the combinational logic selected by the industry customer.

[0096] It should be noted that the beneficial effects of the VBF-based self-service method for carrier industry customers provided in the above embodiments are the same as those of the VBF-based self-service system for carrier industry customers described above, and will not be repeated here. Furthermore, the method and system embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the system embodiments, which will not be repeated here.

[0097] An electronic device according to an embodiment of the present invention 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 VBF-based operator industry customer self-service methods.

[0098] An embodiment of the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-mentioned VBF-based operator industry customer self-service methods.

[0099] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A self-service system for telecom operators based on VBF, characterized in that, It includes a VBF encapsulation module, a portal module, a VBF orchestration module, a solution processing module, and a service activation module; The VBF encapsulation module is used to: encapsulate the operator's existing multiple support capabilities into independent virtualized service function units, and publish the encapsulated virtualized service function units to the online marketplace. The portal module is used to: display multiple virtualized business function units that have been published in the online mall to industry customers; The VBF orchestration module is used to: receive at least two target virtualization service function units selected by the industry customer from a plurality of virtualization service function units, and orchestrate the at least two target virtualization service function units according to the combination logic defined by the industry customer to generate a service capability combination scheme; The scheme processing module is used to: verify and standardize the business capability combination scheme, and generate standardized business orders; The service activation module is used to: generate activation instructions based on the standardized service order, and send the activation instructions to the corresponding support system so that the support system can complete the service activation of the service capability combination scheme.

2. The self-service system for telecom operators based on VBF according to claim 1, characterized in that, The VBF encapsulation module configures parameter templates for each virtualization service function unit, and each parameter template is used to configure the configurable attributes of the corresponding virtualization service function unit.

3. A VBF-based customer self-service system for the telecom industry according to claim 1 or 2, characterized in that, The portal module includes a customer authentication unit, which is used to verify the identity information of the industry customers and grant them access to the online mall.

4. A VBF-based customer self-service system for the telecom industry according to claim 1 or 2, characterized in that, The combinational logic provided by the VBF orchestration module includes at least one of sequential execution logic, parallel execution logic, and conditional execution logic. The VBF orchestration module performs process orchestration on the at least two target virtualization business function units according to the combinational logic selected by the industry customer.

5. A self-service method for telecom operator customers based on VBF, characterized in that, include: The operator's existing multiple support capabilities are encapsulated into independent virtualized service function units, and the encapsulated virtualized service function units are published to the online store. Showcase the various virtualized business function units already published in the online marketplace to industry clients; The system receives at least two target virtualization service function units selected by the industry customer from a plurality of virtualization service function units, and orchestrates the at least two target virtualization service function units according to the combination logic defined by the industry customer to generate a service capability combination scheme. The proposed business capability combination scheme is validated and standardized to generate standardized business orders. An activation instruction is generated based on the standardized business order, and the activation instruction is sent to the corresponding support system so that the support system can complete the activation of the business capability combination scheme.

6. A self-service method for telecom operator customers based on VBF according to claim 5, characterized in that, The VBF encapsulation module configures parameter templates for each virtualization service function unit, and each parameter template is used to configure the configurable attributes of the corresponding virtualization service function unit.

7. A self-service method for telecom operator customers based on VBF according to claim 5 or 6, characterized in that, Also includes: Verify the identity information of the industry customers and grant them access to the online mall.

8. A self-service method for telecom operator customers based on VBF according to claim 5 or 6, characterized in that, The combined logic includes at least one of sequential execution logic, parallel execution logic, and conditional execution logic, and the process orchestration is performed on the at least two target virtualization business function units according to the combined logic selected by the industry customer.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement a VBF-based operator industry customer self-service method as described in any one of claims 5 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements a VBF-based self-service method for operator industry customers as described in any one of claims 5 to 8.

Images