Service provisioning method and device based on user demand and network configuration mapping rules

Abstract

The present invention discloses a service activation method based on user demand and network configuration mapping rules, including: issuing an end-to-end service creation request oriented to user demand based on a user-oriented end-to-end service configuration interface; converting user demand into corresponding network-side end-to-end service configuration parameters based on the mapping rules of user demand and network configuration parameters; converting network-side end-to-end service configuration parameters into intra-domain service configuration parameters of each single-domain management and control function according to a splitting or direct mapping method based on the network-side end-to-end service configuration parameters; issuing an intra-domain service pre-calculation request to each single-domain management and control system based on the intra-domain service configuration parameters, and creating services according to the pre-calculation results. The present invention simplifies user service configuration, supports one-click end-to-end service configuration, and realizes rapid mapping of user demand to network configuration parameters. The present invention also provides a corresponding service activation device based on user demand and network configuration mapping rules.

Description

Technical Field

[0001] The present invention belongs to the technical field of network management and control, and more specifically, relates to a service provisioning method and device based on user demand and network configuration mapping rules. Background Art

[0002] Traditional network management and control systems use a step-by-step approach to create end-to-end services. The creation process is complex and the parameter configuration is cumbersome, which is not conducive to the operation of operation and maintenance personnel, resulting in low efficiency in service activation and failure to meet the needs of rapid end-to-end service activation. In addition, the traditional end-to-end service activation method is a configuration method for network management and equipment, and does not support user-oriented configuration methods, that is, it is impossible to map user needs with corresponding network configuration parameters, and cannot meet the needs of rapid end-to-end service activation for users. How to solve the mapping rules between user needs and network configuration parameters, and how to achieve rapid end-to-end service activation for users have become urgent problems that need to be solved. Summary of the invention

[0003] This patent provides a service activation method based on user demand and network configuration mapping rules, which is used to solve the technical problems of realizing end-to-end service rapid activation oriented to user demand: 1. Lack of mapping rules between user demand and network configuration parameters, which cannot quickly convert user demand into corresponding network configuration parameters, resulting in a complicated configuration process. 2. Lack of end-to-end service activation interface based on user demand, which cannot directly issue service creation requests based on user demand.

[0004] To achieve the above object, according to one aspect of the present invention, a service provisioning method based on user demand and network configuration mapping rules is provided, comprising the following steps:

[0005] S11: issuing an end-to-end service creation request oriented to user needs based on the end-to-end service configuration interface oriented to the user;

[0006] S12: based on the mapping rules between user requirements and network configuration parameters, convert the user requirements into corresponding network-side end-to-end service configuration parameters;

[0007] S13: based on the network side end-to-end service configuration parameters, convert the network side end-to-end service configuration parameters into intra-domain service configuration parameters of each single-domain control function according to a splitting or direct mapping method;

[0008] S14: Based on the intra-domain service configuration parameters, a pre-calculation request for the intra-domain service is issued to each single-domain management and control system, and the service is created according to the pre-calculation result.

[0009] In one embodiment of the present invention, the network side end-to-end service configuration parameters in step S12 include:

[0010] Protection and recovery strategy: configure protection, including protection type, protection level and protection attribute; or configure rerouting, including rerouting enable and rerouting level;

[0011] Routing constraint strategy: must-pass resource setting, must-not-pass resource setting, shared risk link group constraint, avoidance of same route or maximum delay;

[0012] Bandwidth policy: CIR configuration and PIR configuration.

[0013] In one embodiment of the present invention, the mapping rule between the user demand and the network configuration parameter in step S12 specifically includes:

[0014] The "reliability" requirement is converted into the "protection and recovery strategy" and "routing constraint strategy" in the network configuration parameter column. Different network configuration parameter values ​​are assigned according to different reliability index requirements of users. Among them, the "protection and recovery strategy" corresponds to the configuration parameters related to protection and rerouting on the network side; the "routing constraint strategy" corresponds to the path-finding related parameter constraints on the network side.

[0015] The "delay" requirement is converted into the "routing constraint strategy-maximum delay" parameter in the network configuration parameter column;

[0016] The "Bandwidth" requirement is converted into the "Bandwidth Strategy" parameter in the network configuration parameter column;

[0017] The "business priority" requirement is converted into the "protection and recovery strategy" in the network configuration parameter column. Different network configuration parameter values ​​are assigned according to different business priorities. The "protection and recovery strategy" corresponds to the protection and rerouting related configuration parameters on the network side.

[0018] In one embodiment of the present invention, the mapping relationship between the network-side end-to-end service configuration parameters and the single-domain service configuration parameters in step S13 is specifically:

[0019] For the protection type, protection level and protection attribute, each single domain adopts a direct mapping method, that is, the protection type, protection level and protection attribute in the single domain are equal to the protection type, protection level and protection attribute in the end-to-end service configuration parameters on the network side;

[0020] For rerouting enable and rerouting level, each single domain adopts a direct mapping method, that is, the rerouting enable and rerouting level in the single domain are equal to the rerouting enable and rerouting level in the end-to-end service configuration parameters on the network side;

[0021] For the maximum delay, if splitting is adopted, the delay value of the end-to-end service configuration on the network side is allocated to the delay parameters of the services configured in each single domain according to the preset weight; if direct mapping is adopted, the delay parameters of the services configured in each single domain are ≤ the delay value of the end-to-end service configuration on the network side;

[0022] For the must-go or must-not-go resource settings, direct mapping is adopted, that is, the must-go / must-not-go resource settings in a single domain are equal to the must-go / must-not-go resource settings in the end-to-end service configuration parameters on the network side;

[0023] For SRLG constraints, direct mapping is adopted, that is, the SRLG setting within a single domain is equal to the SRLG constraint in the end-to-end service configuration parameters on the network side;

[0024] To avoid the same routing, direct mapping is used, that is, the service configuration within a single domain is also set to avoid the same routing constraint;

[0025] For the service CIR configuration or PIR configuration, direct mapping is adopted, that is, the CIR configuration or PIR configuration of the service within a single domain is equal to the CIR configuration or PIR configuration of the end-to-end service on the network side; the service layer path of the service within a single domain must satisfy the service layer path remaining bandwidth ≥ CIR configuration of the end-to-end service on the network side, and the service layer path PIR ≥ PIR of the end-to-end service on the network side.

[0026] In one embodiment of the present invention, step S14 specifically includes:

[0027] When the end-to-end service is a cross-network service, first analyze and determine whether the single-domain management and control system at the service layer already has a service layer path that satisfies the service creation of the customer layer management and control system:

[0028] S141. If it already exists, directly send a pre-calculation request for the intra-domain business to the customer layer management and control system, select the optimal route that meets the conditions according to the result returned by the pre-calculation, and send the intra-domain business creation according to this route;

[0029] S142. If it does not exist, first send a service layer path pre-calculation request to the service layer single domain control function, select the optimal route that meets the conditions based on the result returned by the pre-calculation, and send a service layer path creation request within the domain according to the returned result, and then refer to step S141 to complete the issuance of the service pre-calculation request to the customer layer single domain control function and the subsequent steps to create the service.

[0030] In one embodiment of the present invention, the request parameters of the user-oriented configuration interface in step S11 include:

[0031] Service source information; service destination information; service type; user requirements: including reliability, latency, bandwidth or service priority, and request parameters include one or more parameters in the user requirements.

[0032] In one embodiment of the present invention, the service types include: E-LINE, E-LAN, E-TREE, CES, L3VPN, and the service priorities include: high, medium, and low.

[0033] In one embodiment of the present invention, the protection and recovery strategy is specifically:

[0034] Protection type: 1+1 protection, 1:1 protection, no protection;

[0035] Protection level: the level of objects to be protected;

[0036] Protection attributes: waiting for recovery time, delaying time;

[0037] Rerouting enable: Enable, Disable;

[0038] Rerouting hierarchy: The hierarchy of objects that configure rerouting.

[0039] In one embodiment of the present invention, the routing constraint strategy is specifically:

[0040] Required resource settings: node, port under the node, and specified path;

[0041] The resource settings are required: node, port under the node, and specified path;

[0042] Shared risk link group constraints: avoid using the same optical cable and the same risk links;

[0043] Avoid the same route;

[0044] Maximum delay.

[0045] According to another aspect of the present invention, there is also provided a service activation device based on user demand and network configuration mapping rules, comprising at least one processor and a memory, wherein the at least one processor and the memory are connected via a data bus, and the memory stores instructions that can be executed by the at least one processor, and after the instructions are executed by the processor, they are used to complete the service activation method based on user demand and network configuration mapping rules.

[0046] In general, the above technical solution conceived by the present invention has the following beneficial effects compared with the prior art:

[0047] (1) The present invention simplifies user service configuration by defining an end-to-end service creation interface oriented to user needs, and supports one-click end-to-end service configuration;

[0048] (2) The present invention realizes rapid mapping of user requirements to network configuration parameters based on user requirements and network configuration mapping rules, thereby meeting the demand for rapid activation of user-oriented services. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A flow chart of a service provisioning method based on user demand and network configuration mapping rules in an embodiment of the present invention;

[0050] Figure 2 A schematic diagram of mapping rules between user requirements and network configuration parameters in an embodiment of the present invention;

[0051] Figure 3 A schematic diagram of an end-to-end service creation process under collaborative management of an IP network and an optical network in Example 1 of the present invention (no available tunnel, no available IP link);

[0052] Figure 4 This is a schematic diagram of the end-to-end service creation process under the collaborative management of the IP network and the optical network in Example 2 of the present invention (there are available tunnels, and the optical network path associated with the tunnel also meets the requirements). DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0054] like Figure 1 As shown, the service provisioning method based on user demand and network configuration mapping rules provided by the present invention comprises the following steps:

[0055] S11: Sending an end-to-end service creation request oriented to user needs based on the end-to-end service configuration interface oriented to the user.

[0056] The user-oriented configuration interface request parameters in S11 include but are not limited to the following information: service source information; service sink information; service type; user requirements: reliability, delay, bandwidth, service priority. The request parameters may include one or more parameters in the user requirements.

[0057] Furthermore, the specific user demand parameters are described as follows:

[0058] ■Business source information;

[0059] ■Business destination information;

[0060] ■Service type: Ethernet-Eline(Service), E-Line, Ethernet-Local Aera Network(Service), E-LAN, Ethernet-Tree(Service), E-Tree, Circuit Emulation Service (CES) or Layer Three Virtual Private Networks (L3VPN);

[0061] ■User needs:

[0062] reliability;

[0063] Delay;

[0064] bandwidth;

[0065] Business priority: high, medium, or low;

[0066] S12: Based on a mapping rule between user requirements and network configuration parameters, convert the user requirements into corresponding network-side end-to-end service configuration parameters.

[0067] The specific information of the network configuration parameters described in S12 is as follows:

[0068] Protection recovery strategy: configure protection, including protection type, protection level and protection attribute; or configure rerouting, including rerouting enable and rerouting level.

[0069] Routing constraint strategies: must-pass resource settings, must-not-pass resource settings, shared risk link group (SRLG) constraints, avoidance of the same route or maximum delay.

[0070] Bandwidth policy: Committed Information Rate (CIR) configuration and Peak Information Rate (PIR) configuration.

[0071] Furthermore, the specific network side configuration parameters are described as follows:

[0072] ■Protection recovery strategy:

[0073] Protection type: 1+1 protection, 1:1 protection or no protection;

[0074] Protection level: the level of objects to be protected;

[0075] Protection attributes: waiting time for recovery and delay time;

[0076] Rerouting enable: enable or disable;

[0077] Rerouting hierarchy: The hierarchy of objects that configure rerouting.

[0078] ■Route constraint strategy:

[0079] Required resource settings: node, port under the node or specified path;

[0080] Resource settings are not required: node, port under the node, or specified path;

[0081] Shared Risk Link Group (SRLG) constraints: avoid the same optical cable and avoid links with the same risk;

[0082] Avoid the same route;

[0083] Maximum delay.

[0084] ■Bandwidth strategy:

[0085] CIR configuration;

[0086] PIR configuration.

[0087] The mapping rules between user requirements and network configuration parameters in S12 are as follows: Figure 2 As shown, the detailed mapping relationship is as follows Table 1:

[0088] Table 1 Mapping rules between user requirements and network configuration parameters

[0089]

[0090]

[0091] The "reliability" requirement is converted into the "protection and recovery strategy" and "routing constraint strategy" in the network configuration parameter column. Different network configuration parameter values ​​are assigned according to different user requirements for reliability indicators. The "protection and recovery strategy" corresponds to the configuration parameters related to protection and rerouting on the network side; the "routing constraint strategy" corresponds to the path-finding related parameter constraints on the network side, such as the must-pass / must-not-pass path, SRLG constraint, avoidance of the same route, etc.

[0092] The "Delay" requirement is converted into the "Routing Constraint Strategy-Maximum Delay" parameter in the network configuration parameter column. This corresponds to the delay constraint of the path finding on the network side. The path delay obtained by the path finding must not exceed the maximum delay set here.

[0093] The "Bandwidth" requirement is converted into the "Bandwidth Policy" parameter in the network configuration parameter column. The bandwidth policy corresponds to the CIR configuration and PIR configuration parameters.

[0094] The "Service Priority" requirement is converted into the "Protection and Recovery Strategy" in the network configuration parameter column. Different network configuration parameter values ​​are assigned according to different service priorities. The "Protection and Recovery Strategy" corresponds to the configuration parameters related to protection and rerouting on the network side.

[0095] S13: Based on the network-side end-to-end service configuration parameters, the network-side end-to-end service configuration parameters are converted into intra-domain service configuration parameters of each single-domain management and control function according to a splitting or direct mapping method.

[0096] Based on the network topology, the boundaries of each domain are analyzed. At the same time, based on the end-to-end service configuration parameters on the network side, the intra-domain service configuration parameters of each single-domain control function are obtained by splitting or directly mapping. The mapping relationship between the end-to-end service configuration parameters on the network side and the intra-domain service configuration parameters of a single domain is described in Table 2:

[0097] Table 2 Mapping relationship between network-side end-to-end service configuration parameters and single-domain service configuration parameters

[0098]

[0099]

[0100] S14: Based on the intra-domain service configuration parameters, a pre-calculation request for intra-domain services is issued to each single-domain management and control system, and services are created according to the pre-calculation results. The details are as follows:

[0101] When the end-to-end service is a cross-network service, first analyze and determine whether the single-domain management and control system at the service layer already has a service layer path that satisfies the service creation of the customer layer management and control system:

[0102] S141. If it already exists, directly send a pre-calculation request for the intra-domain service to the customer layer management and control system, select the best route that meets the conditions according to the result returned by the pre-calculation, and send the intra-domain service creation according to this route.

[0103] S142. If it does not exist, first send a service layer path pre-calculation request to the service layer single domain control function, select the optimal route that meets the conditions based on the result returned by the pre-calculation, and send a service layer path creation request within the domain according to the returned result, and then refer to step S141 to complete the issuance of the service pre-calculation request to the customer layer single domain control function and the subsequent steps to create the service.

[0104] Embodiment 1, as Figure 3 As shown, the end-to-end service creation under the collaborative management of IP network and optical network is taken as an example to describe the service activation method based on user needs and network configuration mapping rules. In this embodiment, it is assumed that there are no available tunnels and IP links. The specific implementation method is as follows:

[0105] 1) The application layer user calls the end-to-end service activation interface and sends an L2VPN ELINE service creation request, which carries the following parameter requirements:

[0106] ■Service source information = NE A, Ethernet user side interface 1;

[0107] ■Service destination information = network element Z, Ethernet user side interface 2;

[0108] ■Business type = ELINE;

[0109] ■User needs:

[0110] Business reliability = 99.999%;

[0111] Bandwidth = 500M;

[0112] Latency ≤ 9ms.

[0113] 2) The collaboration layer converts user requirements into end-to-end service configuration parameters on the network side according to the "user requirements and network configuration parameter mapping rules", as follows:

[0114] ■ 99.99% reliability is converted into the following network-side end-to-end service configuration parameters:

[0115] <Protection type=1+1;

[0116] Protection level = tunnel;

[0117] Protection attribute = waiting time for recovery is 1 minute, and the protection delay time takes the default value of 60ms; >

[0118] <Protection type=1+1;

[0119] Protection level = Optical Channel Data Unit-k (ODUk);

[0120] Protection attribute = waiting time for recovery is 1 minute, and the protection delay time takes the default value of 10ms; >

[0121] Routing constraint strategy = primary and backup paths should avoid using the same optical cable, and primary and backup paths should avoid using the same route;

[0122] ■ Bandwidth 500M is converted into the following network-side end-to-end service configuration parameters:

[0123] The service bandwidth of Layer Two Virtual Private Networks (L2VPN) is CIR = 500M, PIR = physical port rate value;

[0124] The remaining bandwidth of the service layer tunnel of L2VPN service is ≥500M;

[0125] The remaining bandwidth of the IP link is ≥500M;

[0126] ■ The latency of 9ms is converted into the following network-side end-to-end service configuration parameters:

[0127] L2VPN service latency ≤ 9ms.

[0128] 3) The collaboration layer analyzes the boundary information of each domain based on the topology information; at the same time, based on the network-side end-to-end service configuration parameters obtained in step 2), the intra-domain service configuration parameters of each single domain are obtained by splitting or directly mapping, as follows:

[0129]

[0130]

[0131] 4) The collaboration layer obtains tunnel information from each single-domain IP network control function.

[0132] 5) The single-domain IP network control function returns the tunnel information within each domain to the collaboration layer.

[0133] 6) The collaborative layer completes cross-domain end-to-end tunnel splicing based on the acquired tunnel information and analyzes whether there are tunnels that meet the conditions, that is, whether there are tunnels that meet the requirements in step (2) (including whether the optical network services associated with the tunnel meet the requirements of step (2)).

[0134] 7) According to the conclusion obtained in step 6), if there is no available tunnel, the coordination layer analyzes whether there is an existing IP link that meets the conditions in this layer.

[0135] 8) If there is no available IP link, the collaborative layer sends a single-domain optical network client-side service pre-calculation request to the single-domain optical layer management and control function based on the analyzed optical network boundary and the service configuration parameters of each single-domain optical network domain analyzed in step 3).

[0136] 9) Each single-domain optical layer control function completes the pre-calculation within the domain.

[0137] 10) Each single-domain optical layer control function returns the pre-calculation results of the services in its own domain to the collaboration layer.

[0138] 11) The collaborative layer splices the optimal optical network client-side service path and parameters that meet the conditions based on the pre-calculated results of each single-domain optical network control function received.

[0139] 12) The collaborative layer creates a request for the optical network client-side service under each single-domain optical network management and control function based on the optical network client-side service path and parameters obtained in step 11).

[0140] 13) Each single-domain optical layer control function returns the service creation results within its own domain to the collaborative layer.

[0141] 14) The coordination layer splices and generates end-to-end optical network client-side services based on the results returned in step 13), and associates and generates IP links.

[0142] 15) The collaboration layer obtains the range of available resources (such as tunnel labels, etc.) in each domain from the IP layer control function of each single domain.

[0143] 16) Each single domain IP layer control function returns the available resource information of each domain to the collaboration layer.

[0144] 17) The collaboration layer sends intra-domain VPN pre-calculation requests to each single-domain IP network control function based on the boundary information of each single-domain IP network and the intra-domain service configuration parameters obtained in step 3), the IP link obtained in step 14), and the available resources obtained in step 16).

[0145] 18) Each single-domain IP network control function completes the pre-calculation of intra-domain tunnels.

[0146] 19) Each single-domain IP network control function returns the pre-calculated results of the tunnels in its own domain to the collaboration layer.

[0147] 20) The collaboration layer obtains the optimal end-to-end tunnel path and parameters that meet the conditions based on the pre-calculated results of the intra-domain tunnels received from the single-domain IP network control functions.

[0148] 21) The collaborative layer sends a service creation request to each domain (the request parameters include the tunnel path and parameter constraints) based on the IP network boundary information of each single domain and the service configuration parameters within the domain obtained in step 3), the available resources obtained in step 16), and the available tunnel path and parameters obtained in step 20).

[0149] 22) Each single-domain IP network management and control function completes the creation of tunnels and services within the domain.

[0150] 23) Each single-domain IP network control function returns the tunnel creation results and service creation results within its own domain to the collaboration layer.

[0151] 24) The coordination layer splices and generates end-to-end tunnels and end-to-end services based on the results of the single-domain IP network control functions received.

[0152] 25) The collaboration layer returns the end-to-end service creation result to the application layer.

[0153] In a specific implementation, it can also be implemented by directly creating without pre-calculation.

[0154] Embodiment 2, as Figure 4 Taking the end-to-end service creation under the coordinated management of IP network and optical network as an example, the service activation method based on user demand and network configuration mapping rules is described. In this embodiment, there are available tunnels that meet the requirements and the associated optical network side services also meet the requirements:

[0155] 1) The application layer user calls the end-to-end service activation interface and sends an L2VPN ELINE service creation request, which carries the following parameter requirements:

[0156] Service source information = network element A, Ethernet user side interface 1;

[0157] Service destination information = network element Z, Ethernet user side interface 2;

[0158] Business Type = E-Line;

[0159] User requirements:

[0160] Business reliability = 99.999%;

[0161] Bandwidth = 500M;

[0162] Latency ≤ 9ms.

[0163] 2) The collaboration layer converts user requirements into end-to-end service configuration parameters on the network side according to the "user requirements and network configuration parameter mapping rules", as follows:

[0164] ■ 99.99% reliability is converted into the following network-side end-to-end service configuration parameters:

[0165] <Protection type=1+1;

[0166] Protection level = tunnel;

[0167] Protection attribute = waiting time for recovery is 1 minute, and the protection delay time takes the default value of 60ms; >

[0168] <Protection type=1+1;

[0169] Protection level = ODUk;

[0170] Protection attribute = waiting time for recovery is 1 minute, protection delay time is 10ms; >

[0171] Routing constraint strategy = primary and backup paths should avoid using the same optical cable, and primary and backup paths should avoid using the same route;

[0172] ■ Bandwidth 500M is converted into the following network-side end-to-end service configuration parameters:

[0173] L2VPN service bandwidth CIR = 500M, PIR = physical port rate value;

[0174] The remaining bandwidth of the service layer tunnel of L2VPN service is ≥500M;

[0175] The remaining bandwidth of the IP link is ≥500M;

[0176] ODUk channel in the associated optical network ≥ 500M

[0177] ■ The latency of 9ms is converted into the following network-side end-to-end service configuration parameters:

[0178] L2VPN service latency ≤ 9ms.

[0179] 3) The collaboration layer analyzes the boundary information of each domain based on the topology information; at the same time, based on the network side end-to-end service configuration parameters obtained in step 2), the service configuration parameters of each single domain are obtained by splitting or directly mapping, as follows:

[0180]

[0181]

[0182] 4) The collaboration layer obtains tunnel information from each single-domain IP network control function.

[0183] 5) The single-domain IP network control function returns the tunnel information within each domain to the collaboration layer.

[0184] 6) The coordination layer completes cross-domain end-to-end tunnel splicing based on the acquired tunnel information and analyzes whether there are tunnels that meet the conditions (including tunnel-associated optical layer services that also meet the requirements of step 2)).

[0185] 7) If there are available tunnels and the associated optical network services meet the requirements, the collaboration layer sends a service creation request to each single-domain IP network control function based on the intra-domain configuration parameters and domain boundaries obtained in step 3).

[0186] 8) Each single domain IP network management and control function completes the creation of services within the domain.

[0187] 9) Each single-domain IP network control function returns the service creation results within its own domain to the collaboration layer.

[0188] 10) The collaboration layer generates end-to-end services based on the service creation results received from each single-domain IP network control function domain.

[0189] 11) The collaboration layer returns the end-to-end service creation result to the application layer.

[0190] Embodiment three, further, the present invention also provides a service activation device based on user needs and network configuration mapping rules, including at least one processor and a memory, the at least one processor and the memory are connected via a data bus, the memory stores instructions that can be executed by the at least one processor, and the instructions, after being executed by the processor, are used to complete the service activation method based on user needs and network configuration mapping rules.

[0191] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A service provisioning method based on user demand and network configuration mapping rules, characterized in that: The following steps are involved: S11: issuing an end-to-end service creation request oriented to user needs based on the end-to-end service configuration interface oriented to the user; S12: based on the mapping rules between user requirements and network configuration parameters, convert the user requirements into corresponding network-side end-to-end service configuration parameters; the network-side end-to-end service configuration parameters in step S12 include: protection recovery strategy: configure protection, including protection type, protection level and protection attribute; or configure rerouting, including rerouting enablement and rerouting level; routing constraint strategy: must-pass resource setting, must-not-pass resource setting, shared risk link group constraint, avoidance of same route or maximum delay; bandwidth strategy: CIR configuration and PIR configuration; S13: based on the network side end-to-end service configuration parameters, convert the network side end-to-end service configuration parameters into intra-domain service configuration parameters of each single-domain control function according to a splitting or direct mapping method; S14: Based on the intra-domain service configuration parameters, a pre-calculation request for the intra-domain service is issued to each single-domain management and control system, and the service is created according to the pre-calculation result.

2. The service provisioning method based on user demand and network configuration mapping rules according to claim 1, characterized in that: The mapping rules between user requirements and network configuration parameters in step S12 specifically include: The "reliability" requirement is converted into the "protection and recovery strategy" and "routing constraint strategy" in the network configuration parameter column. Different network configuration parameter values ​​are assigned according to different reliability index requirements of users. Among them, the "protection and recovery strategy" corresponds to the configuration parameters related to protection and rerouting on the network side; the "routing constraint strategy" corresponds to the path-finding related parameter constraints on the network side. The "delay" requirement is converted into the "routing constraint strategy-maximum delay" parameter in the network configuration parameter column; The "Bandwidth" requirement is converted into the "Bandwidth Strategy" parameter in the network configuration parameter column; The "Business Priority" requirement is converted into the "Protection and Recovery Strategy" in the network configuration parameter column. Different network configuration parameter values ​​are assigned according to different business priorities. The "Protection and Recovery Strategy" corresponds to the protection and rerouting-related configuration parameters on the network side.

3. The service provisioning method based on user demand and network configuration mapping rules according to claim 1, characterized in that: The mapping relationship between the network-side end-to-end service configuration parameters and the single-domain service configuration parameters in step S13 is specifically: For the protection type, protection level and protection attribute, each single domain adopts a direct mapping method, that is, the protection type, protection level and protection attribute in the single domain are equal to the protection type, protection level and protection attribute in the end-to-end service configuration parameters on the network side; For rerouting enable and rerouting level, each single domain adopts a direct mapping method, that is, the rerouting enable and rerouting level in the single domain are equal to the rerouting enable and rerouting level in the end-to-end service configuration parameters on the network side; For the maximum delay, if splitting is adopted, the delay value of the end-to-end service configuration on the network side is allocated to the delay parameters of the services configured in each single domain according to the preset weight; if direct mapping is adopted, the delay parameters of the services configured in each single domain are ≤ the delay value of the end-to-end service configuration on the network side; For the must-go or must-not-go resource settings, direct mapping is adopted, that is, the must-go / must-not-go resource settings in a single domain are equal to the must-go / must-not-go resource settings in the end-to-end service configuration parameters on the network side; For SRLG constraints, direct mapping is adopted, that is, the SRLG setting within a single domain is equal to the SRLG constraint in the end-to-end service configuration parameters on the network side; To avoid the same routing, direct mapping is used, that is, the service configuration within a single domain is also set to avoid the same routing constraint; For the service CIR configuration or PIR configuration, direct mapping is adopted, that is, the CIR configuration or PIR configuration of the service within a single domain is equal to the CIR configuration or PIR configuration of the end-to-end service on the network side; the service layer path of the service within a single domain must satisfy the service layer path remaining bandwidth ≥ CIR configuration of the end-to-end service on the network side, and the service layer path PIR ≥ PIR of the end-to-end service on the network side.

4. The service provisioning method based on user demand and network configuration mapping rules according to claim 1, characterized in that: The step S14 specifically includes: When the end-to-end service is a cross-network service, first analyze and determine whether the single-domain management and control system at the service layer already has a service layer path that satisfies the service creation of the customer layer management and control system: S141. If it already exists, directly send a pre-calculation request for the intra-domain business to the customer layer management and control system, select the optimal route that meets the conditions according to the result returned by the pre-calculation, and send the intra-domain business creation according to this route; S142. If it does not exist, first send a service layer path pre-calculation request to the service layer single domain control function, select the optimal route that meets the conditions based on the result returned by the pre-calculation, and send a service layer path creation request within the domain according to the returned result, and then refer to step S141 to complete the issuance of the service pre-calculation request to the customer layer single domain control function and the subsequent steps to create the service.

5. The service provisioning method based on user demand and network configuration mapping rules according to claim 1, characterized in that: The request parameters of the user-oriented configuration interface in step S11 include: Service source information; service destination information; service type; user requirements: including reliability, latency, bandwidth or service priority, and request parameters include one or more parameters in the user requirements.

6. The service provisioning method based on user demand and network configuration mapping rules according to claim 5, characterized in that: The service types include: E-LINE, E-LAN, E-TREE, CES, L3VPN, and the service priorities include: high, medium, and low.

7. The service provisioning method based on user demand and network configuration mapping rules according to claim 1, characterized in that: The protection and recovery strategy is specifically as follows: Protection type: 1+1 protection, 1:1 protection, no protection; Protection level: the level of objects to be protected; Protection attributes: waiting for recovery time, delaying time; Rerouting enable: Enable, Disable; Rerouting hierarchy: The hierarchy of objects that configure rerouting.

8. The service provisioning method based on user demand and network configuration mapping rules according to claim 1, characterized in that: The routing constraint strategy is specifically as follows: Required resource settings: node, port under the node, and specified path; The resource settings are required: node, port under the node, and specified path; Shared risk link group constraints: avoid using the same optical cable and the same risk links; Avoid the same route; Maximum delay.

9. A service provisioning device based on user demand and network configuration mapping rules, characterized in that: It includes at least one processor and a memory, the at least one processor and the memory are connected via a data bus, the memory stores instructions that can be executed by the at least one processor, and the instructions, after being executed by the processor, are used to complete the service activation method based on user demand and network configuration mapping rules as described in any one of claims 1-8.

Images