WO2016082574A1 - 报文的接收处理、发送处理方法及装置 - Google Patents

报文的接收处理、发送处理方法及装置 Download PDF

Info

Publication number
WO2016082574A1
WO2016082574A1 PCT/CN2015/086044 CN2015086044W WO2016082574A1 WO 2016082574 A1 WO2016082574 A1 WO 2016082574A1 CN 2015086044 W CN2015086044 W CN 2015086044W WO 2016082574 A1 WO2016082574 A1 WO 2016082574A1
Authority
WO
WIPO (PCT)
Prior art keywords
vendor attribute
vendor
attribute
packet
correspondence
Prior art date
Application number
PCT/CN2015/086044
Other languages
English (en)
French (fr)
Inventor
靳康
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016082574A1 publication Critical patent/WO2016082574A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention relates to the field of communications, and in particular to a method and a device for receiving and processing a message.
  • the Remote Authentication Dial In User Service is a type of network application protocol for authentication, authorization, and accounting (AAA). It is used for authentication, authorization, and accounting. Features. This protocol enables remote control of user access.
  • the RADIUS protocol stipulates that different vendors' devices can define specific vendor attributes. Therefore, the RADIUS server must support the vendor attributes of all connected devices. When adding new vendors' devices to the network, how can the RADIUS server be convenient and new? The vendor attribute is processed without the need for the device to make changes. The existing technology does not give a specific implementation.
  • an embodiment of the present invention provides a method and a device for receiving and processing a message.
  • a method for receiving a message comprising: determining whether a first vendor attribute of a received Internet Protocol IP packet is the same as a locally stored second vendor attribute; If yes, the corresponding relationship between the first vendor attribute and the second vendor attribute is obtained; and the first vendor attribute in the IP packet is modified according to the corresponding relationship.
  • modifying the first vendor attribute in the IP packet according to the corresponding relationship comprises: converting the first vendor attribute to a second vendor attribute according to the correspondence.
  • the method before determining whether the first vendor attribute of the received Internet Protocol IP packet is the same as the locally stored second vendor attribute, the method further includes: parsing the received IP packet; determining the first according to the parsing result Whether a vendor attribute is the same as the second vendor attribute.
  • the corresponding relationship is configured by: receiving an input operation instruction; configuring the correspondence according to the operation instruction.
  • a method for processing a packet includes: Determining whether the first vendor attribute in the Internet Protocol IP packet to be sent is the same as the second vendor attribute of the destination end indicated by the IP packet;
  • modifying the first vendor attribute in the IP packet according to the corresponding relationship comprises: converting the first vendor attribute to a second vendor attribute according to the correspondence.
  • a packet processing apparatus includes: a determining module, configured to determine that the first vendor attribute of the Internet Protocol IP packet is received and the locally stored And the acquiring module is configured to: obtain, when the first vendor attribute is different from the second vendor attribute, obtain a pre-configured correspondence between the first vendor attribute and the second vendor attribute; And the module is configured to modify the first vendor attribute in the IP packet according to the correspondence.
  • the modifying module is configured to convert the first vendor attribute into a second vendor attribute according to the correspondence.
  • a packet processing apparatus includes: a determining module, configured to determine a first vendor attribute in the Internet Protocol IP packet to be sent, and the Whether the second vendor attribute of the destination end of the IP packet is the same; the obtaining module is configured to acquire the pre-configured first vendor attribute and the foregoing when the first vendor attribute is different from the second vendor attribute Corresponding relationship of the second vendor attribute; the modifying module is configured to modify the first vendor attribute in the IP packet according to the corresponding relationship; and the sending module is configured to send the modified IP packet to the destination end.
  • the modifying module is configured to convert the first vendor attribute into a second vendor attribute according to the correspondence.
  • the related technology is solved by configuring the corresponding relationship between the new vendor attribute and the vendor attribute of other used devices, converting the unknown vendor attribute into a known vendor attribute, and then processing the technical means.
  • a device with a new vendor attribute is added to the network, the other devices in the network cannot be compatible, and the problem of device compatibility in the network is better.
  • FIG. 1 is a flowchart of a method for receiving a message according to an embodiment of the present invention
  • FIG. 2 is a structural block diagram of a message receiving and processing apparatus according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for sending a message according to an embodiment of the present invention
  • FIG. 4 is a structural block diagram of a message transmission processing apparatus according to an embodiment of the present invention.
  • FIG. 5 is a block diagram of a network architecture in accordance with a preferred embodiment of the present invention.
  • FIG. 6 is a flowchart of processing for receiving a RADIUS packet according to a preferred embodiment of the present invention
  • FIG. 7 is a flowchart of a process of transmitting a RADIUS message according to a preferred embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for receiving a message according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps:
  • Step S102 Determine whether the first vendor attribute of the received IP packet is the same as the locally stored second vendor attribute.
  • Step S104 if no, acquiring a pre-configured correspondence between the first vendor attribute and the second vendor attribute;
  • Step S106 Modify the first vendor attribute in the IP packet according to the foregoing correspondence.
  • the pre-configured first vendor attribute and the second vendor attribute are used in the foregoing steps.
  • the compatibility problem caused by different vendor-defined attributes is such that the RADIUS device or the server does not need to make any hardware or software changes, and the corresponding relationship between different vendor attributes is established through command configuration, that is, the newly added device is solved.
  • the foregoing step S106 may be implemented in multiple manners.
  • the foregoing step S106 may be implemented by converting the first vendor attribute to the second according to the foregoing relationship.
  • the vendor attribute can further process the IP packet according to the converted second vendor attribute.
  • step S102 that is, before determining whether the first vendor attribute of the received Internet Protocol IP packet is the same as the locally stored second vendor attribute, the following process may also be performed: The packet is parsed; and according to the parsing result, it is determined whether the first vendor attribute is the same as the second vendor attribute.
  • the corresponding operation relationship is configured by receiving the input operation instruction; configuring the corresponding relationship (ie, manual input) according to the operation instruction.
  • FIG. 2 is a structural block diagram of a message receiving and processing apparatus according to an embodiment of the present invention. As shown in Figure 2, the device comprises:
  • the determining module 20 is configured to determine whether the first vendor attribute of the received Internet Protocol IP packet is the same as the locally stored second vendor attribute;
  • the obtaining module 22 is connected to the determining module 20, and is configured to obtain a correspondence between the first vendor attribute and the second vendor attribute that are pre-configured when the first vendor attribute is different from the second vendor attribute.
  • the modification module 24 is connected to the acquisition module 22 and configured to modify the first vendor attribute in the IP packet according to the corresponding relationship.
  • the first vendor attribute of the IP packet is different from the locally stored second vendor attribute when receiving the IP packet, the first vendor attribute and the second
  • the corresponding relationship between the vendor attributes modifies the technical means of the first vendor attribute, and solves the problem that the other devices in the network cannot be compatible when the device with the new vendor attribute is added to the network in the related art, and the network (can be RADIUS) protocol is allowed to be overcome.
  • the compatibility problem caused by different vendors' custom attributes is used by different devices.
  • the RADIUS device or server does not need to make any hardware or software changes.
  • the command configuration is used to establish the corresponding relationship between different vendor attributes. The connection between the newly added device and the RADIUS server on the network.
  • a further improvement of the foregoing technical solution in the embodiment of the present invention is that the modifying module 24 is configured to convert the first vendor attribute into a second vendor attribute according to the foregoing correspondence.
  • FIG. 3 is a flowchart of a method for processing a packet according to an embodiment of the present invention, as shown in FIG. The process includes the following steps:
  • Step S302 determining whether the first vendor attribute in the IP packet to be sent is the same as the second vendor attribute of the destination end indicated by the IP packet;
  • Step S304 if no, acquiring a pre-configured correspondence between the first vendor attribute and the second vendor attribute;
  • Step S306 modifying the first vendor attribute in the IP packet according to the corresponding relationship, and sending the modified IP packet to the destination end.
  • the corresponding relationship between the first vendor attribute and the second vendor attribute is configured according to the pre-configured relationship.
  • the technical means of modifying the attributes of the first vendor solves the problem that other devices in the network cannot be compatible when a device with a new vendor attribute is added to the network in the related art, and the network (which may be a RADIUS) protocol allows different devices to use different ones.
  • the compatibility problem caused by the vendor's custom attributes is such that the RADIUS device or the server does not need to make any hardware or software changes.
  • the command configuration and other methods are used to establish the correspondence between different vendor attributes, that is, to solve the new device and the device. Docking problems between network RADIUS servers.
  • the technical solution of the foregoing step S306 may be implemented by converting the foregoing first vendor attribute into a second vendor attribute according to the foregoing correspondence.
  • the mapping between the vendor attribute of the new access device and the vendor attribute of the other device is configured in advance.
  • the new vendor attribute of the packet is converted to other vendor attributes used in the network.
  • the other vendor attributes in the packet are converted to the vendor attributes of the device.
  • the corresponding relationship between the new vendor attribute and the vendor attribute of the used device is configured in advance.
  • the device is converted to the used device through the previously configured correspondence. Vendor attribute; when sending RADIUS packets to the device of the new manufacturer, the other vendor attributes in the message are converted into new vendor attributes;
  • the foregoing technical solution provided by the embodiment of the present invention can provide a registration function for the corresponding relationship of different vendor attributes on the RADIUS device and the device peer to which the RADIUS device is applied.
  • the vendor attribute the vendor attribute corresponding to the new access device
  • the corresponding relationship table is searched, and the vendor attribute that cannot be processed is converted into a vendor attribute that can be processed, so that the original process can be processed.
  • the RADIUS device and the device peer of the application RADIUS register the correspondence between the unprocessable vendor attribute and the vendor attribute that can be processed;
  • Receive process When receiving a RADIUS packet, the packet content is parsed. If there is a vendor attribute that cannot be processed, the corresponding relationship table is searched and converted into a corresponding vendor attribute for processing.
  • Sending process Before sending a RADIUS packet, look up the corresponding relationship table. If there is another vendor attribute, replace the vendor attribute in the original transmission, and then send it out.
  • FIG. 4 is a structural block diagram of a message transmission processing apparatus according to an embodiment of the present invention. As shown in Figure 4, the device comprises:
  • the determining module 40 is configured to determine whether the first vendor attribute in the Internet Protocol IP packet to be sent is the same as the second vendor attribute of the destination end indicated by the IP packet;
  • the obtaining module 42 is connected to the determining module 40, and is configured to acquire a correspondence between the first vendor attribute and the second vendor attribute that are pre-configured when the first vendor attribute is different from the second vendor attribute.
  • the modification module 44 is connected to the obtaining module 42 and configured to modify the first vendor attribute in the IP packet according to the corresponding relationship;
  • the sending module 46 is connected to the modifying module 44 and configured to send the modified IP packet to the destination end.
  • the pre-configured first vendor attribute and the second vendor attribute are used before the IP packet is sent.
  • the corresponding relationship modifies the technical means of the first vendor attribute, and solves the problem that other devices in the network cannot be compatible when the device of the new vendor attribute is added to the network in the related art, and the network (can be RADIUS) protocol is allowed to allow different devices.
  • the compatibility problem caused by the use of different vendor-defined attributes is such that the RADIUS device or server does not need to make any hardware or software changes, and the corresponding relationship between different vendor attributes is established through command configuration, that is, the new join is resolved.
  • the modifying module 44 is configured to convert the first vendor attribute to the second vendor attribute according to the foregoing correspondence.
  • FIG. 5 is a schematic diagram of a network architecture according to a preferred embodiment of the present invention. As shown in FIG. 5, device A and device B are running on an IP network, and the device running on the live network is working normally with the RADIUS server. Device X also needs to be added to the IP network to work with the RADIUS server.
  • FIG. 6 is a flowchart of a process for receiving a RADIUS packet according to a preferred embodiment of the present invention. As shown in FIG. 6, the technical solution and the RADIUS server provided by the preferred embodiment of the present invention are implemented when receiving a RADIUS packet on the new device X. The specific process of working together:
  • Step S602 first, manually register the correspondence between the vendor number (VendorID_X) + attribute number M(M) of the device X and the vendor number (VendorID_A) + attribute number N of the device A on the device X. If there are multiple groups of correspondences, Continue to register;
  • step S604 the RADIUS packet is received, and the attribute number of the Vendor ID_A is N, and the corresponding relationship table is searched in step S602.
  • the attribute numbered N of Vendor ID_A is replaced with the attribute numbered M of VendorID_X according to the search result.
  • Step S606 continuing to process the received RADIUS packet, and repeating step S604 until the processing is completed.
  • FIG. 7 is a flowchart of a process for transmitting a RADIUS packet according to a preferred embodiment of the present invention.
  • the TECH server provides a technical solution provided by the embodiment of the present invention when the RADIUS packet is sent on the new device X.
  • Step S702 first register the device number (VendorID_X) + attribute number M(M) of the device X manually on the device X. Correspondence relationship between the vendor number (VendorID_A) + attribute number N of the device A, if there are multiple groups of correspondences, continue to register;
  • Step S704 before the RADIUS packet is sent, the attribute of the number of the VendorID_X is M, and the corresponding relationship table is searched for in the step S702.
  • the attribute of the number of the VendorID_X is replaced by the attribute of the number of the VendorID_A with the number N. ;
  • Step S706 continuing to process the RADIUS packet, and repeating step S704 until the processing is completed.
  • the embodiment of the present invention achieves the following technical effects: the problem that the other devices in the network cannot be compatible when the device with the new vendor attribute is added to the network in the related art is overcome, and the network (which may be a RADIUS) protocol is overcome. Allows different devices to use the compatibility problems caused by different vendor-defined attributes, so that the RADIUS device or server does not need to make any hardware or software changes, and establish the corresponding relationship between different vendor attributes through command configuration. Solve the problem of docking between the newly added device and the RADIUS server on the network.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明提供了一种报文的接收处理、发送处理方法及装置，其中，所述方法包括：判断接收的互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；如果否，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；根据所述对应关系修改所述IP报文中的第一厂商属性。采用本发明提供的上述技术方案，解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，较好的提高网络中设备兼容性的问题。

Description

报文的接收处理、发送处理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种报文的接收处理、发送处理方法及装置。
背景技术
远程用户拨号认证系统(Remote Authentication Dial In User Service，简称为RADIUS)是一种认证授权计费(Authentication、Authorization、Accounting，简称为AAA)类型的网络应用协议，用于认证、授权和计费等功能。该协议实现了对于用户接入的远程控制。RADIUS协议规定了不同厂商的设备可以定义特定的厂商属性，这样RADIUS服务器必须支持所有对接的设备的厂商属性，当在网络中增加新的厂商的设备时，RADIUS服务器如何能方便快捷的对新的厂商属性进行处理，而不需要设备做出改动现有技术中并没有给出具体的实现方式，同样，新增加厂商的设备如何能与原在网的RADIUS服务器进行对接，能够让原RADIUS服务器处理自身的厂商属性，同时能够接收并正确处理RADIUS服务器下发的厂商属性，而不需要在网的RADIUS服务器做出改动现有技术中也没有给出具体的实施方式。
针对相关技术中，当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，尚未提出有效的解决方案。
发明内容
为了解决上述技术问题，本发明实施例提供了一种报文的接收处理、发送处理方法及装置。
根据本发明实施例的一个方面，提供了一种报文的接收处理方法，所述方法包括：判断接收的互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；如果否，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；根据所述对应关系修改所述IP报文中的第一厂商属性。
优选地，根据所述对应关系修改所述IP报文中的第一厂商属性，包括：根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
优选地，判断接收的互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同之前，还包括：对接收到的所述IP报文进行解析；根据解析结果判断所述第一厂商属性与所述第二厂商属性是否相同。
优选地，通过以下方式配置所述对应关系：接收输入的操作指令；按照该操作指令配置所述对应关系。
根据本发明实施例的另一个方面，还提供了一种报文的发送处理方法，所述方法包括： 判断待发送的互联网协议IP报文中的第一厂商属性与所述IP报文指示的目的端的第二厂商属性是否相同；
如果否，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；
根据所述对应关系修改所述IP报文中的第一厂商属性，并向所述目的端发送修改后的IP报文。
优选地，根据所述对应关系修改所述IP报文中的第一厂商属性，包括：根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
根据本发明实施例的另一个方面，还提供了一种报文的接收处理装置，所述装置包括：判断模块，设置为判断接收到互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；获取模块，设置为在所述第一厂商属性与所述第二厂商属性不同时，获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；修改模块，设置为根据所述对应关系修改所述IP报文中的第一厂商属性。
优选地，所述修改模块，设置为根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
根据本发明实施例的另一个方面，还提供了一种报文的发送处理装置，所述装置包括：判断模块，设置为判断待发送的互联网协议IP报文中的第一厂商属性与所述IP报文指示的目的端的第二厂商属性是否相同；获取模块，设置为在所述第一厂商属性与所述第二厂商属性不同时，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；修改模块，设置为根据所述对应关系修改所述IP报文中的第一厂商属性；发送模块，设置为向所述目的端发送修改后的IP报文。
优选地，所述修改模块，设置为根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
通过本发明实施例，采用通过配置新的厂商属性与其他已使用设备的厂商属性的对应关系，将未知的厂商属性转换为已知的厂商属性，然后再进行处理的技术手段，解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，较好的提高网络中设备兼容性的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的报文的接收处理方法的流程图；
图2为根据本发明实施例的报文的接收处理装置的结构框图；
图3是根据本发明实施例的报文的发送处理方法的流程图；
图4为根据本发明实施例的报文的发送处理装置的结构框图；
图5为根据本发明优选实施例的网络架构释义图；
图6为根据本发明优选实施例的接收RADIUS报文的处理流程图；
图7为根据本发明优选实施例的发送RADIUS报文的处理流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明实施例的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明实施例的目的和其他优点可通过在所写的说明书、权利要求书、以及附图中所特别指出的结构来实现和获得。
为了使本技术领域的人员更好地理解本发明实施例方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
在本实施例中提供了一种报文的接收处理方法，图1是根据本发明实施例的报文的接收处理方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，判断接收的IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；
步骤S104，如果否，则获取预先配置的上述第一厂商属性与上述第二厂商属性的对应关系；
步骤S106；根据上述对应关系修改上述IP报文中的第一厂商属性。
通过上述各个步骤，采用在接收到IP报文时，如果IP报文的第一厂商属性与本地存储的第二厂商属性不同，则按照预先配置的上述第一厂商属性与上述第二厂商属性的对应关系修改第一厂商属性的技术手段，解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，克服网络(可以是RADIUS)协议允许不同设备使用不同的厂商自定义属性带来的兼容性问题，使RADIUS设备或者服务器不需要做任何硬件或者软件上的改动，通过命令配置等方式建立起不同厂商属性之间的对应关系，即解决新加入设备与在网RADIUS服务器之间的对接问题。
可选地，上述步骤S106可以有多种实现方式，在本发明实施例的一个可选示例中，可以通过以下技术方案实现上述步骤S106：根据上述对应关系将上述第一厂商属性转化为第二厂商属性，进而能够根据转换后的第二厂商属性对IP报文进行处理。
需要说明的是，在执行步骤S102之前，即在判断接收的互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同之前，还可以执行以下过程：对接收到的上述IP报文进行解析；根据解析结果判断上述第一厂商属性与上述第二厂商属性是否相同。
在本发明实施例中，通过接收输入的操作指令；按照该操作指令配置所述对应关系(即手动输入)配置上述对应关系。
在本实施例中还提供了一种报文的接收处理装置，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。图2为根据本发明实施例的报文的接收处理装置的结构框图。如图2所示，该装置包括：
判断模块20，设置为判断接收到互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；
获取模块22，与判断模块20连接，设置为在上述第一厂商属性与上述第二厂商属性不同时，获取预先配置的上述第一厂商属性与上述第二厂商属性的对应关系；
修改模块24，与获取模块22连接，设置为根据上述对应关系修改上述IP报文中的第一厂商属性。
通过上述各个模块的综合作用，采用在接收到IP报文时，如果IP报文的第一厂商属性与本地存储的第二厂商属性不同，则按照预先配置的上述第一厂商属性与上述第二厂商属性的对应关系修改第一厂商属性的技术手段，解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，克服网络(可以是RADIUS)协议允许不同设备使用不同的厂商自定义属性带来的兼容性问题，使RADIUS设备或者服务器不需要做任何硬件或者软件上的改动，通过命令配置等方式建立起不同厂商属性之间的对应关系，即解决新加入设备与在网RADIUS服务器之间的对接问题。
本发明实施例对上述技术方案的进一步改进在于，修改模块24，设置为根据上述对应关系将上述第一厂商属性转化为第二厂商属性。
为了完善上述实施例的技术方案，在本实施例中提供了一种报文的发送处理方法，图3是根据本发明实施例的报文的发送处理方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，判断待发送的IP报文中的第一厂商属性与上述IP报文指示的目的端的第二厂商属性是否相同；
步骤S304，如果否，则获取预先配置的上述第一厂商属性与上述第二厂商属性的对应关系；
步骤S306，根据上述对应关系修改上述IP报文中的第一厂商属性，并向上述目的端发送修改后的IP报文。
通过上述各个步骤，采用在发送IP报文前，如果IP报文的第一厂商属性与目的端的第二厂商属性不同，则按照预先配置的上述第一厂商属性与上述第二厂商属性的对应关系修改第一厂商属性的技术手段，解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，克服网络(可以是RADIUS)协议允许不同设备使用不同的厂商自定义属性带来的兼容性问题，使RADIUS设备或者服务器不需要做任何硬件或者软件上的改动，通过命令配置等方式建立起不同厂商属性之间的对应关系，即解决新加入设备与在网RADIUS服务器之间的对接问题。
在本发明实施例的一个可选示例中，可以通过如下技术方案实现上述步骤S306的技术方案根据上述对应关系将上述第一厂商属性转化为第二厂商属性。
综上所述，对于网络中的设备(可以是RADIUS设备)，事先配置新接入设备的厂商属性与其他已使用设备的厂商属性的对应关系，当发送RADIUS报文时，依据对应关系，将报文中的新接入的厂商属性转换为其他在网使用的厂商属性，当接收RADIUS报文时，将报文中的其他厂商属性转换为本设备的厂商属性。
而对于RADIUS服务器：事先配置新的厂商属性与其他已使用设备的厂商属性的对应关系，当接收到的RADIUS报文中存在未知的厂商属性时，通过事先配置的对应关系，转换为已使用设备的厂商属性；当向新厂商的设备发送RADIUS报文时，将报文中的其他厂商属性转换为新的厂商属性；
也就是说，本发明实施例提供的上述技术方案，在应用RADIUS的设备与应用RADIUS的设备对等端的任意一侧，都能够提供对于不同厂商属性对应关系的登记功能，当RADIUS报文中包含无法处理的厂商属性(新接入设备对应的厂商属性)时，查找该对应关系表，将无法处理的厂商属性转换为能够处理的厂商属性，从而可以按原有流程进行处理。
具体而言，在应用RADIUS的设备与应用RADIUS的设备对等端的任意一侧，登记无法处理的厂商属性与能处理的厂商属性的对应关系；
接收过程：当接收到RADIUS报文时，对报文内容进行解析，如果存在无法处理的厂商属性时，则查找对应关系表，将其转换为对应的厂商属性进行处理。
发送过程：在发送RADIUS报文前，查找对应关系表，如果存在对应其他厂商属性，则替换原待发送中的厂商属性，然后再发送出去。
在本实施例中还提供了一种报文的发送处理装置，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。图4为根据本发明实施例的报文的发送处理装置的结构框图。如图4所示，该装置包括：
判断模块40，设置为判断待发送的互联网协议IP报文中的第一厂商属性与上述IP报文指示的目的端的第二厂商属性是否相同；
获取模块42，与判断模块40连接，设置为在上述第一厂商属性与上述第二厂商属性不同时，则获取预先配置的上述第一厂商属性与上述第二厂商属性的对应关系；
修改模块44，与获取模块42连接，设置为根据上述对应关系修改上述IP报文中的第一厂商属性；
发送模块46，与修改模块44连接，设置为向上述目的端发送修改后的IP报文。
通过上述各个模块的综合作用，采用在发送IP报文前，如果IP报文的第一厂商属性与目的端的第二厂商属性不同，则按照预先配置的上述第一厂商属性与上述第二厂商属性的对应关系修改第一厂商属性的技术手段，解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，克服网络(可以是RADIUS)协议允许不同设备使用不同的厂商自定义属性带来的兼容性问题，使RADIUS设备或者服务器不需要做任何硬件或者软件上的改动，通过命令配置等方式建立起不同厂商属性之间的对应关系，即解决新加入设备与在网RADIUS服务器之间的对接问题。
可选地，修改模块44，设置为根据上述对应关系将上述第一厂商属性转化为第二厂商属性。
为了更好的理解上述实施例提供的技术方案，以下结合优选实施例以及附图5-7进行说明：
图5为根据本发明优选实施例的网络架构释义图，如图5所示，设备A和设备B运行在IP网络上，为现网运行的设备，与RADIUS服务器之间是正常工作的，新的设备X也需要加入到IP网络中，与RADIUS服务器进行配合工作。
图6为根据本发明优选实施例的接收RADIUS报文的处理流程图，如图6所示，实现了在新设备X上接收RADIUS报文时采用本发明优选实施例提供的技术方案与RADIUS服务器配合工作的具体流程：
步骤S602，首先手工在设备X上登记设备X的厂商编号(VendorID_X)+属性编号M(M)与设备A的厂商编号(VendorID_A)+属性编号N的对应关系，如果存在多组对应关系，则继续登记；
步骤S604，接收RADIUS报文，报文中存在VendorID_A的编号为N的属性，查找步骤S602中对应关系表，根据查找结果，将VendorID_A的编号为N的属性替换为VendorID_X的编号为M的属性；
步骤S606，继续处理接收的RADIUS报文，重复步骤S604，直到处理完成。
图7为根据本发明优选实施例的发送RADIUS报文的处理流程图，如图7所示，实现了在新设备X上发送RADIUS报文时采用本发明实施例提供的技术方案与RADIUS服务器配合工作的具体流程：
步骤S702，首先手工在设备X上登记设备X的厂商编号(VendorID_X)+属性编号M(M) 与设备A的厂商编号(VendorID_A)+属性编号N的对应关系，如果存在多组对应关系，则继续登记；
步骤S704，发送RADIUS报文之前，报文中存在VendorID_X的编号为M的属性，查找步骤S702中对应关系表，根据查找结果，将VendorID_X的编号为M的属性替换为VendorID_A的编号为N的属性；
步骤S706，继续处理该RADIUS报文，重复步骤S704，直到处理完成。
综上所述，本发明实施例达到了以下技术效果：解决了相关技术中当网络中增加新的厂商属性的设备时，网络中的其他设备无法兼容的问题，克服网络(可以是RADIUS)协议允许不同设备使用不同的厂商自定义属性带来的兼容性问题，使RADIUS设备或者服务器不需要做任何硬件或者软件上的改动，通过命令配置等方式建立起不同厂商属性之间的对应关系，即解决新加入设备与在网RADIUS服务器之间的对接问题。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及优选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的对象在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，解决了相关技术中当网络中增加新的 厂商属性的设备时，网络中的其他设备无法兼容的问题，较好的提高网络中设备兼容性的问题。

Claims (10)

  1. 一种报文的接收处理方法，所述方法包括：
    判断接收的互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；
    如果否，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；
    根据所述对应关系修改所述IP报文中的第一厂商属性。
  2. 根据权利要求1所述的方法，其中，根据所述对应关系修改所述IP报文中的第一厂商属性，包括：
    根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
  3. 根据权利要求1所述的方法，其中，判断接收的互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同之前，还包括：
    对接收到的所述IP报文进行解析；
    根据解析结果判断所述第一厂商属性与所述第二厂商属性是否相同。
  4. 根据权利要求1所述的方法，其中，通过以下方式配置所述对应关系：接收输入的操作指令；按照该操作指令配置所述对应关系。
  5. 一种报文的发送处理方法，所述方法包括：
    判断待发送的互联网协议IP报文中的第一厂商属性与所述IP报文指示的目的端的第二厂商属性是否相同；
    如果否，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；
    根据所述对应关系修改所述IP报文中的第一厂商属性，并向所述目的端发送修改后的IP报文。
  6. 根据权利要求5所述的方法，其中，根据所述对应关系修改所述IP报文中的第一厂商属性，包括：
    根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
  7. 一种报文的接收处理装置，所述装置包括：
    判断模块，设置为判断接收到互联网协议IP报文的第一厂商属性与本地存储的第二厂商属性是否相同；
    获取模块，设置为在所述第一厂商属性与所述第二厂商属性不同时，获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；
    修改模块，设置为根据所述对应关系修改所述IP报文中的第一厂商属性。
  8. 根据权利要求7所述的装置，其中，所述修改模块，设置为根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
  9. 一种报文的发送处理装置，所述装置包括：
    判断模块，设置为判断待发送的互联网协议IP报文中的第一厂商属性与所述IP报文指示的目的端的第二厂商属性是否相同；
    获取模块，设置为在所述第一厂商属性与所述第二厂商属性不同时，则获取预先配置的所述第一厂商属性与所述第二厂商属性的对应关系；
    修改模块，设置为根据所述对应关系修改所述IP报文中的第一厂商属性；
    发送模块，设置为向所述目的端发送修改后的IP报文。
  10. 根据权利要求9所述的装置，其中，所述修改模块，设置为根据所述对应关系将所述第一厂商属性转化为第二厂商属性。
PCT/CN2015/086044 2014-11-24 2015-08-04 报文的接收处理、发送处理方法及装置 WO2016082574A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410682655.1 2014-11-24
CN201410682655.1A CN105704082A (zh) 2014-11-24 2014-11-24 报文的接收处理、发送处理方法及装置

Publications (1)

Publication Number Publication Date
WO2016082574A1 true WO2016082574A1 (zh) 2016-06-02

Family

ID=56073540

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/086044 WO2016082574A1 (zh) 2014-11-24 2015-08-04 报文的接收处理、发送处理方法及装置

Country Status (2)

Country Link
CN (1) CN105704082A (zh)
WO (1) WO2016082574A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605099A (zh) * 2009-07-01 2009-12-16 中兴通讯股份有限公司 一种业务绑定方法及装置
CN101729388A (zh) * 2008-10-22 2010-06-09 华为技术有限公司 一种实现网络地址转换的方法、媒体网关和网络系统
EP2693712A1 (en) * 2012-08-03 2014-02-05 Juniper Networks, Inc. Drop sensitive prefix (bgp path) attribute modification

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101958900B (zh) * 2010-09-27 2014-12-10 中兴通讯股份有限公司 一种服务器处理业务的方法及装置
CN102333070A (zh) * 2011-05-26 2012-01-25 杭州华三通信技术有限公司 一种信息的获取方法和设备
CN102281189B (zh) * 2011-06-28 2015-07-22 杭州华三通信技术有限公司 一种基于第三方设备私有属性的业务实现方法及其装置
US20140214930A1 (en) * 2013-01-25 2014-07-31 Richard Hayman-Joyce Changing settings

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729388A (zh) * 2008-10-22 2010-06-09 华为技术有限公司 一种实现网络地址转换的方法、媒体网关和网络系统
CN101605099A (zh) * 2009-07-01 2009-12-16 中兴通讯股份有限公司 一种业务绑定方法及装置
EP2693712A1 (en) * 2012-08-03 2014-02-05 Juniper Networks, Inc. Drop sensitive prefix (bgp path) attribute modification

Also Published As

Publication number Publication date
CN105704082A (zh) 2016-06-22

Similar Documents

Publication Publication Date Title
CN107592209B (zh) 一种多网卡服务器自动配置ip地址信息的方法和系统
EP2220852B1 (en) Communicating a selection of a potential configuration
JP5711754B2 (ja) スマートクライアントルーティング
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
JP6656612B2 (ja) ネットワークサービス構成方法およびネットワーク管理装置
EP2866389A1 (en) Method and device thereof for automatically finding and configuring virtual network
Juan et al. Multi-master ros systems
WO2015143794A1 (zh) 制作、升级方法及服务器、终端、升级系统和存储介质
TW201706901A (zh) 用戶端登錄伺服器端的鑑別方法、裝置、系統及電子設備
WO2017161965A1 (zh) 一种动态域名系统dns重定向方法、装置及系统
JP2020500374A5 (zh)
WO2016169260A1 (zh) 光接入模块的认证注册方法、装置及系统
WO2016078291A1 (zh) 共享文件服务器的访问方法、装置及系统
WO2016101510A1 (zh) 获取nat信息的方法及bras设备
CN110620706B (zh) 一种参数调整方法和设备
CN105049546A (zh) 一种dhcp服务器为客户端分配ip地址的方法及装置
CN105120454A (zh) 信息传输方法、联网接入方法及相应的终端
CN109788528B (zh) 接入点及其上网业务开通方法和系统
WO2012041029A1 (zh) 一种服务器处理业务的方法及装置
WO2014086236A1 (zh) 通信处理方法、服务器及终端
WO2015058413A1 (zh) 一种数据配置方法及网络管理服务器
CN104468194B (zh) 一种网络设备的兼容方法及转发服务器
WO2016095751A1 (zh) 一种域名解析方法及装置
WO2013159591A1 (zh) 一种区分无线终端的方法及装置
WO2016082574A1 (zh) 报文的接收处理、发送处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15864125

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15864125

Country of ref document: EP

Kind code of ref document: A1