CN114363306A - Data transmission method based on Netconf protocol and related equipment - Google Patents
Data transmission method based on Netconf protocol and related equipmentDownload PDFInfo
- Publication number
- CN114363306A CN114363306ACN202111511027.3ACN202111511027ACN114363306ACN 114363306 ACN114363306 ACN 114363306ACN 202111511027 ACN202111511027 ACN 202111511027ACN 114363306 ACN114363306 ACN 114363306A
- Authority
- CN
- China
- Prior art keywords
- server
- client
- identifier
- hello packet
- hello
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
Description
Translated fromChinese技术领域technical field
本申请涉及网络配置领域，尤其涉及一种基于Netconf协议的数据传输方法及相关设备。The present application relates to the field of network configuration, and in particular, to a data transmission method and related equipment based on the Netconf protocol.
背景技术Background technique
随着信息时代的发展，网络配置协议(network configuration protocol,Netconf)在软件定义网络(software define network，SDN)中广泛使用。Netconf协议采用客户端(client)和服务端(server)的结构。With the development of the information age, network configuration protocol (Netconf) is widely used in software defined network (SDN). Netconf protocol adopts the structure of client (client) and server (server).
客户端与服务端建立通信通道完成连接需要进行多次交互，一般的交互方式是客户端与服务端首先利用hello报文协商使得双方建立会话，之后客户端向服务端发送查询报文用于查询服务端的设备类型、厂商以及版本等设备标识，接下来客户端接收服务端发送的携带自身设备标识的查询响应，进而客户端安装与服务端对应的设备驱动。The client and the server need to interact several times to establish a communication channel to complete the connection. The general interaction method is that the client and the server first use the hello message to negotiate to establish a session, and then the client sends a query message to the server for query. The device type, manufacturer, version and other device identifiers of the server, and then the client receives the query response that carries its own device identifier sent by the server, and then the client installs the device driver corresponding to the server.
然而，客户端与服务端之间除了hello报文交互外，还需要查询报文的交互，双方建立通信通道所需要的交互耗时较长，导致连接效率较低。However, in addition to the hello message interaction between the client and the server, the interaction of the query message is also required. The interaction required by the two parties to establish a communication channel takes a long time, resulting in low connection efficiency.
发明内容SUMMARY OF THE INVENTION
本申请实施例提供了一种基于Netconf协议的数据传输方法及相关设备，缩短了客户端与服务端建立通信通道所需要的时间，提高了连接效率。The embodiments of the present application provide a data transmission method and related equipment based on the Netconf protocol, which shortens the time required for establishing a communication channel between a client and a server, and improves connection efficiency.
第一方面，本申请实施例提供了一种基于Netconf协议的数据传输方法，该方法包括如下步骤。In a first aspect, an embodiment of the present application provides a data transmission method based on the Netconf protocol, and the method includes the following steps.
客户端接收服务端发送的第一hello报文，其中，第一hello报文包括服务端的第一能力信息集合以及服务端的设备标识，进而客户端根据服务端的设备标识安装与服务端对应的设备驱动。The client receives the first hello packet sent by the server, where the first hello packet includes the first capability information set of the server and the device identifier of the server, and then the client installs a device driver corresponding to the server according to the device identifier of the server .
在该实施方式中，客户端在与服务端进行hello报文协商的过程中即可获取服务端的设备标识，无需再进行额外的交互客户端就可以完成设备驱动的选择及安装，缩短了客户端与服务端建立通信通道所需要的时间，提高了连接效率。In this embodiment, the client can obtain the device identifier of the server during the hello message negotiation process with the server, and the selection and installation of the device driver can be completed without any additional interaction on the client, which shortens the time required for the client. The time required to establish a communication channel with the server improves the connection efficiency.
可选地，在一些可能的实施方式中，服务端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the device identifier of the server includes at least one of a device type, a device manufacturer, a device version, and a device model.
在该实施方式中，列举了服务端设备标识的具体类型，提高了本方案的实用性。In this implementation manner, the specific types of the server device identification are listed, which improves the practicability of this solution.
可选地，在一些可能的实施方式中，客户端根据服务端的设备标识安装与服务端对应的设备驱动包括：Optionally, in some possible implementations, the installation of the device driver corresponding to the server by the client according to the device identifier of the server includes:
客户端从预置的设备驱动集合中查找与服务端的设备标识对应的设备驱动，进而客户端安装设备驱动。The client searches for the device driver corresponding to the device identifier of the server from the preset device driver set, and then the client installs the device driver.
在该实施方式中，提供了一种客户端根据服务端的设备标识安装设备驱动的具体实施方式，提高了本方案的可实现性。In this implementation manner, a specific implementation manner in which the client installs the device driver according to the device identification of the server is provided, which improves the practicability of this solution.
可选地，在一些可能的实施方式中，方法还包括：Optionally, in some possible implementations, the method further includes:
客户端向服务端发送第二hello报文，第二hello报文包括客户端的第二能力信息集合。The client sends a second hello packet to the server, where the second hello packet includes the second capability information set of the client.
在该实施方式中，客户端与服务端需要通过相互向对端发送携带各自能力信息集合的hello报文来进行hello报文协商，使得本方案更加完整。In this implementation manner, the client and the server need to perform hello packet negotiation by sending hello packets carrying respective capability information sets to each other to each other, so that this solution is more complete.
可选地，在一些可能的实施方式中，第二hello报文还包括客户端的设备标识，客户端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the second hello packet further includes a device identifier of the client, and the device identifier of the client includes at least one of a device type, a device manufacturer, a device version, and a device model.
在该实施方式中，同第一hello报文类似，第二hello报文也可以携带客户端的设备标识，提高了本方案的扩展性。In this embodiment, similar to the first hello packet, the second hello packet can also carry the device identifier of the client, which improves the scalability of the solution.
可选地，在一些可能的实施方式中，第一hello报文还包括会话标识，会话标识用于标识客户端与服务端之间建立的会话。Optionally, in some possible implementation manners, the first hello packet further includes a session identifier, where the session identifier is used to identify a session established between the client and the server.
在该实施方式中，每一组客户端与服务端之间的会话都有与之对应的会话标识，具体的该会话标识可以携带在第一hello报文中，进一步提高了本方案的完整性。In this embodiment, each session between the client and the server has a corresponding session identifier, and the specific session identifier can be carried in the first hello packet, which further improves the integrity of the solution. .
第二方面，本申请实施例提供了一种基于Netconf协议的数据传输方法，该方法包括如下步骤。In a second aspect, an embodiment of the present application provides a data transmission method based on the Netconf protocol, and the method includes the following steps.
服务端向客户端发送第一hello报文，以使得客户端根据服务端的设备标识安装与服务端对应的设备驱动，第一hello报文包括服务端的第一能力信息集合以及服务端的设备标识。The server sends a first hello packet to the client, so that the client installs a device driver corresponding to the server according to the device identifier of the server. The first hello packet includes the first capability information set of the server and the device identifier of the server.
可选地，在一些可能的实施方式中，服务端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the device identifier of the server includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选地，在一些可能的实施方式中，方法还包括：Optionally, in some possible implementations, the method further includes:
服务端接收客户端发送的第二hello报文，第二hello报文包括客户端的第二能力信息集合。The server receives the second hello packet sent by the client, where the second hello packet includes the second capability information set of the client.
可选地，在一些可能的实施方式中，第二hello报文还包括客户端的设备标识，客户端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the second hello packet further includes a device identifier of the client, and the device identifier of the client includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选地，在一些可能的实施方式中，第一hello报文还包括会话标识，会话标识用于标识客户端与服务端之间建立的会话。Optionally, in some possible implementation manners, the first hello packet further includes a session identifier, where the session identifier is used to identify a session established between the client and the server.
第三方面，本申请实施例提供了一种基于Netconf协议的客户端，包括：In a third aspect, an embodiment of the present application provides a client based on the Netconf protocol, including:
接收单元，用于接收服务端发送的第一hello报文，第一hello报文包括服务端的第一能力信息集合以及服务端的设备标识；a receiving unit, configured to receive the first hello message sent by the server, where the first hello message includes the first capability information set of the server and the device identifier of the server;
安装单元，用于根据服务端的设备标识安装与服务端对应的设备驱动。The installation unit is used to install the device driver corresponding to the server according to the device identifier of the server.
可选地，在一些可能的实施方式中，服务端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the device identifier of the server includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选地，在一些可能的实施方式中，安装单元具体用于：Optionally, in some possible implementations, the installation unit is specifically used for:
从预置的设备驱动集合中查找与服务端的设备标识对应的设备驱动；Find the device driver corresponding to the device ID of the server from the preset device driver set;
安装设备驱动。Install the device driver.
可选地，在一些可能的实施方式中，客户端还包括：Optionally, in some possible implementations, the client further includes:
发送单元，用于向服务端发送第二hello报文，第二hello报文包括客户端的第二能力信息集合。The sending unit is configured to send a second hello packet to the server, where the second hello packet includes the second capability information set of the client.
可选地，在一些可能的实施方式中，第二hello报文还包括客户端的设备标识，客户端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the second hello packet further includes a device identifier of the client, and the device identifier of the client includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选地，在一些可能的实施方式中，第一hello报文还包括会话标识，会话标识用于标识客户端与服务端之间建立的会话。Optionally, in some possible implementation manners, the first hello packet further includes a session identifier, where the session identifier is used to identify a session established between the client and the server.
第四方面，本申请实施例提供了一种基于Netconf协议的服务端，包括：In a fourth aspect, an embodiment of the present application provides a Netconf protocol-based server, including:
发送单元，用于向客户端发送第一hello报文，以使得客户端根据服务端的设备标识安装与服务端对应的设备驱动，第一hello报文包括服务端的第一能力信息集合以及服务端的设备标识。A sending unit, configured to send a first hello message to the client, so that the client installs a device driver corresponding to the server according to the device identifier of the server, and the first hello message includes the first capability information set of the server and the device of the server. logo.
可选地，在一些可能的实施方式中，服务端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the device identifier of the server includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选地，在一些可能的实施方式中，服务端还包括：Optionally, in some possible implementations, the server further includes:
接收单元，用于接收客户端发送的第二hello报文，第二hello报文包括客户端的第二能力信息集合。The receiving unit is configured to receive a second hello packet sent by the client, where the second hello packet includes the second capability information set of the client.
可选地，在一些可能的实施方式中，第二hello报文还包括客户端的设备标识，客户端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, in some possible implementation manners, the second hello packet further includes a device identifier of the client, and the device identifier of the client includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选地，在一些可能的实施方式中，第一hello报文还包括会话标识，会话标识用于标识客户端与服务端之间建立的会话。Optionally, in some possible implementation manners, the first hello packet further includes a session identifier, where the session identifier is used to identify a session established between the client and the server.
第五方面，本申请实施例提供了一种基于Netconf协议的客户端，包括：In a fifth aspect, an embodiment of the present application provides a client based on the Netconf protocol, including:
处理器、存储器、总线以及输入输出接口；processor, memory, bus and input and output interface;
存储器中存储有程序代码；program code is stored in the memory;
处理器调用存储器中的程序代码时执行如第一方面任一实施方式中基于Netconf协议的数据传输方法。When the processor calls the program code in the memory, the data transmission method based on the Netconf protocol in any one of the embodiments of the first aspect is executed.
第六方面，本申请实施例提供了一种基于Netconf协议的服务端，包括：In a sixth aspect, an embodiment of the present application provides a server based on the Netconf protocol, including:
处理器、存储器、总线以及输入输出接口；processor, memory, bus and input and output interface;
存储器中存储有程序代码；program code is stored in the memory;
处理器调用存储器中的程序代码时执行如第二方面任一实施方式中基于Netconf协议的数据传输方法。When the processor calls the program code in the memory, the data transmission method based on the Netconf protocol in any embodiment of the second aspect is executed.
第七方面，本申请实施例提供一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述第一方面的任一实施方式中基于Netconf协议的数据传输方法。In a seventh aspect, an embodiment of the present application provides a computer storage medium, including instructions, which, when run on a computer, cause the computer to execute the data transmission method based on the Netconf protocol in any implementation manner of the foregoing first aspect.
第八方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面的任一实施方式中的基于Netconf协议的数据传输方法。In an eighth aspect, an embodiment of the present application provides a computer program product including instructions, which, when running on a computer, enables the computer to execute the Netconf protocol-based data transmission method in any implementation manner of the first aspect.
从以上技术方案可以看出，本申请实施例具有以下优点：As can be seen from the above technical solutions, the embodiments of the present application have the following advantages:
本申请实施例中，客户端接收服务端发送的第一hello报文，其中，第一hello报文中包括服务端的第一能力信息集合以及服务端的设备标识，进而客户端根据该服务端的设备标识安装与服务端对应的设备驱动。通过上述描述，客户端在与服务端进行hello报文协商的过程中即可获取服务端的设备标识，无需再进行额外的交互客户端就可以完成设备驱动的选择及安装，缩短了客户端与服务端建立通信通道所需要的时间，提高了连接效率。In the embodiment of the present application, the client receives the first hello packet sent by the server, where the first hello packet includes the first capability information set of the server and the device identifier of the server, and then the client receives the device identifier of the server according to the device identifier of the server. Install the device driver corresponding to the server. According to the above description, the client can obtain the device identifier of the server during the hello message negotiation process with the server, and the selection and installation of the device driver can be completed without additional interaction with the client, which shortens the time between the client and the service. The time required for the terminal to establish a communication channel is improved, and the connection efficiency is improved.
附图说明Description of drawings
图1为SDN的结构示意图；Figure 1 is a schematic diagram of the structure of SDN;
图2为本申请基于Netconf协议的数据传输方法的一个实施例示意图；2 is a schematic diagram of an embodiment of a data transmission method based on the Netconf protocol of the present application;
图3为第一hello报文的结构示意图；3 is a schematic structural diagram of a first hello message;
图4为本申请基于Netconf协议的数据传输方法的另一个实施例示意图；4 is a schematic diagram of another embodiment of the data transmission method based on the Netconf protocol of the present application;
图5为本申请基于Netconf协议的客户端的一个实施例示意图；5 is a schematic diagram of an embodiment of a client based on the Netconf protocol of the present application;
图6为申请基于Netconf协议的服务端的一个实施例示意图；6 is a schematic diagram of an embodiment of applying for a server based on the Netconf protocol;
图7为本申请基于Netconf协议的客户端的结构示意图；7 is a schematic structural diagram of a client based on the Netconf protocol of the application;
图8为本申请基于Netconf协议的服务端的结构示意图。FIG. 8 is a schematic structural diagram of a server based on the Netconf protocol of the present application.
具体实施方式Detailed ways
本申请实施例提供了一种基于Netconf协议的数据传输方法及相关设备，客户端在与服务端进行hello报文协商的过程中即可获取服务端的设备标识，无需再进行额外的交互客户端就可以完成设备驱动的选择及安装，缩短了客户端与服务端建立通信通道完成连接的时间，提高了连接效率。The embodiments of the present application provide a data transmission method and related equipment based on the Netconf protocol. The client can obtain the device identifier of the server during the hello message negotiation process with the server, and no additional interaction is required. The selection and installation of the device driver can be completed, the time for establishing a communication channel between the client and the server to complete the connection is shortened, and the connection efficiency is improved.
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。The terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the application described herein can, for example, be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.
下面首先对本申请所采用的Netconf协议进行介绍：The following first introduces the Netconf protocol used in this application:
Netconf协议是基于可扩展标记语言(extensible markup language，XML)的网络配置和管理协议，使用简单的基于远程过程调用(remote procedure call，RPC)机制实现客户端(client)和服务端(server)之间通信。其中，客户端可以是脚本或者网管上运行的一个应用程序，服务端可以是一个典型的网络设备。The Netconf protocol is a network configuration and management protocol based on extensible markup language (XML), which uses a simple remote procedure call (RPC) mechanism to implement the communication between the client (client) and the server (server). communication between. The client can be a script or an application running on the network management, and the server can be a typical network device.
Netconf协议采用了分层结构。每层分别对协议的某一方面进行包装，并向上层提供相关服务。分层结构使每层只关注协议的一个方面，实现起来更简单，同时使各层之间的依赖、内部实现的变更对其他层的影响降到最低。具体的，Netconf协议可以划分为以下四层。The Netconf protocol adopts a layered structure. Each layer wraps a certain aspect of the protocol and provides related services to the upper layer. The layered structure makes each layer only focus on one aspect of the protocol, making it easier to implement, while minimizing the impact of dependencies between layers and changes in internal implementation on other layers. Specifically, the Netconf protocol can be divided into the following four layers.
安全传输层(secure transport)：为客户端和服务端之间交互提供通讯路径。可以使用任何符合基本要求的传输层协议承载，例如，安全外壳(secure shell，SSH)协议可以作为Netconf协议的承载协议。Secure transport layer: Provides a communication path for interaction between client and server. Any transport layer protocol that meets the basic requirements can be used for the bearer, for example, the secure shell (SSH) protocol can be used as the bearer protocol of the Netconf protocol.
消息(messages)层：提供一种简单的不依赖传输协议层的，生成RPC请求和回应消息框架的机制。客户端把RPC请求内容封装在一个<rpc>元素内并发送给服务端，服务端把请求处理结果封装在一个<rpc-reply>元素内并回应给客户端。Messages layer: Provides a simple mechanism for generating RPC request and response message frames without relying on the transport protocol layer. The client encapsulates the RPC request content in an <rpc> element and sends it to the server, and the server encapsulates the request processing result in an <rpc-reply> element and responds to the client.
操作(operations)层：定义一组基本的操作，作为RPC的调用方法，可以使用XML编码的参数调用这些方法。The operations layer: defines a set of basic operations as RPC invocation methods, which can be invoked with XML-encoded parameters.
内容(content)层：由管理对象的数据模型定义，数据模型定义依赖Netconf协议的实现情况。Content (content) layer: defined by the data model of the management object, the data model definition depends on the implementation of the Netconf protocol.
客户端的主要作用包括：利用Netconf协议对网络设备进行系统管理；向服务端发送<rpc>请求，查询或修改一个或多个具体的参数值；接收服务端主动发送的告警和事件，以获知被管理设备的当前状态。The main functions of the client include: using the Netconf protocol for system management of network devices; sending <rpc> requests to the server to query or modify one or more specific parameter values; Manage the current state of the device.
服务端的主要作用包括：维护被管理设备的信息数据并响应客户端的请求；收到客户端的请求后会进行数据解析，然后给客户端返回响应；当设备发生故障或其他事件时，服务端主动将设备的告警和事件通知给客户端，向客户端报告设备的当前状态变化。The main functions of the server include: maintaining the information data of the managed device and responding to the client's request; after receiving the client's request, it will parse the data, and then return a response to the client; when the device fails or other events, the server will take the initiative to The alarms and events of the device are notified to the client, and the current state change of the device is reported to the client.
上面对Netconf协议进行了介绍，下面对本申请基于Netconf协议的一个具体应用场景进行介绍：The Netconf protocol has been introduced above, and a specific application scenario based on the Netconf protocol of this application is introduced below:
本申请可以应用于软件定义网络(software define network，SDN)中，请参阅图1，图1为SDN的结构示意图。SDN的网络结构为三层模型，其中，协同应用层主要是体现用户意图的各种上层应用程序，此类应用程序称为协同层应用程序，典型的应用包括运营支撑系统(operation support system，OSS)等。控制层是系统的控制中心，控制器负责网络的内部交换路径和边界业务路由的生成，并负责处理网络状态变化事件。转发层主要由网络设备构成基础转发网络，这一层负责执行用户数据的转发，转发过程中所需要的转发表项是由控制层生成的。The present application can be applied to a software defined network (software defined network, SDN). Please refer to FIG. 1, which is a schematic structural diagram of an SDN. The network structure of SDN is a three-layer model. Among them, the collaborative application layer is mainly a variety of upper-layer applications that reflect user intentions. Such applications are called collaborative layer applications. Typical applications include operation support system (OSS, OSS). )Wait. The control layer is the control center of the system, the controller is responsible for the generation of the internal switching paths and border service routes of the network, and is responsible for processing network state change events. The forwarding layer is mainly composed of network devices to form a basic forwarding network. This layer is responsible for forwarding user data. The forwarding entries required in the forwarding process are generated by the control layer.
在SDN中，网元的控制平面在控制器上，负责协议计算，产生流表，而转发平面只在网络设备上。网络设备通过控制器集中管理和下发流表，这样就不需要对网络设备进行逐一操作，只需要对控制器进行配置即可。第三方应用只需要通过控制器提供的开放接口，通过编程方式定义一个新的网络功能，然后在控制器上运行即可。In SDN, the control plane of the network element is on the controller, which is responsible for protocol calculation and generation of flow tables, while the forwarding plane is only on the network device. The network device centrally manages and delivers the flow table through the controller, so that there is no need to operate the network devices one by one, only the controller needs to be configured. Third-party applications only need to define a new network function programmatically through the open interface provided by the controller, and then run on the controller.
需要说明的是，上述Netconf协议中客户端相当于SDN场景中的控制器，上述Netconf协议中服务端相当于SDN场景中的网络设备。本申请统一采用客户端和服务端的称谓进行描述。另外，除了SDN场景外，本申请也可以在基于上述Netconf协议的其他网络场景中应用，具体此处不做限定。It should be noted that the client in the above Netconf protocol is equivalent to the controller in the SDN scenario, and the server in the above Netconf protocol is equivalent to the network device in the SDN scenario. This application uniformly uses the appellations of the client and the server for description. In addition, in addition to the SDN scenario, the present application can also be applied in other network scenarios based on the above-mentioned Netconf protocol, which is not specifically limited here.
在SDN场景中，客户端可能会对接多个服务端，客户端与服务端之间的交互除了hello报文协商外，客户端还需要根据服务端的厂商、版本以及类型等设备标识进行驱动选择，以使得客户端可以安装与不同服务端所分别对应的驱动，在驱动安装成功后即建立了双方之间的通信通道，客户端再进一步通过通信通道向对应的服务端发送配置信息。具体的，客户端可以通过向服务端发送查询报文的方式获取服务端的设备标识，那么客户端与服务端之间建立通信通道需要进行包括hello报文以及查询报文的多次交互，效率较低。In the SDN scenario, the client may connect to multiple servers. In addition to the hello packet negotiation, the client also needs to select the driver according to the server's manufacturer, version, and type and other device identifiers. This enables the client to install drivers corresponding to different servers. After the driver is installed successfully, a communication channel is established between the two parties, and the client further sends configuration information to the corresponding server through the communication channel. Specifically, the client can obtain the device identifier of the server by sending a query message to the server, then establishing a communication channel between the client and the server requires multiple interactions including hello messages and query messages, which is more efficient. Low.
本申请的整体思路是在hello报文协商阶段客户端即可获取服务端的设备标识，无需再进行额外的交互客户端就可以完成设备驱动的选择及安装，缩短了客户端与服务端之间建立通信通道所需要的时间，提高了连接效率。The overall idea of this application is that the client can obtain the device identifier of the server in the hello message negotiation stage, and the selection and installation of the device driver can be completed without any additional interaction on the client, which shortens the establishment between the client and the server. The time required for the communication channel improves the connection efficiency.
下面对本申请实施例进行详细的介绍：The embodiments of the present application are described in detail below:
请参阅图2，图2为本申请基于Netconf协议的数据传输方法的一个实施例示意图。在该示例中，基于Netconf协议的数据传输方法包括如下步骤。Please refer to FIG. 2 , which is a schematic diagram of an embodiment of a data transmission method based on the Netconf protocol of the present application. In this example, the data transmission method based on the Netconf protocol includes the following steps.
201、客户端向服务端发送第二hello报文。201. The client sends a second hello packet to the server.
本实施例中，客户端为了与服务端建立会话需要与服务端交换各自的能力信息集合，那么客户端可以向服务端发送第二hello报文，其中，第二hello报文包括客户端的第二能力信息集合。In this embodiment, in order to establish a session with the server, the client needs to exchange respective sets of capability information with the server, and then the client may send a second hello packet to the server, where the second hello packet includes the second hello packet of the client. A collection of capability information.
需要说明的是，客户端与服务端之间的会话承载于SSH协议之上，因此在客户端与服务端进行hello报文交互之前，客户端还需要先发起与服务端之间的SSH连接。It should be noted that the session between the client and the server is carried over the SSH protocol. Therefore, before the client and the server exchange hello packets, the client also needs to initiate an SSH connection with the server.
202、服务端向客户端发送第一hello报文。202. The server sends a first hello packet to the client.
本实施例中，在服务端收到客户端发送的第二hello报文后，服务端进一步向客户端发送第一hello报文，以此完成客户端与服务端之间的hello报文协商，客户端可以通过hello报文协商发现服务端的功能，并使用由这些能力信息集合定义的操作，参数和内容。In this embodiment, after the server receives the second hello packet sent by the client, the server further sends the first hello packet to the client, so as to complete the hello packet negotiation between the client and the server, The client can negotiate and discover the capabilities of the server through hello packets, and use the operations, parameters and content defined by these capability information sets.
请参阅图3所示的第一hello报文的结构示意图，第一hello报文包括安全传输层协议(例如SSH)、消息标识(例如hello)以及净荷，其中，净荷中除了包含服务端的第一能力信息集合外，还包括服务端的设备标识。该服务端的设备标识可以包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。需要说明的是，在实际应用中，该服务端的设备标识包括但不限于上述举例的内容。Please refer to the schematic structural diagram of the first hello packet shown in FIG. 3. The first hello packet includes a transport layer security protocol (such as SSH), a message identifier (such as hello), and a payload. In addition to the first capability information set, the device identifier of the server is also included. The device identifier of the server may include at least one of a device type, a device manufacturer, a device version, and a device model. It should be noted that, in practical applications, the device identifier of the server includes, but is not limited to, the above examples.
可选的，第一hello报文中还可以包括会话标识(session-id)，即服务端可以为本次会话分配一个会话标识，用于唯一标识该会话。Optionally, the first hello packet may further include a session ID (session-id), that is, the server may allocate a session ID for this session to uniquely identify the session.
需要说明的是，上述第二hello报文以及第一hello报文可以采用XML的编码格式，用文本表示复杂的层次化数据，既支持使用传统的文本编译工具，也支持使用XML专用的编辑工具读取、保存和操作配置数据。It should be noted that, the above-mentioned second hello message and first hello message can be encoded in XML, and the complex hierarchical data can be represented by text, which supports the use of both traditional text compilation tools and XML-specific editing tools. Read, save and manipulate configuration data.
下面列举一种第一hello报文的净荷中内容的具体形式。A specific form of the content in the payload of the first hello packet is listed below.
</hello></hello>
其中，<capabilities>的标签表示服务端的第一能力信息集合，<session-id>的标签表示本次会话的会话标识，<system-identifiers>的标签标识服务端的设备标识，进一步在该<system-identifiers>标签下包括有<device-type>表示设备类型(例如OLT)、<version>表示设备版本(例如Release1.0.0)、<vendor>表示设备厂商(例如Huawei)以及<model>表示设备模型(例如MA5800)。Among them, the tag of <capabilities> represents the first capability information set of the server, the tag of <session-id> represents the session identifier of this session, the tag of <system-identifiers> represents the device identifier of the server, and further in the <system-identifiers> The identifiers> tag includes <device-type> for device type (such as OLT), <version> for device version (such as Release1.0.0), <vendor> for device manufacturer (such as Huawei) and <model> for device model ( such as MA5800).
需要说明的是，上述<system-identifiers>的标签名称只是一种示例，在实际应用中也可以采用其他的标签名称表示服务端的设备标识，具体此处不做限定。另外，对于设备标识的设置方式，除了采用上述的标签下再设置子标签的方式外，还可以直接将各设备标识平铺设置，不再设置类似<system-identifiers>的总标签，具体可以如下所示：It should be noted that the tag name of the above <system-identifiers> is only an example, and other tag names may also be used to represent the device identifier of the server in practical applications, which is not specifically limited here. In addition, for the setting method of device identification, in addition to the above method of setting sub-tags under the label, you can also directly set each device identification tile, and no longer set the general label similar to <system-identifiers>, the details can be as follows shown:
203、客户端根据服务端的设备标识安装与服务端对应的设备驱动。203. The client installs a device driver corresponding to the server according to the device identifier of the server.
本实施例中，客户端为了与服务端建立通信通道需要安装与服务端对应的驱动，在驱动安装成功后才能通过驱动接口(通信通道)向服务端发送配置信息。因此，客户端收到服务端的设备标识后，可以根据设备标识确定与服务端对应的设备驱动。In this embodiment, the client needs to install a driver corresponding to the server in order to establish a communication channel with the server, and can send configuration information to the server through the driver interface (communication channel) after the driver is installed successfully. Therefore, after receiving the device identifier of the server, the client can determine the device driver corresponding to the server according to the device identifier.
具体的，客户端本地可以存储有多个服务端所分别对应的设备驱动集合，并且每个设备驱动都有与之对应的设备标识，例如，设备标识A对应设备驱动A、设备标识B对应设备驱动B等等。那么客户端可以根据收到的服务端的设备标识从设备驱动集合中选择出与该设备标识对应的设备驱动，下一步客户端即可安装该设备驱动。Specifically, the client can locally store device driver sets corresponding to multiple servers, and each device driver has a corresponding device identifier. For example, device identifier A corresponds to device driver A, and device identifier B corresponds to device Drive B and so on. Then the client can select a device driver corresponding to the device identifier from the device driver set according to the received device identifier of the server, and the client can install the device driver in the next step.
需要说明的是，上述客户端选择并安装设备驱动的方式只是一种示例，在实际应用中也可以有其他的实施方式，例如，客户端收到服务端的设备标识后可以从专门用于存储设备驱动的服务器上下载与该设备标识对应的设备驱动，并进一步完成该设备驱动的安装。具体此处不做限定。It should be noted that the above-mentioned method for the client to select and install the device driver is just an example, and other implementations are also possible in practical applications. The device driver corresponding to the device identifier is downloaded from the driver server, and the installation of the device driver is further completed. There is no specific limitation here.
需要说明的是，除了上述所描述的设备驱动外，客户端还可以根据服务端的设备标识安装与该服务端对应的设备适配器(device adaptor)。It should be noted that, in addition to the device driver described above, the client can also install a device adaptor corresponding to the server according to the device identifier of the server.
本申请实施例中，客户端向服务端发送携带客户端的第二能力信息集合的第二hello报文，之后客户端接收服务端发送的第一hello报文，其中，第一hello报文中包括服务端的第一能力信息集合以及服务端的设备标识，进而客户端根据该服务端的设备标识安装与服务端对应的设备驱动。通过上述描述，客户端在与服务端进行hello报文协商的过程中即可获取服务端的设备标识，无需再进行额外的交互客户端就可以完成设备驱动的选择及安装，缩短了客户端与服务端建立通信通道所需要的时间，提高了连接效率。In this embodiment of the present application, the client sends a second hello packet that carries the second capability information set of the client to the server, and then the client receives the first hello packet sent by the server, where the first hello packet includes The first capability information set of the server and the device identifier of the server, and then the client installs a device driver corresponding to the server according to the device identifier of the server. According to the above description, the client can obtain the device identifier of the server during the hello message negotiation process with the server, and the selection and installation of the device driver can be completed without additional interaction with the client, which shortens the time between the client and the service. The time required for the terminal to establish a communication channel is improved, and the connection efficiency is improved.
可选的，在上述步骤201中客户端向服务端发送的第二hello报文中也可以携带客户端自身的设备标识。下面请参阅图4，图4为本申请基于Netconf协议的数据传输方法的另一个实施例示意图。在该示例中，基于Netconf协议的数据传输方法包括如下步骤。Optionally, the second hello packet sent by the client to the server in the foregoing step 201 may also carry the device identifier of the client itself. Please refer to FIG. 4 below. FIG. 4 is a schematic diagram of another embodiment of the data transmission method based on the Netconf protocol of the present application. In this example, the data transmission method based on the Netconf protocol includes the following steps.
401、客户端向服务端发送第二hello报文。401. The client sends a second hello packet to the server.
本实施例中，客户端向服务端发送的第二hello报文中除了携带有客户端的第二能力信息集合外还携带有客户端的设备标识。需要说明的是，该客户端的设备标识与上述服务端的设备标识类似，也可以包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。另外，该第二hello报文的结构以及其中净荷的具体形式与图2所示实施例中步骤202的相关描述类似，具体此处不再赘述。In this embodiment, the second hello packet sent by the client to the server carries the device identifier of the client in addition to the second capability information set of the client. It should be noted that the device identifier of the client is similar to the device identifier of the server, and may also include at least one of a device type, a device manufacturer, a device version, and a device model. In addition, the structure of the second hello packet and the specific form of the payload therein are similar to the related description of step 202 in the embodiment shown in FIG. 2 , and details are not repeated here.
402、服务端根据客户端的设备标识判断是否接受hello报文协商，若否，则执行步骤403，若是，则执行步骤404。402. The server determines whether to accept the hello message negotiation according to the device identifier of the client, and if not, executes step 403, and if so, executes step 404.
本实施例中，服务端收到客户端发送的第二hello报文后，可以根据第二hello报文中携带的客户端的设备标识来判断是否接受客户端发起的hello报文协商。例如，在某些场景下，服务端A只能接受客户端A发起的hello报文协商，而不能接受诸如客户端B等其他客户端发起的hello报文协商，那么服务端本地可以存储有客户端A的设备标识，进一步服务端核对收到的hello报文中携带的设备标识以及本地存储的设备标识，若核对成功则接受该hello报文协商，若核对失败则拒绝该hello报文协商。In this embodiment, after receiving the second hello packet sent by the client, the server can determine whether to accept the hello packet negotiation initiated by the client according to the device identifier of the client carried in the second hello packet. For example, in some scenarios, server A can only accept hello message negotiation initiated by client A, but cannot accept hello message negotiation initiated by other clients such as client B, then the server can store the client The device identification of terminal A, and the server further checks the device identification carried in the received hello packet and the device identification stored locally. If the verification is successful, the hello packet negotiation is accepted, and if the verification fails, the hello packet negotiation is rejected.
403、若服务端拒绝该hello报文协商，则服务端向客户端发送拒绝响应。403. If the server rejects the hello packet negotiation, the server sends a rejection response to the client.
404、若服务端接受该hello报文协商，则服务端向客户端发送携带第一能力信息集合以及服务端的设备标识的第一hello报文。404. If the server accepts the hello packet negotiation, the server sends to the client a first hello packet that carries the first capability information set and the device identifier of the server.
405、客户端根据服务端的设备标识安装与服务端对应的设备驱动。405. The client installs a device driver corresponding to the server according to the device identifier of the server.
本实施例中，步骤404-405与图2所示实施例中的步骤202-203类似，具体此处不再赘述。In this embodiment, steps 404 to 405 are similar to steps 202 to 203 in the embodiment shown in FIG. 2 , and details are not repeated here.
上面对本申请实施例中基于Netconf协议的数据传输方法进行了描述，下面对本申请实施例中基于Netconf协议的客户端进行介绍：The data transmission method based on the Netconf protocol in the embodiment of the present application has been described above, and the client based on the Netconf protocol in the embodiment of the present application is introduced below:
请参阅图5，本申请实施例中基于Netconf协议的客户端的一个实施例包括：Referring to FIG. 5, an embodiment of the client based on the Netconf protocol in the embodiment of the present application includes:
发送单元501、用于向服务端发送第二hello报文，第二hello报文包括客户端的第二能力信息集合；A sending
接收单元502、用于接收服务端发送的第一hello报文，第一hello报文包括服务端的第一能力信息集合以及服务端的设备标识；A receiving
安装单元503、用于根据服务端的设备标识安装与服务端对应的设备驱动。The
可选的，服务端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, the device identifier of the server includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选的，安装单元503具体用于：Optionally, the
从预置的设备驱动集合中查找与服务端的设备标识对应的设备驱动；Find the device driver corresponding to the device ID of the server from the preset device driver set;
安装设备驱动。Install the device driver.
可选的，第二hello报文还包括客户端的设备标识，客户端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, the second hello packet further includes a device identifier of the client, and the device identifier of the client includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选的，第一hello报文还包括会话标识，会话标识用于标识客户端与服务端之间建立的会话。Optionally, the first hello packet further includes a session identifier, where the session identifier is used to identify a session established between the client and the server.
本申请实施例中，发送单元501向服务端发送携带客户端的第二能力信息集合的第二hello报文，接收单元502接收服务端发送的第一hello报文，其中，第一hello报文中包括服务端的第一能力信息集合以及服务端的设备标识，进而安装单元503根据该服务端的设备标识安装与服务端对应的设备驱动。通过上述描述，客户端在与服务端进行hello报文协商的过程中即可获取服务端的设备标识，无需再进行额外的交互客户端就可以完成设备驱动的选择及安装，缩短了客户端与服务端建立通信通道所需要的时间，提高了连接效率。In the embodiment of the present application, the sending
下面对本申请实施例中基于Netconf协议的服务端进行介绍：The following describes the server based on the Netconf protocol in the embodiment of the present application:
请参阅图6，本申请实施例中基于Netconf协议的服务端的一个实施例包括：Referring to FIG. 6, an embodiment of the server based on the Netconf protocol in the embodiment of the present application includes:
接收单元601，用于接收客户端发送的第二hello报文，第二hello报文包括客户端的第一能力集合；A receiving
发送单元602，用于向客户端发送第一hello报文，以使得客户端根据服务端的设备标识安装与服务端对应的设备驱动，第一hello报文包括服务端的第一能力信息集合以及服务端的设备标识。The sending
可选的，服务端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, the device identifier of the server includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选的，第二hello报文还包括客户端的设备标识，客户端的设备标识包括设备类型、设备厂商、设备版本以及设备模型中的至少一项。Optionally, the second hello packet further includes a device identifier of the client, and the device identifier of the client includes at least one of a device type, a device manufacturer, a device version, and a device model.
可选的，第一hello报文还包括会话标识，会话标识用于标识客户端与服务端之间建立的会话。Optionally, the first hello packet further includes a session identifier, where the session identifier is used to identify a session established between the client and the server.
上面从模块化功能实体的角度对本申请实施例中的客户端以服务端进行了描述，下面从硬件处理的角度对本申请施例中的客户端以及服务端进行描述：The client in the embodiment of the present application is described above as a server from the perspective of a modular functional entity, and the client and the server in the embodiment of the present application are described below from the perspective of hardware processing:
请参阅图7，本申请中客户端包括一个或多个处理器701、存储器702及通信接口703，其中，处理器701、存储器702及通信接口703之间通过总线互相连接。Referring to FIG. 7 , in the present application, the client includes one or
存储器702可以是短暂存储或持久存储，用于存储相关的指令及数据，通信接口703用于接收和发送数据。更进一步地，处理器701可以配置为与存储器702通信，执行存储器702中的一系列指令操作。The
具体的，该客户端可以用于执行图2以及图4所示实施例中客户端所执行的全部或部分动作。Specifically, the client can be used to perform all or part of the actions performed by the client in the embodiments shown in FIG. 2 and FIG. 4 .
请参阅图8，本申请中服务端包括一个或多个处理器801、存储器802及通信接口803，其中，处理器801、存储器802及通信接口803之间通过总线互相连接。Please refer to FIG. 8 , in this application, the server includes one or
存储器802可以是短暂存储或持久存储，用于存储相关的指令及数据，通信接口803用于接收和发送数据。更进一步地，处理器801可以配置为与存储器802通信，执行存储器802中的一系列指令操作。The
具体的，该服务端可以用于执行图2以及图4所示实施例中服务端所执行的全部或部分动作。Specifically, the server can be used to perform all or part of the actions performed by the server in the embodiments shown in FIG. 2 and FIG. 4 .
应理解，本申请实施例中提及的处理器可以是中央处理单元(CentralProcessing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital SignalProcessor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuits) Integrated Circuit, ASIC), off-the-shelf Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double DataRate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。It should also be understood that the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be 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 RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double DataRate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) And direct memory bus random access memory (Direct Rambus RAM, DR RAM).
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, the memory (storage module) is integrated in the processor.
属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, 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 may be implemented in the form of software functional units.
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，read-onlymemory)、随机存取存储器(RAM，random access memory)、磁碟或者光盘等各种可以存储程序代码的介质。The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), magnetic disk or optical disk and other media that can store program codes.
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: The technical solutions described in the embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application.
Claims (27)
Translated fromChinesePriority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111511027.3ACN114363306A (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111511027.3ACN114363306A (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
| CN201910618734.9ACN112217845B (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910618734.9ADivisionCN112217845B (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114363306Atrue CN114363306A (en) | 2022-04-15 |
Family
ID=74048349
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111511027.3APendingCN114363306A (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
| CN201910618734.9AActiveCN112217845B (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910618734.9AActiveCN112217845B (en) | 2019-07-09 | 2019-07-09 | Data transmission method based on Netconf protocol and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114363306A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115632947A (en)* | 2022-10-26 | 2023-01-20 | 新华三信息安全技术有限公司 | Configuration issuing method and device |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113141390B (en)* | 2021-03-11 | 2022-05-27 | 新华三技术有限公司合肥分公司 | Netconf channel management method and device |
| CN114024998B (en)* | 2021-11-11 | 2023-05-23 | 瑞斯康达科技发展股份有限公司 | Method and device for supporting multiple sessions based on netconf protocol |
| CN115622955B (en)* | 2022-10-09 | 2024-11-26 | 重庆奥普泰通信技术有限公司 | Differentiated services code point configuration method, device, equipment and medium |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060174103A1 (en)* | 2004-09-16 | 2006-08-03 | Nokia Corporation | System and method for integrating PKI and XML-based security mechanisms in SyncML |
| US11336511B2 (en)* | 2006-09-25 | 2022-05-17 | Remot3.It, Inc. | Managing network connected devices |
| US20090089408A1 (en)* | 2007-09-28 | 2009-04-02 | Alcatel Lucent | XML Router and method of XML Router Network Overlay Topology Creation |
| CN101296124B (en)* | 2008-06-27 | 2012-04-04 | 华为技术有限公司 | Method for acquiring equipment information |
| CN105281940B (en)* | 2014-07-18 | 2020-08-21 | 南京中兴软件有限责任公司 | Method, equipment and system for HELLO message interaction based on NETCONF protocol |
| CN107222321B (en)* | 2016-03-21 | 2020-08-14 | 华为技术有限公司 | Configuration message sending method and device |
| CN107306202B (en)* | 2016-04-25 | 2020-09-04 | 华为技术有限公司 | A network management method, server, client and system |
| CN109413123A (en)* | 2017-08-16 | 2019-03-01 | 华为技术有限公司 | Session keeping method and relevant device |
| CN109936505B (en)* | 2017-12-15 | 2021-06-22 | 上海诺基亚贝尔股份有限公司 | Method and apparatus in data-centric software-defined networks |
| CN109151095B (en)* | 2018-11-01 | 2021-03-19 | 联想(北京)有限公司 | Method and apparatus for network communication |
- 2019
- 2019-07-09CNCN202111511027.3Apatent/CN114363306A/enactivePending
- 2019-07-09CNCN201910618734.9Apatent/CN112217845B/enactiveActive
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115632947A (en)* | 2022-10-26 | 2023-01-20 | 新华三信息安全技术有限公司 | Configuration issuing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112217845A (en) | 2021-01-12 |
| CN112217845B (en) | 2022-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111278031B (en) | PDU type setting method, UE policy setting method, entity and storage medium | |
| CN114363306A (en) | Data transmission method based on Netconf protocol and related equipment | |
| CN112020844B (en) | Systems, functions, and interfaces for the control and management of interconnected multi-domain network shards | |
| CN111294399B (en) | A data transmission method and device | |
| CN109995713A (en) | Service processing method and relevant device in a kind of micro services frame | |
| CN109614147B (en) | A PHY register reading and writing method and device | |
| CN114827241A (en) | Cross-platform deployment method and system | |
| CN104883266A (en) | Network configuration accessing method and device thereof | |
| CN111865662B (en) | Network equipment configuration method and system | |
| WO2021063129A1 (en) | Core network capability calling method and system | |
| US12323293B2 (en) | Method, apparatus, and system for sending control request based on key value configuration | |
| CN113556359A (en) | A communication protocol conversion method, device, system and gateway device | |
| JP4896532B2 (en) | Communication channel model | |
| CN115486038B (en) | Internet of things configuration method, internet of things configuration device, computer equipment and storage medium | |
| CN115550377B (en) | NVMF (network video and frequency) storage cluster node interconnection method, device, equipment and medium | |
| WO2018036521A1 (en) | Resource adjustment method, apparatus, and system | |
| CN110771117B (en) | A Session Layer Communication Using ID-Oriented Networks | |
| EP2466814B1 (en) | Method, remote access server and system for configuring quality of service | |
| WO2022067509A1 (en) | Device upgrade control method and apparatus, and computer device and storage medium | |
| CN115442913B (en) | Protocol access method, communication method, development equipment, gateway and storage medium | |
| CN118301787B (en) | 5GLAN adaptive networking method, device, terminal equipment and storage medium | |
| CN112804144B (en) | An information configuration method and network device | |
| CN114979079B (en) | Information processing method, information processing device, related equipment and storage medium | |
| CN115766587B (en) | Load balancing implementation method, device, equipment and medium based on source tracing gateway | |
| CN110493038B (en) | A communication model optimization method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |