A model-driven intelligent operation and maintenance middle platform portal method and device

Abstract

The present invention discloses a model-driven intelligent operation and maintenance middle platform portal method and device. The method of the present invention includes: each business component of the intelligent operation and maintenance middle platform constructs a touchpoint model file for each scenario according to the touchpoint model specification; the touchpoint capability management module stores the touchpoint model files for each scenario according to the specification of one scenario and one directory; after the touchpoint model analyzer scans and analyzes the touchable model files that can be matched according to the scenario value of the set scenario, the touchpoint capability management module collects touchpoint model data from the matched touchpoint model files and aggregates the collected touchpoint model data by scenario, so as to provide a middle platform portal by scenario by binding the middle platform user to the scenario.

Description

Technical Field

[0001] The present invention relates to the field of communications, and particularly to a model-driven intelligent operation and maintenance middle platform portal method and device. Background Art

[0002] In the telecommunications field, with the gradual deepening of the SDN / NFV architecture, the accelerating development of 5G network cloud reconstruction and MEC edge computing innovation, the application scenarios of multi-cloud access, cloud network integration, and cloud-edge collaboration are becoming increasingly rich. To adapt to the rapid and complex network requirements and business changes, telecom operators and communication equipment manufacturers have successively proposed the construction of middle platforms, transforming from the traditional single-specialty management mode to integrated management and centralized management, and transforming from the traditional monolithic application to cloudification, microservices, and middle platform in terms of technical architecture. In 5G intelligent operation and maintenance, the middle platform technology is an inevitable trend. For middle platforms, there are usually business middle platforms, data middle platforms, AI middle platforms, technology middle platforms, etc. In 5G intelligent operation and maintenance, the business middle platform integrates various isolated business domains, integrates network management capabilities such as 5G core network / VOLTE, radio network, bearer network, DC, big data, and AI, breaks the chimney-style construction of each specialty, constructs a new type of 5G intelligent network management capability through the middle platform, completes the reconstruction of 5G intelligent operation and maintenance, realizes the sharing of capabilities, breaks through data and capability barriers, and shortens the online cycle of new services.

[0003] Under the traditional single-specialty management mode, operation and maintenance systems are usually independently deployed by specialty, such as independently deploying systems for the core network, bearer network, radio, etc. The operation and maintenance portals are independent of each other, and the business functions are different, and the operation and maintenance interfaces are also independent; while the 5G intelligent operation and maintenance based on the middle platform covers systems in multiple different domains, aggregates a large number of business functions, forms numerous front-end applications, and at the same time the front-end faces more and more complex end-user groups. Different operators have different display requirements for front-end applications. In particular, different organizational structures of different operators will affect the differences in business management models. Within the same operator, scenarios will also be divided according to the positions and functions of operation and maintenance personnel, and different business functions will be provided according to the scenarios. For example, in the 5G intelligent operation and maintenance portal, it can be divided according to operators such as China Mobile, China Telecom, and China Unicom, and within the operator, it can be divided according to scenarios such as slices, sub-slices, 5G, 4G, core network, bearer network, radio network, NOC, network data analysis, etc.

[0004] In response to the requirement of providing different business services according to scenarios for the 5G intelligent operation and maintenance middle platform portal, the traditional approach usually involves manufacturers custom-developing a new portal according to the personalized needs of operators. After customization, a new version needs to be released to meet the differentiated requirements of operators. This approach will result in a large number of portal entities, increasing a large amount of computing resources, and the login addresses of different portals cannot be unified. The development cycle is long, the cost is high, and it is very inflexible. Especially after the 5G intelligent operation and maintenance is middle-platformed, a large number of systems are aggregated, and it also involves cross-vendors. If the on-demand customized development of the portal is still adopted, it will face great difficulties, and the existing methods are difficult to meet the requirements. Summary of the Invention

[0005] The present invention aims to provide a model-driven intelligent operation and maintenance middle platform portal method and device for quickly constructing a front-end application according to scenarios in an intelligent operation and maintenance portal, solving the display requirements of different end-user groups for the portal, unifying the portal address, saving the computing resource overhead of the portal, and quickly adapting to the display requirements of different end-users for the portal under the middle-platform architecture.

[0006] According to the first aspect of the present invention, there is provided a model-driven intelligent operation and maintenance middle platform portal method, including:

[0007] Each business component of the intelligent operation and maintenance middle platform constructs a touchpoint model file for each scenario according to the touchpoint model specification.

[0008] The touchpoint capability management module saves the touchpoint model file of each scenario according to the specification of one scenario and one directory.

[0009] The touchpoint capability management module scans and analyzes the touchpoint model files that can be matched according to the scenario value of the set scenario in the touchpoint model analyzer, collects touchpoint model data from the touchpoint model files that can be matched, and aggregates the touchpoint model data according to the scenario, so as to provide a middle platform portal according to the scenario by binding the middle platform users with the scenario.

[0010] The above method of the present invention further includes a touchpoint model life cycle management step after aggregating all touchpoint model data according to the scenario, specifically:

[0011] It also includes a touchpoint model life cycle management step after aggregating the collected touchpoint model data according to the scenario, specifically:

[0012] The touchpoint capability management module forms a touchpoint model by aggregating the collected touchpoint model data according to the scenario.

[0013] The touchpoint capability management module maintains the life cycle of the touchpoint model in real time according to the life cycle of each business component of the intelligent operation and maintenance middle platform.

[0014] Preferably, the service component is a program that provides complete services for a certain function and is independently deployed; the middle platform portal provides a unified login entry, and the business functions in the portal are composed of a series of touchpoints and are displayed according to application scenarios; the touchpoint is the function entry for user operations in the middle platform portal.

[0015] Preferably, the touchpoint model file includes: touchpoint ID; touchpoint name; touchpoint response href; touchpoint hanging relationship parentId and sorting sequence number order.

[0016] Preferably, the touchpoint model analyzer scans and analyzes the matchable touchpoint models according to the scenario values of the set scenarios, including:

[0017] After each service component listens to the scenario notification carrying the scenario value broadcast by the message middleware, it starts the touchpoint model scanner;

[0018] The touchpoint model scanner scans the touchpoint model file according to the scenario value and analyzes the matchable touchpoint models to obtain touchpoint model data.

[0019] Preferably, the middle platform portal provided by binding the middle platform user to the scenario includes:

[0020] According to the job responsibilities of the middle platform user and the corresponding usage scenarios, each middle platform user is bound to the corresponding usage scenario;

[0021] When the user accesses the middle platform portal, the portal service module obtains the touchpoint model data matching the scenario according to the binding relationship between the middle platform user and the scenario;

[0022] After the portal service module obtains the touchpoint model data, it instantiates the touchpoints according to the touchpoint model and displays them in the portal.

[0023] Preferably, the binding of each middle platform user to the corresponding usage scenario includes: setting the scenario label of the corresponding usage scenario for each middle platform user.

[0024] Preferably, when the user accesses the middle platform portal, the portal service module obtains the touchpoint model data matching the scenario according to the binding relationship between the middle platform user and the scenario, including:

[0025] After the middle platform user logs in to the middle platform portal, the touchpoint model is queried from the touchpoint capability management module using the scenario label;

[0026] The touchpoint capability management module instantiates the portal according to the scenario based on all the queried touchpoint model data and displays the business functions belonging to the middle platform user.

[0027] According to the second aspect of the present invention, there is provided a model-driven intelligent operation and maintenance middle platform portal device, including:

[0028] Each business component of the intelligent operation and maintenance middle platform is used to construct a contact model file for each scenario according to the contact model specification;

[0029] The contact model analyzer is used to scan and analyze the matchable contact model files according to the scenario values of the set scenarios;

[0030] The contact capability management module saves the contact model files of each scenario according to the specification of one scenario and one directory for the user; and after the contact model analyzer scans and analyzes the matchable contact model files according to the scenario values of the set scenarios, it collects contact model data from the matchable contact model files and aggregates the collected contact model data by scenario, so as to provide a middle platform portal by binding the middle platform users to the scenarios.

[0031] A model-driven intelligent operation and maintenance middle platform portal device of the present invention further includes: a user management module for binding middle platform users to scenarios; a portal service module for obtaining contact model data in response to a user login request and instantiating according to the contact model description to provide a middle platform portal by scenario.

[0032] Compared with the prior art, the beneficial technical effects of the present invention are as follows: 1) By abstracting the contacts in the portal into models, the models are standardized and used as the standard output parts of each component in the middle platform system; 2) By model-driven scenario modeling, the models are dynamic and can be started as needed; 3) Design professional scenarios according to operation and maintenance requirements, enumerate the corresponding operation and maintenance functions according to the professional scenarios, and build models accordingly to solve the problem of multiple scenarios and multiple models; 4) The portal service is framed, and the only portal framework can display different combinations of business functions according to the scenario tags of different users, with a unified entry, saving computing resources;

[0033] The present invention will be described in detail below with reference to the accompanying drawings. Description of the Drawings

[0034] Figure 1A is a schematic diagram of a model-driven intelligent operation and maintenance middle platform portal method of the present invention;

[0035] Figure 1B is a schematic diagram of a model-driven intelligent operation and maintenance middle platform portal device of the present invention;

[0036] Figure 2 is a schematic diagram of the 5G intelligent operation and maintenance architecture level and front-end application;

[0037] Figure 3 is a schematic diagram of the front and back ends of the 5G intelligent operation and maintenance architecture;

[0038] Figure 4 is a schematic diagram of the middle platform portal of the present invention displayed according to the operation and maintenance scenarios;

[0039] Figure 5 It is a schematic diagram of the corresponding relationship between the scenario name and the contact model in the components of the present invention;

[0040] Figure 6 It is a data processing flow chart of the present invention;

[0041] Figure 7 It is a process diagram of the binding between the middle - platform user and the scenario of the present invention;

[0042] Figure 8 It is a flow chart of the instantiation of the middle - platform portal of the present invention. Detailed implementation manners

[0043] For the convenience of description, the concepts and related contents involved in the present invention are described as follows:

[0044] Portal: It is constructed by a series of function points for users to operate. The entry of each function point is called an application contact. In the present invention, the application contacts are abstracted into models, the contact models are standardized, and the dynamics of the portal are realized through model - driven.

[0045] Component: A program that provides a complete service for a certain function and is independently deployed;

[0046] Component pool: The complete set of components composed of a series of independent components;

[0047] Product portfolio: Select the corresponding components from the component pool according to the product requirements and combine them into a specific product;

[0048] Front - end application: The operable function combination provided by business components for users;

[0049] Application contact: The business function navigation point in the middle - platform portal;

[0050] Middle - platform portal: It provides a unified login entry. The business functions in the portal are composed of a series of contacts and display business functions according to the application scenarios.

[0051] Scenario management: Manage the scenarios supported by the system and set scenario values for each scenario. Scenarios include: classified by operators such as China Mobile, China Telecom, China Unicom, etc.; classified by specialties such as by slice, sub - slice, 5G, 4G, core network, bearer network, wireless network, NOC, network data analysis, etc.; classified by users, such as pre - defined scenarios for enterprise - government users, configuration users, partners, etc., and perform scenario - based setting management according to requirements after the system is deployed.

[0052] Contact capability management: Contact capability management has functions of contact model definition, contact model analysis, and contact model life - cycle management.

[0053] Model Definition: A contact point is the functional entry for user operations, defined by business components. To standardize the management of contact points, the contact point capability management provides a standard description specification for the contact point model. The model format can be xml / json / yml. The model content should at least include the contact point ID, contact point response href, contact point attachment relationship, sorting serial number, etc. The business components shall describe the contact point model according to the agreed specifications, describe the specific contact point models according to multiple scenarios, and the model description. The attributes in the model can be extended according to functional requirements. A set of corresponding model files shall be defined for each business scenario.

[0054] Contact Point Model Analysis: Scan and analyze the contact point models of each component according to the current running scenario, and complete the aggregation of the contact point file content of the entire system through distributed message middleware technology, and generate complete contact point data.

[0055] Contact Point Model Lifecycle Management: Components involve life cycles such as addition, uninstallation, start, and stop. The contact points corresponding to the components also need to synchronously perform addition and deletion lifecycle management.

[0056] Contact Point Management: Responsible for the management of the contact point model data after analysis and synthesis, responsible for the persistence of contact point data, and maintaining the data after the life cycle change of the contact point response, and providing a displayable contact point data model for the middle platform portal.

[0057] Portal Service: The portal service responds to the front-end portal login request. There is only one deployment entity for the portal service, which is responsible for obtaining the contact point model data from the contact point management capability center, instantiating according to the contact point model description, and providing the middle platform portal according to the business scenario.

[0058] User Management: When an administrator creates a new user, configure the mapping relationship binding between the user and the scenario label, and be responsible for establishing the corresponding relationship between the scenario and the user.

[0059] Figure 1A Disclosed is a model-driven intelligent operation and maintenance middle platform portal method of the present invention. The method shown in FIG. 1 includes: each business component of the intelligent operation and maintenance middle platform constructs a contact point model file for each scenario according to the contact point model specification; the contact point capability management module saves the contact point model file for each scenario according to the specification of one scenario one directory; after the contact point model analyzer scans and analyzes the matchable contact point model files according to the scenario value of the set scenario, the contact point capability management module collects the contact point model data from the matchable contact point model files, and aggregates the collected contact point model data according to the scenario, so as to provide a middle platform portal according to the scenario by binding the middle platform user with the scenario.

[0060] Figure 1A The model-driven intelligent operation and maintenance middle platform portal method of the present invention shown also includes a contact point model lifecycle management step after aggregating all contact point model data according to the scenario. Specifically:

[0061] The contact point capability management module forms a contact point model by aggregating the collected contact point model data according to scenarios.

[0062] The contact point capability management module maintains the life cycle of the contact point model in real time according to the life cycle of each business component of the intelligent operation and maintenance middle platform.

[0063] The business component described in the present invention is a program that provides a complete service for a certain function and is independently deployed; the middle platform portal provides a unified login entrance, the business functions in the portal are composed of a series of contact points, and the business functions are displayed according to the application scenarios; the contact point is the function entrance for user operations in the middle platform portal.

[0064] The contact point model file described in the present invention includes: contact point ID; contact point name; contact point response href; contact point attachment relationship parentId, and sorting serial number order.

[0065] In the above method of the present invention, after each business component listens to the scenario notification carrying the scenario value broadcast by the message middleware, it starts the contact point model scanner; the contact point model scanner scans the contact point model file according to the scenario value, and analyzes the matchable contact point models to obtain the contact point model data.

[0066] The above method of the present invention provides a middle platform portal by binding the middle platform user with the scenario, including: binding each middle platform user with the corresponding usage scenario according to the work responsibilities of the middle platform user and the corresponding usage scenario; when the user accesses the middle platform portal, the portal service module obtains the contact point model data matching the scenario according to the binding relationship between the middle platform user and the scenario; after the portal service module obtains the contact point model data, it instantiates the contact points according to the contact point model and displays them in the portal.

[0067] The binding of each middle platform user with the corresponding usage scenario described in the above method of the present invention includes: setting the scenario label of the corresponding usage scenario for each middle platform user.

[0068] The portal service module described in the above method of the present invention obtains the contact point model data matching the scenario according to the binding relationship between the middle platform user and the scenario, including: after the middle platform user logs in to the middle platform portal, using the scenario label to query the contact point model from the contact point capability management module; the contact point capability management module instantiates the portal according to the scenario based on all the queried contact point model data and displays the business functions belonging to the middle platform user.

[0069] In a specific example of the present invention, the above method of the present invention can be implemented through the following eight steps.

[0070] Step 1: Plan the scenarios that the system needs to support and set scenario values for each scenario; the scenarios include: classified by operators such as China Mobile, China Telecom, China Unicom, etc.; classified by specialties such as by slices, sub-slices, 5G, 4G, core network, bearer network, wireless network, NOC, network data analysis, etc.; classified by users such as enterprise and government users, configuration users, partner users, etc. Determine the touchpoint scope and organizational relationship between touchpoints for each scenario.

[0071] Step 2: The business components follow the touchpoint model specification, and in combination with the scenarios in Step 1 above, design the touchpoint model files for each scenario and save them according to the specification of one scenario per directory.

[0072] Step 3: Set the scenarios as needed after the system installation and deployment are completed.

[0073] Step 4: After the scenario setting in Step 3 is completed, the touchpoint capability management scans and analyzes the matching touchpoint models according to the scenario values by the touchpoint model analyzer. The touchpoint capability management module is responsible for collecting the model data of all components, aggregating the full amount of touchpoint model data by scenario, and maintaining the lifecycle management of the touchpoint models in real time according to the lifecycle of the components.

[0074] Step 5: The system administrator maintains the binding between users and scenarios.

[0075] Step 6: The user accesses the middleware portal.

[0076] Step 7: The portal service calls the touchpoint capability management interface and obtains the matching touchpoint model data according to the current scenario.

[0077] Step 8: After the portal service obtains the touchpoint model data, it instantiates the touchpoints according to the touchpoint model and displays them in the portal.

[0078] Figure 1B Disclosed is a model-driven intelligent operation and maintenance middleware portal device of the present invention, which is characterized by including: each business component of the intelligent operation and maintenance middleware, used to construct the touchpoint model files for each scenario according to the touchpoint model specification; a touchpoint model analyzer, used to scan and analyze the matching touchpoint model files according to the scenario values of the set scenarios; a touchpoint capability management module, used to save the touchpoint model files for each scenario according to the specification of one scenario per directory; and after the touchpoint model analyzer scans and analyzes the matching touchpoint model files according to the scenario values of the set scenarios, collect the touchpoint model data from the matching touchpoint model files and aggregate the collected touchpoint model data by scenario, so as to provide a middleware portal by binding the middleware users with the scenarios.

[0079] In addition, the above-mentioned model-driven intelligent operation and maintenance middle platform portal device of the present invention further includes: a user management module for binding middle platform users to scenarios; a portal service module for responding to user login requests to obtain touchpoint model data, instantiating according to the touchpoint model description, and providing a middle platform portal according to scenarios.

[0080] The following Figures 2 to 8 Taking 5G as an example, the present invention will be described in detail. It should be noted that the present invention can also be applied to mobile communication systems after 5G.

[0081] Figure 2 shows the intelligent operation and maintenance architecture level and front-end applications. 5G intelligent operation and maintenance can be divided into three major levels, namely the professional service layer, the end-to-end service layer, and the front-end application layer. Intelligent operation and maintenance integrates multiple domains and multiple systems to achieve the integration of business design and intelligent operation and maintenance operation management. In the front-end application layer, major business functions are integrated through the middle platform portal to provide business services for different users.

[0082] Figure 3 shows the front and back ends. The front-end portal can be divided into slices, sub-slices, 5G, 4G, core network, bearer network, radio network, etc. positions according to operation and maintenance functions. The business functions used by different positions are not the same. See Figure 4 the different business functions displayed by different positions in

[0083] The 5G intelligent operation and maintenance middle platform involves a large number of business components and business functions, such as radio network element configuration, wireless VNF management, signaling trace analysis, device perception management, topology management, bearer network element configuration, automatic discovery, network slicing, intent management, intelligent inspection, alarm management, performance management, resource analysis, PLMN, etc. components, with up to hundreds of function touchpoints.

[0084] For Figure 4 the professional position operation and maintenance scenarios, the implementation is carried out according to the following steps:

[0085] Step 1: Design scenarios. As Figure 4 shown, for the scenario name, the scenario for the radio network operation and maintenance position is "RAN (Radio Access) OAM (Operation and Maintenance)", the scenario for the bearer network operation and maintenance position is "BN (Bearer Network) OAM", the scenario for the core network operation and maintenance position is "CN (Core Network) OAM", and the 5G operation and maintenance scenario is "5G OAM".

[0086] The touchpoint model descriptions of business components designed for scenarios are as follows

[0087] Radio network element configuration component: The touchpoint model file is ran-ne-cm-touch.json. For easy understanding, the model code snippet is shown as follows:

[0088]

[0089] The contact model content includes contact ID, contact name, contact response href, contact attachment relationship parentId, and sorting sequence number order.

[0090] Wireless VNF management component: The contact model file is ran-vnf-mgt-touch.json, and the model code is shown above;

[0091] Auto-discovery component: The contact model file is ne-discover-touch.json, and the model code is shown above.

[0092] The same business component can describe different contact models for different business scenarios. For example, the alarm management component can be mounted at different positions in the scenarios of wireless network, bearer network, and core network. Examples are as follows:

[0093] Contact model file for wireless network scenario: fm-ran-touch.json

[0094]

[0095] Contact model file for bearer network: fm-bn-touch.json

[0096]

[0097] Contact model file for core network scenario: fm-cn-touch.json

[0098]

[0099] It should be noted that when the same function is mounted at different positions in different scenarios, only the different parent node parentIds need to be described in the model description, and the parent-child attachment relationship can be flexibly defined.

[0100] After completing the contact model of the business component, save it according to the specification of one scenario, one directory, and one model, as shown in Figure 5 as shown.

[0101] Figure 6 Shows the data processing flow involved in the present invention, including:

[0102] Step 1: Product installation and deployment;

[0103] Step 2: Set the scenario value according to the actual scenario and broadcast the message through the message middleware; for example, set to support three professional scenarios of RAN OAM, CN OAM, and BN OAM

[0104] Step 3: The component listens to the scenario notification and starts the model scanner; see Figure 5As shown in the figure, taking the alarm component as an example, model files such as fm-ran-touch.json will be scanned by RAN OAM according to the scenario name, fm-bn-touch.json will be scanned by BN OAM, and fm-cn-touch.json will be scanned by CN OAM. Other components are similar and will not be listed one by one.

[0105] Step 4: The model analyzer scans the contact model files according to the scenario value and sends the contact model data in the scanned contact model files to the contact capability management.

[0106] Step 5: The contact capability management receives the model message, is responsible for synthesizing all eligible contact models into a total contact model according to the scenario and persisting it, and synchronously starts the contact model lifecycle management; see Figure 5 The model corresponds to the scenario. After this step is completed, the following aggregated model schematic will be formed:

[0107]

[0108]

[0109] Figure 7 It shows the binding of the mid-platform user to the scenario, and assigns scenario tags to the user, including:

[0110] Step 1: The system administrator enters the user management and sets the corresponding usage scenario according to the user's job responsibilities.

[0111] Step 2: Create a new user or modify an existing user; for example, create a user User A for the wireless network operation and maintenance position.

[0112] Step 3: Set the binding relationship between the user and the scenario; set the scenario tag of User A as RAN OAM.

[0113] Figure 8 It shows the process of portal instantiation for user login:

[0114] Step 1: The mid-platform user User A logs in to the portal.

[0115] Step 2: After authentication, request portal instance data from the portal service.

[0116] Step 3: Automatically verify the user scenario tag. The scenario of User A is RAN OAM.

[0117] Step 4: The user brings the scenario tag, obtains that the user belongs to the scenario tag RAN OAM, and queries the contact model from the contact capability management with the RAN OAM tag, and returns the contact model related to RAN OAM in Embodiment 3.

[0118] Step 5: The contact point capability management returns all the contact point model data according to the RAN OAM scenario;

[0119] Step 6: Instantiate the portal according to the RAN OAM scenario and display the service functions belonging to User A.

[0120] Although the present invention has been described in detail above, the present invention is not limited thereto, and those skilled in the art of the present technology can make various modifications according to the principles of the present invention. Therefore, all modifications made according to the principles of the present invention should be understood to fall within the protection scope of the present invention.

Claims

1. A model-driven intelligent operation and maintenance middle platform portal method, characterized in that, Including: Each business component of the intelligent operation and maintenance middle platform constructs a contact model file for each scenario according to the contact model specification; The contact capability management module stores the contact model files for each scenario according to the specification of one scenario and one directory; After each business component listens to the scenario notification carried with the scenario value broadcast by the message middleware, it starts the contact model scanner; The contact model scanner scans and analyzes the matchable contact model files according to the scenario value, collects the contact model data from the matched contact model files, and aggregates the collected contact model data by scenario, so as to provide a middle platform portal by binding the middle platform users to the scenarios.

2. The method according to claim 1, characterized in that, It also includes the life cycle management steps of the contact model after aggregating the collected contact model data by scenario, specifically: The contact capability management module forms a contact model by aggregating the collected contact model data by scenario; The contact capability management module maintains the life cycle of the contact model in real time according to the life cycles of each business component of the intelligent operation and maintenance middle platform.

3. The method according to claim 1 or 2, characterized in that, The business component is a program that provides complete services for a certain function and is independently deployed; the middle platform portal provides a unified login entrance, the business functions in the portal are composed of a series of contacts, and the business functions are displayed according to the application scenarios; the contact is the function entrance for users to operate in the middle platform portal.

4. The method according to claim 1 or 2, characterized in that, The contact model file includes: contact ID; contact name; contact response href; contact attachment relationship parent Id and sorting serial number order.

5. The method according to claim 1 or 2, characterized in that, The providing of the middle platform portal by binding the middle platform users to the scenarios includes: Binding each middle platform user to the corresponding usage scenario according to the job responsibilities of the middle platform user and its corresponding usage scenario; When a user accesses the middle platform portal, the portal service module obtains the contact model data matching the scenario according to the binding relationship between the middle platform user and the scenario; After the portal service module obtains the contact model data, it instantiates the contacts according to the contact model and displays them in the portal.

6. The method according to claim 1 or 2, characterized in that, The binding of each middle platform user to the corresponding usage scenario includes: setting the scenario label of the corresponding usage scenario for each middle platform user.

7. The method according to claim 1 or 2, characterized in that, When a user accesses the middle platform portal, the portal service module obtaining the contact model data matching the scenario according to the binding relationship between the middle platform user and the scenario includes: After the middle platform user logs in to the middle platform portal, it queries the contact model from the contact capability management module by using the scenario label; The contact capability management module instantiates the portal according to the scenario based on all the queried contact model data and displays the business functions belonging to the middle platform user.

8. A model-driven intelligent operation and maintenance middle platform portal device, characterized in that, Including: Each business component of the intelligent operation and maintenance middle platform is used to construct a contact model file for each scenario according to the contact model specification; The contact model analyzer is used to scan and analyze the matchable contact model files according to the scenario value of the set scenario; Contact ability management module, where users save the contact model files of each scenario according to the specification of one scenario - one catalog; and after each business component listens to the scenario notification carried with the scenario value broadcast by the message middleware, start the contact model scanner; the contact model scanner scans and analyzes the matchable contact model files according to the scenario value, collects the contact model data from the matchable contact model files, and aggregates the contact model data by scenario, so as to provide a scenario - based middleware portal by binding the middleware users with the scenarios.

9. The model-driven intelligent operation and maintenance middle platform portal device according to claim 8, characterized in that, It further includes: User management module, which is used to bind the middleware users with the scenarios; Portal service module, which is used to obtain the contact model data in response to the user login request, instantiate according to the contact model description, and provide a scenario - based middleware portal.

Images