CN103036694A - Service distribution method and device of distributed network - Google Patents

Abstract

The invention discloses a service configuration method and device in a distributed network. Wherein, the method includes: determining the involved NE according to the currently configured service; receiving the initial configuration information of the service input by the administrator through SMS; wherein, the SMS includes an abstract management model; obtaining the device layer of the NE from the NE according to the initial configuration information and network layer configuration data, and store the obtained configuration data in a configuration database based on an abstract management model; create service configuration data according to the configuration data in the configuration database, and store the service configuration data in the configuration database; The above configuration database generates service configuration information of the NE; configures the service configuration information to the NE. The present invention solves the problem that the service configuration mode in the existing distributed network is complex and inconvenient for operators to use, and further achieves the effect of improving service configuration efficiency and enhancing system performance.

Description

Service Configuration Method and Device in Distributed Network

technical field

The present invention relates to the communication field, in particular, to a service configuration method and device in a distributed network.

Background technique

A basic trend in the development of the next-generation access network is to use the FTTX (Fiber To The x) network architecture to support IP-based full-service converged access. Among them, access network equipment tends to be deployed in a distributed manner, that is, the location is moved down from the central computer room of the central office to an external environment close to customers. Businesses place more emphasis on end-to-end management and service quality assurance. In addition, operators have various types of access network equipment and inconsistent configuration and management interfaces. These factors make the provisioning and management of access network services very complicated, especially in terms of end-to-end service configuration and management. For example, at present, MSO (Multi-Service Operator, multi-service operator) has EPON (Ethernet Passive Optical Network, Ethernet Passive Optical Network, Ethernet passive Optical network) OLT (Optical Line Terminal, optical line terminal), ONU (Optical Network Unit, optical network unit), DEMARC (demarcation, separation equipment), CMC (Converged Media Converter, centralized media converter), CBAT (Coaxial Broadband Access Terminal , coaxial broadband access terminal), edge modulator (IPQAM), MDU (Management Data Unit, management data unit) and Cable Modem (cable modem). Hereinafter, these distributed access network devices are collectively referred to as NE (Network Element, network device).

At present, the mode of configuring and managing NE in the prior art consists of two parts: 1) manual configuration of the network equipment at the central office by means of command line and SNMP (Simple Network Management Protocol); 2) DOCSIS and TR-069 The method is used for automatic configuration of terminal access equipment, and this method is only for configuring Cable Modem, DSL Modem (Digital Subscriber Line Modem), ONU and other single user-side terminal equipment.

In the above mode, the configuration of network devices is centered on the function of the device or a single node, and is manually created and maintained by network managers, and then the configuration is sent to each network device in different ways. For the remote NE, when there are multiple services that need to be configured, the above configuration method will be more complicated and inconvenient for the operator to use.

Contents of the invention

The main purpose of the present invention is to provide a service configuration method and device in a distributed network, so as to at least solve the above-mentioned problem that the configuration method is complicated and inconvenient for operators to use.

According to one aspect of the present invention, a service configuration method in a distributed network is provided, including: determining the involved NE according to the currently configured service; receiving the initial configuration information of the service input by the administrator through SMS; wherein, the SMS includes Abstract management model; obtain device layer and network layer configuration data of NE from NE according to the initial configuration information, and store the obtained configuration data in the configuration database based on the abstract management model; create service configuration according to the configuration data in the configuration database data, storing the service configuration data in the configuration database; generating service configuration information of the NE based on the configuration database; and configuring the service configuration information to the NE.

Before receiving the initial configuration information of the service input by the administrator through the SMS, the above method also includes: establishing an abstract management model according to the NE and the service, wherein the abstract management model includes a device layer, a network layer and a service layer; based on the abstract management model is The service creates an SMS, wherein the SMS includes a configuration database provided with an abstract management model.

After the above-mentioned business configuration data is stored in the configuration database, the above method also includes: performing end-to-end and business-related cross-validation on the configuration data according to the constraints corresponding to the business, and after passing the verification, execute the process of generating NE. Steps for business configuration information.

The service configuration information of the NE generated above includes one of the following: XML-based configuration files, TLV-based configuration files, or MIB-based configuration objects.

The above configuration of the service configuration information to the NE includes one of the following: sending the service configuration information to the NE through a configuration update command; sending the service configuration information to the NE during the initialization process of the NE.

The aforementioned NEs include at least one of the following: central office NEs, outdoor NEs and user terminal NEs.

The above abstract management model is a visualized graph structure.

According to another aspect of the present invention, a service configuration device in a distributed network is provided, including: a network element determination module, used to determine the involved NE according to the currently configured service; an initial configuration information receiving module, used to Receive the initial configuration information of the service input by the administrator; wherein, the SMS includes an abstract management model; the configuration data acquisition module is used to obtain the device layer and network layer configuration data of the NE from the NE according to the initial configuration information received by the initial configuration information receiving module , and store the obtained configuration data in the configuration database based on the abstract management model; the configuration data creation module is used to create business configuration data according to the configuration data in the configuration database, and store the business configuration data in the configuration database; business configuration The information generation module is used to generate the service configuration information of the NE based on the configuration data in the abstract management model; the configuration module is used to configure the service configuration information generated by the service configuration information generation module to the NE.

The above device also includes: a model building module, used to create an abstract management model according to NEs and services, wherein the abstract management model includes a device layer, a network layer and a service layer; an SMS creation module, used to create SMS for services based on the abstract management model , wherein the SMS includes a configuration database provided with an abstract management model.

The above device also includes: a verification module, which is used to perform end-to-end and business-related cross-verification of the business configuration data created by the business configuration data creation module according to the constraints corresponding to the business; a trigger module, which is used for the verification module After the verification results of the end-to-end and cross-verification are all passed, the service configuration information generation module is triggered to generate the service configuration information of the NE.

The aforementioned NEs include at least one of the following: central office NEs, outdoor NEs and user terminal NEs.

Through the present invention, service configuration information is generated through the abstract management model of SMS, and service configuration can be performed on various types of NEs, and the configuration method is simple and easy, which solves the problem that the service configuration method in the existing distributed network is complicated and inconvenient for operators The problem of use can achieve the effect of improving business configuration efficiency and enhancing system performance.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 is a flowchart of a service configuration method in a distributed network according to an embodiment of the present invention;

FIG. 2 is a specific flowchart of a service configuration method in a distributed network according to an embodiment of the present invention;

3 is a schematic diagram of a multi-dimensional abstract management model created according to the service configuration management of S-OAM in Example 1 of the present invention;

Fig. 4 is a flow chart of a method for S-OAM service configuration and device information interaction between SMS and S-NE according to Example 1 of the present invention;

FIG. 5 is a schematic diagram of a configuration management architecture for multiple services on heterogeneous devices according to Example 2 of the present invention;

Fig. 6 is a schematic diagram of an abstract management model for configuration management of multiple services on heterogeneous devices according to Example 2 of the present invention;

7 is a flowchart of a method for configuring multiple access services and interacting with device information according to Example 2 of the present invention;

Fig. 8 is a structural block diagram of a service configuration device in a distributed network according to an embodiment of the present invention;

Fig. 9 is a specific structural block diagram of a service configuration device in a distributed network according to an embodiment of the present invention.

Detailed ways

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

The NE in the embodiment of the present invention is a network device in a distributed network environment. The NE can be a central office NE, an outdoor NE, or a user terminal NE (that is, user-side equipment, such as SFU/SBU/HGU and intelligent set-top boxes, etc.) . By establishing an abstract data model and a configuration database for global business configuration, and on this basis, cooperate with automatic discovery of network devices and dynamic reading of device information to create an abstract management system based on the business configuration management server (hereinafter referred to as SMS, Service Management Server). The business configuration of the model. SMS provides the following unique configuration management functions: 1) SMS can automatically discover and identify NEs deployed in a distributed manner, and collect information on the device layer and network layer of NEs; 2) SMS has a global service configuration database and visualized service The configuration creation view (also called an abstract management model) can facilitate network administrators to create service configurations globally and end-to-end. 3) SMS can dynamically generate configurations for heterogeneous devices supporting different services, and provide convenience for unifying standards and interfaces of heterogeneous NE configurations. 4) SMS can support end-to-end and multi-service configuration cross-validation.

Referring to the flow chart of the service configuration method in the distributed network shown in Figure 1, the method can be run on a general server, including the following steps:

Step S102: Determine the involved NE according to the currently configured service.

Step S104: receiving the initial configuration information of the service input by the administrator through SMS; wherein, the SMS includes an abstract management model.

The abstract data model is based on the global service configuration and can be stored in the configuration database in the SMS. The SMS in this embodiment runs on a general server.

Step S106: Obtain device layer and network layer configuration data of the NE from the aforementioned NE according to the aforementioned initial configuration information, and store the acquired configuration data into a configuration database based on an abstract management model.

Step S108: Create service configuration data according to the configuration data in the configuration database, and store the service configuration data in the configuration database.

Step S110: Generate service configuration information of the NE based on the configuration database.

Step S112: Configure the above-mentioned service configuration information to the above-mentioned NE.

This embodiment generates service configuration information through the abstract management model of SMS, and can perform service configuration on various types of NEs, and the configuration method is simple and easy, which solves the problem of complex service configuration methods in existing distributed networks, which are not convenient for operators to use problems, to achieve the effect of improving business configuration efficiency and enhancing system performance.

The creation process of the above-mentioned SMS may include: establishing an abstract management model according to the above-mentioned NE and the above-mentioned service, wherein the abstract management model includes a device layer, a network layer and a service layer; creating an SMS for the service based on the abstract management model, wherein the SMS A configuration database provided with the abstract management model is included. It can be seen that this abstract management model is designed according to the specific services and devices to be configured, and the configuration parameters (ie, service configuration information) will be defined according to this model and stored in the SMS configuration database. The configuration in this embodiment has different levels, including service-oriented, network-oriented and equipment-oriented. This hierarchical abstract management model can make business configuration clearer and more intuitive.

In this embodiment, when performing service configuration, a multi-dimensional abstract management model is created according to the service to be configured. This management model has three dimensions: business layer, network layer and device layer. Based on this abstract configuration management model, build an SMS to centrally save and manage service configuration information, and automatically generate corresponding configurations for each NE. Then design a corresponding standard process and interface for business configuration and device information interaction. This information delivery process can be based on the established network management channel between SMS and NE. In the carrier network, it generally refers to connecting NE and SMS to the same management network (Management Network).

In order to enhance data security, after storing the obtained configuration data in the configuration database based on the abstract management model, the method further includes: performing end-to-end association of the configuration data with the business according to the constraints corresponding to the business After the cross-verification of various services passes the verification, the above step of generating the service configuration information of the NE is performed. Wherein, the constraint conditions here are pre-defined according to the service to be configured.

The business configuration information of the NE generated by this embodiment includes one of the following: a configuration file based on XML (eXtensible MarkupLanguage, Extensible Markup Language), a configuration file based on TLV (Tag Length Value, tag, length, value), or based on MIB (Management Information Base, Management Information Base) configuration object.

In order to ensure that the service configuration information on the server side is synchronized with the service configuration information on the NE, this embodiment can adopt one of the following methods to configure the service configuration information to the NE: 1) send the service configuration information to the above-mentioned NE through a configuration update command; 2) Sending the service configuration information to the NE during the initialization process of the above NE.

Based on the SMS created above, this embodiment also provides a specific method of a service configuration method in a distributed network. Referring to FIG. 2, the method includes the following steps:

Step S202: The user (network administrator) inputs initial information of NE related to service configuration (for example: NE's IP, password and service ID) on SMS.

Step S204: The SMS dynamically reads the information of the NE, and imports the configuration data of the device layer and the network layer of the NE into the model of the device layer and the network layer in the SMS.

After the above NE is started, the SMS reads relevant information from the NE to establish a basic service view (data).

Step S206: On the basis of the configuration data model of the relevant equipment layer and network layer, the user creates an end-to-end and multi-service configuration management model on the SMS (here is an example of creating this model specifically (it needs to be implemented with data) model)), and save the business configuration model data in SMS.

Step S208: The SMS can automatically perform end-to-end and multi-service cross-validation on the stored service configuration model data according to predetermined constraints, so as to ensure the correctness of the service configuration.

Step S210: The SMS automatically generates an XML or TLV-based configuration file or MIB configuration object for each relevant NE according to the service configuration model data, and downloads the configuration to the NE. This process can be triggered by an action on the SMS or NE to ensure that the configuration on the SMS is synchronized with the configuration on the device (for example, both the configuration update command on the SMS and the initialization of the NE can trigger this configuration synchronization process). The synchronization process is to synchronize the configuration saved in the SMS with the configuration downloaded to the device. That is, the service configuration on the NS is generated by the SMS and downloaded to the device.

Step S212: According to the received configuration file or MIB configuration object, the NE loads the service configuration, and feeds back the configuration status to the SMS.

The service configuration method in this embodiment can better support the deployment and maintenance of end-to-end and multiple services, and can complement the existing DOCSIS Provisioning and TR-069 equipment configuration process of the operator. The basic service parameters of the user terminal equipment ONU and CableModem can also be configured by DOCSIS Provisioning and TR-069, and the method of this embodiment can be used to uniformly configure and manage the central office NE, outdoor NE and user terminal NE, and End-to-end and complex service configurations are supported. Of course, the above methods can also be integrated into the functions of DOCSIS Provisioning and TR-069 to realize a unified service configuration platform.

The above-mentioned method is illustrated below through specific examples.

Example 1

This example is an example of end-to-end service configuration, which is the service configuration of S-OAM (Service OAM) for L2VPN service in the DOCSIS Provisioning over EPON (DPON) network environment. In order to realize the end-to-end management and monitoring of the customer's L2VPN link, the operator needs to configure MEP (Maintenance End Point) (or MIP ), so as to configure the S-OAM service parameters end-to-end. Before starting to configure S-OAM, the L2VPN link already exists, and the IP-based management channel between SMS and S-NE has been established. The following is the specific implementation process of this example.

FIG. 3 is a schematic diagram of a multi-dimensional abstract management model created by S-OAM service configuration management. In order to abstract and clearly define the objects involved in business configuration, so that SMS can configure the operation of model objects, the following is an example of this abstract management model.

S-OAM-capable NE (S-NE)-Container of BridgeElements (device layer)

Management IP (Management IP)

Bridge Elements: For example (i.e. {BE-a1, BE-a2, BE-a3})

Bridge Element (BE) (network layer)

Unique identifier: Bridge MAC (Identifier: Bridge MAC)

Type: ONU, OLT, VFI, PBB, Demarc, CMTS and CM

Virtual private network instance (VPN Service Instance) (business layer)

Unique identifier (Identifier): VPNID i.e.VPN-a

Type: EPL/ETREE/ELAN

Maintenance instance point MEP (business layer)

Name: i.e.BE-a1

Maintenance level (MD Level)

Maintenance instance pairs (MEP Peers): i.e. {MEP-a2, MEP-a3, MEP-a4}

Configure Bridge Element to Deploy: i.e.BE-a1

Fault Management (FM) Attributes

Performance Management (PM) Attributes

On the basis of this abstract management model, an S-OAM service configuration management service is established on SMS. The flow chart of the method for S-OAM service configuration and device information interaction between SMS and S-NE as shown in Figure 4 includes the following steps:

Step S402: The user inputs initial information (such as DML IP, password, VPN ID) related to the designated VPN service S-NE.

Step S404: The SMS dynamically reads the S-NE and Bridge Element information related to the specified VPNID, and imports the data into the data model of the device layer and the network layer in the SMS.

Step S406: Based on the bridge element data model, the user sets the MEP on the bridge element end-to-end on the SMS, configures the S-OAM parameters for the VPN service, and saves the service configuration model data in the SMS.

Step S408: SMS automatically performs end-to-end cross-validation on the S-OAM configuration model data according to predetermined constraints, so as to ensure correct service configuration.

The constraint condition may be that the parameters of the two MEPs configured on different devices must cooperate with each other (their parameter settings must cooperate with each other according to the S-OAM specification), so as to form a Peer, otherwise there will be problems with the configured Peer.

Step S410: The SMS automatically generates an XML configuration file or MIB configuration object for each relevant S-NE according to the S-OAM service configuration model data, and downloads the configuration to the S-NE. This process can be triggered by a configuration update command on the SMS to ensure that the configuration on the SMS is synchronized with the configuration on the device.

Step S412: The S-NE loads the configuration of the S-OAM, and feeds back the configuration status to the SMS.

Example 2

This example is an example of configuring and managing multiple services on heterogeneous devices. Under the FTTX access network architecture centered on the DOCSIS Provisioning over EPON (DPoE) system, in order to support Internet access, digital TV and video on demand, etc. This service is used to centrally configure distributed NEs. As shown in Figure 5, a schematic diagram of the configuration management architecture for multiple services on heterogeneous equipment, which involves IP, VLAN, QOS on PON and CMC system equipment, and IP-to-QAM video stream conversion and coaxial on IPQAM equipment near the user side Interrelated and complex multiple service configurations such as line frequency band allocation. However, terminal equipment such as ONU and CM can still be configured by the existing DOCSIS Provisioning method. Before performing service configuration on NE, the IP-based management channel between SMS and NE has been established. The following is the specific implementation process of this example.

Figure 6 is a schematic diagram of an abstract management model for configuration management of multiple services on heterogeneous devices. In this example, a multi-dimensional abstract management model is created to support centralized configuration management of multiple access services. The abstraction is as follows Example of a management model.

Converged Network Element (C-NE)-(Network Layer)

Management IP (Management IP)

Access headend list (Access Network Nodes): i.e. {AN1, AN2...ANn}

Equipment performance parameters (Capacity)

Device Configurations

Access Headend (Access Node) (Network Layer)

Unique identifier (Identifier): head end number or name (Node Name)

Access network element list (A-NEs): {NE1, NE2...NEn}

Access Network Element (A-NE) (Device Layer)

Unique identifier (Identifier): network element MAC

Category (Type): OLT, IPQAM, CMC or IPQAM+CMC

model

Software version (SW Version)

Equipment performance parameters (Capacity)

ONU-related (Related)

IPQAM related (Related)

CMC related (Related)

Device Configurations

IPQAM (service layer)

Unique identifier (Identifier): network element MAC (IPQAM NE’s MAC)

Access headend identification (Access Network Node): headend number or name (Node Name)

RF Channel Configuration

Stream Mapping (TS Mapping)

VLAN configuration (Configurations)

Other Configurations

IP Internet (service layer)

Unique identifier: network element MAC (Identifier: CMC NE’s MAC)

Access headend identification: headend number or name (AccessNetworkNode: NodeName)

RF Channel Configuration

DOCSIS configuration (Configuration)

DHCP relay configuration (Relay Configuration)

VLAN configuration (Configurations)

Routing Configuration (IP Routing Configuration)

Other Configurations

On the basis of this abstract management model, a multi-access service configuration management service is established on SMS. The flow chart of the method for multiple access service configuration and device information interaction as shown in Figure 7 includes the following steps:

Step S702: The user enters the initial information of the relevant C-NE (such as DML IP, password) on the SMS.

Step S704: Dynamically read the relevant access node and all downlink A-NE information from the C-NE, and import the model data (that is, the information about the device layer and the network layer) into the SMS.

Step S706: On the data models of A-NE, access node and C-NE, create an overall configuration model of multiple devices and multiple services.

Step S708: Perform cross-validation between multiple services on the overall configuration model, such as RF channel frequency allocation conflict detection for IP HSD and IPQAM services under the access node.

Step S710: The SMS automatically generates an XML configuration file or MIB object configuration for each NE, and downloads the configuration to the NE.

Step S712: The NE loads the configuration, and feeds back its configuration status to the SMS.

The above examples provide end-to-end service configuration and management of various service configurations on heterogeneous devices. Through model service configuration, various types of services can be uniformly configured intuitively, which is simple to implement and highly efficient in service configuration.

Referring to the structural block diagram of the service configuration device in the distributed network shown in Figure 8, the device can be set on a general server, and it includes the following modules:

A network element determining module 81, configured to determine the involved network element NE according to the currently configured service;

The initial configuration information receiving module 82 is connected to the network element determination module 81, and is used to receive the initial configuration information of the service input by the administrator through SMS; wherein, the SMS includes an abstract management model;

The configuration data obtaining module 83 is connected with the initial configuration information receiving module 82, and is used to obtain the device layer and network layer configuration data of the NE from the above-mentioned NE according to the initial configuration information received by the initial configuration information receiving module 82, and the obtained configuration Data is stored in a configuration database based on an abstract management model;

The service configuration data creation module 84 is connected with the configuration data acquisition module 83, and is used to create service configuration data according to the configuration data in the configuration database, and store the service configuration data in the configuration database; the abstract management model of this embodiment can be Visual support for network management personnel to create business configurations, such as support for device layer and network layer information visualization;

The service configuration information generation module 85 is connected to the service configuration data creation module 84, and is used to generate the service configuration information of the above-mentioned NE based on the configuration database;

The configuration module 86 is connected to the service configuration information generation module 85 and configured to configure the service configuration information generated by the service configuration information generation module 85 to the above-mentioned NE.

This embodiment generates service configuration information through the abstract management model of SMS, and can perform service configuration on various types of NEs, and the configuration method is simple and easy, which solves the problem of complex service configuration methods in existing distributed networks, which are not convenient for operators to use problems, to achieve the effect of improving business configuration efficiency and enhancing system performance.

Wherein, the device further includes: a model building module, used to build an abstract management model according to NEs and services, wherein, the abstract management model includes a device layer, a network layer and a service layer; an SMS creation module, used to create an abstract management model for services based on the abstract management model SMS, wherein the SMS includes a configuration database provided with an abstract management model.

In order to enhance the security of the system, referring to FIG. 9, in addition to the various modules shown in FIG. 8, the device may also include: a verification module 92, which is connected to the business configuration data creation module 84, and is used to, according to the constraints corresponding to the business, The business configuration data created by the business configuration data creation module 84 is carried out end-to-end and the cross-validation of multiple services associated with the business; the trigger module 94 is connected with the business configuration information generation module 85, and the verification result for the verification module is end-to-end After both the NE and the cross-validation pass, the service configuration information generation module 85 is triggered to generate the service configuration information of the NE.

The NE in this embodiment includes at least one of the following: a central office NE, an outdoor NE, and a user terminal NE.

The service configuration information of the NE generated by the service configuration information generation module 85 in this embodiment includes one of the following: XML-based configuration files, TLV-based configuration files, or MIB-based configuration objects.

In order to ensure that the service configuration information on the server side is synchronized with the service configuration information on the NE, the configuration module 86 of this embodiment can configure the service configuration information to the NE in one of the following ways: 1) issue the service configuration information through a configuration update command to the above NE; 2) sending the service configuration information to the NE during the initialization process of the above NE. As can be seen from the above description, the above-mentioned embodiment creates a service configuration model based on device layer and network layer information, and changes the existing configuration operation to manually perform service configuration on the NE using a command line (including viewing service-related devices and network layer information), the SMS in the above embodiments can provide tools for service creation and a configuration database based on an abstract management model, and can also automatically obtain device and network layer data, and provide visibility for the obtained data Support, with end-to-end network service management views and capabilities, capable of overall and automatic configuration of NEs that support multiple services and distributed deployments, and adopt unified configuration standards and interfaces for heterogeneous NEs, improving the performance of service configuration.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (11)

1. A service configuration method in a distributed network, characterized in that it comprises: Determine the involved network element NE according to the currently configured service; Receive the initial configuration information of the service input by the administrator through the service configuration management server SMS; wherein, the SMS includes an abstract management model; Obtain device layer and network layer configuration data of the NE from the NE according to the initial configuration information, and store the acquired configuration data into a configuration database based on an abstract management model; creating service configuration data according to the configuration data in the configuration database, and storing the service configuration data in the configuration database; generating service configuration information of the NE based on the configuration database; Configuring the service configuration information to the NE. 2. The method according to claim 1, characterized in that, before receiving the initial configuration information of the service input by the administrator via SMS, the method further comprises: Establishing an abstract management model according to the NE and the service, wherein the abstract management model includes a device layer, a network layer and a service layer; An SMS is created for the service based on the abstract management model, wherein the SMS includes a configuration database provided with the abstract management model. 3. The method according to claim 1, characterized in that, after storing the service configuration data in the configuration database, the method further comprises: Perform end-to-end cross-validation on the configuration data and multiple services associated with the service according to the constraint conditions corresponding to the service, and execute the step of generating service configuration information of the NE after all pass the verification. 4. The method according to claim 1, wherein the generated service configuration information of the NE includes one of the following: a configuration file based on Extensible Markup Language XML, a configuration file based on label, length, and value TLV, Or based on the configuration object of the management information base MIB. 5. The method according to claim 1, wherein configuring the service configuration information to the NE comprises one of the following: sending the service configuration information to the NE through a configuration update command; Sending the service configuration information to the NE during the initialization process of the NE. 6. The method according to claim 1, wherein the NE includes at least one of the following: a central office NE, an outdoor NE, and a user terminal NE. 7. The method according to any one of claims 1-6, wherein the abstract management model is a visualized graph structure. 8. A service configuration device in a distributed network, characterized in that it comprises: A network element determining module, configured to determine the involved network element NE according to the currently configured service; The initial configuration information receiving module is used to receive the initial configuration information of the service input by the administrator through the service configuration management server SMS; wherein, the SMS includes an abstract management model; The configuration data obtaining module is configured to obtain the device layer and network layer configuration data of the NE from the NE according to the initial configuration information received by the initial configuration information receiving module, and store the obtained configuration data in an abstract-based Manage the model's configuration database; A business configuration data creation module, configured to create business configuration data according to the configuration data in the configuration database, and store the business configuration data in the configuration database; A service configuration information generating module, configured to generate service configuration information of the NE based on the configuration database; The configuration module is configured to configure the service configuration information generated by the service configuration information generation module to the NE. 9. The device according to claim 8, further comprising: A model building module, configured to create an abstract management model according to the NE and the service, where the abstract management model includes a device layer, a network layer and a service layer; An SMS creating module, configured to create an SMS for the service based on the abstract management model, wherein the SMS includes a configuration database configured with the abstract management model. 10. The device according to claim 8, further comprising: A verification module, configured to perform end-to-end cross-verification of various services associated with the business on the business configuration data created by the business configuration data creation module according to the constraints corresponding to the business; The triggering module is used to trigger the service configuration information generation module to generate the service configuration information of the NE after the verification result of the verification module is that both the end-to-end and cross-verification pass. 11. The device according to claim 8, wherein the NE comprises at least one of the following: a central office NE, an outdoor NE, and a user terminal NE.

Images