CN112865999A

CN112865999A - Information processing method and related equipment

Info

Publication number: CN112865999A
Application number: CN201911195547.0A
Authority: CN
Inventors: 吴展
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-11-28
Filing date: 2019-11-28
Publication date: 2021-05-28
Anticipated expiration: 2039-11-28
Also published as: WO2021103801A1; CN112865999B

Abstract

The embodiment of the application provides an information processing method and related equipment, wherein the method is applied to a software defined network and comprises the following steps: acquiring data in a second model format, wherein the second model format comprises second model field information, and the second model field information comprises field information of model formats supported by one or more repeaters; comparing the second model field information with third model field information to obtain a comparison result, wherein the third model field information is field information included in a third model format, and the third model format is a model format supported by the first transponder; converting the data in the second model format into data in a third model format if the comparison result indicates that the second model field information can be converted into the third model field information; and sending the data in the third model format to the first transponder. By adopting the embodiment of the application, the development cost and the maintenance cost of engineering can be saved.

Description

Information processing method and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to an information processing method and a related device.

Background

A controller of a Software Defined Network (SDN) manages different types and versions of repeaters (repeaters include devices such as switches and routers), a southbound interface of the controller is connected with a northbound interface of the repeater, and the northbound interface of each repeater continuously evolves along with version upgrading. In the prior art, in order to adapt the data model of the southbound interface of the controller to the data model of the updated northbound interface of the transponder, a large number of drivers need to be continuously written according to the updating condition of the transponder and deployed in the controller, so as to adapt to the corresponding northbound interface model of the transponder.

In addition, the northbound interface models of different types of repeaters are different, and if a driver needs to be written for each type of repeater in different versions, the workload is huge, and the development cost and the maintenance cost are increased.

Disclosure of Invention

The embodiment of the application discloses an information processing method and related equipment, and the SDN controller can realize self-adaptive matching of models and the models of repeaters of different manufacturers in different versions without upgrading versions, so that development cost and engineering maintenance cost are saved.

In a first aspect, an embodiment of the present application discloses an information processing method, which is applied to a software defined network, and the method may be implemented by an SDN controller, but based on that the SDN controller is actually a computer application in an SDN and needs to be able to run depending on a device, an actual executor of the information processing method disclosed in the embodiment of the present application is a device that carries the SDN controller. The device may be a physical server, a cloud server, or other device capable of running the SDN controller. The method can comprise the following steps:

acquiring data in a second model format, wherein the second model format comprises second model field information, and the second model field information comprises field information of model formats supported by one or more repeaters;

comparing the second model field information with third model field information to obtain a comparison result, wherein the third model field information is field information included in a third model format, and the third model format is a model format supported by the first transponder;

converting the data in the second model format to data in a third model format if the comparison result indicates that the second model field information is convertible to the third model field information;

transmitting the data in the third model format to the first transponder.

Compared with the prior art, the SDN controller can realize the self-adaptive matching of the model and the models of the repeaters of different manufacturers in different versions without updating the versions, and saves the development cost and the engineering maintenance cost.

In one possible implementation, the converting the data in the second model format into the data in the third model format in the case that the comparison result indicates that the second model field information can be converted into the third model field information includes:

and deleting the first field in the data in the second model format and the data included in the first field if the comparison result is that the first field included in the second model field information is absent in the fields included in the third model field information, wherein the first field includes one or more fields.

The embodiment of the application realizes the conversion of the model by deleting redundant fields and information in the data in the second model format.

and adding the second field and the data included by the second field in the data in the second model format when the comparison result is that the second field included in the second model field information is absent in the fields included in the second model field information, wherein the second field includes one or more fields.

The embodiment of the application realizes the conversion of the model by adding the fields and information which are lacked in the data in the second model format.

and converting the data type of a third field in the data in the second model format into the first data type under the condition that the comparison result is that the first data type is different from a second data type, wherein the second data type can be converted into the first data type, the first data type is the data type of the third field included in the information of the third model field, and the second data type is the data type of the third field included in the information of the second model field.

The embodiment of the application realizes the conversion of the model by converting the data type of the field in the data in the second model format.

In one possible implementation, the range of values of the first data type includes the range of values of the second data type.

In one possible implementation, the obtaining data in the second model format includes: receiving data in a first model format; and mapping the data in the first model format into the data in the second model format.

In one possible implementation manner, after comparing the second model field information and the third model field information to obtain a comparison result, the method further includes:

and outputting indication information that the data in the second model format cannot be converted into the data in the third model format when the comparison result indicates that the value range of the fourth data type exceeds the value range of the third data type, wherein the third data type is the data type of a fourth field included in the field information of the third model, and the fourth data type is the data type of the fourth field included in the field information of the second model.

According to the embodiment of the application, the user is reminded to carry out corresponding processing through the prompt that the output model cannot be converted, so that the user can timely notice the problem, and the processing efficiency is improved.

In a second aspect, an embodiment of the present application discloses an apparatus, where the apparatus is applied to a software-defined network, and the apparatus includes:

an obtaining unit, configured to obtain data in a second model format, where the second model format includes second model field information, and the second model field information includes field information in a model format supported by one or more repeaters;

a comparing unit, configured to compare the second model field information with third model field information to obtain a comparison result, where the third model field information is field information included in a third model format, and the third model format is a model format supported by the first repeater;

a conversion unit configured to convert the data in the second model format into data in a third model format if the comparison result indicates that the second model field information is convertible into the third model field information;

a sending unit, configured to send the data in the third model format to the first transponder.

In one possible implementation, the conversion unit is specifically configured to: and deleting the first field in the data in the second model format and the data included in the first field if the comparison result is that the first field included in the second model field information is absent in the fields included in the third model field information, wherein the first field includes one or more fields.

In one possible implementation, the conversion unit is further specifically configured to: and adding the second field and the data included in the second field in the data in the second model format when the comparison result indicates that the second field included in the second model field information is absent in the fields included in the second model field information, wherein the second field includes one or more fields.

In one possible implementation, the conversion unit is specifically configured to: and converting the data type of a third field in the data in the second model format into the first data type under the condition that the comparison result is that the first data type is different from a second data type, wherein the second data type can be converted into the first data type, the first data type is the data type of the third field included in the information of the third model field, and the second data type is the data type of the third field included in the information of the second model field.

In one possible implementation, the obtaining unit includes:

a receiving unit, configured to receive data in a first model format;

a mapping unit, configured to map the data in the first model format to the data in the second model format.

In one possible embodiment, the apparatus further includes an output unit, configured to, after comparing the second model field information and the third model field information to obtain a comparison result,

The beneficial effects of any one of the second aspect are described with reference to the first aspect, and are not described herein again.

In a third aspect, an embodiment of the present application discloses an apparatus, which is applied to a software-defined network, and includes a processor, a communication interface, and a memory, where the memory is configured to store a computer program and/or data, and the processor is configured to execute the computer program stored in the memory, so that the apparatus performs the following operations:

transmitting the data in the third model format to the first transponder.

deleting the first field and the data included in the first field in the data in the second model format when the comparison result is that the first field included in the second model field information is absent in the field included in the third model field information; the first field includes one or more fields.

and adding the second field and the data included in the second field in the data in the second model format when the comparison result indicates that the second field included in the second model field information is absent in the fields included in the second model field information, wherein the second field includes one or more fields.

and outputting, by the communication interface, indication information that the data in the second model format cannot be converted into the data in the third model format when the comparison result indicates that the value range of the fourth data type exceeds the value range of the third data type, where the third data type is a data type of a fourth field included in the field information of the third model, and the fourth data type is a data type of the fourth field included in the field information of the second model.

The beneficial effects of any one of the third aspect are described with reference to the first aspect, and are not described herein again.

In a fourth aspect, the present application discloses a computer-readable storage medium storing a computer program, which is executed by a processor to implement the method of any one of the above first aspects.

In a fifth aspect, the present application discloses a computer program product, which when being read and executed by a computer, is to carry out the method of any one of the above first aspects.

In a sixth aspect, embodiments of the present application disclose a computer program, which, when executed on a computer, will make the computer implement the method of any one of the above first aspects.

To sum up, in the embodiment of the present application, a second model format including a field of a model format supported by one or more repeaters and a data type of the field is configured in advance in an SDN controller of a device, and information of a user is converted into information matched with the model format of the repeater in a self-adaptive manner through the second model format, so that the information of the user is delivered to the repeater. Compared with the prior art, the SDN controller can realize the self-adaptive matching of the model and the models of the repeaters of different manufacturers in different versions without updating the versions, and saves the development cost and the engineering maintenance cost.

Drawings

The drawings to be used in the embodiments of the present application will be described below.

Fig. 1 is a schematic diagram of a system architecture of an information processing method according to an embodiment of the present disclosure;

fig. 2 is an interaction flow diagram of an information processing method according to an embodiment of the present disclosure;

fig. 3 is a schematic diagram of a model in an information processing method according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of another model in the information processing method according to the embodiment of the present disclosure;

fig. 5 is a schematic diagram of another model in the information processing method according to the embodiment of the present disclosure;

fig. 6 is a schematic diagram of another model in the information processing method according to the embodiment of the present disclosure;

fig. 7 is a schematic flowchart of another information processing method according to an embodiment of the present disclosure;

fig. 8 is a schematic logical structure diagram of an apparatus according to an embodiment of the present invention;

fig. 9 is a schematic diagram of a hardware structure of the device according to the embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application are described below with reference to the drawings.

In order to better understand an information processing method provided in the embodiment of the present application, a system architecture applicable to the embodiment of the present application is described below. The system architecture to which the information processing method provided in the embodiment of the present application is applicable may be a Software Defined Network (SDN) system architecture. As shown in fig. 1, a system architecture of an SDN may include three layers, where a first layer is an application layer, a second layer is a control layer, and a third layer is an infrastructure layer. The application layer may include one or more SDN applications, each SDN application may implement a different user service; the control layer may include one or more SDN controllers; the infrastructure layer includes one or more repeaters. The SDN controller of the control layer establishes communication with the SDN application of the application layer through a northbound interface, and the SDN controller of the control layer establishes communication with the repeater of the infrastructure layer through a southbound interface.

The application layer implements various upper layer applications intended by the user, such applications may be referred to as collaborative layer applications, and typical applications include Operation Support Systems (OSS), Openstack, and the like. The OSS is responsible for service coordination throughout the network. Openstack is responsible for coordination of network, calculation and storage in a data center.

The control layer is the control center of the system, and is responsible for generating internal switching paths and boundary service routes of the network and processing network state change events. When the network has a state change, such as a link failure, a node failure, network congestion, etc., the control layer may adjust the network switching path and the traffic route according to the change of the network state, so that the network can be always in a normal service state. The implementation entity of the control layer is an SDN controller, namely, the most core component under an SDN network architecture, the control layer is a brain in an SDN network system, and is a decision-making component, and the core function of the control layer is to implement calculation of a network internal switching path and boundary service routing calculation.

The forwarding layer mainly forms a basic forwarding network by the circuits of the repeaters and the connectors, the layer is responsible for executing the forwarding of user data, and forwarding table items required in the forwarding process are generated by the control layer. The forwarding layer is a system execution unit, which usually does not make a decision, and its core component is a system forwarding engine, which is responsible for forwarding messages according to forwarding data issued by the control layer. The forwarding layer reports the network resource information and state on one hand, and receives the forwarding information sent by the control layer on the other hand.

Specifically, the forwarder may be a device such as an SDN switch and a router, which may implement a forwarding function.

The northbound interface is a management interface, in the same form and type as the management interface provided by the legacy device. Only the content of the provided interfaces is different, the traditional device provides a service management interface of a single device, which is called a configuration interface, and the SDN controller provides a network service management interface. Protocols for implementing such a northbound interface typically include conventional network management interface protocols such as restul interface, Netconf interface, CLI interface, and the like.

The southbound interface is mainly used for data interaction between the SDN controller and the forwarder, and comprises topology information, label resources, statistical information, alarm information and the like collected from equipment, and also comprises control information issued by the SDN controller, such as various flow tables. At present, the main southbound interface control protocols include OpenFlow protocol, Netconf protocol, PCEP, BGP and the like. The SDN controller uses these interface protocols as a transition separation protocol.

It should be noted that the system architecture to which the information processing method provided in the embodiment of the present application is applicable is not limited to the system architecture shown in fig. 1.

An information processing method is introduced below, which may be applied to a system architecture as shown in fig. 1, that is, the method may be applied to a software defined network, and the method may be implemented by an SDN controller, but based on that the SDN controller is actually a computer application in an SDN and needs to be capable of running depending on a device, a practical executor of an information processing method disclosed in this embodiment of the present application is a device bearing the SDN controller. The device may be a physical server, a cloud server, or other device capable of running the SDN controller. In order to better embody the essence of the information processing method provided by the embodiment of the present application, the method is described below with an SDN controller as an execution subject instead of the apparatus.

The method includes, but is not limited to, the steps of:

step 201, the first SDN application sends data in the first model format to the SDN controller.

In a specific embodiment, the first SDN application may be one of one or more SDN applications in the application layer shown in fig. 1, the first SDN application may be management software or other service software of a user such as an operator management SDN system, and a carrier of the first SDN application may be a terminal of the user, and the terminal may be a device such as a computer, a mobile phone, and the like, which may carry application software. The SDN controller may be an SDN controller in the control layer shown in fig. 1.

When the user needs to send information to a forwarder (referred to as a first forwarder), the information may be sent to the SDN controller by the first SDN application, and the SDN controller forwards the information to the first forwarder. Specifically, the information may be data in a first model format. The first model format is a model format when the first SDN application generates the information, and may include field information such as one or more fields and a data type of the field. The first transponder may be a transponder in the forwarding layer shown in fig. 1 described above.

Step 202, the SDN controller receives the data in the first model format.

Specifically, the SDN controller may receive, through a northbound interface, data in the first model format sent by the first SDN application.

Step 203, the SDN controller maps the data in the first model format to data in a second model format, where the second model format includes second model field information, and the second model field information includes field information of model formats supported by one or more repeaters.

Optionally, the second model field information may include information about fields of model formats supported by the one or more repeaters, data types of the fields, and the like.

In a specific embodiment, after the SDN controller receives the data in the first model format, since the data in the first model format is not data in a model format that can be recognized by the SDN controller, the SDN controller needs to map the data in the model format into data in a recognizable model format.

In addition, since the SDN controller is finally intended to send the received data to the repeater, but since model formats supported by different versions of repeaters of different manufacturers are different, the model format of the data needs to be converted into a model format supported by a corresponding repeater before the SDN controller sends the data to the repeater. Therefore, in the embodiment of the present application, a standard model format, which is recognizable by the SDN controller and includes a field of a model format supported by one or more repeaters and a data type of the field, is preconfigured in the SDN controller, and the standard model format is the second model format.

To facilitate understanding of how the data in the first model format is mapped to the data in the second model format, the following description is given by way of example. See tables 1 and 2.

TABLE 1

Field(s)	Field data type	Specific data included in the field
			Field 1	int(1-5)	1
Field 2	int(1-3)	2
			Field 3	string(1-5)	3

TABLE 2

Field(s)	Field data type	Specific data included in the field
			Field a	int(1-5)	-
Field b	int(1-3)	-
			Field c	string(1-5)	-

It is assumed that the above table 1 represents data in the above first model format, including fields, corresponding field data types, and specific data included in the corresponding fields. Assuming that the above table 2 represents the second model format including fields and corresponding field data types, the specific data included in the fields in table 2 is empty, because table 2 represents only one model and does not include the specific data. After receiving the data in table 1, the SDN controller obtains, through parsing, that field 1 in table 1 is mapped as

Field a in table 2, field 2 in table 1 maps to field b in table 2, and field 3 in table 1 maps to field c in table 2. After the mapping relationship of the fields is determined, the SDN controller fills the data included in the fields in table 1 into the positions of the specific data included in the corresponding fields in table 2 according to the mapping relationship to obtain table 3.

TABLE 3

Field(s)	Field data type	Specific data included in the field
			Field a	int(1-5)	1
Field b	int(1-3)	2
			Field c	string(1-5)	3

It should be noted that, how to map model data by the SDN controller is described here only by way of example, and the specific mapping is determined according to specific situations, which is not limited by the present solution.

And 204, the SDN controller compares the second model field information with third model field information to obtain a comparison result, where the third model field information is field information included in a third model format, and the third model format is a model format supported by the first forwarder.

In a specific embodiment, after the SDN controller establishes a connection with the first forwarder, that is, after the SDN controller and the first forwarder can communicate with each other, the SDN controller may obtain a model format supported by the first forwarder, that is, the third model format. For example, the SDN controller may obtain the model format of the first repeater through get schema technology of netconf or other technology. Of course, the third model format includes one or more fields and field information such as data types of the fields, i.e., the third model field information described above.

In one possible implementation, the SDN controller may retrieve the model format of the first forwarder each time a connection is established with the first forwarder. Or, the SDN controller may also establish a connection with the first forwarder for the first time, obtain the model format of the first forwarder, store the model format, and directly take the model format from the stored storage space when the model format needs to be used next time, which may be implemented only when the model format of the first forwarder is not updated.

In a specific embodiment, the SDN controller compares the second model field information with third model field information to obtain a plurality of comparison results, for example, increase or decrease of the third model field information compared with a field included in the second model field information, change of a field data type, whether a value range of the field data type is the same, and the like. And the SDN controller determines whether the data in the second model format can be converted into the data in the third model format according to different comparison results.

Step 205, in a case that the comparison result indicates that the second model field information can be converted into the third model field information, the SDN controller converts the data in the second model format into data in a third model format.

In an embodiment, the comparison result indicates that the second model field information can be converted into the third model field information, and the comparison result includes a plurality of cases, which will be described one by one.

And step 206, the SDN controller sends the data in the third model format to the first forwarder.

After the data in the second model format is converted into the data in the third model format, the SDN controller sends the data in the third model format to the first forwarder, so that the data from the application layer to the infrastructure layer is issued. After receiving the data in the third model format, the first forwarder realizes a routing function according to the indication of the data, so that smooth communication between terminals can be realized, and the terminals can realize information forwarding through the first forwarder.

According to the embodiment of the application, a second model format comprising fields of model formats supported by one or more repeaters and data types of the fields is configured in an SDN controller in equipment in advance, and the data of a user is converted into data matched with the model formats of the repeaters in a self-adaptive mode through the second model format, so that the data of the user is issued to the repeaters. Compared with the prior art, the SDN controller can realize the self-adaptive matching of the model and the models of the repeaters of different manufacturers in different versions without updating the versions, and saves the development cost and the engineering maintenance cost.

The following describes a case where the above-described data in the second model format can be converted into data in the third model format.

In a first case, the comparison result indicates that the first field included in the second model field information is absent from the fields included in the third model field information. In this case, the SDN controller may delete the first field in the data in the second model format and the data included in the first field to obtain the data in the third model format. Of course, the first field may include one or more fields, and specifically includes several fields determined according to specific situations, which are not limited herein.

For ease of understanding, reference may be made to fig. 3. In fig. 3, the second forwarding model format includes A, B, C, D and F five fields, and the third forwarding model format includes A, B and C three fields, that is, the third model format lacks two fields, D and F, of the second model format, then the SDN controller may delete two fields, D and F, of the data in the second model format, and delete specific data included in the two fields, that is, D and F, to obtain the data in the third model format.

Alternatively, in the first case, the SDN controller may add, one by one, data of a field, which is the same as a field included in the third model format, in the data of the second model format to a position, which corresponds to data included in the same field in the third model format.

For ease of understanding, this is illustrated. Still referring to fig. 3, if two fields D and F of the second model format are absent in the third model format, the SDN controller may add data included in three fields A, B and C of the data of the second model format to the position of the data included in three fields A, B and C of the third model format. Specifically, the data included in the a field in the data in the second model format is added to the position of the data included in the a field in the third model format, the data included in the B field in the data in the second model format is added to the position of the data included in the B field in the third model format, and the data included in the C field in the data in the second model format is added to the position of the data included in the C field in the third model format. I.e., data of the same field in both model formats.

In a second case, the comparison result indicates that the second field included in the third model field information is absent from the fields included in the second model field information. In this case, one possible implementation is: the SDN controller may add the second field in the data in the second model format, and add default data to specific data included in the second field, where the default data may be preconfigured data or data determined according to actual conditions. Of course, the second field may include one or more fields, and specifically includes several fields determined according to specific situations, which are not limited herein. Optionally, when the second field is added, information such as the data type of the second field and the value range of the data type may be added.

Another possible implementation is: the SDN controller may add, to the data in the second model format, data specifically included in each field by field to the third model format to obtain data in the third model format, and since there is no corresponding field in the second model format, the data included in the second field in the third model format may not be added. After the SDN controller sends the data in the third model format to the forwarder, the forwarder determines the specific data included in the second field.

For ease of understanding, reference may be made to fig. 4. Similarly, in fig. 4, the second forwarding model format includes A, B, C, D and F five fields, and the third forwarding model format includes A, B, C, D, E and F six fields, that is, the E field in the third model format is absent in the second model format, the SDN controller may add the E field to the data in the second model format, and add default specific data to the E field to obtain the data in the third model format.

Or, the SDN controller may add, to the data in the second model format, data specifically included in each field by field to the third model format to obtain data in the third model format, but may not add the data in the E field. After the SDN controller sends the data in the third model format to the forwarder, the forwarder determines the specific data included in the E field.

In a third case, as a result of the comparison, the data type of the third field included in the third model field information is different from the data type of the third field included in the second model field information, but the data type of the third field included in the third model field information can be converted into the data type of the third field included in the second model field information. In this case, the SDN controller may convert a data type of a third field in the data in the second model format into a data type of a third field included in the third model field information, that is, may obtain the data in the third model format. Of course, the third field may include one or more fields, and specifically includes several fields determined according to specific situations, which are not limited herein.

In a specific embodiment, the data type of the third field in the third model format can be converted into a data type of the third field in the second model format, which can represent: the value range of the data type of the third field included in the third model field information includes the value range of the data type of the third field included in the second model field information.

For ease of understanding, reference may be made to fig. 5. Similarly, in fig. 5, the second forwarding model format includes A, B, C, D and F fields, and the third forwarding model format also includes A, B, C, D and F fields. However, the data type of the F field defined in the second model format is string, and the values range from "1", "2", and "3", while the data type of the F field defined in the third model format is int, and the values range from 1, 2, and 3. Because the data type of the F field defined in the second model format is the data type of the character string, but the value range of the character string is the same as the value range of the integer type of the F field in the third model format, the data type of the F field in the data in the second model format can be converted into the data type of the F field in the data in the third model format. In addition, if the data type of the F field in the third model format is int (1-5), that is, the F field is defined as an integer type and the value ranges from 1, 2, 3, 4, and 5, the data type of the F field in the second model format can also be converted into the data type of the F field in the third model format.

In some possible embodiments, the comparison result may include a comparison result of two or three of the first case, the second case, and the third case.

For example, as a result of the comparison, the field included in the third model field information lacks a first field included in the second model field information, and the field included in the second model field information lacks a second field included in the third model field information.

For another example, as a result of the comparison, the data type of the third field included in the third model field information is different from the data type of the third field included in the second model field information, but the data type of the third field included in the third model field information can be converted into the data type of the third field included in the second model field information.

For another example, the comparison result may include that the second field included in the third model field information is absent from the fields included in the second model field information, and the data type of the third field included in the third model field information is different from the data type of the third field included in the second model field information, but the data type of the third field included in the third model field information can be converted into the data type of the third field included in the second model field information.

For another example, the comparison result may include that the field included in the third model field information lacks a first field included in the second model field information, the field included in the second model field information lacks a second field included in the third model field information, and a data type of the third field included in the third model field information is different from a data type of the third field included in the second model field information, but the data type of the third field included in the third model field information can be converted into the data type of the third field included in the second model field information.

In a specific embodiment, if the comparison result includes two or more of the three cases, the SDN controller may process the data according to the operations of the corresponding cases and then combine two or more processing results to obtain the data in the third model format.

For example, the comparison result includes a field included in the third model field information that lacks a first field included in the second model field information, and a field included in the second model field information that lacks a second field included in the third model field information. Then, the SDN controller may delete the first field in the data in the second model format and the data included in the first field, and the SDN controller may add the second field in the data in the second model format and add default data for specific data included in the second field. The operation of the two cases is completed to obtain the data in the third model format.

Or, the SDN controller may delete the first field in the data in the second model format and the data included in the first field, and add the data specifically included in each field to the third model format according to the field to obtain the data in the third model format, or may not add the data included in the second field.

Here, the processing manner of the SDN controller when the comparison result includes two or more of the three cases is described only by way of example, and the other cases may be referred to for processing, which is not described herein again.

In some possible embodiments, the comparison result obtained in step 204 indicates that the data in the second model format cannot be converted into data in the third model format. The following describes a case where the above-described data in the second model format cannot be converted into data in the third model format.

The comparison result obtained in the step 204 is that the value range of the data type of the fourth field in the second model format exceeds the value range of the data type of the fourth field in the third model format. In this case, the data in the second model format cannot be converted into the data in the third model format. The SDN controller may output an indication that the data in the second model format cannot be converted into the data in the third model format, so as to prompt the user for corresponding subsequent processing.

In this embodiment, regardless of whether the data type of the fourth field in the second model format is the same as the data type of the fourth field in the third model format, as long as the value range of the data type of the fourth field in the second model format exceeds the value range of the data type of the fourth field in the third model format, the data in the second model format cannot be converted into the data in the third model format.

For ease of understanding, reference may be made to fig. 6. Similarly, in fig. 6, the second forwarding model format includes A, B, C, D and F fields, and the third forwarding model format also includes A, B, C, D and F fields. However, the data type of the F field defined in the second model format is string, and the values range from "1", "2", "3", "4", and "5", and the data type of the F field defined in the third model format is int, and the values range from 1, 2, and 3. The value range of the data type of the F field defined in the second model format exceeds the value range of the data type of the F field defined in the third model format, that is, the value range of the data type of the F field in the third model format is incompatible with the value range of the data type of the F field defined in the second model format. Therefore, the data in the second model format cannot be converted into data in the third model format.

Based on the information processing method shown in fig. 2, a possible embodiment is given below, see fig. 7. In fig. 7, the SDN controller first receives data in a first model format sent by a user through a northbound interface, and then maps the data in the first model format to data in a second model format through a service mapping module (for a detailed description of this step, refer to step 203 shown in fig. 2). Then, the SDN controller inputs the obtained data in the second model format to a model automatic mapping module, and converts the data in the second model format into data in a third model format (the detailed description of this step may refer to step 204 and step 205 shown in fig. 2). After obtaining the data in the third model format supported by the first forwarder, the SDN controller sends the data in the third model format to the first forwarder through a southbound interface. Here, only one possible implementation of the information processing method provided in the embodiment of the present application is exemplarily given, and other modified application embodiments exist, which are within the protection scope of the present application and are not described herein for a long time.

The foregoing mainly introduces an information processing method provided in an embodiment of the present application. It is understood that each device comprises corresponding hardware structures and/or software modules for executing each function in order to realize the corresponding function. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, functional modules of the device carrying the SDN controller may be divided according to the method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that the division of the modules in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of dividing functional modules according to corresponding functions, fig. 8 shows a schematic diagram of a possible logical structure of an apparatus carrying an SDN controller according to any one of the above method embodiments, where the apparatus 800 includes an obtaining unit 801, a comparing unit 802, a converting unit 803, and a sending unit 804.

Illustratively, the obtaining unit 801 is configured to perform the steps of obtaining information in the aforementioned illustrated method embodiments, for example, to perform the steps of obtaining data in the second model format. The comparison unit 802 is configured to perform the steps of the comparison in the previously illustrated method embodiment, for example, the steps of performing the comparison between the second model format and the third model format. The conversion unit 803 is used for performing the steps of information conversion in the previously described illustrated method embodiments, for example for performing the steps of converting data in the second model format into data in the third model format. The sending unit 805 is configured to perform the steps of sending information in the foregoing illustrated method embodiments, for example, to perform the steps of sending data in the third model format to the first transponder through the southbound interface, and the like.

Optionally, the obtaining unit 801 may be divided into a receiving unit and a mapping unit, and the receiving unit may be configured to perform a step of receiving information in the foregoing illustrated method embodiment, for example, to perform a step of receiving data in the first model format. The mapping unit may be configured to perform steps of mapping data in the aforementioned illustrated method embodiment, for example, to perform steps of mapping data in the first model format to data in the second model format.

Optionally, the device 800 may further comprise a processing unit and a storage unit. The storage unit is used for storing computer programs (such as the computer application programs of the SDN controller) and data. The processing unit may call the computer program and/or data of the memory unit such that the device 800 may implement any one of the above-described method embodiments.

Fig. 9 is a schematic diagram of a possible hardware structure of a device carrying an SDN controller according to an embodiment of the information processing method provided in the present application. The apparatus 900 comprises: a processor 901, a memory 902, and a communication interface 903. The processor 901, communication interface 903, and memory 902 may be connected to each other or to each other through a bus 904.

Illustratively, the memory 902 is used for storing computer programs (e.g., computer applications of the SDN controller described above) and data of the device 900, and the memory 902 may include, but is not limited to, Random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), and the like. The communication interface 903 is used to support the device 900 for communication, such as to receive or transmit data.

Illustratively, the processor 901 may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, transistor logic, a hardware component, or any combination thereof. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The processor 901 may be configured to read the program stored in the memory 902, and execute the operations performed by the SDN controller in the method described in fig. 2 and the possible embodiments.

The embodiment of the present application also discloses a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method described in the above fig. 2 and possible embodiments.

The embodiment of the present application also discloses a computer program product, and when the computer program product is read and executed by a computer, the method described in the above fig. 2 and possible embodiments will be executed.

The embodiment of the present application also discloses a computer program, which when executed on a computer, will make the computer implement the method described in the above fig. 2 and possible embodiments.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An information processing method applied to a software-defined network, the method comprising:

transmitting the data in the third model format to the first transponder.

2. The method of claim 1, wherein converting the data in the second model format into data in a third model format if the comparison result indicates that the second model field information can be converted into the third model field information comprises:

3. The method according to claim 1 or 2, wherein the converting the data in the second model format into the data in the third model format if the comparison result indicates that the second model field information can be converted into the third model field information comprises:

4. The method according to any one of claims 1 to 3, wherein the converting the data in the second model format into the data in the third model format in the case that the comparison result indicates that the second model field information can be converted into the third model field information comprises:

5. The method of claim 4, wherein the range of values of the first data type comprises a range of values of the second data type.

6. The method of any of claims 1 to 5, wherein said obtaining data in a second model format comprises:

receiving data in a first model format;

and mapping the data in the first model format into the data in the second model format.

7. An apparatus, applied to a software defined network, the apparatus comprising:

8. The device according to claim 7, wherein the conversion unit is specifically configured to: and deleting the first field in the data in the second model format and the data included in the first field if the comparison result is that the first field included in the second model field information is absent in the fields included in the third model field information, wherein the first field includes one or more fields.

9. The device according to claim 7 or 8, wherein the conversion unit is further configured to:

10. The apparatus according to any one of claims 7 to 9, wherein the conversion unit is specifically configured to: and converting the data type of a third field in the data in the second model format into the first data type under the condition that the comparison result is that the first data type is different from a second data type, wherein the second data type can be converted into the first data type, the first data type is the data type of the third field included in the information of the third model field, and the second data type is the data type of the third field included in the information of the second model field.

11. The apparatus of claim 10, wherein the range of values for the first data type comprises a range of values for the second data type.

12. The apparatus according to any one of claims 7 to 11, characterized in that the acquisition unit comprises:

a receiving unit, configured to receive data in a first model format;

13. An apparatus for application to a software defined network, the apparatus comprising a processor, a communication interface, and a memory, wherein the memory is configured to store a computer program and/or data, and wherein the processor is configured to execute the computer program stored in the memory to cause the apparatus to perform the following:

transmitting the data in the third model format to the first transponder.

14. The apparatus of claim 13, wherein the converting the data in the second model format into data in a third model format if the comparison result indicates that the second model field information is convertible to the third model field information comprises:

15. The apparatus according to claim 13 or 14, wherein said converting the data in the second model format into the data in the third model format in case that the comparison result indicates that the second model field information can be converted into the third model field information comprises:

16. The apparatus according to any one of claims 13 to 15, wherein said converting the data in the second model format into the data in the third model format in the case that the comparison result indicates that the second model field information can be converted into the third model field information comprises:

17. The device of claim 16, wherein the range of values for the first data type comprises a range of values for the second data type.

18. The apparatus of claim 16 or 17, wherein said obtaining data in a second model format comprises:

receiving data in a first model format;

19. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which is executed by a processor to implement the method of any one of claims 1 to 6.

20. A computer program product, characterized in that when the computer program product is read and executed by a computer, the method according to any of claims 1 to 6 is executed.

21. A computer program for causing a computer to carry out the method of any one of claims 1 to 6 when the computer program is carried out on the computer.