Operation support system supporting multiple tenants and implementation method thereof

Abstract

The invention discloses an operation support system supporting multiple tenants and an implementation method thereof, and relates to the technical field of communication operation, and the system comprises a multi-tenant architecture module which is used for carrying out logic or physical isolation on different tenants and supporting data isolation through identification fields; the life cycle management module is used for carrying out full life cycle management on the tenants; the tenant portal management module is used for realizing the functions of product autonomous opening, service configuration, visual arrangement and process modeling, user authority management and report viewing; the business and resource isolation module is used for performing isolation processing on order data and service instances on the basis of the tenant identifier for the system core business module; and the interface integration isolation module is used for embedding tenant identification fields in all northbound and southbound APIs, realizing strong isolation of interface calling permission and data dimensions, and performing authentication authorization and auditing on access permission through an interface gateway. The method is suitable for virtual operators, hybrid operators and small and medium-sized communication operators.

Description

Technical Field

[0001] This invention relates to the field of communication operation technology, specifically to an operation support system that supports multi-tenancy and its implementation method. Background Technology

[0002] With the deepening marketization of the telecommunications industry and the advancement of policy liberalization, a large number of virtual network operators (MVNOs), hybrid operators, and regional small and medium-sized operators have rapidly emerged. These operators have differentiated needs in terms of infrastructure, network capabilities, support systems, and technical personnel, typically manifested as follows:

[0003] (a) Fully virtualized operators: have no proprietary network resources and operational capabilities, and rely entirely on the main operator's network, platform, transmission and billing system;

[0004] (b) Operators with partial network capabilities: They have core networks, user management systems (such as ACS), etc., but lack access and transmission networks, and their business implementation relies heavily on third-party resources;

[0005] (c) Regional small and medium-sized operators: They have their own network resources, but lack the ability to build complex OSS systems and find it difficult to independently complete the deployment and maintenance of business support systems.

[0006] Traditional OSS (Operation Support Systems) are mostly designed for a single main operator, with a rigid system architecture, high tenant coupling, and weak resource and data isolation capabilities, making it difficult to meet the needs of multiple types of operators. Especially in critical business areas such as order management, resource allocation, service instances, and API calls, traditional OSS systems have weak tenant isolation mechanisms, resulting in risks such as business conflicts, data leaks, and chaotic access control.

[0007] Therefore, there is an urgent need for a new type of operation support system architecture that can provide multi-tenant support, resource isolation, interface security and self-management capabilities to lower the entry barrier for small and medium-sized operators and improve the overall operability and security of the system. Summary of the Invention

[0008] This invention addresses the problems of traditional OSS systems, such as difficulty in resource sharing, weak tenant isolation, and poor independent operation and maintenance capabilities, when facing virtual operators and small and medium-sized operators. It provides an operation support system that supports multiple tenants and its implementation method.

[0009] In a first aspect, the present invention provides an operation support system that supports multiple tenants, and the technical solution adopted to solve the above-mentioned technical problems is as follows:

[0010] An operation support system supporting multi-tenancy, targeting virtual operators, hybrid operators, and small and medium-sized telecommunications operators, including:

[0011] The multi-tenant architecture module is used to logically or physically isolate different tenants based on the tenant metadata model and containerization technology. It supports private cloud and public cloud deployment and horizontal scaling, provides independent service running space, configuration items, database instances and log channels, and supports data isolation in shared databases through the identifier field tenant_id.

[0012] The lifecycle management module supports network operators in managing tenants throughout their entire lifecycle, including tenant registration, approval, deployment, activation, deactivation, and cancellation. It also supports network operators in configuring tenant templates to implement initialization parameters and resource configuration strategies for different business scenarios.

[0013] The tenant portal management module provides a self-management entry point for tenants, enabling them to independently activate products, configure services, perform visual orchestration and process modeling, manage user permissions, and view reports.

[0014] The interface integration isolation module is used to embed the tenant_id field in all northbound and southbound APIs to achieve strong isolation between interface call permissions and data dimensions, and to authenticate, authorize and audit access permissions through the interface gateway; approved requests are passed to the business and resource isolation module.

[0015] The business and resource isolation module, as a basic system guarantee module, is used to isolate the order process and status flow logic, resource catalog, resource-type order data and service instances based on the tenant identifier for four core business modules of the system: order management, activation management, work order management and resource management.

[0016] Optionally, the multi-tenant architecture module involved is deployed in the Kubernetes container orchestration platform, with different tenants running in independent namespaces or logical domains, supporting elastic scaling and cross-cloud scheduling capabilities, achieving fault isolation between tenants, and being compatible with private cloud and public cloud deployment scenarios.

[0017] Optionally, the tenant portal management module is built on a web front-end framework, supporting interface customization, multi-language switching, visual business process modeling and drag-and-drop arrangement, while ensuring the convenience of tenant self-operation.

[0018] Optionally, the interface integration isolation module uses a combined OAuth2 and JWT authentication mechanism to perform tenant-level authentication and authorization for interface access, and simultaneously supports tenant-level access frequency control and audit log recording functions.

[0019] Optionally, the business and resource isolation module involved serves as a basic system guarantee module. In the resource management business module, it implements the isolation of tenant-level resource catalogs, resource-type order data and service instances, and supports dynamic allocation and reservation mechanisms for resource pools. At the same time, it ensures that the order process and status flow logic of the order management business module, activation management business module and work order management business module follow the tenant isolation strategy.

[0020] Secondly, the present invention provides a method for implementing an operation support system that supports multiple tenants, and the technical solution adopted to solve the above-mentioned technical problems is as follows:

[0021] A method for implementing a multi-tenant operations support system, which implements multi-tenant management based on the operations support system described in the first aspect, specifically includes the following steps:

[0022] S1. Tenant Registration and Access:

[0023] Network operators log in to the operation support system and register virtual operators or small and medium-sized operators as tenants through the lifecycle management module, and enter the tenant's basic enterprise information, business domain scope and service selection;

[0024] After receiving the tenant registration information, the multi-tenant architecture module automatically assigns an identifier field tenant_id to the tenant and triggers the isolation domain initialization process.

[0025] S2. Organizational Structure and Account System Construction:

[0026] Tenants can build their own organizational structure, including departments, positions, and permission role models, through the tenant portal management module;

[0027] Based on the role-based access control model, tenant administrators create multi-level accounts and assign operation permissions for corresponding modules.

[0028] S3, Service Ordering and Configuration:

[0029] Tenants complete the order through the tenant portal management module or their own CRM system, generate an order request, and then initiate a call through the northbound order creation API controlled by the interface integration isolation module;

[0030] After the order request is passed to the business and resource isolation module, the business and resource isolation module creates logically isolated resource-type order data and service instances for the tenant based on the tenant identifier, and synchronizes them to the two business modules of resource management and activation management. Subsequently, through the resource pre-allocation, instruction issuance and order dispatch process, the service configuration and activation are finally completed.

[0031] S4, Service Operation and Maintenance:

[0032] When tenants encounter problems using the customer service provided by the network operator, they submit requests to create fault tickets and complaint tickets through the tenant portal management module.

[0033] After receiving fault tickets and complaint tickets submitted by tenants through the operation support system, the network operator initiates the corresponding business processing procedures according to the type and priority of the ticket.

[0034] S5, Tenant Cancellation:

[0035] The lifecycle management module supports full lifecycle management of tenants, and network operators can use this module to perform activation, suspension, renewal and cancellation operations;

[0036] When a network operator executes a cancellation operation based on a tenant's cancellation request, the lifecycle management module simultaneously performs corresponding resource reclamation, account reclamation, and data clearing operations to ensure efficient governance and release of resources in the operations support system.

[0037] Optionally, the isolation domain initialization includes: creating an independent database schema, dividing a dedicated microservice resource group, and configuring tenant-based access permissions.

[0038] Optionally, tenants can complete the subscription through the tenant portal management module and generate a subscription request. This process specifically includes: the tenant browsing the service catalog provided by the network operator in the tenant portal management module, selecting the required network resources, work order services and resource management products, and generating a subscription request directly after completing the subscription.

[0039] Tenants complete orders and generate order requests through their own CRM system. This process specifically includes: tenants selecting the required network resources, work order services, and resource management products through their own CRM system, and generating order requests through their own CRM system after completing the order.

[0040] Optionally, after the order request is passed to the business and resource isolation module, the business and resource isolation module, based on the tenant identifier and the service content in the order request,

[0041] Create logically isolated resource-type order data and service instances for tenants, and synchronize the order data to the order management business module, and synchronize the service instance information to the resource management and activation management business modules;

[0042] Based on the synchronized service instance information, the resource management business module performs resource pre-allocation to lock the network resources required by the tenant to prevent resource allocation conflicts. Subsequently, the activation management business module issues instructions to the NE / EMS, while the work order management business module dispatches orders according to the order requirements and resource pre-allocation results to ensure that the resource configuration and instruction execution operations are implemented.

[0043] Once all service configurations are complete, the services ordered by the tenant are officially available.

[0044] Optionally, after submitting a request to create a fault ticket or complaint ticket through the tenant portal management module, the tenant can continue to view the current status of the submitted fault ticket or complaint ticket in real time within the same module.

[0045] The multi-tenant operation support system and its implementation method of the present invention have the following advantages compared with the prior art:

[0046] 1. This invention can provide full-process support from tenant registration, organization building, business ordering, service operation and maintenance to tenant deregistration, ensuring the complete closed loop and secure operation of tenant business, and solving the problems of insufficient tenant isolation, serious business coupling and weak self-service capability in the existing operation support system.

[0047] 2. This invention constructs a multi-tenant operating environment based on a tenant metadata model and containerization technology, achieving tenant-level service, data, and resource isolation; through lifecycle management modules, tenant portal management modules, business and resource isolation modules, and interface integration isolation modules, it supports operators to independently configure and flexibly deploy services; it is suitable for virtual operators, hybrid operators, and small and medium-sized telecommunications operators, and has the advantages of high compatibility, low cost, and scalability;

[0048] 3. This invention flexibly adapts to various types of operator access. Whether it is a fully virtualized operator, a hybrid operator with some network resources, or a small and medium-sized operator lacking operational support capabilities, all can quickly deploy services on the operational support system. It fully realizes tenant-level business and resource isolation: achieving two-layer isolation of logic and data in the dimensions of orders, resources, services, and interfaces, effectively avoiding crosstalk and security risks between tenants. It provides a self-management portal for tenants, enabling self-activation of products, configuration of services, visual orchestration and process modeling, user permission management, and report viewing functions, which can improve operational autonomy and efficiency, and significantly reduce technical thresholds and operating costs. Attached Figure Description

[0049] Appendix Figure 1 This is a module connection block diagram of Embodiment 1 of the present invention;

[0050] Appendix Figure 2 This is a flowchart of the method according to Embodiment 2 of the present invention. Detailed Implementation

[0051] To make the technical solution, the technical problem solved, and the technical effect of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with specific embodiments.

[0052] Example 1:

[0053] Combined with appendix Figure 1 This embodiment proposes an operation support system that supports multiple tenants. The system is designed for virtual operators, hybrid operators and small and medium-sized telecommunications operators. It includes a lifecycle management module, a multi-tenant architecture module, a tenant portal management module, a service and resource isolation module and an interface integration isolation module.

[0054] The multi-tenant architecture module, as the core underlying support module of the system, is used to: logically or physically isolate different tenants based on the tenant metadata model and containerization technology (such as Kubernetes), support private cloud and public cloud deployment and horizontal scaling, provide independent service running space, configuration items, database instances and log channels, and support data isolation in shared databases through the identifier field tenant_id.

[0055] Specifically, the multi-tenant architecture module described in this embodiment is deployed in the Kubernetes container orchestration platform. Different tenants run in independent namespaces or logical domains, supporting elastic scaling and cross-cloud scheduling capabilities, achieving fault isolation between tenants, and being compatible with both private cloud and public cloud deployment scenarios.

[0056] The multi-tenant architecture module provides the architectural foundation and isolation capabilities for all subsequent modules.

[0057] The lifecycle management module, based on the tenant metadata model and isolation technology provided by the multi-tenant architecture module, is used to: support network operators in managing the entire lifecycle of tenants, including tenant registration, approval, deployment, activation, deactivation and deregistration; and support network operators in configuring tenant templates to implement initialization parameters and resource configuration strategies under different business scenarios.

[0058] The lifecycle management module also works in conjunction with the business and resource isolation module to allocate / reclaim isolated resources.

[0059] The tenant portal management module, relying on the independent service runtime space and configuration item isolation capabilities provided by the multi-tenant architecture module, is used to: provide tenants with a self-management entry point, and realize functions such as self-service product activation, business configuration, visual orchestration and process modeling, user permission management, and report viewing.

[0060] Specifically, the tenant portal management module described in this embodiment is built on a web front-end framework, supporting interface customization, multi-language switching, visual business process modeling and drag-and-drop arrangement, while ensuring the convenience of tenant self-operation.

[0061] When a tenant initiates an operation through the tenant portal management module, it needs to pass a request containing the identifier field tenant_id through the northbound API controlled by the interface integration isolation module.

[0062] The interface integration isolation module, based on the tenant identification system defined by the multi-tenant architecture module, is used to embed the tenant_id field in all northbound and southbound APIs to achieve strong isolation between interface call permissions and data dimensions. Access permissions are authenticated, authorized, and audited through the interface gateway. Requests that pass the audit are passed to the business and resource isolation module.

[0063] Specifically, the interface integration isolation module described in this embodiment adopts a joint authentication mechanism of OAuth2 and JWT to perform tenant-level authentication and authorization for interface access, and simultaneously supports tenant-level access frequency control and audit log recording functions; approved requests need to be passed to the business and resource isolation module to support business data isolation processing.

[0064] The business and resource isolation module, as a fundamental system guarantee module, relies on the isolation technology framework of the multi-tenant architecture module. It receives resource allocation / reclamation instructions from the lifecycle management module and review requests from the interface integration isolation module. It is used to isolate the order process and status flow logic, resource catalog, resource-type order data and service instances based on the tenant identifier for four types of core system business modules: order management (OM), activation management (AM), work order management (WFM) and resource management (IM).

[0065] Specifically, the business and resource isolation module described in this embodiment implements tenant-level resource catalog, resource order and service instance isolation in the resource management business module, and supports dynamic allocation and reservation mechanism of resource pool; at the same time, it ensures that the order process and status flow logic of the order management business module, activation management business module and work order management business module follow the tenant isolation strategy.

[0066] It should be specifically noted that, for the order management module, the business and resource isolation module isolates the order process logic and order data: ① Ensure that the order creation, review, and fulfillment process logic of tenant A (such as order status flow rules) is completely independent from that of tenant B and does not affect each other; ② Isolate order data (such as order number, order amount, associated customers), and tenant A cannot query / modify any order records of tenant B.

[0067] For the activation management module, the business and resource isolation module isolates the service activation status flow logic and activation records: ① Isolates activation rules for different tenants (such as activation validity period, activation prerequisites) to avoid confusion between rules between tenants; ② Isolates activation data (such as activation code, activation time, activation status), and tenants can only view the activation progress and history of their own services.

[0068] For the work order management module, the business and resource isolation module isolates the work order flow logic and work order data: ① It isolates the work order processing flow specific to each tenant (such as work order priority rules, approval nodes, and processing time limits). For example, tenant C's "fault work order" requires 3 levels of approval, while tenant D only needs 1 level of approval, and the logic does not interfere with each other; ② It isolates the work order content (such as work order description, processing records, and related businesses), and tenants cannot view the work order details of other tenants.

[0069] For the resource management module, the business and resource isolation module isolates the resource catalog, resource order data, and service instances: ① Isolate the resource catalog (e.g., the "cloud server model" and "storage capacity options" seen by tenant E are different from those of tenant F, and the catalog is customized according to tenant permissions); ② Isolate resource order data (e.g., order details of resources purchased by tenants and resource allocation records); ③ Isolate service instances (e.g., the cloud server instance and database instance of tenant E are completely physically / logically isolated from the instance of tenant F, and resource usage does not compete with each other).

[0070] Example 2:

[0071] Combined with appendix Figure 2 This embodiment proposes a method for implementing an operation support system that supports multiple tenants. It implements multi-tenant management based on the operation support system described in Embodiment 1, and specifically includes the following steps:

[0072] S1, Tenant Registration and Access.

[0073] Network operators log in to the operation support system and register virtual operators or small and medium-sized operators as tenants through the lifecycle management module, and enter the tenant's basic enterprise information, business domain scope and service selection.

[0074] After receiving tenant registration information, the multi-tenant architecture module automatically assigns an identifier field, tenant_id, to the tenant and triggers the isolation domain initialization process. Isolation domain initialization specifically includes: creating an independent database schema, dividing a dedicated microservice resource group, and configuring tenant-based access permissions (such as data access permissions and function operation permissions).

[0075] S2. Organizational structure and account system construction.

[0076] Tenants can build their own organizational structure, including departments, positions, and permission role models, through the tenant portal management module.

[0077] Based on the role-based access control model, tenant administrators create multi-level accounts and assign operation permissions for corresponding modules.

[0078] S3, Service Ordering and Configuration.

[0079] Tenants can order services in the following two ways:

[0080] (a) Tenants browse the service catalog provided by the network operator in the tenant portal management module, select the required network resources, work order services and resource management products, and generate a subscription request directly after completing the subscription.

[0081] (b) Tenants select the required network resources, work order services and resource management products through their own CRM system, and after completing the order, their own CRM system generates an order request.

[0082] Subsequently, the order request is initiated through the northbound order creation API controlled by the interface integration isolation module, and then the order request is passed to the business and resource isolation module. Then, the business and resource isolation module creates logically isolated order data and service instances for the tenant based on the tenant identifier and the service content in the order request, and synchronizes the order data to the order management business module, and synchronizes the service instance information to the resource management and activation management business modules.

[0083] Based on the synchronized service instance information, the resource management business module performs resource pre-allocation operations to lock the network resources required by the tenant to prevent resource allocation conflicts. Subsequently, the activation management business module issues instructions to the NE / EMS (Network Element / Network System Management System), while the work order management business module dispatches work orders according to the order requirements and resource pre-allocation results to ensure that the resource configuration and instruction execution operations are implemented.

[0084] Once all service configurations are complete, the services ordered by the tenant are officially available.

[0085] S4, Service Operations and Maintenance.

[0086] Tenants use the customer service provided by the network operator and, when encountering problems, submit requests to create fault tickets and complaint tickets through the tenant portal management module.

[0087] After receiving fault tickets and complaint tickets submitted by tenants through the operation support system, the network operator initiates the corresponding business processing procedures (such as fault investigation, complaint verification, feedback follow-up, etc.) according to the ticket type (fault / complaint) and priority.

[0088] After submitting a request to create a fault ticket or complaint ticket through the tenant portal management module, tenants can continue to view the current status of the submitted fault ticket or complaint ticket in real time within the same module.

[0089] S5, Tenant Cancellation.

[0090] The lifecycle management module supports full lifecycle management of tenants, and network operators can use this module to perform activation, suspension, renewal and cancellation operations;

[0091] When a network operator executes a cancellation operation based on a tenant's cancellation request, the lifecycle management module simultaneously performs corresponding resource reclamation, account reclamation, and data clearing operations to ensure efficient governance and release of resources in the operations support system.

[0092] In summary, the multi-tenant operation support system and its implementation method of the present invention can provide full-process support from tenant registration, organization building, service ordering, service operation and maintenance to tenant deregistration, ensuring the complete closed loop and secure operation of tenant services. It solves the problems of insufficient tenant isolation, serious business coupling, and weak self-service capabilities in existing operation support systems, and is suitable for virtual operators, hybrid operators and small and medium-sized telecommunications operators.

[0093] The above specific examples illustrate the principles and implementation methods of the present invention in detail. These embodiments are merely for the purpose of helping to understand the core technical content of the present invention. Based on the above specific embodiments of the present invention, any improvements and modifications made to the present invention by those skilled in the art without departing from the principles of the present invention should fall within the patent protection scope of the present invention.

Claims

1. A multi-tenant enabled operation support system, which is oriented to virtual operators, hybrid operators and small and medium-sized communication operators, characterized in that, Comprise: A multi-tenant architecture module for logically or physically isolating different tenants based on a tenant metadata model and containerization technology, supporting private cloud and public cloud deployment and horizontal expansion, providing independent service running space, configuration items, database instances and log channels, and supporting shared databases to isolate data through an identification field tenant_id; A life cycle management module for supporting network operators to manage tenants throughout their life cycle, including tenant registration, approval, deployment, activation, deactivation and complete life cycle management; supporting network operators to configure tenant templates to achieve initialization parameters and resource configuration strategies in different business scenarios; A tenant portal management module for providing a tenant self-management portal to achieve product self-provisioning, business configuration, visual orchestration and process modeling, user permission management and report viewing functions; An interface integration isolation module for embedding a tenant identification field tenant_id in all northbound and southbound APIs to achieve strong isolation of interface call permissions and data dimensions, and for authenticating, authorizing and auditing access permissions through an interface gateway; approved requests are passed to the business and resource isolation module; A business and resource isolation module as a system foundation guarantee module for isolating order flow and state logic, resource catalog, resource class order data and service instances based on tenant identification for four types of system core business modules: order management, activation management, work order management and resource management.

2. The multi-tenant enabled OSS of claim 1, wherein, The multi-tenant architecture module is deployed in a Kubernetes container orchestration platform, different tenants run in independent Namespace or logical domains, supporting elastic expansion and cross-cloud scheduling capabilities, achieving fault isolation between tenants, and simultaneously supporting private cloud and public cloud deployment scenarios.

3. The multi-tenant enabled OSS of claim 1, wherein, The tenant portal management module is built based on a Web front-end framework, supporting interface customization, multi-language switching, visual business process modeling and drag-and-drop orchestration, while ensuring the convenience of tenant self-operation.

4. The multi-tenant enabled OSS of claim 1, wherein, The interface integration isolation module uses an OAuth2 and JWT joint authentication mechanism to perform tenant-level authentication and authorization for interface access, and simultaneously supports tenant-level access frequency control and audit log recording functions.

5. The multi-tenant enabled OSS of claim 1, wherein, The business and resource isolation module as a system foundation guarantee module implements tenant-level resource catalog, resource class order data and service instance isolation in the resource management business module, and supports resource pool dynamic allocation and reservation mechanisms; while ensuring that the order flow and state logic of the order management business module, the activation management business module and the work order management business module comply with the tenant isolation strategy.

6. A method for implementing an operation support system supporting multi-tenancy, characterized in that, It implements multi-tenant management based on the operation support system of any one of claims 1-5, specifically comprising the following steps: S1, tenant registration and access: The network operator logs in to the operation support system, registers a virtual operator or a small and medium-sized operator as a tenant through the life cycle management module, and enters the tenant's basic information, business domain range and service selection; After the multi-tenant architecture module receives the tenant registration information, it automatically allocates an identification field tenant_id for the tenant and triggers the isolation domain initialization process; S2, Organizational structure and account system construction: Tenants build their own organizational structure through the tenant portal management module, including departments, positions, and role-based permission models. Based on the role-based permission model, tenant administrators create multi-level accounts and assign operation permissions for corresponding modules (modules corresponding to account levels). S3, Service subscription and configuration: Tenants complete subscription through the tenant portal management module or their own CRM system, generate a subscription request, and then initiate a call through the northbound single creation API controlled by the interface integration isolation module. After the subscription request is passed to the business and resource isolation module, the business and resource isolation module creates logically isolated resource order data and service instances for the tenant based on the tenant identifier, and synchronizes them to the resource management and activation management business modules. Subsequently, through resource pre-occupation, instruction issuance, and order dispatching processes, service configuration and activation are finally completed. S4, Service operation and maintenance: Tenants use customer service provided by network operators and submit fault tickets and complaint tickets through the tenant portal management module when problems occur. After receiving the fault tickets and complaint tickets submitted by tenants, network operators start the corresponding business processing flow based on the type and priority of the tickets. S5, Tenant deregistration: The lifecycle management module supports tenant lifecycle management, and network operators perform enable, suspend, renew, and deregister operations through this module. When network operators perform deregistration operations based on tenant-initiated deregistration applications, the lifecycle management module synchronously performs corresponding resource recovery, account recovery, and data cleaning operations to ensure efficient governance and release of operation support system resources.

7. The method of claim 6, wherein the method further comprises: The isolation domain initialization specifically includes creating independent database schemas, dividing exclusive microservice resource groups, and configuring access permissions based on tenant dimensions.

8. The method of claim 6, wherein the method further comprises: Tenants complete subscription through the tenant portal management module, generating a subscription request, which specifically includes tenants browsing the service catalog provided by network operators in the tenant portal management module, selecting the required network resources, ticket services, and resource management products, and directly generating a subscription request after completing the subscription. Tenants complete subscription through their own CRM system, generating a subscription request, which specifically includes tenants selecting the required network resources, ticket services, and resource management products through their own CRM system, and generating a subscription request after completing the subscription.

9. The method of claim 8, wherein the method further comprises: After the subscription request is passed to the business and resource isolation module, the business and resource isolation module creates logically isolated resource order data and service instances for the tenant based on the tenant identifier, and synchronizes them to the order management business module and the resource management and activation management business modules. Based on the synchronized service instance information, the resource management business module performs resource pre-occupation operations to lock the required network resources for the tenant to prevent resource allocation conflicts. Subsequently, the activation management business module issues instructions to NE / EMS, and the ticket management business module performs order dispatching based on order requirements and resource pre-occupation results to ensure that resource configuration and instruction execution operations are implemented. ​ Finally, all service configurations are completed, and the services ordered by the tenant are officially available.

10. The method of claim 6, wherein the method further comprises: After the tenant submits the operation request of creating a fault work order and a complaint work order through the tenant portal management module, the tenant continues to view the current status of the submitted fault work order or complaint work order in real time in the module.

Images