A data transmission method, device, related equipment and storage medium
By reporting the sending results of network configuration parameters in SDN scenarios by the SDN controller, the operation and maintenance chaos caused by the lack of reporting mechanism of the SDN controller is solved, and NFVO and VIM are timely understanding and abnormal positioning of configuration operations are achieved.
Patent Information
- Application Number
- CN202110030143.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-01-11
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2041-01-11
AI Technical Summary
In the SDN scenario, the SDN controller lacks a network configuration operation reporting mechanism, which causes NFVO to be unable to know the success or failure of the underlying network configuration operation, resulting in confusion in operation and maintenance and difficulty in abnormal positioning.
After the SDN controller receives the operation request of NFV MANO, it sends network configuration parameters to the forwarding device and receives the sending result within the preset time. If the result is abnormal or timed out, the exception information is reported to the NFV MANO to ensure that the SDN controller and MANO data are consistency.
By reporting the sending results of network configuration parameters, NFVO and VIM can promptly understand the success or failure of configuration operations, avoid operation and maintenance chaos, and achieve abnormal positioning and data consistency.
Smart Images

Figure CN114765579B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of Network Function Virtualization (NFV), and in particular to a data transmission method, apparatus, related equipment and storage medium. Background Art
[0002] After NFV introduced software defined network (SDN) technology, the deployment and management of VNF tended to be automated. The NFV management and orchestration (MANO) system can transmit relevant specification configuration parameters to the SDN controller (SDN-C), and the SDN-C will issue instructions to relevant virtual devices, such as SDN gateways and virtual switches, to implement operational requirements such as instantiation, expansion and contraction of virtualized network functions (VNFs). In the SDN scenario, the MANO system defines the concept of network service (NS): an NS instance is a specific network service, which contains one or more VNFs, and the functions of the network service instance are provided by the VNFs it contains. Since SDN-C lacks a reporting mechanism for network configuration operations, the NFV orchestrator (NFVO) and the virtualized infrastructure manager (VIM) cannot be informed. In this case, when the underlying network configuration operation is not completed successfully, resulting in abnormal operation of the NS instance, the NFVO still shows that all network configuration operations have been completed successfully, which will cause O&M confusion and make it impossible to locate the abnormality. Summary of the invention
[0003] In order to solve the existing technical problems, the embodiments of the present invention provide a data transmission method, an apparatus, related equipment and a storage medium.
[0004] To achieve the above object, the technical solution of the embodiment of the present invention is implemented as follows:
[0005] In a first aspect, an embodiment of the present invention provides a data transmission method, the method comprising: an SDN controller receives an operation request from an NFV MANO, and sends network configuration parameters to a forwarding device based on the operation request; obtains a sending result of the network configuration parameters; if the sending result indicates that the network configuration parameters are sent abnormally, sends first information characterizing the network configuration parameters sending abnormality to the NFV MANO.
[0006] In the above scheme, the obtaining of the sending result of the network configuration parameter includes: the SDN controller receives the sending result sent by the forwarding device within a first preset time period; the sending result indicates that the network configuration parameter is sent successfully or the network configuration parameter is sent abnormally; or, the SDN controller does not receive the sending result sent by the forwarding device within the first preset time period, and determines that the network configuration parameter is sent abnormally.
[0007] In the above solution, the obtaining of the sending result of the network configuration parameter includes: the SDN controller monitoring the state of the forwarding device and the sending result of the network configuration parameter.
[0008] In the above solution, after the SDN controller receives the operation request from the NFV MANO, the method further includes: the SDN controller sends an operation result indicating that the operation request has been successfully received to the NFV MANO.
[0009] In the above scheme, the method also includes: the SDN controller receives a first query request from the NFV MANO, queries the network configuration operation result of the forwarding device based on the first query request, and sends the network configuration operation result to the NFV MANO.
[0010] In a second aspect, an embodiment of the present invention further provides a data transmission method, the method comprising: VIM receives a first operation request sent from NFVO, and sends a second operation request to an SDN controller; the second operation request is used to send network configuration parameters to a forwarding device; receives first information sent by the SDN controller, the first information indicates that the network configuration parameters are sent abnormally, and sends information indicating the network configuration parameters are sent abnormally to the NFVO.
[0011] In the above scheme, the VIM receives the first operation request sent from the NFVO, including: the VIM receives the first operation request sent from the NFVO through the first enhanced interface; the first operation request includes at least an NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier.
[0012] In the above solution, after the VIM receives the first operation request sent by the NFVO, the method further includes: the VIM adds the NS instance identifier, the VL operation identifier, and the VL sub-operation identifier to a first operation record table.
[0013] In the above scheme, the first operation record table also includes a first flag bit, and the first flag bit indicates whether the sending result of the network configuration parameter is abnormal; after receiving the first information sent by the SDN controller, the method also includes: the VIM sets the first flag bit in the first operation record table to a first value.
[0014] In the above scheme, the first operation record table also includes a second flag bit, and the second flag bit indicates whether the operation request is successfully received; after the VIM receives the first operation request sent by the NFVO, the method also includes: the VIM records the second flag bit in the first operation record table as a second value.
[0015] In the above scheme, the method also includes: the VIM receives an operation result sent by the SDN controller indicating that the second operation request has been successfully received, and sends the operation result to the NFVO through the first enhanced interface; the operation result includes an NS instance identifier and a VL operation identifier.
[0016] In the above solution, the sending of information indicating abnormal sending of the network configuration parameters to the NFVO includes: the VIM sending information indicating abnormal sending of the network configuration parameters to the NFVO through the first newly added interface; the information includes an NS instance identifier.
[0017] In the above scheme, the sending of information characterizing the abnormal sending of the network configuration parameters to the NFVO includes: the VIM receiving a second query request sent by the NFVO through a second newly added interface, querying the first operation record table based on the second query request, and determining that the network configuration parameter sending is abnormal based on the first flag bit in the first operation record table; and sending information characterizing the abnormal sending of the network configuration parameters to the NFVO through the second newly added interface.
[0018] In the above scheme, the method also includes: the VIM receives the operation query request sent by the NFVO through the first enhanced interface, and sends the operation query request to the SDN controller; the operation query request includes at least one of the following: NS instance identifier, VL operation identifier; receives the network configuration operation result sent by the SDN, and sends the network configuration operation result to the NFVO through the second newly added interface.
[0019] In the above scheme, the first enhanced interface includes one of the following interfaces: CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, CreateTapFlow interface; the extended field in the message received by the VIM from the NFVO through the first enhanced interface includes the NS instance identifier; the extended field in the message sent by the VIM to the NFVO through the first enhanced interface includes the NS instance identifier and the VL operation identifier.
[0020] In a third aspect, an embodiment of the present invention further provides a data transmission method, the method comprising: an NFVO sends an operation request to an SDN controller through a VIM, the operation request being used to send network configuration parameters to a forwarding device; in the event of an abnormality in the sending of the network configuration parameters, the NFVO obtains information characterizing the abnormality in the sending of the network configuration parameters through the VIM.
[0021] In the above scheme, the NFVO sends an operation request to the SDN controller through the VIM, including: the NFVO sends a first operation request to the VIM through the first enhanced interface of the VIM, and the first operation request includes at least an NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier.
[0022] In the above solution, the method further includes: the NFVO adding the NS instance identifier, the VIM identifier, the VL operation type and the VL operation identifier to the second operation record table.
[0023] In the above scheme, after the NFVO sends an operation request to the SDN controller through the VIM, the method also includes: the NFVO receives the operation result sent by the VIM through the first enhanced interface of the VIM, and the operation result indicates that the SDN controller has successfully received the operation request; the operation result includes the NS instance identifier and the VL operation identifier.
[0024] In the above scheme, the NFVO obtains the information characterizing the abnormal sending of the network configuration parameters through the VIM, including: the NFVO receives the information characterizing the abnormal sending of the network configuration parameters sent by the VIM through the first newly added interface of the VIM; the information includes the NS instance identifier.
[0025] In the above scheme, the NFVO obtains the information characterizing the abnormal sending of the network configuration parameters through the VIM, including: the NFVO sends a second query request to the VIM through the second newly added interface of the VIM, and the second query request is used to query whether the network configuration parameters are sent abnormally; the NFVO receives the information characterizing the abnormal sending of the network configuration parameters sent by the VIM through the second newly added interface.
[0026] In the above scheme, the method also includes: the NFVO determines the operation status related to the specific NS instance according to the information recorded in the second operation record table; sends an operation query request to the VIM through the first enhanced interface of the VIM, and the operation query request includes at least one of the following: NS instance identifier, VL operation identifier; the NFVO receives the network configuration operation result sent by the VIM through the second newly added interface of the VIM.
[0027] In a fourth aspect, an embodiment of the present invention further provides a data transmission device, the device comprising: a first interface unit and a second interface unit; wherein:
[0028] The first interface unit is used to receive an operation request from the NFV MANO;
[0029] The second interface unit is used to send the network configuration parameter to the forwarding device based on the operation request; and is also used to obtain the sending result of the network configuration parameter;
[0030] The first interface unit is further configured to send first information characterizing the abnormal sending of the network configuration parameter to the NFV MANO if the sending result indicates that the network configuration parameter is sent abnormally.
[0031] In the above scheme, the second interface unit is used to receive the sending result sent by the forwarding device within a first preset time period; the sending result indicates that the network configuration parameter is sent successfully or the network configuration parameter is sent abnormally; or, if the sending result sent by the forwarding device is not received within the first preset time period, it is determined that the network configuration parameter is sent abnormally.
[0032] In the above solution, the second interface unit is used to monitor the status of the forwarding device and the sending result of the network configuration parameters.
[0033] In the above scheme, the first interface unit is also used to send an operation result indicating that the operation request has been successfully received to the NFV MANO after receiving the operation request from the NFV MANO.
[0034] In the above solution, the first interface unit is further used to receive a first query request from the NFV MANO;
[0035] The second interface unit is further used to query the network configuration operation result of the forwarding device based on the first query request;
[0036] The first interface unit is also used to send the network configuration operation result to the NFV MANO.
[0037] In a fifth aspect, an embodiment of the present invention further provides a data transmission device, the device comprising: a third interface unit and a fourth interface unit; wherein:
[0038] The third interface unit is configured to receive a first operation request sent from the NFVO;
[0039] The fourth interface unit is used to send a second operation request to the SDN controller; the second operation request is used to send network configuration parameters to the forwarding device; and is also used to receive first information sent by the SDN controller, wherein the first information indicates that the network configuration parameters are sent abnormally;
[0040] The third interface unit is further configured to send information indicating abnormality in sending the network configuration parameters to the NFVO.
[0041] In the above solution, the third interface unit is used to receive a first operation request sent by the NFVO through the first enhanced interface; the first operation request at least includes a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier.
[0042] In the above solution, the device also includes a first recording unit, which is used to add the NS instance identifier, the VL operation identifier, and the VL sub-operation identifier to a first operation record table.
[0043] In the above solution, the first operation record table also includes a first flag bit, and the first flag bit indicates whether the sending result of the network configuration parameter is abnormal;
[0044] The first recording unit is further configured to set the first flag position in the first operation record table to a first value after the second receiving unit receives the first information sent by the SDN controller.
[0045] In the above solution, the first operation record table also includes a second flag bit, and the second flag bit indicates whether the operation request is successfully received;
[0046] The first recording unit is further configured to record the second flag bit in the first operation record table as a second value.
[0047] In the above solution, the fourth interface unit is further used to receive an operation result sent by the SDN controller indicating that the second operation request has been successfully received; the operation result includes an NS instance identifier and a VL operation identifier;
[0048] The third interface unit is further configured to send the operation result to the NFVO through the first enhanced interface.
[0049] In the above solution, the third interface unit is used to send information indicating abnormal sending of the network configuration parameters to the NFVO through the first newly added interface; the information includes an NS instance identifier.
[0050] In the above solution, the third interface unit is used to receive the second query request sent by the NFVO through the second newly added interface;
[0051] The first recording unit is further used to query the first operation record table based on the second query request, and determine that the network configuration parameter is sent abnormally based on the first flag bit in the first operation record table;
[0052] The third interface unit is further configured to send information indicating abnormality in sending the network configuration parameter to the NFVO through the second newly added interface.
[0053] In the above solution, the third interface unit is further used to receive an operation query request sent by the NFVO through the first enhanced interface; the operation query request includes at least one of the following: an NS instance identifier and a VL operation identifier;
[0054] The fourth interface unit is further used to send the operation query request to the SDN controller; and is also used to receive the network configuration operation result sent by the SDN;
[0055] The third interface unit is further used to send the network configuration operation result to the NFVO through the second newly added interface.
[0056] In the above scheme, the first enhanced interface includes one of the following interfaces: CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, CreateTapFlow interface;
[0057] The extended field in the message received by the third interface unit from the NFVO through the first enhanced interface includes an NS instance identifier;
[0058] The extended field in the message sent by the third interface unit to the NFVO through the first enhanced interface includes the NS instance identifier and the VL operation identifier.
[0059] In a sixth aspect, an embodiment of the present invention further provides a data transmission device, the device comprising: a first sending unit and a first receiving unit; wherein,
[0060] The first sending unit is used to send an operation request to the SDN controller through the VIM, where the operation request is used to send network configuration parameters to the forwarding device;
[0061] The first receiving unit is used to obtain information characterizing the abnormal sending of the network configuration parameter through the VIM when the network configuration parameter is sent abnormally.
[0062] In the above solution, the first sending unit is used to send a first operation request to the VIM through the first enhanced interface of the VIM, and the first operation request at least includes a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier.
[0063] In the above solution, the device further includes a second recording unit, which is used to add the NS instance identifier, VIM identifier, VL operation type and VL operation identifier to a second operation record table.
[0064] In the above scheme, the first receiving unit is also used to receive the operation result sent by the VIM through the first enhanced interface of the VIM after sending the operation request to the SDN controller through the VIM, and the operation result indicates that the SDN controller has successfully received the operation request; the operation result includes the NS instance identifier and the VL operation identifier.
[0065] In the above solution, the first receiving unit is used to receive information sent by the VIM through the first newly added interface of the VIM, which indicates that the network configuration parameter is sent abnormally; the information includes the NS instance identifier.
[0066] In the above solution, the first sending unit is used to send a second query request to the VIM through the second newly added interface of the VIM, and the second query request is used to query whether the network configuration parameter is sent abnormally;
[0067] The first receiving unit is configured to receive, through the second newly added interface, information sent by the VIM indicating that the network configuration parameter is sent abnormally.
[0068] In the above solution, the second recording unit is further used to determine the operation status related to querying a specific NS instance according to the information recorded in the second operation record table;
[0069] The first sending unit is further used to send an operation query request to the VIM through the first enhanced interface of the VIM, wherein the operation query request includes at least one of the following: an NS instance identifier and a VL operation identifier;
[0070] The first receiving unit is further configured to receive a network configuration operation result sent by the VIM through a second newly added interface of the VIM.
[0071] In the seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect, the second aspect or the third aspect of the embodiment of the present invention.
[0072] In an eighth aspect, an embodiment of the present invention further provides a communication device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the method described in the first aspect, the second aspect, or the third aspect of the embodiment of the present invention are implemented.
[0073] The data transmission method, apparatus, related equipment and storage medium provided by the embodiment of the present invention include: the SDN controller receives an operation request from the NFV MANO, sends network configuration parameters to the forwarding device based on the operation request; obtains the sending result of the network configuration parameters; if the sending result indicates that the network configuration parameters are sent abnormally, sends the first information characterizing the sending abnormality of the network configuration parameters to the NFV MANO. In this way, the sending result of the network configuration parameters is reported by the SDN controller, so that the SDN controller and MANO data are consistent. BRIEF DESCRIPTION OF THE DRAWINGS
[0074] Figure 1 This is a schematic diagram of the structure of the core network cloud platform system;
[0075] Figure 2 This is a schematic diagram of a network service instance of NFV architecture based on SDN;
[0076] Figure 3 The data transmission method according to the embodiment of the present invention is shown in FIG. Figure 1 ;
[0077] Figure 4 The data transmission method according to the embodiment of the present invention is shown in FIG. Figure 2 ;
[0078] Figure 5 The data transmission method according to the embodiment of the present invention is shown in FIG. Figure 3 ;
[0079] Figure 6 A schematic diagram of parameter association management in an operation record table in a data transmission method according to an embodiment of the present invention;
[0080] Figure 7 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 1 ;
[0081] Figure 8 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 2 ;
[0082] Fig. 9 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 3 ;
[0083] Fig.10 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 4 ;
[0084] Fig.11 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 1 ;
[0085] Fig.12 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 2 ;
[0086] Fig.13 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 3 ;
[0087] Fig.14 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 4 ;
[0088] Fig.15 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 5 ;
[0089] Fig.16 The figure is a schematic diagram of the hardware structure of the communication device according to the embodiment of the present invention. DETAILED DESCRIPTION
[0090] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0091] Before describing the data transmission scheme of the embodiment of the present invention in detail, the related scheme is briefly described first.
[0092] Traditional network equipment manufacturers customize equipment based on specific specifications and specific technical requirements. The equipment maintenance and update process is relatively complicated, and the operating costs of business promotion are high. In order to reduce the complexity and cost of network deployment and business promotion, the decoupling of software and hardware based on a general hardware platform can effectively reduce the cost of equipment upgrades and accelerate the deployment of new services. NFV was proposed based on the above background. NFV implements the management function of the core cloud through the MANO system and network management system (such as the operation support system (OSS)). The core cloud platform system architecture is as follows: Figure 1 shown.
[0093] The MANO system was proposed by ETSI and includes three major components: NFVO, Virtualized Network Function Manager (VNFM), and VIM. Its main functions include life cycle management of network elements, creation of images required for network elements, management of templates and software required for network elements, and allocation and management of network resources. Among them:
[0094] NFVO: responsible for unified resource scheduling, creating VNF automatic expansion and contraction policies, and providing VNF instantiation specification configuration parameters;
[0095] VNFM: responsible for VNF lifecycle management, such as parsing and processing virtualized network function descriptors (VNFDs), initializing VNF instances, and scaling VNFs.
[0096] VIM: responsible for the scheduling and management of hardware resources and virtualization resources.
[0097] After NFV introduced SDN technology, the deployment and management of VNF tended to be automated. The MANO system can transmit relevant specification configuration parameters to SDN-C, which will issue instructions to relevant virtual devices to implement operational requirements such as VNF instantiation, expansion and contraction.
[0098] In the SDN scenario, the MANO system defines the concept of NS, such as Figure 2 As shown, an NS instance is a specific network service, which contains one or more VNFs. The functions of the network service instance are provided collaboratively by the VNFs it contains.
[0099] In the SDN-based NFV architecture, MANO completes the creation and deletion of related network configurations on the underlying forwarding devices through SDN-C. The overall process is as follows:
[0100] 1) NFVO calls the VIM northbound interface.
[0101] 2) VIM calls the SDN-C northbound interface through the SDN-C plug-in.
[0102] 3) SDN-C sends relevant flow table information to the underlying data communication equipment (such as Figure 1 networking equipment in the network, etc.).
[0103] 4) The underlying data communication device obtains the flow table and completes the relevant configuration.
[0104] However, in the related technical solution, after NFVO sends the related network configuration request to VIM:
[0105] 1) VIM will parse the request operation, and the Neutron component of VIM will call the SDN-C plug-in / SDN-C driver. The SDN-C plug-in / SDN-C driver will call the SDN-C northbound interface to complete the delivery or deletion of the configuration;
[0106] 2) When SDN-C successfully obtains the VIM's operation request through the northbound interface, it immediately returns a successful response to inform VIM;
[0107] 3) After receiving the successful response, VIM returns a successful response to NFVO.
[0108] At this time, NFVO believes that the relevant network configuration operations have been successfully issued through SDN-C. However, whether SDN-C has successfully completed the creation of network configuration through the southbound interface is unknown to NFVO and VIM because SDN-C lacks a reporting mechanism for network configuration operations. In this case, when the underlying network configuration operation is not successfully completed, resulting in abnormal operation of the NS instance, NFVO still shows that all network configuration operations have been successfully completed, which will cause confusion in operation and maintenance and make it impossible to locate the abnormality.
[0109] Based on this, the following embodiments of the present invention are proposed.
[0110] An embodiment of the present invention provides a data transmission method. Figure 3 The data transmission method according to the embodiment of the present invention is shown in FIG. Figure 1 ;like Figure 3 As shown, the method includes:
[0111] Step 101: The SDN controller receives an operation request from the NFV MANO, and sends network configuration parameters to a forwarding device based on the operation request;
[0112] Step 102: Obtain the sending result of the network configuration parameter;
[0113] Step 103: If the sending result indicates that the network configuration parameter is sent abnormally, first information indicating the network configuration parameter is sent abnormally is sent to the NFV MANO.
[0114] In this embodiment, the SDN controller (SDN-C) receives the operation request of NFV MANO, specifically, NFVO calls the VIM northbound interface and sends the relevant network configuration operation request; VIM receives the network configuration operation request and sends the operation request to the SDN controller (SDN-C), which can also be called a network configuration operation request, which is used to send relevant network configuration parameters to the forwarding device.
[0115] In the related technical solution, after receiving the operation request, the SDN controller sends the network configuration parameters to the forwarding device, but the SDN controller does not inform the NFV MANO, that is, it does not inform the VIM, whether the network configuration parameters are sent successfully. In this embodiment, after obtaining the sending result of the network configuration parameters, if the sending result indicates that the network configuration parameters are sent abnormally, the SDN controller sends the first information indicating the abnormal sending of the network configuration parameters to the MANO.
[0116] As an implementation mode, the obtaining of the sending result of the network configuration parameter includes: the SDN controller receives the sending result sent by the forwarding device within a first preset time period; the sending result indicates that the network configuration parameter is sent successfully or the network configuration parameter is sent abnormally; or, the SDN controller does not receive the sending result sent by the forwarding device within the first preset time period, and determines that the network configuration parameter is sent abnormally.
[0117] This embodiment is applicable to the case where both the northbound interface and the southbound interface of the SDN controller are synchronous interfaces. The so-called synchronous interface means that after a request is issued, the corresponding result is waited for before subsequent operations. Exemplarily, in this embodiment, a timeout duration (i.e., a first preset duration) is set for sending network configuration parameters to the forwarding device through the southbound interface. When the network configuration parameters are sent to the forwarding device, a timer is started, and the timing duration of the timer is the first preset duration; if within the timing duration of the timer, a confirmation response corresponding to the network configuration parameters fed back by the forwarding device is received, it can be indicated that the network configuration parameters are sent successfully, and the sending result of the successful sending of the network configuration parameters is obtained; if within the timing duration of the timer, a failure response corresponding to the network configuration parameters fed back by the forwarding device is received, or within the timing duration of the timer, the response corresponding to the network configuration parameters fed back by the forwarding device is not received, it can be indicated that the network configuration parameters fail to be sent, and the sending result of abnormal sending of the network configuration parameters is obtained.
[0118] As another implementation manner, the obtaining the sending result of the network configuration parameter includes: the SDN controller monitoring the state of the forwarding device and the sending result of the network configuration parameter.
[0119] This embodiment is applicable to the case where both the northbound interface and the southbound interface of the SDN controller are asynchronous interfaces. The so-called asynchronous interface means that after a request is issued or received, a successful reception is fed back, but whether the network configuration parameters are successfully sent down is not fed back. Therefore, in some optional embodiments, after the SDN controller receives an operation request from the NFV MANO, the method further includes: the SDN controller sends an operation result to the NFV MANO indicating that the operation request has been successfully received.
[0120] In this embodiment, the SDN controller monitors the state of the forwarding device and the sending result of the network configuration parameter, so as to obtain whether the sending of the network configuration parameter is abnormal and obtain the sending result of the abnormal sending of the network configuration parameter.
[0121] In some optional embodiments of the present invention, the method further includes: the SDN controller receives a first query request from the NFV MANO, queries a network configuration operation result of a forwarding device based on the first query request, and sends the network configuration operation result to the NFV MANO.
[0122] In this embodiment, the NFVO in the NFV MANO can query the network connection parameter configuration operation status related to a specific NS example based on the operation record information, that is, issue a first query request; the VIM receives the first query request and transmits the first query request to the SDN controller; the SDN controller queries the network configuration operation result of the forwarding device based on the first query request, and sends the network configuration operation result to the NFV MANO.
[0123] Based on the above embodiments, an embodiment of the present invention further provides a data transmission method. Figure 4 The data transmission method according to the embodiment of the present invention is shown in FIG. Figure 2 ;like Figure 4 As shown, the method includes:
[0124] Step 201: The VIM receives a first operation request sent from the NFVO, and sends a second operation request to the SDN controller; the second operation request is used to send network configuration parameters to the forwarding device;
[0125] Step 202: Receive first information sent by the SDN controller, where the first information indicates that the network configuration parameter is sent abnormally, and send information indicating the network configuration parameter sending abnormality to the NFVO.
[0126] In this embodiment, NFVO calls the VIM northbound interface and sends a related network configuration operation request, which is also the first operation request; VIM receives the network configuration operation request and sends an operation request to the SDN controller (SDN-C), which can also be called a network configuration operation request, that is, the second operation request, which is used to send related network configuration parameters to the forwarding device.
[0127] In the related technical solution, after receiving the operation request, the SDN controller sends the network configuration parameters to the forwarding device, but the SDN controller does not inform the VIM whether the network configuration parameters are sent successfully. In this embodiment, in the case of abnormal sending of the network configuration parameters, the VIM receives the first information indicating the abnormal sending of the network configuration parameters sent by the SDN controller, and sends the information indicating the abnormal sending of the network configuration parameters to the NFVO, so that the NFVO and the VIM can promptly know that the network configuration operation has not been successfully completed.
[0128] In some optional embodiments of the present invention, the VIM receives the first operation request sent from the NFVO, including: the VIM receives the first operation request sent from the NFVO through the first enhanced interface; the first operation request includes at least the NS instance identifier, the VIM identifier, the VL operation type and the VL operation identifier. In other words, the VIM receives the first operation request sent from the NFVO through the first enhanced interface message; the NS instance identifier is carried through the extended field in the first enhanced interface message. Wherein, VL represents the virtual connection between VNFs.
[0129] In this embodiment, the first enhanced interface represents a further enhancement or extension of the original interface, and on the basis of the variables defined in the original interface, the data or information that needs to be additionally carried in this embodiment is carried through the newly defined or extended variables. In other words, the first enhanced interface message is a further enhancement or extension of the original interface message, and the data or information that needs to be additionally carried in this embodiment is carried through the extended field of the original message.
[0130] Exemplarily, the first enhanced interface refers to the VIM northbound enhanced interface. The VIM northbound enhanced interface is a further enhancement based on the VIM northbound interface. Figure 1 As shown in the figure, the VIM northbound interface refers to the Or-Vi interface of the VIM northbound for communication with the NFVO.
[0131] In some optional embodiments, the method further includes: the VIM receives an operation result sent by the SDN controller indicating that the second operation request has been successfully received, and sends the operation result to the NFVO through the first enhanced interface; the operation result includes an NS instance identifier and a VL operation identifier.
[0132] Exemplarily, the first enhanced interface includes one of the following interfaces: CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, CreateTapFlow interface; the extended field in the message received by the VIM from the NFVO through the first enhanced interface includes the NS instance identifier; the extended field in the message sent by the VIM to the NFVO through the first enhanced interface includes the NS instance identifier and the VL operation identifier.
[0133] In this embodiment, the first enhanced interface carries different contents in the extended fields of messages in different directions. This is described below in conjunction with different interfaces.
[0134] 1. VIM northbound enhanced interface: CreateBGPNeighbor interface, as shown in Table 1 below, where the bold part is the newly added content in the embodiment of the present invention, that is, the extended part.
[0135] Table 1
[0136]
[0137] 2. VIM northbound enhanced interface: CreateExroutes interface, as shown in Table 2 below, where the bold part is the newly added content in the embodiment of the present invention, that is, the extended part.
[0138] Table 2
[0139]
[0140] 3. VIM northbound enhanced interface: CreateVPCConnection interface, as shown in Table 3 below, where the bold part is the new content in the embodiment of the present invention, that is, the extended part.
[0141] Table 3
[0142]
[0143] 4. VIM northbound enhanced interface: CreateTapService interface, as shown in Table 4 below, where the bold part is the newly added content in the embodiment of the present invention, that is, the extended part.
[0144] Table 4
[0145]
[0146] 5. VIM northbound enhanced interface: CreateTapFlow interface, as shown in Table 5 below, where the bold part is the newly added content in the embodiment of the present invention, that is, the extended part.
[0147] Table 5
[0148]
[0149] Specifically, in the above five examples of the first enhanced interface, it can be understood that the message sent by NFVO received by VIM carries the NS instance ID through the extended field; the message sent by VIM to NFVO carries the operation ID (OperationID) and the NS instance ID (NS Instance ID) through the extended field.
[0150] In this embodiment, after receiving the first information indicating the abnormality of sending the network configuration parameter sent by the SDN controller, the VIM may send the information indicating the abnormality of sending the network configuration parameter to the NFVO in the following manner:
[0151] As an implementation manner, the sending of information indicating abnormal sending of the network configuration parameters to the NFVO includes: the VIM sending information indicating abnormal sending of the network configuration parameters to the NFVO through the first newly added interface; the information includes an NS instance identifier.
[0152] As another implementation manner, the sending of information characterizing the abnormal sending of the network configuration parameters to the NFVO includes: the VIM receiving a second query request sent by the NFVO through a second newly added interface, querying the first operation record table based on the second query request, and determining that the network configuration parameter sending is abnormal based on the first flag bit in the first operation record table; and sending information characterizing the abnormal sending of the network configuration parameters to the NFVO through the second newly added interface.
[0153] The first method is that the VIM actively sends the information of abnormal network configuration parameter transmission to the NFVO. The second method is that the NFVO queries the VIM to obtain whether the network configuration parameter transmission is abnormal.
[0154] Exemplarily, the first newly added interface may be, for example, a FailedOperationDetail interface, and the extended field in the message sent by the VIM to the NFVO through the first newly added interface includes an NS instance identifier, as shown in Table 6 below.
[0155] Table 6
[0156]
[0157] Exemplarily, the above-mentioned second newly added interface can be, for example, a QueryOperationDetail interface, and the extended field in the message sent by the VIM to the NFVO through the second newly added interface includes the VL operation result; the extended field in the message sent by the NFVO received by the VIM through the second newly added interface includes the NS instance identifier, as shown in Table 7 below.
[0158] Table 7
[0159]
[0160] In some optional embodiments of the present invention, after the VIM receives the first operation request sent from the NFVO, the method further includes: the VIM adding the NS instance identifier, the VL operation identifier, and the VL sub-operation identifier to a first operation record table.
[0161] In some optional embodiments, the first operation record table also includes a first flag bit, and the first flag bit indicates whether the sending result of the network configuration parameter is abnormal; after receiving the sending result of the network configuration parameter sent by the SDN controller, the method also includes: the VIM sets the first flag bit in the first operation record table to a first value.
[0162] Exemplarily, if the first flag position is 0, it may indicate that the network configuration parameter is sent successfully; if the first flag position is 1, it may indicate that the network configuration parameter is sent abnormally.
[0163] In some optional embodiments, the first operation record table also includes a second flag bit, and the second flag bit indicates whether the operation request is successfully received; after the VIM receives the first operation request sent by the NFVO, the method further includes: the VIM records the second flag bit in the first operation record table as a second value.
[0164] For example, if the second flag is 0, it may indicate that the VIM has not successfully received the operation request of the NFVO; if the second flag is 1, it may indicate that the VIM has successfully received the operation request of the NFVO. The first operation record table may be specifically shown in Table 8, in which the abnormal flag is also the first flag in this embodiment; the flag of successfully receiving the operation request is also the second flag in this embodiment.
[0165] Table 8
[0166]
[0167] In some optional embodiments of the present invention, the method further includes: the VIM receives an operation query request sent by the NFVO through a first enhanced interface, and sends the operation query request to the SDN controller based on the operation query request; the operation query request includes at least one of the following: an NS instance identifier, a VL operation identifier; receiving a network configuration operation result sent by the SDN, and sending the network configuration operation result to the NFVO through a second newly added interface.
[0168] Based on the above embodiments, an embodiment of the present invention further provides a data transmission method. Figure 5 The data transmission method according to the embodiment of the present invention is shown in FIG. Figure 3 ;like Figure 5 As shown, the method includes:
[0169] Step 301: The NFVO sends an operation request to the SDN controller through the VIM, where the operation request is used to send network configuration parameters to the forwarding device;
[0170] Step 302: When the network configuration parameter is sent abnormally, the NFVO obtains information indicating the network configuration parameter sending abnormality through the VIM.
[0171] The NFVO sends an operation request to the SDN controller through the VIM, including: the NFVO sends a first operation request to the VIM through a first enhanced interface of the VIM, and the first operation request at least includes an NS instance identifier, a VIM identifier, a VL operation type, and a VL operation identifier.
[0172] In this embodiment, NFVO calls the VIM northbound interface and sends a related network configuration operation request, which is also the first operation request; VIM receives the network configuration operation request and sends an operation request to the SDN controller (SDN-C), which can also be called a network configuration operation request, that is, the second operation request, which is used to send related network configuration parameters to the forwarding device.
[0173] In the related technical solution, after receiving the operation request, the SDN controller sends the network configuration parameters to the forwarding device, but the SDN controller does not inform the VIM whether the network configuration parameters are sent successfully. In this embodiment, in the case of abnormal sending of the network configuration parameters, the VIM receives the first information indicating the abnormal sending of the network configuration parameters sent by the SDN controller, and sends the information indicating the abnormal sending of the network configuration parameters to the NFVO, so that the NFVO and the VIM can promptly know that the network configuration operation has not been successfully completed.
[0174] In some optional embodiments of the present invention, the method further includes: the NFVO adding the NS instance identifier, VIM identifier, VL operation type and VL operation identifier to a second operation record table. The second operation record table may be, for example, as shown in Table 9 below.
[0175] Table 9
[0176]
[0177] In some optional embodiments of the present invention, after the NFVO sends an operation request to the SDN controller through the VIM, the method further includes: the NFVO receives the operation result sent by the VIM through the first enhanced interface of the VIM, and the operation result indicates that the SDN controller has successfully received the operation request; the operation result includes an NS instance identifier and a VL operation identifier. Accordingly, the NFVO sends a first operation request to the VIM through the first enhanced interface; the VIM sends a second operation request to the SDN controller to send network configuration parameters to the forwarding device. The first enhanced interface can be specifically described in the aforementioned embodiment, and will not be repeated here.
[0178] In some optional embodiments of the present invention, the NFVO obtains the information characterizing the abnormal sending of the network configuration parameter through the VIM, including: the NFVO receives the information characterizing the abnormal sending of the network configuration parameter sent by the VIM through the first newly added interface of the VIM; the information includes the NS instance identifier. The first newly added interface can be specifically described in the above embodiment, which will not be repeated here.
[0179] In some optional embodiments of the present invention, the NFVO obtains information characterizing the abnormal sending of the network configuration parameter through the VIM, including: the NFVO sends a second query request to the VIM through the second newly added interface of the VIM, the second query request is used to query whether the network configuration parameter is sent abnormally; the NFVO receives the information characterizing the abnormal sending of the network configuration parameter sent by the VIM through the second newly added interface. The second newly added interface can be specifically referred to in the above embodiment, and will not be repeated here.
[0180] In some optional embodiments of the present invention, the method further includes: the NFVO determines, based on the information recorded in the second operation record table, an operation status related to querying a specific NS instance; sending an operation query request to the VIM through the first enhanced interface of the VIM, the operation query request including at least one of the following: an NS instance identifier, a VL operation identifier; and the NFVO receives a network configuration operation result sent by the VIM through the second newly added interface of the VIM.
[0181] Figure 6 Schematic diagram of parameter association management in the operation record table in the data transmission method of an embodiment of the present invention; see Figure 6 As shown, the VL operation is triggered through any first enhanced interface among CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, and CreateTapFlow interface, so as to further carry the NS instance ID and VL operation type in the NFVO to VIM direction, and further carry the operation ID, NS instance identifier, and VL operation type in the VIM to NFVO direction. The VIM has a VL operation record table, also called the first operation record table, in which the following are recorded: NS instance ID, VL operation ID, VL sub-operation ID, first flag bit, and second flag bit. The NFVO has a VL operation record table, also called the second operation record table, in which the VIM ID, NS instance ID, VL operation type, and VL operation ID are recorded. By adding the VIM northbound interfaces FailedOperationDetail and QueryOperationDetail, when an exception occurs during the VL operation, the VIM can actively report the exception information through FailedOperationDetail, or the NFVO can actively query the exception information of the related operation through QueryOperationDetail.
[0182] The embodiments of the present invention are described in detail below with reference to specific examples.
[0183] Example 1
[0184] In this embodiment, both the northbound interface and the southbound interface of the SDN-C are synchronous interfaces, and the interface timeout period is set, as shown in Table 10.
[0185] Table 10
[0186]
[0187] Figure 7 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 1 ;like Figure 7 As shown, the method includes:
[0188] Step 301: NFVO calls the VIM northbound interface to create a network connectivity resource VL, that is, sends a first operation request to the VIM, where the first operation request is used to create the network connectivity resource VL. The VIM northbound interface is a synchronous interface, and the timeout period is set to T1.
[0189] Step 302: After receiving the first operation request, VIM assigns the network resource creation task to the Neutron component based on the Openstack mechanism. The Neutron component calls the SDN-C Plug-in, SDN-C Driver, etc., and requests to create the relevant network connectivity resource VL by calling the SDN-C northbound interface, that is, sending a second operation request to SDN-C. Among them, the SDN-C northbound interface is a synchronous interface, and the timeout period is set to T2.
[0190] Step 303: SDN-C sends network configuration parameters to the forwarding device through the southbound interface. The southbound interface of SDN-C is a synchronous interface, and the timeout period is set to T3.
[0191] Step 304: within the T3 duration, if the network configuration parameters are sent successfully, the network configuration parameters are sent successfully; if the network configuration parameters are sent unsuccessfully, the network configuration parameters are returned to be sent unsuccessfully; if the SDN-C does not receive any sending result within the T3 duration, it is considered that the network configuration parameters have been sent unsuccessfully.
[0192] Step 305: Within the T2 duration, the SDN-C sends the network configuration parameter delivery result to the VIM through the northbound interface and stores it in the database.
[0193] Exemplarily, the SDN-C may also send a sending result indicating that the network configuration parameter is sent abnormally to the VIM only when the network configuration parameter is sent abnormally.
[0194] Step 306: Within the duration T1, the VIM returns the sending result to the NFVO.
[0195] Exemplarily, the VIM may send a sending result indicating that the network configuration parameter is sent abnormally to the NFVO only when the network configuration parameter is sent abnormally.
[0196] Example 2
[0197] In this example, the southbound interface and northbound interface of SDN-C are both asynchronous interfaces. SDN-C sends information related to abnormal operations to VIM, and VIM actively reports to NFVO. The specific interfaces are shown in Table 11 below.
[0198] Table 11
[0199]
[0200] The VIM northbound interfaces involved in this example may include the following interfaces:
[0201] 1) CreateBGPNeighbor;
[0202] 2) CreateExroutes;
[0203] 3) CreateVPCConnection;
[0204] 4)CreateTapService;
[0205] 5)CreateTapFlow;
[0206] 6)FailedOperationDetail;
[0207] Among them, the first five interfaces are the first enhanced interfaces in the above-mentioned embodiment, and the sixth interface is the first newly added interface. In the following method steps, unless otherwise specified, the VIM northbound interface can be implemented through the first five interfaces.
[0208] Figure 8 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 2 ;like Figure 8 As shown, the method includes:
[0209] Step 401: NFVO calls the VIM northbound interface and sends a first operation request to the VIM, that is, sends a related network configuration operation request.
[0210] Exemplarily, the NFVO writes parameters such as VIM ID, NS instance ID, VL operation type, and VL operation ID into the second operation record table in the above embodiment, as shown in Table 9.
[0211] Step 402: VIM sends the second operation request to SDN-C via the northbound interface of SDN-C. SDN-C northbound is an asynchronous interface, that is, when SDN-C successfully receives the operation request, it returns the operation result of "request successfully received" to VIM.
[0212] Here, after receiving the first operation request, the VIM sets the "successful operation request reception flag" in the first operation record table (see Table 8) in the above embodiment to "1", and returns the operation success result to the NFVO.
[0213] Here, VIM obtains the relevant operation request and the associated NS instance ID, calls the SDN-C plug-in, SDN-C Driver, etc. through the Neutron component, transmits the atomic operation request of the relevant operation and the associated NS ID, and writes the NS instance ID, VL operation ID, and VL sub-operation ID into the first operation record table.
[0214] Step 403: The SDN-C sends the network configuration parameters to the forwarding device through the southbound interface.
[0215] Step 404: SDN-C will continue to monitor the status of the underlying forwarding device and the delivery of network configuration parameters.
[0216] Step 405: If the network configuration parameter is sent abnormally, SDN-C actively returns the network configuration parameter sending abnormality to VIM and records it in the VIM database. At the same time, VIM sets the corresponding "abnormal flag bit" in the first operation record table (as shown in Table 8) to "1".
[0217] Step 406: VIM sends the network configuration parameters abnormally and returns it to NFVO through the FailedOperationDetail interface.
[0218] Example 3
[0219] In this example, NFVO queries VIM for the relevant network configuration delivery status by specifying a specific network connectivity operation request in a specific NS instance. Among them, the southbound interface and northbound interface of SDN-C are both asynchronous interfaces, and the specific interfaces are shown in Table 12 below.
[0220] Table 12
[0221]
[0222] The VIM northbound interfaces involved in this example may include the following interfaces:
[0223] 1) CreateBGPNeighbor;
[0224] 2) CreateExroutes;
[0225] 3) CreateVPCConnection;
[0226] 4)CreateTapService;
[0227] 5)CreateTapFlow;
[0228] 6)QueryOperationDetail;
[0229] The first five interfaces are the first enhanced interfaces in the above-mentioned embodiment, and the sixth interface is the second newly added interface. In the following method steps, unless otherwise specified, the VIM northbound interface can be implemented through the first five interfaces.
[0230] Fig. 9 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 3 ;like Fig. 9 As shown, the method includes:
[0231] Step 501: NFVO calls the VIM northbound interface and sends a query request to the VIM.
[0232] Here, the NFVO queries the network connectivity parameter configuration operation status related to the specific NS instance based on the record information in the second operation record table (including NS instance ID, VL operation ID, etc.). Exemplarily, the query request may include a specific NS instance identifier.
[0233] The VIM northbound interface may be specifically implemented through the first enhanced interface in the aforementioned embodiment.
[0234] Step 502: VIM receives the query request, calls SDN-C Plugin, SDN-C driver, etc. through Neutron components, and transmits the relevant query request to SDN-C through the SDN-C northbound interface.
[0235] Step 503: The SDN-C queries the network configuration operation result to the specific forwarding device through the southbound interface.
[0236] Step 504: The SDN-C obtains the network configuration operation result.
[0237] Step 505: SDN-C returns the network configuration operation result to VIM via the northbound interface and writes it into the database.
[0238] Step 506: The VIM returns the query result to the NFVO.
[0239] Example 4
[0240] In this example, SDN-C sends information related to abnormal operations to VIM, and VIM will not actively report to NFVO. NFVO needs to actively query VIM to obtain relevant abnormal information. Among them, the southbound interface and northbound interface of SDN-C are both asynchronous interfaces. The specific interfaces are shown in Table 13 below.
[0241] Table 13
[0242]
[0243] The VIM northbound interfaces involved in this example may include the following interfaces:
[0244] 1) CreateBGPNeighbor;
[0245] 2) CreateExroutes;
[0246] 3) CreateVPCConnection;
[0247] 4)CreateTapService;
[0248] 5)CreateTapFlow;
[0249] 6)QueryOperationDetail;
[0250] The first five interfaces are the first enhanced interfaces in the above-mentioned embodiment, and the sixth interface is the second newly added interface. In the following method steps, unless otherwise specified, the VIM northbound interface can be implemented through the first five interfaces.
[0251] Fig.10 The application process of the data transmission method according to the embodiment of the present invention is shown as follows: Figure 4 ;like Fig.10 As shown, the method includes:
[0252] Step 601: NFVO calls the VIM northbound interface and sends a first operation request to the VIM, that is, sends a related network configuration operation request.
[0253] Exemplarily, the NFVO writes parameters such as VIM ID, NS instance ID, VL operation type, and VL operation ID into the second operation record table in the above embodiment, as shown in Table 9.
[0254] Step 602: VIM sends the second operation request to SDN-C via the northbound interface of SDN-C. SDN-C northbound is an asynchronous interface, that is, when SDN-C successfully receives the operation request, it returns the operation result of "request successfully received" to VIM.
[0255] Here, after receiving the first operation request, the VIM sets the "successful operation request reception flag" in the first operation record table (see Table 8) in the above embodiment to "1", and returns the operation success result to the NFVO.
[0256] Here, VIM obtains the relevant operation request and the associated NS instance ID, calls the SDN-C plug-in, SDN-C Driver, etc. through the Neutron component, transmits the atomic operation request of the relevant operation and the associated NS ID, and writes the NS instance ID, VL operation ID, and VL sub-operation ID into the first operation record table.
[0257] Step 603: The SDN-C sends the network configuration parameters to the forwarding device through the southbound interface.
[0258] Step 604: SDN-C will continue to monitor the status of the underlying forwarding device and the delivery of network configuration parameters.
[0259] Step 605: If the network configuration parameter is sent abnormally, SDN-C actively returns the network configuration parameter sending abnormality to VIM and records it in the VIM database. At the same time, VIM sets the corresponding "abnormal flag bit" in the first operation record table (as shown in Table 8) to "1".
[0260] Step 606: NFVO calls the VIM northbound interface QueryOperationDetail to proactively query the VIM for relevant operation results and obtain information indicating abnormalities in the delivery of network configuration parameters.
[0261] The technical solution of the embodiment of the present invention is adopted. Firstly, the SDN controller reports the sending result of the network configuration parameters to achieve consistency between the SDN controller and the MANO data. Secondly, the existing VIM northbound interface is enhanced, and the NS instance identifier and the operation identifier are added to associate the VL operation with the NS instance; based on the association relationship and related identifiers between the VL operation and the NS instance, the VIM northbound interface FailedOperationDetail and QueryOperationDetail are added to achieve that when an exception occurs during the VL operation, the VIM can actively report the exception information through FailedOperationDetail, or the NFVO can actively query the exception information of the related operation through QueryOperationDetail. Thirdly, by adding an operation record table in NFVO and VIM to record the NS instance ID, VL operation ID, and operation exception flag associated with the relevant VL operation, the consistency reconciliation of the network configuration operation information records of NFVO-VIM-SDN controller can be achieved under the two interface settings of "NFVO-VIM interface is a synchronous interface, and the south / northbound of SDN controller is an asynchronous interface" or "NFVO-VIM interface and south / northbound of SDN controller are both synchronous interfaces".
[0262] The embodiment of the present invention further provides a data transmission device, which is applied in an SDN controller. Fig.11 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 1 ;like Fig.11 As shown, the device comprises: a first interface unit 11 and a second interface unit 12; wherein,
[0263] The first interface unit 11 is used to receive an operation request from the NFV MANO;
[0264] The second interface unit 12 is used to send the network configuration parameters to the forwarding device based on the operation request; and is also used to obtain the sending result of the network configuration parameters;
[0265] The first interface unit 11 is further configured to send first information indicating that the network configuration parameter sending is abnormal to the NFV MANO if the sending result indicates that the network configuration parameter sending is abnormal.
[0266] In some optional embodiments of the present invention, the second interface unit 12 is used to receive a sending result sent by the forwarding device within a first preset time period; the sending result indicates that the network configuration parameter is sent successfully or the network configuration parameter is sent abnormally; or, if the sending result sent by the forwarding device is not received within the first preset time period, it is determined that the network configuration parameter is sent abnormally.
[0267] In some optional embodiments of the present invention, the second interface unit 12 is used to monitor the status of the forwarding device and the sending result of the network configuration parameter.
[0268] In some optional embodiments of the present invention, the first interface unit 11 is further configured to, after receiving an operation request from the NFV MANO, send an operation result indicating that the operation request has been successfully received to the NFV MANO.
[0269] In some optional embodiments of the present invention, the first interface unit 11 is further configured to receive a first query request from the NFVMANO;
[0270] The second interface unit 12 is further used to query the network configuration operation result of the forwarding device based on the first query request;
[0271] The first interface unit 11 is also used to send the network configuration operation result to the NFV MANO.
[0272] In the embodiment of the present invention, the first interface unit 11 and the second interface unit 12 in the device can be implemented in actual applications through a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna.
[0273] The embodiment of the present invention further provides a data transmission device, which is applied in VIM. Fig.12 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 2 ;like Fig.12 As shown, the device comprises: a third interface unit 21 and a fourth interface unit 22; wherein,
[0274] The third interface unit 21 is configured to receive a first operation request sent from the NFVO;
[0275] The fourth interface unit 22 is used to send a second operation request to the SDN controller; the second operation request is used to send network configuration parameters to the forwarding device; and is also used to receive first information sent by the SDN controller, wherein the first information indicates that the network configuration parameters are sent abnormally;
[0276] The third interface unit 21 is further configured to send information indicating abnormality in sending the network configuration parameters to the NFVO.
[0277] In some optional embodiments of the present invention, the third interface unit 21 is used to receive a first operation request sent by the NFVO through the first enhanced interface; the first operation request includes at least a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier.
[0278] In some optional embodiments of the present invention, Fig.13 As shown, the device further includes a first recording unit 23, which is used to add the NS instance identifier, the VL operation identifier, and the VL sub-operation identifier to a first operation record table.
[0279] In some optional embodiments of the present invention, the first operation record table further includes a first flag bit, and the first flag bit indicates whether the sending result of the network configuration parameter is abnormal;
[0280] The first recording unit 23 is further configured to set the first flag position in the first operation record table to a first value after the second receiving unit receives the first information sent by the SDN controller.
[0281] In some optional embodiments of the present invention, the first operation record table further includes a second flag bit, and the second flag bit indicates whether the operation request is successfully received;
[0282] The first recording unit 23 is further configured to record the second flag bit in the first operation record table as a second value.
[0283] In some optional embodiments of the present invention, the fourth interface unit 22 is further configured to receive an operation result sent by the SDN controller indicating that the second operation request has been successfully received; the operation result includes an NS instance identifier and a VL operation identifier;
[0284] The third interface unit 21 is further configured to send the operation result to the NFVO through the first enhanced interface.
[0285] In some optional embodiments of the present invention, the third interface unit 21 is used to send information indicating abnormality in sending the network configuration parameters to the NFVO through the first newly added interface; the information includes an NS instance identifier.
[0286] In some optional embodiments of the present invention, the third interface unit 21 is configured to receive a second query request sent by the NFVO through a second newly added interface;
[0287] The first recording unit 23 is further configured to query the first operation record table based on the second query request, and determine that the network configuration parameter is sent abnormally based on the first flag bit in the first operation record table;
[0288] The third interface unit 21 is further configured to send information indicating abnormality in sending the network configuration parameters to the NFVO through the second newly added interface.
[0289] In some optional embodiments of the present invention, the third interface unit 21 is further configured to receive an operation query request sent by the NFVO through the first enhanced interface; the operation query request includes at least one of the following: an NS instance identifier and a VL operation identifier;
[0290] The fourth interface unit 22 is further used to send the operation query request to the SDN controller; and is also used to receive the network configuration operation result sent by the SDN;
[0291] The third interface unit 21 is further used to send the network configuration operation result to the NFVO through the second newly added interface.
[0292] In some optional embodiments of the present invention, the first enhanced interface includes one of the following interfaces: CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, CreateTapFlow interface;
[0293] The extended field in the message received by the third interface unit 21 from the NFVO through the first enhanced interface includes an NS instance identifier;
[0294] The extended field in the message sent by the third interface unit 21 to the NFVO through the first enhanced interface includes the NS instance identifier and the VL operation identifier.
[0295] In an embodiment of the present invention, the first recording unit 23 in the device can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a programmable gate array (FPGA) in actual applications; the third interface unit 21 and the fourth interface unit 22 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual applications.
[0296] An embodiment of the present invention further provides a data transmission device, which is applied in NFVO. Fig.14 The structure diagram of the data transmission device according to the embodiment of the present invention is shown in FIG. Figure 4 ;like Fig.14 As shown, the device includes: a first sending unit 31 and a first receiving unit 32; wherein,
[0297] The first sending unit 31 is used to send an operation request to the SDN controller through the VIM, and the operation request is used to send network configuration parameters to the forwarding device;
[0298] The first receiving unit 32 is used for obtaining, through the VIM, information indicating that the network configuration parameter is abnormally sent when the network configuration parameter is abnormally sent.
[0299] In some optional embodiments of the present invention, the first sending unit 31 is used to send a first operation request to the VIM through the first enhanced interface of the VIM, and the first operation request at least includes an NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier.
[0300] In some optional embodiments of the present invention, Fig.15 As shown, the device further includes a second recording unit 33, which is used to add the NS instance identifier, the VIM identifier, the VL operation type and the VL operation identifier to a second operation record table.
[0301] In some optional embodiments of the present invention, the first receiving unit 32 is further used to receive an operation result sent by the VIM through the first enhanced interface of the VIM after sending an operation request to the SDN controller through the VIM, wherein the operation result indicates that the SDN controller has successfully received the operation request; the operation result includes an NS instance identifier and a VL operation identifier.
[0302] In some optional embodiments of the present invention, the first receiving unit 32 is used to receive information sent by the VIM through the first newly added interface of the VIM, which indicates that the network configuration parameter is sent abnormally; the information includes an NS instance identifier.
[0303] In some optional embodiments of the present invention, the first sending unit 31 is used to send a second query request to the VIM through the second newly added interface of the VIM, and the second query request is used to query whether the network configuration parameter is sent abnormally;
[0304] The first receiving unit 32 is configured to receive, through the second newly added interface, information sent by the VIM indicating that the network configuration parameter is sent abnormally.
[0305] In some optional embodiments of the present invention, the second recording unit 33 is further used to determine the operation status related to querying a specific NS instance according to the information recorded in the second operation record table;
[0306] The first sending unit 31 is further configured to send an operation query request to the VIM through the first enhanced interface of the VIM, wherein the operation query request includes at least one of the following: an NS instance identifier and a VL operation identifier;
[0307] The first receiving unit 32 is further configured to receive a network configuration operation result sent by the VIM through the second newly added interface of the VIM.
[0308] In an embodiment of the present invention, the second recording unit 33 in the device can be implemented by a CPU, a DSP, an MCU or an FPGA in actual applications; the first sending unit 31 and the first receiving unit 32 in the device can be implemented by a communication module (including: a basic communication kit, an operating system, a communication module, a standardized interface and protocol, etc.) and a transceiver antenna in actual applications.
[0309] It should be noted that: the data transmission device provided in the above embodiment only uses the division of the above program modules as an example when performing data transmission. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the data transmission device provided in the above embodiment and the data transmission method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
[0310] An embodiment of the present invention further provides a communication device, which may specifically be the SDN controller, VIM or NFVO in the aforementioned embodiment. Fig.16 FIG. 1 is a schematic diagram of the hardware structure of a communication device according to an embodiment of the present invention. Fig.16 As shown, the communication device includes a memory 42, a processor 41, and a computer program stored in the memory 42 and executable on the processor 41. When the processor 41 executes the program, the steps of the data transmission method applied to the SDN controller in the embodiment of the present invention are implemented; or, when the processor 41 executes the program, the steps of the data transmission method applied to the VIM in the embodiment of the present invention are implemented; or, when the processor 41 executes the program, the steps of the data transmission method applied to the NFVO in the embodiment of the present invention are implemented.
[0311] The communication device may further include a communication interface 43. It is understood that the various components in the communication device are coupled together via a bus system 44. It is understood that the bus system 44 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 44 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.16 Various buses are labeled as bus system 44 .
[0312] It can be understood that the memory 42 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 42 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.
[0313] The method disclosed in the above embodiment of the present invention can be applied to the processor 41, or implemented by the processor 41. The processor 41 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 41 or the instruction in the form of software. The above processor 41 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 41 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present invention, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 42. The processor 41 reads the information in the memory 42 and completes the steps of the above method in combination with its hardware.
[0314] In an exemplary embodiment, the communication device may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), FPGA, general purpose processor, controller, MCU, microprocessor, or other electronic components to execute the aforementioned method.
[0315] In an exemplary embodiment, the present invention also provides a computer-readable storage medium, such as a memory 42 including a computer program, and the computer program can be executed by a processor 41 of a communication device to complete the steps of the aforementioned method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM; or it can be various devices including one or any combination of the above memories.
[0316] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the data transmission method applied to the SDN controller in the embodiment of the present invention; or, when executed by a processor, implements the steps of the data transmission method applied to the VIM in the embodiment of the present invention; or, when executed by a processor, implements the steps of the data transmission method applied to the NFVO in the embodiment of the present invention.
[0317] The methods disclosed in several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.
[0318] The features disclosed in several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.
[0319] The features disclosed in several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.
[0320] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0321] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0322] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.
[0323] A person of ordinary skill in the art can understand that: all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium, which, when executed, executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, disks or optical disks.
[0324] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.
[0325] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. A data transmission method, characterized in that: The method comprises: The software defined network SDN controller receives an operation request from the network function virtualization management and orchestration NFV MANO, and sends a network configuration parameter to the forwarding device based on the operation request; Obtaining a sending result of the network configuration parameter; If the sending result indicates that the network configuration parameter is sent abnormally, first information indicating the network configuration parameter is sent abnormally is sent to the NFV MANO.
2. The method according to claim 1, characterized in that: The obtaining of the sending result of the network configuration parameter includes: The SDN controller receives a sending result sent by the forwarding device within a first preset time period; the sending result indicates that the network configuration parameter is sent successfully or the network configuration parameter is sent abnormally; or, The SDN controller does not receive the sending result sent by the forwarding device within the first preset time period, and determines that the sending of the network configuration parameter is abnormal.
3. The method according to claim 1, characterized in that The obtaining of the sending result of the network configuration parameter includes: The SDN controller monitors the status of the forwarding device and the sending result of the network configuration parameters.
4. The method according to claim 3, characterized in that After the SDN controller receives the operation request from the NFV MANO, the method further includes: The SDN controller sends an operation result indicating that the operation request has been successfully received to the NFV MANO.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The SDN controller receives a first query request from the NFV MANO, queries a network configuration operation result of a forwarding device based on the first query request, and sends the network configuration operation result to the NFV MANO.
6. A data transmission method, characterized in that: The method comprises: The virtualized infrastructure manager VIM receives a first operation request sent from the network function virtualization NFV orchestrator NFVO, and sends a second operation request to the software defined network SDN controller; the second operation request is used to send network configuration parameters to the forwarding device; Receive first information sent by the SDN controller, where the first information indicates that the network configuration parameter is sent abnormally, and send information indicating the network configuration parameter is sent abnormally to the NFVO.
7. The method according to claim 6, characterized in that The VIM receives a first operation request sent by the NFVO, including: The VIM receives a first operation request sent from the NFVO through a first enhanced interface; the first operation request includes at least a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier; VL represents a virtual connection between virtualized network functions VNFs.
8. The method according to claim 7, characterized in that After the VIM receives the first operation request sent by the NFVO, the method further includes: The VIM adds the NS instance identifier, the VL operation identifier, and the VL sub-operation identifier to the first operation record table.
9. The method according to claim 8, characterized in that The first operation record table also includes a first flag bit, and the first flag bit indicates whether the sending result of the network configuration parameter is abnormal; After receiving the first information sent by the SDN controller, the method further includes: The VIM sets the first flag position in the first operation record table to a first value.
10. The method according to claim 8, characterized in that The first operation record table also includes a second flag bit, and the second flag bit indicates whether the operation request is successfully received; After the VIM receives the first operation request sent by the NFVO, the method further includes: The VIM records the second flag bit in the first operation record table as a second value.
11. The method according to claim 7, characterized in that The method further comprises: The VIM receives an operation result sent by the SDN controller indicating that the second operation request has been successfully received, and sends the operation result to the NFVO through the first enhanced interface; the operation result includes an NS instance identifier and a VL operation identifier.
12. The method according to claim 6, characterized in that The sending of information indicating that the network configuration parameter is abnormal to the NFVO includes: The VIM sends information indicating abnormal sending of the network configuration parameters to the NFVO through the first newly added interface; the information includes a network service NS instance identifier.
13. The method according to claim 9, characterized in that The sending of information indicating that the network configuration parameter is abnormal to the NFVO includes: The VIM receives a second query request sent by the NFVO through a second newly added interface, queries the first operation record table based on the second query request, and determines that the sending of the network configuration parameter is abnormal based on the first flag bit in the first operation record table; Information indicating that the network configuration parameter is abnormally sent is sent to the NFVO through the second newly added interface.
14. The method according to claim 6, characterized in that The method further comprises: The VIM receives the operation query request sent by the NFVO through the first enhanced interface, and sends the operation query request to the SDN controller; the operation query request includes at least one of the following: a network service NS instance identifier and a VL operation identifier; VL represents a virtual connection between virtualized network functions VNF; Receive the network configuration operation result sent by the SDN, and send the network configuration operation result to the NFVO through the second newly added interface.
15. The method according to claim 7, 11 or 14, characterized in that The first enhanced interface includes one of the following interfaces: CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, CreateTapFlow interface; The extended field in the message received by the VIM from the NFVO through the first enhanced interface includes an NS instance identifier; The extended field in the message sent by the VIM to the NFVO through the first enhanced interface includes the NS instance identifier and the VL operation identifier.
16. A data transmission method, characterized in that: The method comprises: The network function virtualization NFV orchestrator NFVO sends an operation request to the software defined network SDN controller through the virtualization infrastructure manager VIM, wherein the operation request is used to send network configuration parameters to the forwarding device; In the case where the network configuration parameter is sent abnormally, the NFVO obtains, through the VIM, information sent by the SDN controller indicating that the network configuration parameter is sent abnormally.
17. The method according to claim 16, characterized in that The NFVO sends an operation request to the SDN controller through the VIM, including: The NFVO sends a first operation request to the VIM through the first enhanced interface of the VIM, wherein the first operation request includes at least a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier; VL represents a virtual connection between virtualized network functions VNFs.
18. The method according to claim 17, characterized in that The method further comprises: The NFVO adds the NS instance identifier, the VIM identifier, the VL operation type and the VL operation identifier to the second operation record table.
19. The method according to claim 16, characterized in that After the NFVO sends the operation request to the SDN controller through the VIM, the method further includes: The NFVO receives the operation result sent by the VIM through the first enhanced interface of the VIM, and the operation result indicates that the SDN controller has successfully received the operation request; the operation result includes the network service NS instance identifier and the VL operation identifier; VL represents the virtual connection between virtualized network functions VNF.
20. The method according to claim 16, characterized in that The NFVO obtains, through the VIM, information indicating that the network configuration parameter is abnormally sent, including: The NFVO receives information sent by the VIM through the first newly added interface of the VIM, which indicates that the network configuration parameter is sent abnormally; the information includes an NS instance identifier.
21. The method according to claim 16, characterized in that The NFVO obtains, through the VIM, information indicating that the network configuration parameter is abnormally sent, including: The NFVO sends a second query request to the VIM through a second newly added interface of the VIM, where the second query request is used to query whether the network configuration parameter is sent abnormally; The NFVO receives, through the second newly added interface, information sent by the VIM indicating that the network configuration parameter is sent abnormally.
22. The method according to claim 18, characterized in that The method further comprises: The NFVO determines, according to the information recorded in the second operation record table, to query the operation status related to the specific NS instance; Sending an operation query request to the VIM through the first enhanced interface of the VIM, wherein the operation query request includes at least one of the following: an NS instance identifier and a VL operation identifier; The NFVO receives the network configuration operation result sent by the VIM through the second newly added interface of the VIM.
23. A data transmission device, characterized in that: The device comprises: a first interface unit and a second interface unit; wherein, The first interface unit is used to receive an operation request from the network function virtualization management and orchestration NFV MANO; The second interface unit is used to send the network configuration parameter to the forwarding device based on the operation request; and is also used to obtain the sending result of the network configuration parameter; The first interface unit is further configured to send first information characterizing the abnormal sending of the network configuration parameter to the NFV MANO if the sending result indicates that the network configuration parameter is sent abnormally.
24. The device according to claim 23, characterized in that The second interface unit is used to receive a sending result sent by the forwarding device within a first preset time period; the sending result indicates that the network configuration parameter is sent successfully or the network configuration parameter is sent abnormally; Alternatively, if the sending result sent by the forwarding device is not received within the first preset time period, it is determined that the sending of the network configuration parameter is abnormal.
25. The device according to claim 23, characterized in that The second interface unit is used to monitor the status of the forwarding device and the sending result of the network configuration parameters.
26. The device according to claim 25, characterized in that The first interface unit is further configured to, after receiving an operation request from the NFV MANO, send an operation result indicating that the operation request has been successfully received to the NFV MANO.
27. The device according to any one of claims 23 to 26, characterized in that The first interface unit is further used to receive a first query request from the NFV MANO; The second interface unit is further used to query the network configuration operation result of the forwarding device based on the first query request; The first interface unit is also used to send the network configuration operation result to the NFV MANO.
28. A data transmission device, characterized in that: The device comprises: a third interface unit and a fourth interface unit; wherein, The third interface unit is used to receive a first operation request sent from the network function virtualization orchestrator NFVO; The fourth interface unit is used to send a second operation request to the software defined network SDN controller; the second operation request is used to send network configuration parameters to the forwarding device; and is also used to receive first information sent by the SDN controller, wherein the first information indicates that the network configuration parameters are sent abnormally; The third interface unit is further configured to send information indicating abnormality in sending the network configuration parameters to the NFVO.
29. The device according to claim 28, characterized in that The third interface unit is used to receive a first operation request sent by the NFVO through the first enhanced interface; the first operation request includes at least a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier; VL represents a virtual connection between virtualized network functions VNFs.
30. The device according to claim 29, characterized in that The device also includes a first recording unit, which is used to add the NS instance identifier, the VL operation identifier, and the VL sub-operation identifier to a first operation record table.
31. The device according to claim 30, characterized in that The first operation record table also includes a first flag bit, and the first flag bit indicates whether the sending result of the network configuration parameter is abnormal; The first recording unit is further configured to set the first flag position in the first operation record table to a first value after the fourth interface unit receives the first information sent by the SDN controller.
32. The device according to claim 30, characterized in that The first operation record table also includes a second flag bit, and the second flag bit indicates whether the operation request is successfully received; The first recording unit is further configured to record the second flag bit in the first operation record table as a second value.
33. The device according to claim 29, characterized in that The fourth interface unit is further configured to receive an operation result sent by the SDN controller indicating that the second operation request has been successfully received; the operation result includes an NS instance identifier and a VL operation identifier; The third interface unit is further configured to send the operation result to the NFVO through the first enhanced interface.
34. The device according to claim 28, characterized in that The third interface unit is used to send information indicating abnormality in sending the network configuration parameters to the NFVO through the first newly added interface; the information includes a network service NS instance identifier.
35. The device according to claim 31, characterized in that The third interface unit is configured to receive a second query request sent by the NFVO through a second newly added interface; The first recording unit is further used to query the first operation record table based on the second query request, and determine that the network configuration parameter is sent abnormally based on the first flag bit in the first operation record table; The third interface unit is further configured to send information indicating abnormality in sending the network configuration parameter to the NFVO through the second newly added interface.
36. The device according to claim 28, characterized in that The third interface unit is further configured to receive an operation query request sent by the NFVO through the first enhanced interface; the operation query request includes at least one of the following: a network service NS instance identifier and a VL operation identifier; VL represents a virtual connection between virtualized network functions VNFs; The fourth interface unit is further used to send the operation query request to the SDN controller; and is also used to receive the network configuration operation result sent by the SDN; The third interface unit is further configured to send the network configuration operation result to the NFVO through the second newly added interface.
37. The device according to claim 29, 33 or 36, characterized in that The first enhanced interface includes one of the following interfaces: CreateBGPNeighbor interface, CreateExroutes interface, CreateVPCConnection interface, CreateTapService interface, CreateTapFlow interface; The extended field in the message received by the third interface unit from the NFVO through the first enhanced interface includes an NS instance identifier; The extended field in the message sent by the third interface unit to the NFVO through the first enhanced interface includes the NS instance identifier and the VL operation identifier.
38. A data transmission device, characterized in that: The device comprises: a first sending unit and a first receiving unit; wherein, The first sending unit is used to send an operation request to the software defined network SDN controller through the virtualization infrastructure manager VIM, and the operation request is used to send network configuration parameters to the forwarding device; The first receiving unit is configured to obtain, through the VIM, information sent by the SDN controller indicating that the network configuration parameter is abnormally sent, when the network configuration parameter is abnormally sent.
39. The device according to claim 38, characterized in that The first sending unit is used to send a first operation request to the VIM through the first enhanced interface of the VIM, and the first operation request includes at least a network service NS instance identifier, a VIM identifier, a VL operation type and a VL operation identifier; VL represents a virtual connection between virtualized network functions VNF.
40. The device according to claim 39, characterized in that The device also includes a second recording unit, which is used to add the NS instance identifier, the VIM identifier, the VL operation type and the VL operation identifier to a second operation record table.
41. The device according to claim 38, characterized in that The first receiving unit is also used to receive the operation result sent by the VIM through the first enhanced interface of the VIM after sending the operation request to the SDN controller through the VIM, and the operation result indicates that the SDN controller has successfully received the operation request; the operation result includes the network service NS instance identifier and the VL operation identifier; VL represents the virtual connection between the virtualized network functions VNF.
42. The device according to claim 38, characterized in that The first receiving unit is used to receive information sent by the VIM through the first newly added interface of the VIM, which indicates that the network configuration parameter is sent abnormally; the information includes a network service NS instance identifier.
43. The device according to claim 38, characterized in that The first sending unit is used to send a second query request to the VIM through the second newly added interface of the VIM, where the second query request is used to query whether the network configuration parameter is sent abnormally; The first receiving unit is configured to receive, through the second newly added interface, information sent by the VIM indicating that the network configuration parameter is sent abnormally.
44. The device according to claim 40, characterized in that The second recording unit is further used to determine the operation status related to querying a specific NS instance according to the information recorded in the second operation record table; The first sending unit is further used to send an operation query request to the VIM through the first enhanced interface of the VIM, wherein the operation query request includes at least one of the following: an NS instance identifier and a VL operation identifier; The first receiving unit is further configured to receive a network configuration operation result sent by the VIM through a second newly added interface of the VIM.
45. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 5; or, when the program is executed by a processor, it implements the steps of the method described in any one of claims 6 to 15; or, when the program is executed by a processor, it implements the steps of the method described in any one of claims 16 to 22.
46. A communication device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method described in any one of claims 1 to 5 are implemented; or, when the processor executes the program, the steps of the method described in any one of claims 6 to 15 are implemented; or, when the processor executes the program, the steps of the method described in any one of claims 16 to 22 are implemented.
