WO2020135574A1 - 报文处理方法、装置、控制面设备和计算机存储介质 - Google Patents

报文处理方法、装置、控制面设备和计算机存储介质 Download PDF

Info

Publication number
WO2020135574A1
WO2020135574A1 PCT/CN2019/128654 CN2019128654W WO2020135574A1 WO 2020135574 A1 WO2020135574 A1 WO 2020135574A1 CN 2019128654 W CN2019128654 W CN 2019128654W WO 2020135574 A1 WO2020135574 A1 WO 2020135574A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
identification information
vbras
vendor
target device
Prior art date
Application number
PCT/CN2019/128654
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 中兴通讯股份有限公司
Priority to EP19902328.4A priority Critical patent/EP3905598B1/en
Priority to US17/271,901 priority patent/US11575592B2/en
Publication of WO2020135574A1 publication Critical patent/WO2020135574A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/287—Remote access server, e.g. BRAS
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • 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/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/18—Protocol analysers

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of message processing of a virtual broadband remote access server, for example, to a message processing method, device, control plane device, and computer storage medium.
  • the virtual broadband remote access server (virtual Broadband Remote Access Server, vBRAS) realizes the traditional broadband remote access by adopting advanced software-defined network (Software Defined Network, SDN) and network function virtualization (Network Function, Virtualization, NFV) technologies Server (Broadband Remote Access Server, BRAS) product transfer control separation;
  • vBRAS can be divided into vBRAS control plane and vBRAS forwarding plane, vBRAS forwarding plane to achieve distributed deployment, and diversified forms, including based on traditional network processors (Network Processor, NP ) Realized hard forwarding plane and virtual forwarding plane based on X86 server;
  • vBRAS control plane centrally controls and manages vBRAS forwarding plane, supports centralized control and management of vBRAS forwarding plane devices produced by different manufacturers, making up for traditional physical broadband remote access The shortage of server products.
  • the embodiments of the present application provide a message processing method, device, control plane device, and computer storage medium, which can be compatible to realize the analysis of data in private formats of different manufacturers.
  • An embodiment of the present application provides a packet processing method, and the method includes:
  • the target device Determine the identification information of the target device according to the first message, select a message parsing plug-in matching the determined identification information of the target device; send the first message to the selected message parsing plug-in, and receive the The parsed data of the selected message parsing plug-in; the parsed data is data obtained by parsing at least one private format data in the first message by the selected message parsing plug-in;
  • An embodiment of the present application also provides a message processing apparatus, including a processor and a memory configured to store a computer program that can be run on the processor; wherein, the processor is configured to run the computer program To execute the packet processing method described in any embodiment of the present application.
  • An embodiment of the present application also provides a packet processing device, including:
  • the receiving module is configured to receive the first message containing at least one private format data
  • the first processing module is configured to determine the identification information of the target device according to the first packet, select a packet parsing plug-in matching the determined identification information of the target device; send the first packet to the selected packet parsing plug-in A message, receiving the parsed data from the selected message analysis plug-in; wherein, the parsed data is performed by the selected message analysis plug-in on at least one private format data in the first message The data obtained after analysis;
  • the second processing module is configured to determine, according to the parsed data, the processing manner of the second message used by the target device to access the website.
  • An embodiment of the present application also provides a control plane device, including the packet processing device described in any embodiment of the present application.
  • An embodiment of the present application also provides a computer storage medium on which a computer program is stored, and when the computer program is executed by a processor, the message processing method described in any embodiment of the present application is implemented.
  • FIG. 1 is a schematic diagram of a network configuration of an entity BRAS and a remote user dial-up authentication service (Remote Authentication Dial-in User Service, RADIUS) server provided by an embodiment of the present application;
  • RADIUS Remote Authentication Dial-in User Service
  • FIG. 2 is a flowchart of a packet processing method provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a system networking compatible with private format data parsing of different manufacturers provided by an embodiment of the present application;
  • FIG. 5 is a schematic diagram of another system networking compatible with data analysis in a private format of different manufacturers provided by an embodiment of the present application;
  • FIG. 6 is a flowchart of another message processing method provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another system networking compatible with data analysis in private formats of different manufacturers provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another system networking compatible with data analysis of private formats of different manufacturers provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another system networking compatible with data analysis in private formats of different manufacturers provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a composition of a packet processing device according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a hardware structure of a packet processing apparatus provided by an embodiment of the present application.
  • the physical BRAS includes the control plane and the forwarding plane.
  • the physical BRAS of each manufacturer can act as a RADIUS client, follow the RADIUS protocol defined by Request (For Comments), and directly communicate with the RADIUS server through the RADIUS server. Authentication, authorization, and accounting for broadband user access.
  • FIG. 1 is a schematic diagram of a network connection between an entity BRAS and a RADIUS server according to an embodiment of the present application. As shown in FIG.
  • BRAS device (vendor A), BRAS device (vendor B), and BRAS device (vendor C) respectively represent 3 Entity BRAS of different manufacturers, BRAS equipment (Vendor A), BRAS equipment (Vendor B) and BRAS equipment (Vendor C) can communicate with the RADIUS service respectively.
  • the RADIUS protocol is extensible, and the No. 26 attribute (Vendor-Specific) attribute is defined in the RADIUS protocol to support the expansion of private attributes of different vendors.
  • the Vendor-Specific attribute includes the vendor-identity (Vendor -Identifier, Vendor-ID) and vendor-defined private sub-attributes, where Vendor-ID represents the vendor ID, and the entity BRAS only parses the private attributes of the Vendor-ID in the Vendor-Specific attribute that matches the device manufacturer’s ID; if Vendor-ID If it does not match the equipment manufacturer's logo, the attribute of unrecognized type is ignored.
  • the control plane and the forwarding plane can be separated.
  • the vBRAS control plane centrally controls and manages vBRAS forwarding plane devices produced by different manufacturers
  • the vBRAS control plane provided by a single manufacturer communicates with the RADIUS server
  • the server returns the problem of private attributes customized by different vendors.
  • vBRAS is already the future development direction of physical BRAS.
  • vBRAS has not yet implemented vBRAS control plane to centrally control and manage vBRAS forwarding plane equipment produced by different manufacturers. The main reason is that the interface standard between vBRAS control plane and vBRAS forwarding plane has not been defined.
  • microservices architecture is to apply It is divided into a series of small services, that is, the miniaturization of services. Each service is so small that it only needs to focus on one thing. It runs in an independent process. The boundaries between services are clear.
  • the microservice architecture uses a lightweight communication mechanism (such as HyperText Transfer Protocol (HTTP)/Representational State Transfer (RESTFUL)) communicate with each other, and achieve a complete application through the cooperation of multiple services, which can meet the needs of business and users.
  • HTTP HyperText Transfer Protocol
  • RESTFUL Real-Representational State Transfer
  • the first embodiment of the present application proposes a message processing method, which can be applied to a control plane device.
  • the control plane device here may be a vBRAS control plane device.
  • FIG. 2 is a flowchart of a message processing method provided by an embodiment of the present application. As shown in FIG. 2, the process may include:
  • Step 2010 Receive a first message containing at least one private format data.
  • the private format data may be private attribute data defined by the manufacturer.
  • a private format data source can send a message containing private format data to the control plane device, and the control plane device can receive the above message from the private format data source.
  • the private format data source sends a private message containing at least one vendor definition. Device for formatting data messages.
  • the private format data source may be an authentication and authorization server.
  • the private format data source may be a RADIUS server or other types of authentication and authorization servers.
  • the control plane device is set to centrally control and manage multiple controlled devices, and communicate with the private format data source in a unified manner.
  • the controlled device no longer communicates with the private format data source.
  • the controlled device may be a forwarding plane device.
  • the vBRAS control plane device can communicate with the RADIUS server through the RADIUS protocol defined by the RFC to complete the authentication, authorization, and accounting processing of broadband user access, and through the communication protocol between the vBRAS control plane and the vBRAS forwarding plane, Centralized control and management of vBRAS forwarding plane equipment.
  • Step 2020 Determine the identification information of the target device according to the first message, select a message parsing plug-in that matches the determined identification information of the target device; send the at least one private format data to the selected message parsing plug-in, and receive Parsed data from the selected message parsing plug-in; the parsed data is obtained by parsing at least one private format data by the selected message parsing plug-in.
  • the target device may be a service processing device provided by different manufacturers.
  • the target device belongs to a controlled device under the control of a vBRAS control plane device, and all target devices may establish a connection with the vBRAS control plane device.
  • the number of target devices that establish a connection with the vBRAS control plane device may be one or more; each target device may report identification information to the vBRAS control plane device through a communication protocol that multiple manufacturers jointly abide by. It also receives the control attributes delivered by the vBRAS control plane device.
  • the target device belongs to the forwarding plane device, for example, the target device is a vBRAS forwarding plane device; as an implementation, the target device may include at least one of the following: BRAS, broadband network gateway (Broadband Network Gateway, BNG), broadband Service Gateway (Broadband Service Gateway, BSG), Service Router (Service Router, SR), Broadband Access Server (Broadband Access Server, BAS), Open Flow Logical Switch (Openflow Logical Switch, referred to as OFLS), Open Flow Switch (Openflow Switch, OFS, wireless access controller (Access Controller, AC), optical line terminal equipment (Optical Line Terminal, OLT), aggregation switch, analog physical broadband access server function that can run on a server that provides computing services software.
  • BNG broadband Network Gateway
  • BSG broadband Service Gateway
  • Service Router Service Router
  • BAS Broadband Access Server
  • OFLS Open Flow Logical Switch
  • OFLS Open Flow Switch
  • OFS Open Flow Switch
  • OFS wireless access controller
  • OLT optical line terminal equipment
  • the identification information of the target device is used to identify the target device.
  • the identification information of the target device may include: category identification information and unique identification information; the category identification information is used to identify the category of the target device, and the unique identification information is used to uniquely identify the target equipment. For different target devices, when different target devices belong to the same category, the category identification information can be the same. In this way, the category identification information can identify the target devices that belong to a unified category.
  • the category identification information is beneficial to the batch deployment of the target devices ;
  • the unique identification information corresponds one-to-one with the target device.
  • the unique identification information facilitates the target device to be upgraded independently and does not affect the normal operation of other devices. That is to say, when a target device is upgraded independently, only the unique identifier corresponding to the target device needs to be changed The information is sufficient, and there is no need to change the identification information of other target devices.
  • identification information can be mixed in a system, that is, in a system composed of multiple target devices, control plane devices, and private format data sources, each target device corresponds to
  • the identification information includes both category identification information and unique identification information.
  • the category identification information includes an identifier (ID) of the manufacturer to which the target device belongs.
  • the unique identification information may include the ID of the target device.
  • the identifier in the first message may be used (Identifier) field value to determine the identification information of the target device.
  • the corresponding broadband user access information can be found according to the above-mentioned Identifier field value; and the identification information of the target device is determined according to the broadband user access information.
  • the corresponding target device and the identification information reported by the found target device can be found based on the broadband user access information, and then the identification information of the target device can be determined.
  • a corresponding message parsing plug-in can be identified by the class identification information.
  • a common Message parsing plug-in when unique identification information is used to identify the target device, the message parsing plug-in corresponds to the target device one-to-one.
  • the message parsing plug-in may be a service module provided by each manufacturer with the capability of parsing private format data.
  • the message parsing plug-in may receive manufacturer-defined private format data sent by the control plane device. It can analyze the identification information of the manufacturer to which the plug-in belongs according to its own message, analyze the private format data that can be recognized by itself, and can return the analysis result to the control plane device.
  • the message sent by the control plane device to the message parsing plug-in may contain the private format data of multiple vendors. Therefore, the message received by one message parsing plug-in may include the private format data of multiple different vendors.
  • the message parsing plug-in receives at least one private format data, and then can analyze the at least one private format data The private format data is parsed to obtain the parsed data; the message parsing plug-in can send the parsed data to the control plane device.
  • control plane device when it receives a message containing private format data of multiple different vendors, it can send a message containing private format data of multiple different vendors to a message parsing plug-in; message parsing
  • the plug-in receives messages containing private format data of multiple different manufacturers, and can filter messages containing private format data of multiple different vendors according to its own identification information, so that it can be analyzed for private format data that can be parsed by itself Analyze, and then, get the parsed data.
  • the signal transmission channel between the message parsing plug-in and the control plane device may be an independently set signal transmission channel.
  • the signal transmission channel between the message parsing plug-in and the control plane device may be an independently set signal transmission channel.
  • the signal transmission channel between the control plane device and the message parsing plug-in, and the channel between the control plane device and the forwarding plane device are integrated deployment channels, that is, the control plane device and the packet.
  • the signal transmission channel between the analysis plug-ins can share the signal transmission channel between the control plane device and the forwarding plane device.
  • the signal transmission channel between the control plane device and the message parsing plug-in, and the signal transmission channel between the control plane device and the forwarding plane device are unified deployment channels.
  • a correspondence relationship between the target device's identification information and the message parsing plug-in identification information needs to be established in advance.
  • the control plane device may select a message parsing plug-in that matches the determined identification information of the target device according to the above correspondence.
  • the message parsing plug-in can report identification information to the control plane device through a communication protocol that multiple manufacturers jointly abide by.
  • a corresponding relationship may be established between the identification information of the corresponding target device and the message analysis plug-in identification information; For example, when the identification information reported by the i-th target device is the same as or matches the identification information reported by the j-th packet analysis plug-in, the identification information of the i-th target device and the identification information of the j-th packet analysis plug-in may be considered correspond.
  • the identification information reported by each target device includes the ID of the vendor of the corresponding target device, or the identification information reported by each target device includes the ID of the vendor of the corresponding target device and the ID of the corresponding target device.
  • the identification information reported by each message analysis plug-in includes the ID of the manufacturer to which the corresponding message analysis plug-in belongs, or the identification information reported by each message analysis plug-in includes the ID and the ID of the manufacturer to which the corresponding message analysis plug-in belongs.
  • the ID of the target device includes the ID of the manufacturer to which the corresponding message analysis plug-in belongs.
  • the above correspondence is updated according to the identification information reported by the newly deployed target device and the identification information reported by the newly deployed packet analysis plug-in.
  • a message parsing plug-in that matches the determined category identification information and unique identification information of the target device it can be determined whether a message parsing plug-in that matches the determined category identification information and unique identification information of the target device can be found; if it can be found The message parsing plug-in that matches the category identification information and unique identification information of the determined target device, then select the found message parsing plug-in as the message parsing plug-in that matches the determined target device identification information. If a message parsing plug-in that matches the determined category identification information and unique identification information of the target device is found, it is determined whether a message parsing plug-in matching the determined target device category identification information can be found.
  • the found message parsing plug-in is selected as the message parsing plug-in matching the determined target device identification information; if it cannot be found.
  • the message parsing plug-in matching the determined category identification information of the target device may ignore the first message.
  • the deployment method of the message parsing plug-in is: deployment independent of the forwarding plane device, for example, the message parsing plug-in is deployed independently in the form of microservices; in another example, The deployment method of the message parsing plug-in is: deploying at the forwarding plane device.
  • Step 2030 Determine, according to the parsed data, the processing manner of the second message used by the target device to access the website.
  • the control plane device may obtain a broadband user according to the parsed data and the analysis result of the first message by the control plane device Authorization information (private data required by the target device), and then, the broadband user authorization information can be sent to the target device, and the target device can determine the processing method of the second message according to the broadband user authorization information.
  • the target device may write the above-mentioned broadband user authorization information into the user forwarding table, and then, may process the message of the broadband user accessing the website according to the user forwarding table.
  • the processing method for the second message used to access the website may be forwarding or other processing methods.
  • control plane device can deliver the broadband user authorization information to the corresponding target device through a communication protocol that multiple manufacturers jointly abide by.
  • steps 2010 to 2030 may be implemented by a processor in the control plane device, and the processor may be an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP) , Digital signal processing device (Digital Signaling Processing Device, DSPD), programmable logic device (Programmable Logic Device, PLD), field programmable gate array (Field Programmable Gate Array, FPGA), central processing unit (Central Processing Unit, CPU) , A controller, a microcontroller, or a microprocessor.
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal Processor
  • DSPD Digital Signaling Processing Device
  • PLD programmable logic device
  • FPGA field programmable gate array
  • CPU Central Processing Unit
  • CPU Central Processing Unit
  • An embodiment of the present application provides a packet processing method, by receiving a first packet containing at least one private format data; determining identification information of a target device according to the first packet, and selecting a target device with the determined A message parsing plug-in with matching identification information; sending the at least one private format data to the selected message parsing plug-in and receiving the parsed data from the selected message parsing plug-in; the parsed data is determined by the selected Is obtained by parsing the at least one private format data by the message parsing plug-in; based on the parsed data, determining the processing method of the second message used by the target device to access the website.
  • the use of a message plug-in can be compatible to realize the analysis of data in private formats from different manufacturers.
  • FIG. 3 is a schematic diagram of a system networking provided by an embodiment of the present application that is compatible with data analysis in private formats of different vendors.
  • the system may include a centralized Control point, target device A, target device B, target device C, parsing plug-in A, parsing plug-in B, parsing plug-in C and private format data source; where the centralized control point is the above vBRAS control plane device, target device A, target device B and target device C are three target devices, and analysis plug-in A, analysis plug-in B, and analysis plug-in C are three different message analysis plug-ins.
  • target device A corresponds to analysis plug-in A, that is, target device A Of the identification information matches the analysis plug-in A;
  • target device B corresponds to the analysis plug-in B, that is, the identification information of the target device B matches the analysis plug-in B;
  • target device C corresponds to the analysis plug-in C, that is, the identification information of the target device C matches Parse plugin C matching.
  • the centralized control point can communicate with the private format data source, target device A, target device B, target device C, parsing plug-in A, parsing plug-in B, and parsing plug-in C, respectively.
  • FIG. 4 is a flowchart of another packet processing method provided by an embodiment of the present application. As shown in FIGS. 3 and 4, the process may include:
  • Step S0010 All target devices and parsing plug-ins connected to the centralized control point report their identification information. For this step, refer to the arrowed lines marked with characters 1a, 1b, 1c, 1d, 1e, and 1f in FIG. 3.
  • Step S0020 The private format data source is triggered to send a message containing multiple private format data to the centralized control point. For this step, refer to the arrowed line marked with the number 2 in FIG. 3.
  • Step S0030 After receiving the message, the centralized control point selects the matching message parsing plug-in according to the identification information of the target device, and sends the message to the selected message parsing plug-in for parsing. For this step, see Figure 3 3 marked lines with arrows.
  • Step S0040 After the message parsing plugin correctly parses the message of interest, the parsing result (parsed data) is returned to the centralized control point. For this step, refer to the arrowed line marked with the number 4 in FIG. 3.
  • Step S0050 After obtaining the analysis result returned by the message parsing plug-in, the centralized control point sends the private data required by the target device to the corresponding through the communication protocol defined by the multiple control companies between the centralized control point and the target device. The target device.
  • the analysis result is private data required by the target device.
  • the centralized control point when the centralized control point receives the private format data defined by different manufacturers, it can correctly parse out the private format data without knowing the private format definition (ie, the private protocol defined by the manufacturer). That is to say, the technical solutions of the embodiments of the present application can be compatible to realize the analysis of data in private formats from different manufacturers.
  • the vBRAS control plane and the forwarding plane can be separated, and the vBRAS control plane can centrally control and manage vBRAS forwarding plane devices produced by different manufacturers. , Correctly parse out the private format data customized by different manufacturers, so that the vBRAS device is compatible with the existing private authorization attributes provided by different manufacturers. For example, when the vBRAS control plane communicates with the RADIUS server, the vBRAS control plane can correctly parse the private format data customized by different vendors and returned by the RADIUS server.
  • the vBRAS forwarding plane equipment manufacturer needs to extend private attributes (private protocol) in order to provide special functions and performance, it is only necessary to independently upgrade the vendor-related vBRAS forwarding plane and the corresponding message parsing plug-in, and install it on the RADIUS server.
  • the vendor-defined private authorization attribute (private protocol) is added to the vBRAS control plane, and the vBRAS control plane and the vBRAS forwarding plane of other vendors are stable.
  • the centralized control point is the vBRAS control plane.
  • the vBRAS control plane Through the OpenFlow protocol defined by the Open Networking Foundation (ONF), the vBRAS control plane centrally controls and manages the vBRAS forwarding plane. It supports the microservices architecture and supports multiple vendors. Provide private extension functions in the form of microservices; through the RESTFUL interface, the vBRAS control plane interfaces with the message parsing plug-in microservices provided by these vendors; the vBRAS control plane and the message parsing plug-in microservices provided by multiple vendors are deployed on the X86 server And the data center virtualization platform built by the switch.
  • OMF Open Networking Foundation
  • the private format data source is a RADIUS server.
  • the RADIUS server sends private extended attributes defined by multiple vendors to the vBRAS control plane; the private extended attributes are The 26th attribute defined by the RADIUS protocol is the Vendor-Specific attribute; each Vendor-Specific attribute in the RADIUS protocol packet contains the vendor identifier Vendor-ID and the private sub-attribute extended by the vendor.
  • IETF Internet Engineering Task Force
  • the message parsing plug-in is a microservice provided by the manufacturer, which supports the identification and parsing of Vendor-Specific attributes related to the vendor. It can receive the Vendor-Specific attribute information sent by the vBRAS control plane through the RESTFUL interface, and parse Vendor-defined Vendor-defined attributes. -Specific attribute, and send the analysis result as a response to the vBRAS control plane.
  • the target device is a vBRAS forwarding plane device that is centrally controlled and managed by the vBRAS control plane.
  • the vBRAS forwarding plane can report its identifier to the vBRAS control plane and receive the authorization issued by the vBRAS control plane. information.
  • the hardware module part includes: X86 server and BRAS equipment.
  • FIG. 5 is a schematic diagram of another system networking compatible with private format data parsing provided by embodiments of the present application.
  • the vBRAS control plane (vendor B) is a control plane device provided by vendor B.
  • the vendor The A parsing plug-in and Vendor C parsing plug-in respectively represent the packet parsing plug-ins provided by Vendor A and Vendor C, and vBRAS forwarding plane 1 (Vendor A) and vBRAS forwarding plane 2 (Vendor A) respectively represent the two vBRAS provided by Vendor A Forwarding plane equipment, vBRAS forwarding plane (vendor B) and vBRAS forwarding plane (vendor C) represent two vBRAS forwarding plane devices provided by vendor B and vendor C, respectively.
  • Vendor B which supports interfacing with the message parsing plug-in microservices provided by other vendors through the RESTFUL interface; in order to be able to interface with the vBRAS control plane provided by Vendor B, the vBRAS forwarding plane equipment of other vendors, in addition to complying with the vBRAS control plane
  • the vBRAS forwarding plane equipment of other vendors in addition to complying with the vBRAS control plane
  • the provided message parsing plug-in can analyze the private format data defined by the RADIUS server and sent to the vBRAS control plane by the manufacturer.
  • vBRAS forwarding plane 1 (vendor A) and vBRAS forwarding plane 2 (vendor A) can share the vendor A resolution plug-in.
  • the vBRAS control plane uses the vendor ID Vendor-ID as the identification information of the target device and the packet analysis plug-in.
  • FIG. 6 is a flowchart of another packet processing method provided by an embodiment of the present application.
  • the vBRAS control plane, The workflow between the RADIUS server, vBRAS forwarding plane, and resolution plug-in is shown in Figure 6.
  • the flow of the message processing method may include:
  • Step 5010 Deploy the vBRAS control plane device, create a new virtual machine or container on the cloud platform in the data center, and start the vBRAS control plane device provided by manufacturer B in the virtual machine or container.
  • Step 5020 Deploy the vendor A parsing plug-in, create a new virtual machine or container on the cloud platform in the data center, and start the vendor A parsing plug-in in the virtual machine or container.
  • Step 5030 Deploy the vendor C parsing plug-in, create a new virtual machine or container on the cloud platform in the data center, and start the vendor C parsing plug-in in the virtual machine or container.
  • Step 5040 Configure the connection between the vBRAS control plane device and the RADIUS server, including configuring the Internet Protocol (IP) address and RADIUS protocol port number of the RADIUS server.
  • IP Internet Protocol
  • Step 5050 Configure all vBRAS forwarding plane devices of Vendor A, Vendor B, and Vendor C to connect to the vBRAS control plane device, including establishing and extending a virtual extended local area network (VxLAN) tunnel from the vBRAS forwarding plane to the vBRAS control plane. OpenFlow connection from vBRAS forwarding plane to vBRAS control plane.
  • VxLAN virtual extended local area network
  • Step 5060 Configure the vendor A parsing plug-in to register with the vBRAS control plane.
  • URI Uniform Resource Identifier
  • the vendor A parsing plug-in provides the vBRAS control plane with its own information, including the communication address and vendor ID (Vendor-ID) .
  • Vendor-ID vendor ID
  • Step 5070 Configure the vendor C parsing plug-in to register with the vBRAS control plane.
  • the vendor C parsing plug-in provides the vBRAS control plane with its own information, including the communication address and vendor ID (Vendor-ID).
  • Vendor-ID vendor ID
  • Step 5080 Through the OpenFlow protocol, the vBRAS forwarding plane device actively reports its own identification information, that is, the vendor identification Vendor-ID, to the vBRAS control plane.
  • the vendor identification Vendor-ID the vendor identification Vendor-ID
  • Step 5080 refer to the arrowed lines marked with the characters 1a, 1b, 1c, and 1d in FIG. 5 and the steps (1a), (1b), (1c), and (1d) in FIG. 6, respectively.
  • Step 5090 The broadband user starts to go online, and the vBRAS forwarding plane 1 (vendor A) receives the Ethernet-based Point-to-Point Protocol (PPPoE) access request message sent by the broadband user through the VxLAN tunnel And send the received original PPPoE access request message and corresponding receiving interface information (for example, interface Fei-2/1/0/2) to the vBRAS control plane.
  • PPPoE Point-to-Point Protocol
  • interface information for example, interface Fei-2/1/0/2
  • Step 5100 After receiving the PPPoE access request message, the vBRAS control plane device is responsible for processing and responding to the PPPoE access request message according to the PPPoE protocol. Through the PPPoE access protocol message interaction, the vBRAS control plane device obtains the user name information of the broadband user. The vBRAS control plane device writes the user name information in the Access-Request authentication message defined by the RADIUS protocol, and sends an Access-Request authentication request to the RADIUS server. For this step, refer to the arrowed line marked with the number 3 in FIG. 5 and step (3) in FIG. 6.
  • Step 5110 After receiving the Access-Request authentication request, the RADIUS server performs authentication according to the user name information carried in the authentication request. If the authentication is successful, it sends an Access-Accept authentication response to the vBRAS control plane device. Access-Accept authentication response can carry multiple Vendor-Specific attributes. For this step, refer to the arrowed line marked with the number 4 in FIG. 5 and step (4) in FIG. 6.
  • Step 5120 After receiving the Access-Accept authentication response message, the vBRAS control plane device finds the corresponding broadband user access information, including broadband access interface information, for example, interface Fei-2 according to the Identifier field value in the packet /1/0/2. Through the broadband access interface information, the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and its reported identifier, that is, the vendor identification (Vendor-ID). The vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • broadband access interface information for example, interface Fei-2 according to the Identifier field value in the packet /1/0/2.
  • broadband access interface information for example, interface Fei-2 according to the Identifier field value in the packet /1/0/2.
  • the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and its reported identifier, that is, the vendor identification (Vendor-ID).
  • the vBRAS control plane device parses the Attributes
  • the vBRAS control plane device uses the above corresponding vBRAS Forwarding surface identification information, that is, vendor identification (Vendor-ID), to find matching message parsing plug-ins. If the corresponding message parsing plug-in is found, the vBRAS control plane device sends all Vendor-Specific attributes in the above Access-Accept authentication response message to the corresponding message through the RESTFUL interface according to the communication address registered by the message parsing plug-in Analyze the plugin to do the processing. For this step, refer to the arrowed line marked with the number 5 in FIG. 5 and step (5) in FIG. 6.
  • Step 5130 The vendor A parsing plug-in receives the Vendor-Specific attribute from the vBRAS control plane device through the RESTFUL interface, and first judges whether the Vendor-ID value in the Vendor-Specific attribute is consistent with the vendor identification (Vendor-ID) of the parsing plug-in , If the Vendor-ID is inconsistent, then give up parsing, if the Vendor-ID value is consistent, then according to the definition of Vendor A, Vendor-Specific A’s vendor identification is 4097, when Vendor A’s resolution plug-in receives the 3 sent by the vBRAS control plane device Vendor-Specific attributes.
  • Vendor-ID vendor identification
  • the Vendor-ID values carried by the three Vendor-Specific attributes are 4096, 4097, and 4098, respectively.
  • the vendor A parsing plugin only parses the Vendor-Specific attributes that carry the Vendor-ID value of 4097; according to the vendor A definition
  • the private data format of Vendor A parses out all sub-attributes contained in the Vendor-Specific attribute with a Vendor-ID value of 4097.
  • the vendor A parsing plug-in finishes parsing all the Vendor-Specific attributes and the sub-attributes it contains, it sends the sub-attributes required by the vBRAS control plane to the vBRAS control plane device by responding to a POST request. For this step, refer to the arrowed line marked with the number 6 in FIG. 5 and step (6) in FIG. 6.
  • Step 5140 The vBRAS control plane device receives the analysis result of the Vendor-Specific attribute sent by the message analysis plug-in from the RESTFUL interface. Through the analysis result returned by the message analysis plug-in and its own analysis of other attributes carried in the Access-Accept authentication response message, the vBRAS control plane device obtains the authorization information of the broadband user.
  • Step 5150 The vBRAS control plane device converts the authorization information that needs to be delivered to the vBRAS forwarding plane into the attributes defined by the communication protocol between the vBRAS control plane and the forwarding plane, and then passes the vBRAS control plane (vendor B) and the vBRAS forwarding plane 1 (vendor A)
  • the OpenFlow channel established between the two uses the type length attribute value (Type Length Value, TLV) method to send the authorization information of the broadband user to the vBRAS forwarding plane 1 (Vendor A).
  • TLV method that is, each attribute value in the authorization information is transmitted according to the attribute type (Type), attribute length (Length), and attribute value (Value).
  • TLV method that is, each attribute value in the authorization information is transmitted according to the attribute type (Type), attribute length (Length), and attribute value (Value).
  • Step 5160 According to the definition of the communication protocol between the vBRAS control plane and the forwarding plane, the vBRAS forwarding plane device receives the broadband user authorization information and writes the authorization information into the user forwarding table. The vBRAS forwarding plane device subsequently processes and forwards the packets of broadband users visiting websites according to the user forwarding table.
  • the centralized control point is the vBRAS control plane, and the vBRAS control plane centrally controls and manages the vBRAS forwarding plane of the physical device form and the virtualization form;
  • the key devices contained in the vBRAS forwarding plane device of the physical device form are dedicated processors (such as NP, FPGA , ASIC, etc.), processing and forwarding high-traffic broadband access user service packets through a dedicated processor;
  • the key component contained in the virtualized vBRAS forwarding surface device is a general-purpose X86 processor, set to process and forward small-flow broadband Access user service messages.
  • This embodiment describes the use of a control plane and user plane separation protocol (Control-plane and User-plane Separation Protocol, CUSP) between the vBRAS control plane and the vBRAS forwarding plane.
  • CUSP is defined between the vBRAS control plane and the vBRAS forwarding plane.
  • the communication protocol based on Transmission Control Protocol (TCP), which is commonly followed by multiple manufacturers.
  • TCP Transmission Control Protocol
  • the vBRAS control plane is provided by a third party (non-vBRAS forwarding plane equipment manufacturer), deployed on a data center virtualization platform constructed by X86 servers and switches, and running in a virtual computer.
  • the private format data source is a RADIUS server.
  • the RADIUS server sends private extended attributes defined by multiple vendors to the vBRAS control plane; the private extended attributes are attributes No. 26 defined by the RADIUS protocol, that is, Vendor-Specific attributes .
  • Each Vendor-Specific attribute in the RADIUS protocol packet contains the vendor identifier Vendor-ID and the vendor-extended private sub-attribute.
  • the message analysis plug-in is a software module provided by the vBRAS forwarding plane equipment manufacturer, which can identify and parse Vendor-Specific attributes related to the manufacturer. It is deployed together with the virtualized vBRAS forwarding plane. Through the CUSP, the message analysis The plug-in registers and reports its own identification information with the vBRAS control plane, receives the Vendor-Specific attribute information sent by the vBRAS control plane, parses the Vendor-Specific attributes defined by the manufacturer, and sends the analysis result as a response to the vBRAS control plane.
  • the target devices are vBRAS forwarding plane devices centrally controlled and managed by the vBRAS control plane, including vBRAS forwarding plane devices in the form of physical devices and virtualized vBRAS forwarding plane devices.
  • the vBRAS forwards its own identification information for the vBRAS control plane and receives the authorization information issued by the vBRAS control plane.
  • the hardware module part includes: X86 server and BRAS equipment.
  • FIG. 7 is a schematic diagram of another system networking compatible with private format data parsing of different vendors provided by an embodiment of the present application.
  • a vBRAS control plane (non-vendor) is controlled by a third party (non-vBRAS forwarding plane equipment vendor) Provided, Vendor A forwarding plane (X86), Vendor B forwarding plane (X86) and Vendor C forwarding plane (X86) respectively represent the virtualized vBRAS forwarding plane equipment provided by Vendor A, Vendor B and Vendor C, Vendor A forwarding plane (X86), Vendor B forwarding plane (X86) and Vendor C forwarding plane (X86) provide corresponding message parsing plug-ins (see parsing plug-in in Figure 7); Vendor A vBRAS forwarding plane (NP), Vendor B vBRAS forwarding Surface (NP) and Vendor C vBRAS forwarding surface (NP) represent the vBRAS forwarding surface equipment of the physical device form provided
  • Vendor A vBRAS forwarding plane (NP), Vendor B vBRAS forwarding plane (NP) and Vendor C vBRAS forwarding plane (NP) can pass data.
  • the central gateway communicates with the vBRAS control plane (non-vendor), and the RADIUS server can communicate with the vBRAS control plane (non-vendor) and the data center gateway.
  • the vBRAS control plane can control and manage the vBRAS forwarding plane device through the CUSP, and the vBRAS forwarding plane device includes a physical device vBRAS forwarding plane device and a virtualized vBRAS forwarding plane device.
  • the vBRAS forwarding plane device in the form of a physical device is deployed at the edge of the metropolitan area network and is used for high-traffic user access services, such as high-speed Internet access (High Speed Internet, HSI), 4K ultra-high-definition network TV (Internet Protocol, IPTV), video Chat, real-time games and other services.
  • high-speed Internet access High Speed Internet, HSI
  • 4K ultra-high-definition network TV Internet Protocol, IPTV
  • video Chat real-time games and other services.
  • Virtualized vBRAS forwarding plane equipment is deployed in the data center for small-flow user access services, such as VoIP (Voice over Internet Protocol, VoIP), and the Network Management Protocol (Technical Report 069, TR069) defined in the Broadband Forum Technical Report 069 ) And other services.
  • the message parsing plug-in is deployed as a software module and the virtualized vBRAS forwarding plane provided by its own vendor, without the need to independently allocate additional resources (including CPU cores, memory, storage, network and other resources).
  • the message analysis plug-in also reports its own identification information to the vBRAS control plane through the CUSP, and the protocol processing is unified, which reduces the workload of vBRAS control plane protocol development.
  • the vBRAS control plane uses the vendor ID Vendor-ID as the identification information of the vBRAS forwarding plane and the packet parsing plug-in.
  • the workflow between the vBRAS control plane, RADIUS server, vBRAS forwarding plane, and parsing plug-in is shown in FIG. 7 .
  • the flow of the message processing method may include:
  • Step 7010 Deploy the vBRAS control plane device, create a new virtual machine or container on the cloud platform of the data center, and start the vBRAS control plane device provided by a third party (non-vBRAS forwarding plane device manufacturer) in the virtual machine or container.
  • a third party non-vBRAS forwarding plane device manufacturer
  • Step 7020 Deploy a virtualized vBRAS forwarding plane provided by multiple vendors, create a new virtual machine or container on the cloud platform in the data center, and start the virtualized vBRAS forwarding plane software provided by multiple vendors in the virtual machine or container And message parsing plugin.
  • Step 7030 Configure the connection between the vBRAS control plane device and the RADIUS server, including configuring the IP address and RADIUS protocol port number of the RADIUS server.
  • Step 7040 Configure all vBRAS forwarding plane devices of Vendor A, Vendor B, and Vendor C to connect to the vBRAS control plane; vBRAS forwarding plane devices include physical device vBRAS forwarding plane devices and virtualized vBRAS forwarding plane devices.
  • the above configuration process includes establishing a VxLAN tunnel from the vBRAS forwarding plane to the vBRAS control plane and establishing a CUSP connection from the vBRAS forwarding plane to the vBRAS control plane.
  • Step 7050 Configure the packet analysis plug-in of vendor A to register with the vBRAS control plane through the CUSP.
  • the packet analysis plug-in of vendor A provides its own information to the vBRAS control plane, including the communication address and vendor ID (Vendor-ID).
  • Vendor-ID vendor ID
  • Step 7060 Configure the packet analysis plug-in of manufacturer B to register with the vBRAS control plane through the CUSP.
  • the packet parsing plug-in of Vendor B provides its own information to the vBRAS control plane, including the communication address and Vendor ID (Vendor-ID).
  • Vendor-ID Vendor ID
  • Step 7070 Configure the packet parsing plug-in of manufacturer C to register with the vBRAS control plane through the CUSP.
  • the message parsing plug-in of vendor C provides its own information to the vBRAS control plane, including the communication address and vendor ID (Vendor-ID). For this step, see the arrowed lines marked with the characters 1f in Figure 7.
  • Step 7080 Through CUSP, all vBRAS forwarding plane devices of Vendor A, Vendor B, and Vendor C actively report their identification information, that is, Vendor-ID, to the vBRAS control plane.
  • the vBRAS forwarding plane device includes a physical device vBRAS forwarding plane device and a virtualized vBRAS forwarding plane device. For this step, refer to the arrowed lines marked with characters 1a, 1b, 1c, 1d, 1e, and 1f in FIG. 7, respectively. .
  • Step 7090 The broadband user starts to go online.
  • the vBRAS forwarding plane device (for example, vBRAS forwarding plane device in the form of physical equipment of manufacturer A) receives the PPPoE access request message sent by the broadband user.
  • the vBRAS forwarding plane passes the VxLAN tunnel to receive the received
  • the original PPPoE access request message and the corresponding receiving interface information (for example, interface Fei-2/1/0/2) are sent to the vBRAS control plane.
  • the corresponding receiving interface information for example, interface Fei-2/1/0/2
  • Step 7100 After receiving the PPPoE access request message, the vBRAS control plane device is responsible for processing and responding to the PPPoE access request message according to the PPPoE protocol. Through the PPPoE access protocol message interaction, the vBRAS control plane device obtains the user name information of the broadband user. The vBRAS control plane device writes the user name information in the Access-Request authentication message defined by the RADIUS protocol, and sends the Access-Request authentication request to the RADIUS server. For this step, refer to the arrowed line marked with the number 3 in Figure 7.
  • Step 7110 After receiving the Access-Request authentication request, the RADIUS server performs authentication according to the user name information carried in the authentication request. If the authentication is successful, an Access-Accept authentication response is sent to the vBRAS control plane. This step can be used in FIG. 7 Arrow line marked by the number 4.
  • Step 7120 After receiving the Access-Accept authentication response message, the vBRAS control plane device finds the corresponding broadband user access information according to the Identifier field value in the packet, including broadband access interface information, for example, interface Fei-2 /1/0/2. Through the broadband access interface information, the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and the identification information reported by it, that is, the vendor identification (Vendor-ID). The vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • broadband access interface information for example, interface Fei-2 /1/0/2.
  • the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and the identification information reported by it, that is, the vendor identification (Vendor-ID).
  • the vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • the vBRAS control plane device uses the above corresponding vBRAS Forwarding surface identification information, that is, vendor identification (Vendor-ID), to find matching message parsing plug-ins. If the corresponding message parsing plug-in is found, the vBRAS control plane connects via the CUSP according to the communication address registered by the message parsing plug-in, and sends all Vendor-Specific attributes in the above Access-Accept authentication response message to the corresponding message parsing The plug-in does the processing. For this step, you can refer to the arrowed lines marked with the number 5 in Figure 7.
  • Step 7130 The message parsing plug-in provided by Vendor A receives the Vendor-Specific attribute from the vBRAS control plane, and first determines whether the Vendor-ID value in the Vendor-Specific attribute is the same as the Vendor-ID of the message parsing plug-in (Vendor-ID) ) Consistent, if the Vendor-ID is inconsistent, then give up parsing, if the Vendor-ID value is consistent, then resolve Vendor-Specific attributes according to the definition of Vendor A. For example, the vendor ID of vendor A is 4097.
  • the Vendor-ID values carried by the three Vendor-Specific attributes are 4096, 4097 and 4098.
  • the packet parsing plug-in of Vendor A only parses the Vendor-Specific attribute with a Vendor-ID value of 4097.
  • the packet parsing plugin of Vendor A parses out all the sub-attributes contained in the Vendor-Specific attribute with a Vendor-ID value of 4097.
  • the packet parsing plugin of Vendor A After the packet parsing plugin of Vendor A completes the parsing of all Vendor-Specific attributes and the sub-attributes it contains, the sub-attributes required by the vBRAS control plane are sent to the vBRAS control through the CUSP connection established by the vBRAS forwarding plane and the control plane. For this step, you can refer to the arrowed lines marked with the number 6 in Figure 7.
  • Step 7140 The vBRAS control plane device receives the analysis result of the Vendor-Specific attribute sent by the message analysis plug-in. Through the analysis result returned by the message analysis plug-in and its own analysis of other attributes carried in the Access-Accept authentication response message, the vBRAS control plane device obtains the authorization information of the broadband user.
  • Step 7150 The vBRAS control plane device converts the authorization information that needs to be delivered to the vBRAS forwarding plane into the attributes defined by the communication protocol between the vBRAS control plane and the forwarding plane, and then passes the vBRAS forwarding plane (vBRAS forwarding plane device in the form of a physical device of manufacturer A). )
  • the CUSP connection established with the vBRAS control plane uses TLV to send the broadband user authorization information to the corresponding vBRAS forwarding plane.
  • the TLV method that is, each attribute value in the authorization information is transmitted according to the attribute type (Type), attribute length (Length), and attribute value (Value). For this step, refer to the arrow marked with the number 7 in Figure 7 Lines.
  • Step 7160 According to the definition of the communication protocol between the vBRAS control plane and the forwarding plane, the vBRAS forwarding plane device (vBRAS forwarding plane device in the form of physical device of manufacturer A) receives the broadband user authorization information and writes the authorization information into the user forwarding table. The vBRAS forwarding plane device subsequently processes and forwards the packets of broadband users visiting websites according to the user forwarding table.
  • the centralized control point is the vBRAS control plane.
  • the vBRAS control plane centrally controls and manages the vBRAS forwarding plane, and the communication between the vBRAS control plane and the message parsing plug-in.
  • the vBRAS control plane is deployed on the data center virtualization platform constructed by X86 servers and switches.
  • the private format data source is a RADIUS server.
  • the RADIUS server sends private extended attributes defined by multiple vendors to the vBRAS control plane.
  • the private extended attribute is attribute 26 defined by the RADIUS protocol, that is, the Vendor-Specific attribute.
  • Each Vendor-Specific attribute in the RADIUS protocol packet contains the vendor identifier Vendor-ID and the vendor-extended private sub-attribute.
  • the message parsing plug-in is a software module provided by the vBRAS forwarding plane equipment manufacturer, which can identify and parse Vendor-Specific attributes related to the manufacturer. It is deployed with the vBRAS forwarding plane device. Through the CUSP protocol, the parsing plug-in registers with the vBRAS control plane and reports its own identification information, receives the Vendor-Specific attribute information sent by the vBRAS control plane, and parses the Vendor-defined by the manufacturer. Specific attribute, and send the analysis result as a response to the vBRAS control plane.
  • the target device is a vBRAS forwarding plane device that is centrally controlled and managed by the vBRAS control plane.
  • the vBRAS forwards its own identification information for the vBRAS control plane and receives the authorization information issued by the vBRAS control plane.
  • the hardware module part includes: X86 server and BRAS equipment.
  • FIG. 8 is a schematic diagram of another system networking compatible with private format data parsing of different vendors provided by an embodiment of the present application.
  • a vBRAS control plane (non-vendor) is controlled by a third party (non-vBRAS forwarding plane equipment vendor)
  • Vendor A vBRAS forwarding plane 1 and Vendor A vBRAS forwarding plane 2 respectively represent the two vBRAS forwarding plane equipment provided by Vendor A, Vendor B vBRAS forwarding plane and Vendor C vBRAS forwarding plane respectively represent the two provided by Vendor B and Vendor C vBRAS forwarding plane equipment
  • Vendor A vBRAS forwarding plane 1, Vendor A vBRAS forwarding plane, Vendor B vBRAS forwarding plane and Vendor C vBRAS forwarding plane all provide corresponding message parsing plug-ins (see parsing plug-in in Figure 8); Vendor A vBRAS Forwarding plane 1.
  • Vendor A's vBRAS forwarding plane, Vendor B's vBRAS forwarding plane, Vendor C's vBRAS and their corresponding analysis plug-ins can all communicate with the vBRAS control plane (non-vendor), and the vBRAS control plane (non-vendor) can also communicate with the RADIUS server. Communicate.
  • the vBRAS control plane controls and manages the vBRAS forwarding plane equipment through CUSP; the message parsing plug-in is deployed as a software module with the vBRAS forwarding plane equipment provided by its own manufacturer. Correspondence, the closing of the vBRAS forwarding plane device will not affect the private attribute resolution of other vBRAS forwarding plane devices, and maintenance is convenient and flexible.
  • the message analysis plug-in also reports its own identification information to the vBRAS control plane through CUSP, and the protocol processing is unified, which reduces the development workload of the vBRAS control plane protocol.
  • the vBRAS control plane uses the vendor identification (Vendor-ID) and the vBRAS forwarding plane device identification information as identification information to identify the vBRAS forwarding plane device and the message parsing plug-in.
  • Vendor-ID vendor identification
  • vBRAS forwarding plane device identification information as identification information to identify the vBRAS forwarding plane device and the message parsing plug-in.
  • the flow of the message processing method may include:
  • Step 8010 Deploy the vBRAS control plane device, create a new virtual machine or container on the cloud platform in the data center, and start the vBRAS control plane provided by a third party (non-vBRAS forwarding plane equipment manufacturer) in the virtual machine or container.
  • a third party non-vBRAS forwarding plane equipment manufacturer
  • Step 8020 Configure the connection between the vBRAS control plane device and the RADIUS server, including configuring the IP address and RADIUS protocol port number of the RADIUS server.
  • Step 8030 Configure all vBRAS forwarding plane devices of vendor A, vendor B, and vendor C to connect to the vBRAS control plane.
  • the above configuration process includes establishing a VxLAN tunnel from the vBRAS forwarding plane to the vBRAS control plane and establishing a CUSP connection from the vBRAS forwarding plane to the vBRAS control plane.
  • Step 8040 Configure the packet analysis plug-in of vendor A to register with the vBRAS control plane through CUSP.
  • Vendor A's message parsing plug-in provides its own information to the vBRAS control plane, including the communication address, vendor ID (Vendor-ID) and corresponding vBRAS forwarding plane device identification information.
  • Vendor-ID vendor ID
  • vBRAS forwarding plane device identification information For this step, refer to Figure 8 with the characters 1a and 1b respectively Of lines with arrows.
  • Step 8050 Configure the packet analysis plug-in of manufacturer B to register with the vBRAS control plane through CUSP.
  • Vendor B's message parsing plug-in provides its own information to the vBRAS control plane, including the communication address, vendor ID (Vendor-ID) and corresponding vBRAS forwarding plane device identification information.
  • Vendor-ID vendor ID
  • vBRAS forwarding plane device identification information For this step, see the arrow marked with the character 1c in Figure 8 Lines.
  • Step 8060 Configure the packet parsing plug-in of manufacturer C to register with the vBRAS control plane through CUSP.
  • the packet analysis plug-in of vendor C provides its own information to the vBRAS control plane, including the communication address, vendor ID (Vendor-ID) and corresponding vBRAS forwarding plane device identification information. For this step, see the arrow marked with the character 1d in Figure 8 Lines.
  • Step 8070 Through the CUSP protocol, all vBRAS forwarding plane devices of Vendor A, Vendor B, and Vendor C actively report their identification information, that is, device identification information and Vendor ID (Vendor-ID) to the vBRAS control plane. For this step, see the figure. Lines with arrows marked with characters 1a, 1b, 1c and 1d in 8 respectively.
  • Step 8080 The broadband user starts to go online, and the vBRAS forwarding plane device (for example, vendor A's vBRAS forwarding plane 1 device) receives the dynamic host configuration protocol (Dynamic Host Configuration Protocol, DHCP) access request message sent by the broadband user, and vBRAS forwards
  • DHCP Dynamic Host Configuration Protocol
  • the VxLAN tunnel sends the received original DHCP access request packet and the corresponding receiving interface information (for example, interface Fei-2/1/0/2) to the vBRAS control plane device. Lines with arrows marked with the number 2 in 8.
  • Step 8090 After receiving the DHCP access request message, the vBRAS control plane device is responsible for completing the processing and response of the DHCP access request message according to the DHCP protocol. Through the interaction of DHCP access protocol messages, the vBRAS control plane device obtains the user name information of the broadband user through the Option option in the DHCP message. The vBRAS control plane device writes the user name information in the Access-Request authentication message defined by the RADIUS protocol and sends the Access-Request authentication request to the RADIUS server. For this step, refer to the arrowed line marked with the number 3 in Figure 8.
  • Step 8100 After receiving the Access-Request authentication request, the RADIUS server performs authentication according to the user name information carried in the authentication request. If the authentication is successful, an Access-Accept authentication response is sent to the vBRAS control plane device. This step can be seen in FIG. 8 Arrowed lines marked with the number 4.
  • Step 8110 After receiving the Access-Accept authentication response message, the vBRAS control plane device finds the corresponding broadband user access information according to the Identifier field value in the packet, including broadband access interface information, for example, interface Fei-2 /1/0/2. Through the broadband access interface information, the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and the reported identification information, that is, the vendor identification (Vendor-ID) and device identification information. The vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • broadband access interface information for example, interface Fei-2 /1/0/2.
  • the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and the reported identification information, that is, the vendor identification (Vendor-ID) and device identification information.
  • the vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • the vBRAS control plane device uses the above corresponding vBRAS Forwarding surface identification information, that is, vendor identification (Vendor-ID) and device identification information, to find matching message parsing plug-ins. If the corresponding message parsing plug-in is found, the vBRAS control plane device connects through the CUSP according to the communication address registered by the message parsing plug-in, and sends all the Vendor-Specific attributes in the above Access-Accept authentication response message to the corresponding message Analyze the plug-in for processing. For this step, you can refer to the arrowed lines marked with the number 5 in Figure 8.
  • Step 8120 The message parsing plug-in provided by Vendor A receives the Vendor-Specific attribute from the vBRAS control plane device, and first determines whether the Vendor-ID value in the Vendor-Specific attribute is the same as the vendor identification of the message parsing plug-in (Vendor- ID) is consistent. If the Vendor-ID is inconsistent, the analysis is abandoned. If the Vendor-ID value is consistent, the Vendor-Specific attribute is parsed according to the definition of Vendor A. For example, the vendor ID of vendor A is 4097.
  • the Vendor-ID values carried by the three Vendor-Specific attributes are 4096, 4097 and 4098.
  • the packet parsing plug-in of Vendor A only parses the Vendor-Specific attribute with a Vendor-ID value of 4097.
  • the packet parsing plugin of Vendor A parses out all the sub-attributes contained in the Vendor-Specific attribute with a Vendor-ID value of 4097.
  • the packet parsing plugin of Vendor A After the packet parsing plugin of Vendor A completes the parsing of all Vendor-Specific attributes and the sub-attributes it contains, the sub-attributes required by the vBRAS control plane are sent to the vBRAS control through the CUSP connection established by the vBRAS forwarding plane and the control plane. For this device, you can refer to the arrowed lines marked with the number 6 in Figure 8 for this step.
  • Step 8130 The vBRAS control plane device receives the analysis result of the Vendor-Specific attribute sent by the message analysis plug-in. Through the analysis result returned by the message analysis plug-in and its own analysis of other attributes carried in the Access-Accept authentication response message, the vBRAS control plane device obtains the authorization information of the broadband user.
  • Step 8140 The vBRAS control plane device converts the authorization information that needs to be delivered to the vBRAS forwarding plane into the attributes defined by the communication protocol between the vBRAS control plane and the forwarding plane, and then passes the vBRAS forwarding plane (vBRAS forwarding plane 1 device of vendor A) and The CUSP connection established between vBRAS control planes uses TLV to send the authorization information of broadband users to the corresponding vBRAS forwarding plane.
  • the TLV method that is, each attribute value in the authorization information is transmitted according to the attribute type (Type), attribute length (Length) and attribute value (Value). For this step, refer to the arrowed line.
  • Step 8150 According to the definition of the communication protocol between the vBRAS control plane and the forwarding plane, the vBRAS forwarding plane device (Vendor A vBRAS forwarding plane 1) receives the broadband user authorization information and writes the authorization information into the user forwarding table. The vBRAS forwarding plane device subsequently processes and forwards the packets of broadband users visiting websites according to the user forwarding table.
  • Vendor A vBRAS forwarding plane 1 receives the broadband user authorization information and writes the authorization information into the user forwarding table.
  • the vBRAS forwarding plane device subsequently processes and forwards the packets of broadband users visiting websites according to the user forwarding table.
  • the centralized control point is the vBRAS control plane.
  • the vBRAS control plane centrally controls and manages the vBRAS forwarding plane. It supports the microservice architecture and supports multiple vendors to provide private extension functions in the form of microservices.
  • the vBRAS control plane interfaces with the microservices of message parsing plug-ins provided by these vendors.
  • the vBRAS control plane and the packet analysis plug-in microservices provided by multiple vendors are deployed on the data center virtualization platform built by X86 servers and switches.
  • the private format data source is a RADIUS server.
  • the RADIUS server sends private extended attributes defined by multiple vendors to the vBRAS control plane.
  • the private extended attribute is attribute 26 defined by the RADIUS protocol, that is, the Vendor-Specific attribute.
  • Each Vendor-Specific attribute in the RADIUS protocol packet contains the vendor identifier Vendor-ID and the vendor-extended private sub-attribute.
  • the message parsing plug-in is a microservice provided by the manufacturer, which supports the identification and parsing of Vendor-Specific attributes related to the manufacturer. Through the RESTFUL interface, it receives the Vendor-Specific attribute information sent by the vBRAS control plane device, parses the Vendor-Specific attribute defined by the manufacturer, and sends the analysis result as a response to the vBRAS control plane device.
  • the target device is a vBRAS forwarding plane device that is centrally controlled and managed by the vBRAS control plane.
  • the vBRAS forwards its own identification information for the vBRAS control plane and receives the authorization information issued by the vBRAS control plane.
  • the hardware module part includes: X86 server and BRAS equipment.
  • FIG. 9 is a schematic diagram of another system networking compatible with private format data parsing of different vendors provided by an embodiment of the present application.
  • a vBRAS control plane (non-vendor) is controlled by a third party (non-vBRAS forwarding plane equipment vendor) Provided, vBRAS forwarding plane 1 (vendor A) and vBRAS forwarding plane 2 (vendor A) respectively represent two vBRAS forwarding plane devices provided by vendor A, and vBRAS forwarding plane (vendor B) indicates vBRAS forwarding plane devices provided by vendor B ; Vendor A parsing plug-in 1 and Vendor A parsing plug-in 2 respectively represent the two message parsing plug-ins provided by Vendor A, where Vendor A parsing plug-in 1 matches the identification information of vBRAS forwarding plane 1 (Vendor A), and Vendor A parsing plug-in 2 matches the identification information of vBRAS forwarding plane 2 (vendor A),
  • the BRAS control plane is provided by a third party (non-vBRAS forwarding plane equipment manufacturer), which supports interfacing with parsing plug-in microservices provided by other manufacturers through the RESTFUL interface.
  • the vBRAS forwarding plane equipment provided by the manufacturer needs to provide a message analysis plug-in to the vBRAS control plane in addition to the communication protocol between the vBRAS control plane and the vBRAS forwarding plane.
  • the packet analysis plug-in can analyze the private format data defined by the manufacturer and sent by the RADIUS server to the vBRAS control plane.
  • vBRAS forwarding plane function provided by the same manufacturer has the same function and the corresponding message parsing plug-in function is the same
  • multiple vBRAS forwarding planes provided by the same vendor can share the same message parsing plug-in, that is, each manufacturer only A packet parsing plug-in needs to be deployed to connect with the vBRAS control plane.
  • the vBRAS control plane uses the Vendor-ID as the identification information to identify the vBRAS forwarding plane device and the packet parsing plug-in.
  • the vBRAS forwarding plane device was expanded and upgraded. The original message analysis plug-in could not meet the private format data analysis required by the new device.
  • vBRAS The control plane uses vendor identification (Vendor-ID) and vBRAS forwarding plane device identification information as identification information to identify the new vBRAS forwarding plane device and the new message parsing plug-in.
  • Vendor-ID vendor identification
  • vBRAS forwarding plane device identification information identification information to identify the new vBRAS forwarding plane device and the new message parsing plug-in.
  • the expansion and upgrade of the new vBRAS forwarding plane device does not affect the normal operation of the original device.
  • the vBRAS control plane supports the vendor ID Vendor-ID as the target device and parsing plug-in identification information, as well as the vendor ID (Vendor-ID) and vBRAS forwarding plane device identification information as the target device and message parsing plug-in identification information.
  • Vendor-ID vendor ID
  • Vendor-ID vendor ID
  • vBRAS forwarding plane device identification information as the target device and message parsing plug-in identification information.
  • Step 9010 Deploy the vBRAS control plane device, create a new virtual machine or container on the cloud platform in the data center, and start the vBRAS control plane device provided by a third party (non-vBRAS forwarding plane device manufacturer) in the virtual machine or container.
  • a third party non-vBRAS forwarding plane device manufacturer
  • Step 9020 Deploy vendor A parsing plug-in 1, create a new virtual machine or container on the cloud platform in the data center, and start vendor A parsing plug-in 1 in the virtual machine or container.
  • Step 9030 Deploy the vendor B parsing plug-in, create a new virtual machine or container on the cloud platform in the data center, and start the vendor B parsing plug-in in the virtual machine or container.
  • Step 9040 Configure the connection between the vBRAS control plane device and the RADIUS server, including configuring the IP address and RADIUS protocol port number of the RADIUS server.
  • Step 9050 Configure vBRAS forwarding plane 1 (vendor A) and vBRAS forwarding plane (vendor B) to connect to the vBRAS control plane equipment, including establishing a VxLAN tunnel from the vBRAS forwarding plane to the vBRAS control plane, and establishing a CUSP from the vBRAS forwarding plane to the vBRAS control plane connection.
  • Step 9060 Configure the vendor A parsing plug-in 1 to register with the vBRAS control plane.
  • the vendor A parsing plug-in 1 provides the vBRAS control plane with its own information, including the communication address and vendor ID (Vendor-ID).
  • Vendor-ID vendor ID
  • Step 9070 Configure the vendor B parsing plug-in to register with the vBRAS control plane. Via the URI, the vendor B parsing plug-in provides the vBRAS control plane with its own information, including the communication address and vendor ID (Vendor-ID). For this step, see the characters in Figure 9 1c marked lines with arrows.
  • Step 9080 Through CUSP, the vBRAS forwarding plane 1 (vendor A) and the vBRAS forwarding plane (vendor B) actively report their own identification information to the vBRAS control plane device, that is, the vendor identification Vendor-ID. For this step, refer to Figure 9 respectively. Arrowed lines marked by characters 1a and 1b.
  • Step 9090 Expand and upgrade and deploy Vendor A parsing plug-in 2, create a new virtual machine or container on the cloud platform in the data center, and start Vendor A parsing plug-in 2 in the virtual machine or container.
  • Step 9100 Configure vBRAS forwarding plane 2 (vendor A) to connect to the vBRAS control plane device. This includes establishing a VxLAN tunnel from the vBRAS forwarding plane to the vBRAS control plane and establishing a CUSP connection from the vBRAS forwarding plane to the vBRAS control plane.
  • Step 9110 Configure the vendor A parsing plug-in 2 to register with the vBRAS control plane.
  • the vendor A parsing plug-in 2 provides its own information to the vBRAS control plane device, including the communication address, vendor ID (Vendor-ID) and corresponding vBRAS forwarding plane device
  • this step can refer to the arrowed line marked with the character 1f in FIG. 9.
  • Step 9120 Through CUSP, the vBRAS forwarding plane 2 (Vendor A) actively reports its own identification information to the vBRAS control plane device, that is, the device identifier and the vendor ID (Vendor-ID). For this step, refer to Figure 9 and mark with the character 1e Of lines with arrows.
  • Step 9130 The broadband user starts to go online, the vBRAS forwarding plane 2 (vendor A) receives the PPPoE access request message sent by the broadband user, and the vBRAS forwarding plane passes the received original PPPoE access request message and the corresponding through the VxLAN tunnel
  • the received interface information (for example, interface Fei-2/1/0/2) is sent to the vBRAS control plane.
  • Step 9140 After receiving the PPPoE access request message, the vBRAS control plane device is responsible for processing and responding to the PPPoE access request message according to the PPPoE protocol. Through the PPPoE access protocol message interaction, the vBRAS control plane device obtains the user name information of the broadband user. The vBRAS control plane device writes the user name information in the Access-Request authentication message defined by the RADIUS protocol, and sends the Access-Request authentication request to the RADIUS server. For this step, refer to the arrowed line marked with the number 3 in Figure 9.
  • Step 9150 After receiving the Access-Request authentication request, the RADIUS server performs authentication according to the user name information carried in the authentication request. If the authentication is successful, an Access-Accept authentication response is sent to the vBRAS control plane device. This step can be seen in FIG. 9 Arrowed lines marked with the number 4.
  • Step 9160 After receiving the Access-Accept authentication response message, the vBRAS control plane device finds the corresponding broadband user access information, including broadband access interface information, for example, interface Fei-2 according to the Identifier field value in the packet /1/0/2. Through the broadband access interface information, the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and the reported identification information, that is, the vendor identification (Vendor-ID) and device identification information. The vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • broadband access interface information for example, interface Fei-2 according to the Identifier field value in the packet /1/0/2.
  • the vBRAS control plane device obtains the corresponding vBRAS forwarding plane device and the reported identification information, that is, the vendor identification (Vendor-ID) and device identification information.
  • the vBRAS control plane device parses the Attributes information carried in the Access-Accept authentication response message.
  • the vBRAS control plane device uses the above corresponding vBRAS Forwarding surface identification information, that is, vendor identification (Vendor-ID) and device identification information, to find matching message parsing plug-ins. If the corresponding message parsing plug-in is found, the vBRAS control plane device sends all Vendor-Specific attributes in the above Access-Accept authentication response message to the corresponding message through the RESTFUL interface according to the communication address registered by the message parsing plug-in Analyze the plug-in for processing. For this step, you can refer to the arrowed lines marked with the number 5 in Figure 9.
  • Step 9170 Vendor A parsing plug-in 2 receives the Vendor-Specific attribute from the vBRAS control plane device through the RESTFUL interface, and first determines whether the Vendor-ID value in the Vendor-Specific attribute is the same as the vendor identification of the message parsing plug-in (Vendor- ID) is consistent, if the Vendor-ID is inconsistent, then give up parsing, if the Vendor-ID value is consistent, then according to the definition of Vendor A, Vendor-Specific A’s vendor identification is 4097, when Vendor A’s resolution plug-in 2 receives the vBRAS control plane The three Vendor-Specific attributes are sent.
  • Vendor-ID values carried by the three Vendor-Specific attributes are 4096, 4097, and 4098, respectively.
  • Vendor A parsing plug-in 2 only parses the Vendor-Specific attributes carrying the Vendor-ID value of 4097.
  • vendor A parsing plug-in 2 parses out all the sub-attributes contained in the Vendor-Specific attribute with a Vendor-ID value of 4097.
  • the vendor A parsing plugin 2 After the vendor A parsing plugin 2 completes parsing all the Vendor-Specific attributes and the sub-attributes it contains, it sends the sub-attributes required by the vBRAS control plane to the vBRAS control plane device by responding to the POST request. For this step, see Figure 9 Lines with arrows marked with the number 6 in.
  • Step 9180 The vBRAS control plane device receives the analysis result of the Vendor-Specific attribute sent by the vendor A analysis plug-in 2 from the RESTFUL interface. Through the analysis result returned by the analysis plug-in and its own analysis of other attributes carried in the Access-Accept authentication response message, the vBRAS control plane device obtains the authorization information of the broadband user.
  • Step 9190 The vBRAS control plane device converts the authorization information that needs to be delivered to the vBRAS forwarding plane into the attributes defined by the communication protocol between the vBRAS control plane and the forwarding plane, and then passes the vBRAS forwarding plane (vBRAS forwarding plane 2 (vendor A)) and The CUSP connection established between vBRAS control planes uses TLV to send the authorization information of broadband users to the corresponding vBRAS forwarding plane.
  • the TLV method that is, each attribute value in the authorization information is transmitted according to the attribute type (Type), attribute length (Length) and attribute value (Value). For this step, refer to the arrowed line.
  • Step 9200 According to the definition of the communication protocol between the vBRAS control plane and the forwarding plane, the vBRAS forwarding plane device receives the broadband user authorization information and writes the authorization information into the user forwarding table. The vBRAS forwarding plane device subsequently processes and forwards the packets of broadband users visiting websites according to the user forwarding table.
  • the sixth embodiment of the present application proposes a message processing apparatus, which can be applied to a vBRAS control plane device.
  • the device includes a receiving module 1001, a first processing module 1002, and a second processing module 1003, where,
  • the receiving module 1001 is configured to receive a message containing at least one private format data
  • the first processing module 1002 is configured to determine the identification information of the target device according to the first message, select a message parsing plug-in matching the determined identification information of the target device; send the selected message parsing plug-in to the selected message parsing plug-in At least one private format data, receiving the parsed data from the selected message parsing plugin; the parsed data is obtained by parsing the at least one private format data by the selected message parsing plugin;
  • the second processing module 1003 is configured to determine, according to the parsed data, the processing manner of the second message used by the target device to access the website.
  • the first processing module 1002 is further configured to receive identification information reported by multiple target devices and identification information reported by multiple message parsing plugins; according to the identification information reported by the multiple target devices And the identification information reported by the multiple message parsing plug-ins to establish a correspondence between the identification information of the target device and the message parsing plug-in identification information; according to the corresponding relationship, select a match with the determined identification information of the target device Message parsing plugin.
  • the identification information reported by each target device includes the ID of the vendor to which the target device belongs, or the identification information reported by each target device includes the ID of the vendor to which the target device belongs and the ID of the corresponding target device.
  • the identification information reported by each message analysis plug-in includes the ID of the manufacturer to which the corresponding message analysis plug-in belongs, or the identification information reported by each message analysis plug-in includes the ID and the ID of the manufacturer to which the corresponding message analysis plug-in belongs. The ID of the target device.
  • the determined identification information of the target device includes: class identification information and unique identification information; the class identification information is used to identify the class of the target device, and the unique identification information is used to uniquely identify the target device.
  • the category identification information includes the ID of the manufacturer to which the target device belongs, and the unique identification information includes the ID of the target device.
  • the first processing module 1002 is configured to select the search when a packet analysis plug-in matching the determined category identification information and unique identification information of the determined target device is found according to the corresponding relationship
  • the received message parsing plug-in according to the corresponding relationship, no message parsing plug-in that matches the determined category identification information and unique identification information of the determined target device is found, and the category identification of the determined target device is found
  • the message parsing plug-in with matching information is selected, the found message parsing plug-in is selected.
  • the first processing module 1002 is further configured to, after establishing the correspondence between the identification information of the target device and the identification information of the message parsing plug-in, receive the identification information reported by the newly deployed target device and the new When the identification information reported by the deployed message parsing plugin is updated, the corresponding relationship is updated according to the identification information reported by the newly deployed target device and the identification information reported by the newly deployed message parsing plugin.
  • the first processing module 1002 when the first processing module 1002 is set as the first message is an authentication response message for a broadband access authentication request, according to the Identifier field value in the first message, Determine the identification information of the target device.
  • the first processing module 1002 is configured to find corresponding broadband user access information according to the Identifier field value; and determine the identification information of the target device according to the broadband user access information.
  • the parsed data is determined by the packet analysis plug-in according to the identification information of the vendor to which it belongs. After filtering the private format data, analyze the data.
  • the second processing module 1003 is configured to obtain broadband user authorization information according to the parsed data when the first packet is an authentication response packet for a broadband access authentication request; Sending the broadband user authorization information to the target device, so that the target device determines the processing method of the second message according to the broadband user authorization information.
  • the receiving module 1001, the first processing module 1002, and the second processing module 1003 may be implemented by a CPU, a microprocessor (Micro Processor Unit, MPU), a DSP, or an FPGA.
  • multi-function module in this embodiment may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or software function modules.
  • the integrated unit may be stored in a computer-readable storage medium, and the technical solution of this embodiment may essentially be in the form of a software product It is reflected that the computer software product is stored in a storage medium and includes instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute the method described in this embodiment All or part of the steps.
  • the foregoing storage media include: a U disk, a mobile hard disk, a read-only memory (Read Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and other media that can store program codes.
  • the computer program instructions corresponding to a message processing method in this embodiment can be stored on a storage medium such as an optical disk, a hard disk, a universal serial bus flash disk (Universal Serial Bus flash disk, U disk), etc.
  • a storage medium such as an optical disk, a hard disk, a universal serial bus flash disk (Universal Serial Bus flash disk, U disk), etc.
  • FIG. 11 shows another packet processing apparatus 110 provided by an embodiment of the present application.
  • the apparatus may include: a memory 111 and a processor 112; wherein,
  • the memory 111 is configured to store computer programs and data
  • the processor 112 is configured to execute a computer program stored in the memory to implement any message processing method in the foregoing embodiment.
  • the above-mentioned memory 111 may be a volatile memory (volatile memory), such as RAM; or a non-volatile memory (non-volatile memory), such as ROM, flash memory (flash memory), hard disk (Hard Disk) Drive (HDD) or Solid-State Drive (SSD); or a combination of the above-mentioned types of memory, and provides instructions and data to the processor 112.
  • volatile memory volatile memory
  • non-volatile memory such as ROM, flash memory (flash memory), hard disk (Hard Disk) Drive (HDD) or Solid-State Drive (SSD); or a combination of the above-mentioned types of memory, and provides instructions and data to the processor 112.
  • the processor 112 may be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • DSPD digital signal processor
  • PLD PLD
  • FPGA field-programmable gate array
  • CPU central processing unit
  • controller microcontroller
  • microprocessor microprocessor
  • the deployment method of the message parsing plug-in is: deployment independent of the forwarding plane device, or deployed at the forwarding plane device.
  • the target device belongs to a forwarding plane device.
  • control plane device which includes any message processing device in the sixth embodiment of the present application.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer usable program code.
  • a computer usable storage media including but not limited to disk storage and optical storage, etc.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are performed on the computer or other programmable device to produce computer-implemented processing, which is executed on the computer or other programmable device
  • the instructions provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公开了一种报文处理方法、装置、控制面设备和计算机存储介质，所述方法包括：接收到包含至少一种私有格式数据的第一报文；根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述第一报文，接收来自所选择的报文解析插件的解析后数据；其中，所述解析后数据是由所选择的报文解析插件对所述第一报文中的至少一种私有格式数据进行解析后得出的数据；根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。

Description

报文处理方法、装置、控制面设备和计算机存储介质
本申请要求在2018年12月28日提交中国专利局、申请号为201811619224.5的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及但不限于虚拟宽带远程接入服务器的报文处理领域，例如涉及一种报文处理方法、装置、控制面设备和计算机存储介质。
背景技术
虚拟宽带远程接入服务器(virtual Broadband Remote Access Server，vBRAS)通过采用先进的软件定义网络(Software Defined Network，SDN)和网络功能虚拟化(Network Function Virtualization，NFV)技术，实现了传统宽带远程接入服务器(Broadband Remote Access Server，BRAS)产品转控分离；vBRAS可以分为vBRAS控制面和vBRAS转发面，vBRAS转发面实现分布式部署，并且形态多样化，包括基于传统网络处理器(Network Processor，NP)实现的硬转发面和基于X86服务器实现的虚拟转发面；vBRAS控制面集中控制和管理vBRAS转发面，支持集中控制和管理不同厂商生产的vBRAS转发面设备，弥补了传统的实体宽带远程接入服务器产品的不足。
在vBRAS控制面和vBRAS转发面分离，vBRAS控制面集中控制和管理不同厂商生产的vBRAS转发面设备的场景下，如何解析不同厂商自定义的私有格式数据，是亟待解决的问题。
发明内容
本申请实施例提供了一种报文处理方法、装置、控制面设备和计算机存储介质，可以兼容实现不同厂商私有格式数据的解析。
本申请实施例提供了一种报文处理方法，所述方法包括：
接收到包含至少一种私有格式数据的第一报文；
根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述第一报文，接收来自所选择的报文解析插件的解析后数据；所述解析后数据是由所选择的报文解析插件对所述第一报文中的至少一种私有格式数据进行解析后得出的数据；
根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。
本申请实施例还提供了一种报文处理装置，所述装置包括处理器和设置为存储能够在处理器上运行的计算机程序的存储器；其中，所述处理器设置为运行所述计算机程序时，执行本申请任意实施例所述的报文处理方法。
本申请实施例还提供了一种报文处理装置，包括：
接收模块，设置为接收到包含至少一种私有格式数据的第一报文；
第一处理模块，设置为根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述第一报文，接收来自所选择的报文解析插件的解析后数据；其中，所述解析后数据是由所选择的报文解析插件对所述第一报文中的至少一种私有格式数据进行解析后得出的数据；
第二处理模块，设置为根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。
本申请实施例还提供了一种控制面设备，包括本申请任意实施例所述的报文处理装置。
本申请实施例还提供了一种计算机存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现本申请任意实施例所述的报文处理方法。
附图说明
图1为本申请实施例提供的一种实体BRAS与远程用户拨号认证服务(Remote Authentication Dial In User Service，RADIUS)服务器的组网示意图；
图2为本申请实施例提供的一种报文处理方法的流程图；
图3为本申请实施例提供的一种兼容不同厂商的私有格式数据解析的***组网示意图；
图4为本申请实施例提供的另一种报文处理方法的流程图；
图5为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图；
图6为本申请实施例提供的另一种报文处理方法的流程图；
图7为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图；
图8为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图；
图9为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图；
图10为本申请实施例提供的一种报文处理装置的组成结构示意图；
图11为本申请实施例提供的一种报文处理装置的硬件结构示意图。
具体实施方式
以下结合附图及实施例，对本申请进行说明。此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
相关技术中，实体BRAS包含了控制面和转发面，每个厂商的实体BRAS可以作为RADIUS客户端，遵循征求意见(Request For Comments，RFC)定义的RADIUS协议直接与RADIUS服务器通信，通过RADIUS服务器完成宽带用户接入的认证、授权和计费。图1为本申请实施例提供的一种实体BRAS与RADIUS服务器的组网示意图，如图1所示，BRAS设备(厂商A)、BRAS设备(厂商B)和BRAS设备(厂商C)分别表示3个不同厂商的实体BRAS，BRAS设备(厂商A)、BRAS设备(厂商B)和BRAS设备(厂商C)可以分别与RADIUS服务进行通信。
RADIUS协议具有可扩展性，在RADIUS协议中定义了26号属性(厂商-特性(Vendor-Specific)属性)，用于支持不同厂商私有属性的扩展，Vendor-Specific属性中包含了厂商-标识(Vendor-Identifier，Vendor-ID)和厂商自定义的私有子属性，其中Vendor-ID表示厂商标识，实体BRAS只解析Vendor-Specific属性中Vendor-ID与设备生产厂商标识匹配的私有属性；如果Vendor-ID与设备厂商标识不匹配，则忽略不可识别类型的属性。
而对于vBRAS，可以实现控制面和转发面分离，vBRAS控制面集中控制和管理不同厂商生产的vBRAS转发面设备的场景下，单一厂商提供的vBRAS控制面和RADIUS服务器通信时，存在着如何解析RADIUS服务器返回的不同厂商自定义的私有属性的问题。
vBRAS已经是实体BRAS的未来发展方向，vBRAS还没有实现vBRAS控制面集中控制和管理不同厂商生产的vBRAS转发面设备，主要原因是还没有定义vBRAS控制面和vBRAS转发面之间的接口标准。
另外，在vBRAS架构中，vBRAS控制面已经实现了虚拟化，利用虚拟化技术解决vBRAS遇到的问题，也是一种发展趋势，其中包括采用微服务架构 (Microservices Architecture)，微服务架构是将应用分割成一系列细小的服务，即服务的微型化，每个服务微小到只需专注做好一件事，运行于独立的进程中，服务之间边界清晰，微服务架构采用轻量级通信机制(如超文本传输协议(HyperText Transfer Protocol，HTTP)/表征状态转移(Representational State Transfer，RESTFUL))相互沟通，通过多个服务之间配合来实现完整的应用，可以满足业务和用户的需求。
基于上述记载的内容，提出以下实施例。
第一实施例
本申请第一实施例提出了一种报文处理方法，可以应用于控制面设备中，示例性地，这里的控制面设备可以是vBRAS控制面设备。
图2为本申请实施例提供的一种报文处理方法的流程图，如图2所示，该流程可以包括：
步骤2010：接收到包含至少一种私有格式数据的第一报文。
本实施例中，私有格式数据可以是由厂商定义的私有属性数据。实际应用中，私有格式数据源可以向控制面设备发送包含有私有格式数据的报文，控制面设备可以从私有格式数据源接收上述报文，私有格式数据源是发送含有至少一个厂商定义的私有格式数据的报文的设备。
可选地，上述私有格式数据源可以是认证和授权服务器，例如，上述私有格式数据源为RADIUS服务器，或者其他类型的认证和授权服务器。
实际应用中，控制面设备设置为集中控制和管理多个被控制设备，并统一和私有格式数据源通信，被控制设备不再与私有格式数据源通信。本实施例中，被控制设备可以是转发面设备。示例性地，vBRAS控制面设备可以通过RFC定义的RADIUS协议和RADIUS服务器通信，完成宽带用户接入的认证、授权和计费处理，并且，通过vBRAS控制面和vBRAS转发面之间的通信协议，集中控制和管理vBRAS转发面设备。
步骤2020：根据第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送上述至少一种私有格式数据，接收来自所选择的报文解析插件的解析后数据；解析后数据是由所选择的报文解析插件对至少一种私有格式数据进行解析后得出的。
本实施例中，目标设备可以是不同厂商提供的业务处理设备，示例性地，目标设备属于vBRAS控制面设备控制下的被控制设备，所有目标设备均可以与 vBRAS控制面设备建立连接，本申请实施例中，与vBRAS控制面设备建立连接的目标设备的个数可以是一个，也可以是多个；每个目标设备可以通过多个厂商共同遵守的通信协议向vBRAS控制面设备上报标识信息，并接收vBRAS控制面设备下发的控制属性。
可选地，目标设备属于转发面设备，例如，目标设备为vBRAS转发面设备；作为一种实现方式，目标设备可以包括以下至少一项：BRAS、宽带网络网关(Broadband Network Gateway，BNG)、宽带业务网关(Broadband Service Gateway，BSG)、业务路由器(Service Router，SR)、宽带接入服务器(Broadband Access Server，BAS)、开放流逻辑交换机(Openflow Logical Switch，简称为OFLS)、开放流交换机(Openflow Switch，OFS)、无线接入控制器(Access Controller，AC)、光线路终端设备(Optical Line Terminal，OLT)、汇聚交换机、能够在提供计算服务的服务器上运行的模拟物理宽带接入服务器功能的软件。
目标设备的标识信息用于标识目标设备，目标设备的标识信息可以包括：类别标识信息和唯一标识信息；所述类别标识信息用于标识目标设备的类别、所述唯一标识信息用于唯一标识目标设备。对于不同的目标设备而言，当不同的目标设备属于同一类别时，类别标识信息可以相同，这样，通过类别标识信息，可以识别属于统一类别的目标设备，类别标识信息有利于目标设备的批量部署；唯一标识信息与目标设备一一对应，唯一标识信息有利于目标设备单独升级，不影响其他设备正常运行，也就是说，在一个目标设备单独升级时，只需要更改该目标设备对应的唯一标识信息即可，不需要对其他目标设备的标识信息进行更改。
上述两类标识信息(类别标识信息和唯一标识信息)在一个***中可以混合使用，也就是说，在多个目标设备、控制面设备以及私有格式数据源组成的***中，每个目标设备对应的标识信息既包括类别标识信息，也包括唯一标识信息。
作为一种实现方式，类别标识信息包括目标设备所属厂商的身份标识(Identifier，ID)。
作为一种实现方式，唯一标识信息可以包括目标设备的ID。
对于根据第一报文确定目标设备的标识信息的实现方式，示例性地，当第一报文为针对宽带接入认证请求的认证响应报文时，可以根据第一报文中的标识符(Identifier)域值，确定目标设备的标识信息。可选地，可以根据上述Identifier域值，查找到对应的宽带用户接入信息；根据宽带用户接入信息，确定目标设备的标识信息。实现时，可以根据宽带用户接入信息，查找到对应的目标设备 以及查找到的目标设备上报的标识信息，进而确定出目标设备的标识信息。
本申请实施例中，在采用类别标识信息标识目标设备时，对于同一类别的目标设备，可以通过类别标识信息识别对应的一个报文解析插件，此时，对于同一类别的目标设备，可以共用一个报文解析插件；在采用唯一标识信息标识目标设备时，报文解析插件与目标设备一一对应。
本申请实施例中，报文解析插件可以是由每个厂商提供的具有解析私有格式数据能力的服务模块，实际实施时，报文解析插件可以接收控制面设备发送的厂商定义的私有格式数据，可以根据自身报文解析插件所属厂商的标识信息，解析自身能够识别的私有格式数据，并可以将解析结果返回给控制面设备。
控制面设备向报文解析插件发送的报文可以包含多个厂商的私有格式数据，因而，一个报文解析插件接收的报文可以包括多个不同厂商的私有格式数据，例如，在实施时，当控制面设备向所选择的报文解析插件发送所述至少一种私有格式数据后，报文解析插件接收到至少一种私有格式数据，然后，可以对至少一种私有格式数据中能够解析的私有格式数据进行解析，得到解析后数据；报文解析插件可以将解析后数据发送到控制面设备。
一实施例中，当控制面设备接收到包含多个不同厂商的私有格式数据的报文时，可以将包含多个不同厂商的私有格式数据的报文发送至一个报文解析插件；报文解析插件接收到包含多个不同厂商的私有格式数据的报文，可以根据自身的标识信息对包含多个不同厂商的私有格式数据的报文进行过滤处理，从而，针对自身能够解析的私有格式数据进行解析，进而，得出解析后数据。
实际应用中，在一个示例中，报文解析插件与控制面设备之间的信号传输通道可以是独立设置的信号传输通道。例如，当报文解析插件独立于转发面设备部署时，报文解析插件与控制面设备之间的信号传输通道可以是独立设置的信号传输通道。在另一个示例中，控制面设备与报文解析插件之间的信号传输通道、以及控制面设备与转发面设备之间的通道为合一部署的通道，也就是说，控制面设备与报文解析插件之间的信号传输通道可以共享控制面设备与转发面设备之间的信号传输通道。例如，报文解析插件部署于转发面设备出时，控制面设备与报文解析插件之间的信号传输通道、以及控制面设备与转发面设备之间的信号传输通道为合一部署的通道。
一实施例中，为了选择与所确定的目标设备的标识信息匹配的报文解析插件，需要预先建立目标设备的标识信息与报文解析插件标识信息的对应关系。这样，当控制面设备接收到报文后，可以根据上述对应关系，选择与所确定的目标设备的标识信息匹配的报文解析插件。
对于建立上述对应关系的实现方式，示例性地，可以接收多个目标设备上报的标识信息、以及多个报文解析插件上报的标识信息；然后，根据多个目标设备上报的标识信息、以及多个报文解析插件上报的标识信息，建立目标设备的标识信息与报文解析插件标识信息的对应关系。
实际应用中，报文解析插件可以通过多个厂商共同遵守的通信协议向控制面设备上报标识信息。
本实施例中，一个目标设备上报的标识信息与一个报文解析插件上报的标识信息相同或相匹配时，可以在相应的目标设备的标识信息与报文解析插件标识信息间，建立对应关系；例如，第i个目标设备上报的标识信息与第j个报文解析插件上报的标识信息相同或匹配时，可以认为第i个目标设备的标识信息与第j个报文解析插件的标识信息相对应。
作为一种实现方式，每个目标设备上报的标识信息包括对应目标设备所属厂商的ID，或者，每个目标设备上报的标识信息包括对应目标设备所属厂商的ID和对应目标设备的ID。
作为一种实现方式，每个报文解析插件上报的标识信息包括对应报文解析插件所属厂商的ID，或者，每个报文解析插件上报的标识信息包括对应报文解析插件所属厂商的ID和目标设备的ID。
一实施例中，在建立目标设备的标识信息与报文解析插件标识信息的对应关系后，接收到新部署的目标设备上报的标识信息、以及新部署的报文解析插件上报的标识信息时，根据上述新部署的目标设备上报的标识信息、以及新部署的报文解析插件上报的标识信息，更新上述对应关系。
实际实施时，在确定目标设备的标识信息后，可以根据上述对应关系，判断是否能查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件；如果能查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件，则选择查找到的报文解析插件作为与所确定的目标设备的标识信息匹配的报文解析插件，如果不能查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件，则判断是否能查找到与所确定的目标设备的类别标识信息匹配的报文解析插件。
如果能查找到与所确定的目标设备的类别标识信息匹配的报文解析插件，则选择查找到的报文解析插件作为与所确定的目标设备的标识信息匹配的报文解析插件；如果不能查找到与所确定的目标设备的类别标识信息匹配的报文解析插件，则可以忽略该第一报文。
对于报文解析插件的部署方式，在一个示例中，报文解析插件的部署方式 为：独立于转发面设备进行部署，例如，报文解析插件以微服务形式独立部署；在另一个示例中，报文解析插件的部署方式为：部署在转发面设备处。
步骤2030：根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。
实际应用中，当上述第一报文为针对宽带接入认证请求的认证响应报文时，控制面设备可以根据解析后数据、以及控制面设备对上述第一报文的解析结果，得到宽带用户授权信息(目标设备需要的私有数据)，然后，可以将宽带用户授权信息发送至目标设备，目标设备可以根据上述宽带用户授权信息确定对所述第二报文的处理方式。一实施例中，目标设备可以将上述宽带用户授权信息写入用户转发表，然后，可以根据用户转发表处理宽带用户访问网站的报文。
示例性地，对用于访问网站的第二报文的处理方式可以为转发或其他处理方式。
实际应用中，控制面设备可以通过多个厂商共同遵守的通信协议，将宽带用户授权信息下发到对应的目标设备。
实际应用中，步骤2010至步骤2030可以由上述控制面设备中的处理器实现，上述处理器可以为特定用途集成电路(Application Specific Integrated Circuit，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理装置(Digital Signal Processing Device，DSPD)、可编程逻辑装置(Programmable Logic Device，PLD)、现场可编程门阵列(Field Programmable Gate Array，FPGA)、中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器中的至少一种。
本申请实施例提供一种报文处理方法，通过接收到包含至少一种私有格式数据的第一报文；根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述至少一种私有格式数据，接收来自所选择的报文解析插件的解析后数据；所述解析后数据是由所选择的报文解析插件对至少一种私有格式数据进行解析后得出的；根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。如此，采用本申请实施例的技术方案，利用报文插件可以兼容实现不同厂商私有格式数据的解析。
本申请实施例的报文处理方法还可以用图3和图4进行说明，图3为本申请实施例提供的一种兼容不同厂商的私有格式数据解析的***组网示意图，该***可以包括集中控制点、目标设备A、目标设备B、目标设备C、解析插件A、解析插件B、解析插件C和私有格式数据源；其中，集中控制点为上述vBRAS 控制面设备，目标设备A、目标设备B和目标设备C为3个目标设备，解析插件A、解析插件B和解析插件C为3个不同的报文解析插件，示例性地，目标设备A与解析插件A对应，即，目标设备A的标识信息与解析插件A匹配；目标设备B与解析插件B对应，即，目标设备B的标识信息与解析插件B匹配；目标设备C与解析插件C对应，即，目标设备C的标识信息与解析插件C匹配。图3中，集中控制点可以分别与私有格式数据源、目标设备A、目标设备B、目标设备C、解析插件A、解析插件B和解析插件C进行通信。
图4为本申请实施例提供的另一种报文处理方法的流程图，如图3和图4所示，该流程可以包括：
步骤S0010：所有连接到集中控制点的目标设备和解析插件上报自身标识信息，本步骤可以参见图3中用字符1a、1b、1c、1d、1e和1f标记的带箭头的线条。
步骤S0020：私有格式数据源被触发向集中控制点发送包含有多种私有格式数据的报文，本步骤可以参见图3中用数字2标记的带箭头的线条。
步骤S0030：集中控制点接收到报文后，根据目标设备的标识信息，选择匹配的报文解析插件，将报文发送给所选报文解析插件进行解析，本步骤可以参见图3中用数字3标记的带箭头的线条。
步骤S0040：报文解析插件将自己关注的报文正确解析后，返回解析结果(解析后数据)给集中控制点，本步骤可以参见图3中用数字4标记的带箭头的线条。
步骤S0050：集中控制点获取到报文解析插件返回的解析结果后，通过集中控制点和目标设备之间定义的多个厂商共同遵守的通信协议，将目标设备需要的私有数据下发到对应的目标设备。
本实施例中，解析结果为目标设备需要的私有数据。本步骤可以参见图3中用数字5标记的带箭头的线条。
基于图4所示的流程，集中控制点接收到包含不同厂商定义的私有格式数据时，在不了解私有格式定义(即厂商定义的私有协议)的情况下，可以正确解析出其中的私有格式数据，也就是说，本申请实施例的技术方案可以兼容实现不同厂商私有格式数据的解析。
根据上述记载的内容，可以看出，采用本申请实施例的报文处理方法，可以在vBRAS控制面和转发面分离，且vBRAS控制面集中控制和管理不同厂商生产的vBRAS转发面设备的场景下，正确解析出不同厂商自定义的私有格式数据，实现了vBRAS设备兼容已有的不同厂商提供的私有授权属性。例如，可以 在vBRAS控制面和RADIUS服务器通信时，vBRAS控制面可以正确解析RADIUS服务器返回的不同厂商自定义的私有格式数据。
一实施例中，当vBRAS转发面设备厂商为了提供特色功能和性能，需要扩展私有属性(私有协议)时，只需要独立升级厂商相关的vBRAS转发面和对应的报文解析插件，并在RADIUS服务器中添加厂商自定义的私有授权属性(私有协议)，不需要升级vBRAS控制面，保证了vBRAS控制面和其他厂商的vBRAS转发面运行稳定。
第二实施例
为了能够体现本申请的目的，在本申请第一实施例的基础上，进行举例说明。
下面对本申请第二实施例的组网***进行说明。
集中控制点是vBRAS控制面，通过开放网络基金会(Open Networking Foundation，ONF)定义的开流(OpenFlow)协议，vBRAS控制面集中控制和管理vBRAS转发面，它支持微服务架构，支持多个厂商以微服务的形式提供私有扩展功能；通过RESTFUL接口，vBRAS控制面和这些厂商提供的报文解析插件微服务对接；vBRAS控制面和多个厂商提供的报文解析插件微服务部署在由X86服务器和交换机构建的数据中心虚拟化平台上。
私有格式数据源是RADIUS服务器，RADIUS服务器根据国际互联网工程任务组(The Internet Engineering Task Force，IETF)定义的RADIUS协议，发送多个厂商定义的私有扩展属性到vBRAS控制面；所述私有扩展属性是RADIUS协议定义的26号属性，即Vendor-Specific属性；RADIUS协议报文中的每个Vendor-Specific属性都包含了厂商标识Vendor-ID和厂商扩展的私有子属性。
报文解析插件是由厂商提供的一种微服务，支持识别和解析厂商相关的Vendor-Specific属性，可以通过RESTFUL接口，接收vBRAS控制面发送的Vendor-Specific属性信息，解析属于本厂商定义的Vendor-Specific属性，并将解析结果作为应答发送给vBRAS控制面。
目标设备是vBRAS控制面集中控制和管理的vBRAS转发面设备，通过OpenFlow协议定义的实验者(Experimenter)消息，vBRAS转发面可以向vBRAS控制面上报自身的标识符和接收vBRAS控制面下发的授权信息。
硬件模块部分包括：X86服务器和BRAS设备。
图5为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图，如图5所示，vBRAS控制面(厂商B)是由厂商B提供的控制面设备，厂商A解析插件和厂商C解析插件分别表示由厂商A和厂商C提供的报文解析插件，vBRAS转发面1(厂商A)和vBRAS转发面2(厂商A)分别表示由厂商A提供的两个vBRAS转发面设备，vBRAS转发面(厂商B)和vBRAS转发面(厂商C)分别表示由厂商B和厂商C提供的两个vBRAS转发面设备。
vBRAS控制面(厂商B)，支持通过RESTFUL接口和其他厂商提供的报文解析插件微服务对接；其他厂商的vBRAS转发面设备为了能够和厂商B提供的vBRAS控制面对接，除了遵守vBRAS控制面和vBRAS转发面之间的通信协议之外，还需要提供和vBRAS控制面对接的报文解析插件，提供的报文解析插件能够解析RADIUS服务器发送到vBRAS控制面的厂商自定义的私有格式数据；同一厂商提供的vBRAS转发面功能相同的情况下，对应的报文解析插件功能也相同，因此，同一厂商提供的多个vBRAS转发面可以共享同一个报文解析插件，即每个厂商只需要部署一个报文解析插件和vBRAS控制面对接，简化了报文解析插件的部署操作，也节省了报文解析插件对数据中心资源(CPU核数，内存，存储，网络等资源)的占用。例如，vBRAS转发面1(厂商A)和vBRAS转发面2(厂商A)可以共享厂商A解析插件。
本实施例中，vBRAS控制面以厂商标识Vendor-ID作为目标设备和报文解析插件的标识信息，图6为本申请实施例提供的另一种报文处理方法的流程图，vBRAS控制面、RADIUS服务器、vBRAS转发面以及解析插件之间的工作流程见图6所示。
本申请第二实施例中，报文处理方法的流程可以包括：
步骤5010：部署vBRAS控制面设备，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动厂商B提供的vBRAS控制面设备。
步骤5020：部署厂商A解析插件，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动厂商A解析插件。
步骤5030：部署厂商C解析插件，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动厂商C解析插件。
步骤5040：配置vBRAS控制面设备和RADIUS服务器的连接，包括配置RADIUS服务器的网际互连协议(Internet Protocol，IP)地址和RADIUS协议端口号。
步骤5050：配置厂商A、厂商B和厂商C的所有vBRAS转发面设备连接到vBRAS控制面设备，包括建立vBRAS转发面到vBRAS控制面的虚拟扩展局 域网(Virtual Extensible Local Area Network，VxLAN)隧道和建立vBRAS转发面到vBRAS控制面的OpenFlow连接。
步骤5060：配置厂商A解析插件向vBRAS控制面注册，通过统一资源标识信息(Uniform Resource Identifier，URI)，厂商A解析插件向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)。本步骤可以参见图5中用字符1e标记的带箭头的线条以及图6中的步骤(1e)。
步骤5070：配置厂商C解析插件向vBRAS控制面注册，通过URI，厂商C解析插件向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)。本步骤可以参见图5中用字符1f标记的带箭头的线条以及图6中的步骤(1f)。
步骤5080：通过OpenFlow协议，vBRAS转发面设备向vBRAS控制面主动上报自身的标识信息，即厂商标识Vendor-ID。本步骤可以参见图5中分别用字符1a、1b、1c、1d标记的带箭头的线条以及图6中的步骤(1a)、(1b)、(1c)和(1d)。
步骤5090：宽带用户开始上线，vBRAS转发面1(厂商A)接收到宽带用户发送的基于以太网的点对点通讯协议(Point-to-Point Protocol Over Ethernet，PPPoE)接入请求报文，通过VxLAN隧道，将所接收到的原始PPPoE接入请求报文和对应的接收接口信息(例如，接口Fei-2/1/0/2)上送到vBRAS控制面。本步骤可以参见图5中用数字2标记的带箭头的线条以及图6中的步骤(2)。
步骤5100：vBRAS控制面设备接收到PPPoE接入请求报文后，根据PPPoE协议，负责完成PPPoE接入请求报文处理和应答。通过PPPoE接入协议报文交互，vBRAS控制面设备获取到宽带用户的用户名信息。vBRAS控制面设备将用户名信息写入RADIUS协议定义的接入-请求(Access-Request)认证报文中，向RADIUS服务器发送Access-Request认证请求。本步骤可以参见图5中用数字3标记的带箭头的线条以及图6中的步骤(3)。
步骤5110：RADIUS服务器接收到Access-Request认证请求后，根据认证请求中携带的用户名信息进行认证，如果认证成功，则发送接入-同意(Access-Accept)认证响应给vBRAS控制面设备，在Access-Accept认证响应中可以携带多个Vendor-Specific属性。本步骤可以参见图5中用数字4标记的带箭头的线条以及图6中的步骤(4)。
步骤5120：vBRAS控制面设备接收到Access-Accept认证响应报文后，根据报文中的Identifier域值，查找到对应的宽带用户接入信息，包括宽带接入接口信息，例如，接口Fei-2/1/0/2。通过宽带接入接口信息，vBRAS控制面设备 获取到对应的vBRAS转发面设备及其上报的标识符，即厂商标识(Vendor-ID)。vBRAS控制面设备解析Access-Accept认证响应报文中携带的属性(Attributes)信息，如果Access-Accept认证响应报文中携带RADIUS协议定义的Vendor-Specific属性，vBRAS控制面设备则根据上述对应的vBRAS转发面标识信息，即厂商标识(Vendor-ID)，查找匹配的报文解析插件。如果查找到对应的报文解析插件，vBRAS控制面设备根据报文解析插件注册的通信地址，通过RESTFUL接口，将上述Access-Accept认证响应报文中的所有Vendor-Specific属性发送给对应的报文解析插件做处理。本步骤可以参见图5中用数字5标记的带箭头的线条以及图6中的步骤(5)。
步骤5130：厂商A解析插件通过RESTFUL接口接收到vBRAS控制面设备发来的Vendor-Specific属性，先判断Vendor-Specific属性中的Vendor-ID值是否与本解析插件的厂商标识(Vendor-ID)一致，如果Vendor-ID不一致，则放弃解析，如果Vendor-ID值一致，则按照厂商A的定义，对Vendor-Specific A的厂商标识为4097，当厂商A解析插件接收到了vBRAS控制面设备发送的3个Vendor-Specific属性，3个Vendor-Specific属性携带的Vendor-ID值分别为4096，4097和4098，厂商A解析插件只解析携带的Vendor-ID值为4097的Vendor-Specific属性；根据厂商A定义的私有数据格式，厂商A解析插件解析出Vendor-ID值为4097的Vendor-Specific属性中包含的所有子属性。当厂商A解析插件完成所有Vendor-Specific属性及其包含的子属性的解析后，通过响应邮寄(POST)请求方式，将vBRAS控制面需要的子属性，发送给vBRAS控制面设备。本步骤可以参见图5中用数字6标记的带箭头的线条以及图6中的步骤(6)。
步骤5140：vBRAS控制面设备从RESTFUL接口接收到报文解析插件发送的Vendor-Specific属性的解析结果。通过报文解析插件返回的解析结果和自身对Access-Accept认证响应报文中携带的其他属性的解析，vBRAS控制面设备获取到宽带用户的授权信息。
步骤5150：vBRAS控制面设备将需要下发到vBRAS转发面的授权信息转换成vBRAS控制面和转发面之间通信协议定义的属性后，通过vBRAS控制面(厂商B)和vBRAS转发面1(厂商A)之间建立的OpenFlow通道，采用类型长度属性值(Type Length Value，TLV)方式，将宽带用户的授权信息发送到vBRAS转发面1(厂商A)。所述TLV方式，即授权信息中的每个属性值按照属性类型(Type)，属性长度(Length)和属性值(Value)方式传递。本步骤可以参见图5中用数字7标记的带箭头的线条以及图6中的步骤(7)。
步骤5160：根据vBRAS控制面和转发面之间的通信协议定义，vBRAS转 发面设备接收到宽带用户授权信息，将授权信息写入用户转发表。vBRAS转发面设备后续根据用户转发表处理和转发宽带用户访问网站的报文。
第三实施例
为了能够体现本申请的目的，在本申请第一实施例的基础上，进行举例说明。
下面对本申请第三实施例的组网***进行说明。
集中控制点是vBRAS控制面，vBRAS控制面集中控制和管理物理设备形态和虚拟化形态的vBRAS转发面；所述物理设备形态的vBRAS转发面设备包含的关键器件是专用处理器(例如NP，FPGA，ASIC等)，通过专用处理器处理和转发大流量宽带接入用户业务报文；所述虚拟化形态的vBRAS转发面设备包含的关键器件是通用X86处理器，设置为处理和转发小流量宽带接入用户业务报文。本实施例描述了vBRAS控制面和vBRAS转发面之间采用一种控制面和用户面分离协议(Control-plane and User-plane Separation Protocol，CUSP)，CUSP是vBRAS控制面和vBRAS转发面之间定义的多个厂商共同遵守的基于传输控制协议(Transmission Control Protocol，TCP)的通信协议。vBRAS控制面由第三方(非vBRAS转发面设备厂商)提供，部署在由X86服务器和交换机构建的数据中心虚拟化平台上，运行在虚拟计算机内。
私有格式数据源是RADIUS服务器，RADIUS服务器根据IETF定义的RADIUS协议，发送多个厂商定义的私有扩展属性到vBRAS控制面；所述私有扩展属性是RADIUS协议定义的26号属性，即Vendor-Specific属性。RADIUS协议报文中的每个Vendor-Specific属性都包含了厂商标识Vendor-ID和厂商扩展的私有子属性。
报文解析插件是由vBRAS转发面设备厂商提供的一个软件模块，能够识别和解析厂商相关的Vendor-Specific属性，它和虚拟化形态的vBRAS转发面部署在一起，通过所述CUSP，报文解析插件向vBRAS控制面注册和上报自身的标识信息，接收vBRAS控制面发送的Vendor-Specific属性信息，解析属于本厂商定义的Vendor-Specific属性，并将解析结果作为应答发送给vBRAS控制面。
目标设备是vBRAS控制面集中控制和管理的vBRAS转发面设备，包括物理设备形态的vBRAS转发面设备和虚拟化形态的vBRAS转发面设备。通过所述CUSP，vBRAS转发面向vBRAS控制面上报自身的标识信息和接收vBRAS控制面下发的授权信息。
硬件模块部分包括：X86服务器和BRAS设备。
图7为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图，如图7所示，vBRAS控制面(非厂商)由第三方(非vBRAS转发面设备厂商)提供，厂商A转发面(X86)、厂商B转发面(X86)和厂商C转发面(X86)分别表示厂商A、厂商B和厂商C提供的虚拟化形态的vBRAS转发面设备，厂商A转发面(X86)、厂商B转发面(X86)和厂商C转发面(X86)均提供相应的报文解析插件(参见图7中的解析插件)；厂商A vBRAS转发面(NP)、厂商B vBRAS转发面(NP)和厂商C vBRAS转发面(NP)分别表示厂商A、厂商B和厂商C提供的物理设备形态的vBRAS转发面设备；厂商A转发面(X86)、厂商B转发面(X86)和厂商C转发面(X86)均可以与vBRAS控制面(非厂商)进行通信，厂商A vBRAS转发面(NP)、厂商B vBRAS转发面(NP)和厂商C vBRAS转发面(NP)均可以通过数据中心网关与vBRAS控制面(非厂商)进行通信，RADIUS服务器可以与vBRAS控制面(非厂商)和数据中心网关进行通信。
vBRAS控制面(非厂商)可以通过所述CUSP控制和管理vBRAS转发面设备，而vBRAS转发面设备包含物理设备形态的vBRAS转发面设备和虚拟化形态的vBRAS转发面设备。其中物理设备形态的vBRAS转发面设备部署在城域网边缘，用于大流量用户接入服务，例如高速上网(High Speed Internet，HSI)，4K超高清网络电视(Internet Protocol Television，IPTV)，视频聊天，实时游戏等服务。虚拟化形态的vBRAS转发面设备部署在数据中心，用于小流量用户接入服务，例如网络电话(Voice over Internet Protocol，VoIP)，宽带论坛技术报告069中定义的网管协议(Technical Report 069，TR069)等服务。报文解析插件作为一个软件模块和自身厂商提供的虚拟化形态的vBRAS转发面部署在一起，不需要独立分配额外资源(包括CPU核数，内存，存储，网络等资源)。并且，报文解析插件也是通过所述CUSP向vBRAS控制面上报自身标识信息，协议处理统一，使得vBRAS控制面协议开发工作量减少。
本实施例中，vBRAS控制面以厂商标识Vendor-ID作为vBRAS转发面和报文解析插件的标识信息，vBRAS控制面、RADIUS服务器、vBRAS转发面以及解析插件之间的工作流程见图7所示。
本申请第三实施例中，报文处理方法的流程可以包括：
步骤7010：部署vBRAS控制面设备，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动第三方(非vBRAS转发面设备厂商)提供的vBRAS控制面设备。
步骤7020：部署多个厂商提供的虚拟化形态的vBRAS转发面，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动多个厂商提供的虚拟化形态 的vBRAS转发面软件和报文解析插件。
步骤7030：配置vBRAS控制面设备和RADIUS服务器的连接，包括配置RADIUS服务器的IP地址和RADIUS协议端口号。
步骤7040：配置厂商A、厂商B和厂商C的所有vBRAS转发面设备连接到vBRAS控制面；vBRAS转发面设备包括物理设备形态的vBRAS转发面设备和虚拟化形态的vBRAS转发面设备。上述配置过程包括建立vBRAS转发面到vBRAS控制面的VxLAN隧道和建立vBRAS转发面到vBRAS控制面的CUSP连接。
步骤7050：配置厂商A的报文解析插件通过所述CUSP向vBRAS控制面注册。厂商A的报文解析插件向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)，本步骤可以参见图7中用字符1d标记的带箭头的线条。
步骤7060：配置厂商B的报文解析插件通过所述CUSP向vBRAS控制面注册。厂商B的报文解析插件向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)，本步骤可以参见图7中用字符1e标记的带箭头的线条。
步骤7070：配置厂商C的报文解析插件通过所述CUSP向vBRAS控制面注册。厂商C的报文解析插件向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)，本步骤可以参见图7中用字符1f标记的带箭头的线条。
步骤7080：通过CUSP，厂商A、厂商B和厂商C的所有vBRAS转发面设备向vBRAS控制面主动上报自身的标识信息，即厂商标识(Vendor-ID)。vBRAS转发面设备包括物理设备形态的vBRAS转发面设备和虚拟化形态的vBRAS转发面设备，本步骤可以参见图7中分别用字符1a、1b、1c、1d、1e和1f标记的带箭头的线条。
步骤7090：宽带用户开始上线，vBRAS转发面设备(举例，厂商A物理设备形态的vBRAS转发面设备)接收到宽带用户发送的PPPoE接入请求报文，vBRAS转发面通过VxLAN隧道，将所接收到的原始PPPoE接入请求报文和对应的接收接口信息(例如，接口Fei-2/1/0/2)上送到vBRAS控制面，本步骤可以参见图7中用数字2标记的带箭头的线条。
步骤7100：vBRAS控制面设备接收到PPPoE接入请求报文后，根据PPPoE协议，负责完成PPPoE接入请求报文处理和应答。通过PPPoE接入协议报文交互，vBRAS控制面设备获取到宽带用户的用户名信息。vBRAS控制面设备将用户名信息写入RADIUS协议定义的Access-Request认证报文中，向RADIUS服务器发送Access-Request认证请求，本步骤可以参见图7中用数字3标记的带箭头的线条。
步骤7110：RADIUS服务器接收到Access-Request认证请求后，根据认证请求中携带的用户名信息进行认证，如果认证成功，则发送Access-Accept认证响应给vBRAS控制面，本步骤可以参见图7中用数字4标记的带箭头的线条。
步骤7120：vBRAS控制面设备接收到Access-Accept认证响应报文后，根据报文中的Identifier域值，查找到对应的宽带用户接入信息，包括宽带接入接口信息，例如，接口Fei-2/1/0/2。通过宽带接入接口信息，vBRAS控制面设备获取到对应的vBRAS转发面设备及其上报的标识信息，即厂商标识(Vendor-ID)。vBRAS控制面设备解析Access-Accept认证响应报文中携带的属性(Attributes)信息，如果Access-Accept认证响应报文中携带RADIUS协议定义的Vendor-Specific属性，vBRAS控制面设备则根据上述对应的vBRAS转发面标识信息，即厂商标识(Vendor-ID)，查找匹配的报文解析插件。如果查找到对应的报文解析插件，vBRAS控制面根据报文解析插件注册的通信地址，通过CUSP连接，将上述Access-Accept认证响应报文中的所有Vendor-Specific属性发送给对应的报文解析插件做处理，本步骤可以参见图7中用数字5标记的带箭头的线条。
步骤7130：厂商A提供的报文解析插件接收到vBRAS控制面发来的Vendor-Specific属性，先判断Vendor-Specific属性中的Vendor-ID值是否与本报文解析插件的厂商标识(Vendor-ID)一致，如果Vendor-ID不一致，则放弃解析，如果Vendor-ID值一致，则按照厂商A的定义，对Vendor-Specific属性进行解析。举例，厂商A的厂商标识为4097，当厂商A的报文解析插件接收到了vBRAS控制面发送的3个Vendor-Specific属性，3个Vendor-Specific属性携带的Vendor-ID值分别为4096，4097和4098，厂商A的报文解析插件只解析携带的Vendor-ID值为4097的Vendor-Specific属性。根据厂商A定义的私有数据格式，厂商A的报文解析插件解析出Vendor-ID值为4097的Vendor-Specific属性中包含的所有子属性。当厂商A的报文解析插件完成所有Vendor-Specific属性及其包含的子属性的解析后，通过vBRAS转发面和控制面所建立的CUSP连接，将vBRAS控制面需要的子属性，发送给vBRAS控制面，本步骤可以参见图7中用数字6标记的带箭头的线条。
步骤7140：vBRAS控制面设备接收到报文解析插件发送的Vendor-Specific属性的解析结果。通过报文解析插件返回的解析结果和自身对Access-Accept认证响应报文中携带的其他属性的解析，vBRAS控制面设备获取到宽带用户的授权信息。
步骤7150：vBRAS控制面设备将需要下发到vBRAS转发面的授权信息转换成vBRAS控制面和转发面之间通信协议定义的属性后，通过vBRAS转发面 (厂商A物理设备形态的vBRAS转发面设备)和vBRAS控制面之间建立的CUSP连接，采用TLV方式，将宽带用户的授权信息发送到对应的vBRAS转发面。所述TLV方式，即授权信息中的每个属性值按照属性类型(Type)，属性长度(Length)和属性值(Value)方式传递，本步骤可以参见图7中分别用数字7标记的带箭头的线条。
步骤7160：根据vBRAS控制面和转发面之间的通信协议定义，vBRAS转发面设备(厂商A物理设备形态的vBRAS转发面设备)接收到宽带用户授权信息，将授权信息写入用户转发表。vBRAS转发面设备后续根据用户转发表处理和转发宽带用户访问网站的报文。
第四实施例
为了能够体现本申请的目的，在本申请第一实施例的基础上，进行举例说明。
下面对本申请第四实施例的组网***进行说明。
集中控制点是vBRAS控制面，通过所述CUSP，vBRAS控制面集中控制和管理vBRAS转发面，以及vBRAS控制面和报文解析插件之间通信。vBRAS控制面部署在由X86服务器和交换机构建的数据中心虚拟化平台上。
私有格式数据源是RADIUS服务器，RADIUS服务器根据IETF定义的RADIUS协议，发送多个厂商定义的私有扩展属性到vBRAS控制面。所述私有扩展属性是RADIUS协议定义的26号属性，即Vendor-Specific属性。RADIUS协议报文中的每个Vendor-Specific属性都包含了厂商标识Vendor-ID和厂商扩展的私有子属性。
报文解析插件是由vBRAS转发面设备厂商提供的一个软件模块，能够识别和解析厂商相关的Vendor-Specific属性。它和vBRAS转发面设备部署在一起，通过所述CUSP协议，解析插件向vBRAS控制面注册和上报自身的标识信息，接收vBRAS控制面发送的Vendor-Specific属性信息，解析属于本厂商定义的Vendor-Specific属性，并将解析结果作为应答发送给vBRAS控制面。
目标设备是vBRAS控制面集中控制和管理的vBRAS转发面设备。通过所述CUSP，vBRAS转发面向vBRAS控制面上报自身的标识信息和接收vBRAS控制面下发的授权信息。
硬件模块部分包括：X86服务器和BRAS设备。
图8为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的系 统组网示意图，如图8所示，vBRAS控制面(非厂商)由第三方(非vBRAS转发面设备厂商)提供，厂商A vBRAS转发面1和厂商A vBRAS转发面2分别表示厂商A提供的两个vBRAS转发面设备，厂商B vBRAS转发面和厂商C vBRAS转发面分别表示厂商B和厂商C提供的两个vBRAS转发面设备；厂商A vBRAS转发面1、厂商A vBRAS转发面、厂商B vBRAS转发面和厂商C vBRAS转发面均提供相应的报文解析插件(参见图8中的解析插件)；厂商A vBRAS转发面1、厂商A vBRAS转发面、厂商B vBRAS转发面、厂商C vBRAS及其相应的解析插件均可以与vBRAS控制面(非厂商)进行通信，vBRAS控制面(非厂商)还可以与RADIUS服务器进行通信。
vBRAS控制面(非厂商)通过CUSP控制和管理vBRAS转发面设备；报文解析插件作为一个软件模块和自身厂商提供的vBRAS转发面设备部署在一起，报文解析插件和vBRAS转发面设备存在一一对应关系，vBRAS转发面设备的关闭，不会影响针对其他vBRAS转发面设备的私有属性解析，维护方便灵活。并且，报文解析插件也是通过CUSP向vBRAS控制面上报自身标识信息，协议处理统一，使得vBRAS控制面协议开发工作量减少。
vBRAS控制面以厂商标识(Vendor-ID)和vBRAS转发面设备标识信息作为识别vBRAS转发面设备和报文解析插件的标识信息，vBRAS控制面、RADIUS服务器、vBRAS转发面以及报文解析插件之间的工作流程可参考图8。
本申请第四实施例中，报文处理方法的流程可以包括：
步骤8010：部署vBRAS控制面设备，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动第三方(非vBRAS转发面设备厂商)提供的vBRAS控制面。
步骤8020：配置vBRAS控制面设备和RADIUS服务器的连接，包括配置RADIUS服务器的IP地址和RADIUS协议端口号。
步骤8030：配置厂商A、厂商B和厂商C的所有vBRAS转发面设备连接到vBRAS控制面。上述配置过程包括建立vBRAS转发面到vBRAS控制面的VxLAN隧道和建立vBRAS转发面到vBRAS控制面的CUSP连接。
步骤8040：配置厂商A的报文解析插件通过CUSP向vBRAS控制面注册。厂商A的报文解析插件向vBRAS控制面提供自身信息，包括通信地址、厂商标识(Vendor-ID)和对应的vBRAS转发面设备标识信息，本步骤可以参见图8中分别用字符1a和1b标记的带箭头的线条。
步骤8050：配置厂商B的报文解析插件通过CUSP向vBRAS控制面注册。厂商B的报文解析插件向vBRAS控制面提供自身信息，包括通信地址、厂商标 识(Vendor-ID)和对应的vBRAS转发面设备标识信息，本步骤可以参见图8中用字符1c标记的带箭头的线条。
步骤8060：配置厂商C的报文解析插件通过CUSP向vBRAS控制面注册。厂商C的报文解析插件向vBRAS控制面提供自身信息，包括通信地址、厂商标识(Vendor-ID)和对应的vBRAS转发面设备标识信息，本步骤可以参见图8中用字符1d标记的带箭头的线条。
步骤8070：通过CUSP协议，厂商A、厂商B和厂商C的所有vBRAS转发面设备向vBRAS控制面主动上报自身的标识信息，即设备标识信息和厂商标识(Vendor-ID)，本步骤可以参见图8中分别用字符1a、1b、1c和1d标记的带箭头的线条。
步骤8080：宽带用户开始上线，vBRAS转发面设备(举例，厂商A的vBRAS转发面1设备)接收到宽带用户发送的动态主机设置协议(Dynamic Host Configuration Protocol，DHCP)接入请求报文，vBRAS转发面通过VxLAN隧道，将所接收到的原始DHCP接入请求报文和对应的接收接口信息(例如，接口Fei-2/1/0/2)上送到vBRAS控制面设备，本步骤可以参见图8中用数字2标记的带箭头的线条。
步骤8090：vBRAS控制面设备接收到DHCP接入请求报文后，根据DHCP协议，负责完成DHCP接入请求报文处理和应答。通过DHCP接入协议报文交互，vBRAS控制面设备通过DHCP报文中的选择(Option)选项获取到宽带用户的用户名信息。vBRAS控制面设备将用户名信息写入RADIUS协议定义的Access-Request认证报文中，向RADIUS服务器发送Access-Request认证请求，本步骤可以参见图8中用数字3标记的带箭头的线条。
步骤8100：RADIUS服务器接收到Access-Request认证请求后，根据认证请求中携带的用户名信息进行认证，如果认证成功，则发送Access-Accept认证响应给vBRAS控制面设备，本步骤可以参见图8中用数字4标记的带箭头的线条。
步骤8110：vBRAS控制面设备接收到Access-Accept认证响应报文后，根据报文中的Identifier域值，查找到对应的宽带用户接入信息，包括宽带接入接口信息，例如，接口Fei-2/1/0/2。通过宽带接入接口信息，vBRAS控制面设备获取到对应的vBRAS转发面设备及其上报的标识信息，即厂商标识(Vendor-ID)和设备标识信息。vBRAS控制面设备解析Access-Accept认证响应报文中携带的属性(Attributes)信息，如果Access-Accept认证响应报文中携带RADIUS协议定义的Vendor-Specific属性，vBRAS控制面设备则根据上述对应的vBRAS转发面标识信息，即厂商标识(Vendor-ID)和设备标识信息，查找匹配的报文解 析插件。如果查找到对应的报文解析插件，vBRAS控制面设备根据报文解析插件注册的通信地址，通过CUSP连接，将上述Access-Accept认证响应报文中的所有Vendor-Specific属性发送给对应的报文解析插件做处理，本步骤可以参见图8中用数字5标记的带箭头的线条。
步骤8120：厂商A提供的报文解析插件接收到vBRAS控制面设备发来的Vendor-Specific属性，先判断Vendor-Specific属性中的Vendor-ID值是否与本报文解析插件的厂商标识(Vendor-ID)一致，如果Vendor-ID不一致，则放弃解析，如果Vendor-ID值一致，则按照厂商A的定义，对Vendor-Specific属性进行解析。举例，厂商A的厂商标识为4097，当厂商A的报文解析插件接收到了vBRAS控制面发送的3个Vendor-Specific属性，3个Vendor-Specific属性携带的Vendor-ID值分别为4096，4097和4098，厂商A的报文解析插件只解析携带的Vendor-ID值为4097的Vendor-Specific属性。根据厂商A定义的私有数据格式，厂商A的报文解析插件解析出Vendor-ID值为4097的Vendor-Specific属性中包含的所有子属性。当厂商A的报文解析插件完成所有Vendor-Specific属性及其包含的子属性的解析后，通过vBRAS转发面和控制面所建立的CUSP连接，将vBRAS控制面需要的子属性，发送给vBRAS控制面设备，本步骤可以参见图8中用数字6标记的带箭头的线条。
步骤8130：vBRAS控制面设备接收到报文解析插件发送的Vendor-Specific属性的解析结果。通过报文解析插件返回的解析结果和自身对Access-Accept认证响应报文中携带的其他属性的解析，vBRAS控制面设备获取到宽带用户的授权信息。
步骤8140：vBRAS控制面设备将需要下发到vBRAS转发面的授权信息转换成vBRAS控制面和转发面之间通信协议定义的属性后，通过vBRAS转发面(厂商A的vBRAS转发面1设备)和vBRAS控制面之间建立的CUSP连接，采用TLV方式，将宽带用户的授权信息发送到对应的vBRAS转发面。所述TLV方式，即授权信息中的每个属性值按照属性类型(Type)，属性长度(Length)和属性值(Value)方式传递，本步骤可以参见图8中用数字7标记的带箭头的线条。
步骤8150：根据vBRAS控制面和转发面之间的通信协议定义，vBRAS转发面设备(厂商A vBRAS转发面1)接收到宽带用户授权信息，将授权信息写入用户转发表。vBRAS转发面设备后续根据用户转发表处理和转发宽带用户访问网站的报文。
第五实施例
为了能够体现本申请的目的，在本申请第一实施例的基础上，进行举例说明。
下面对本申请第五实施例的组网***进行说明。
集中控制点是vBRAS控制面，通过所述CUSP，vBRAS控制面集中控制和管理vBRAS转发面，它支持微服务架构，支持多个厂商以微服务的形式提供私有扩展功能。通过RESTFUL接口，vBRAS控制面和这些厂商提供的报文解析插件微服务对接。vBRAS控制面和多个厂商提供的报文解析插件微服务部署在由X86服务器和交换机构建的数据中心虚拟化平台上。
私有格式数据源是RADIUS服务器，RADIUS服务器根据IETF定义的RADIUS协议，发送多个厂商定义的私有扩展属性到vBRAS控制面。所述私有扩展属性是RADIUS协议定义的26号属性，即Vendor-Specific属性。RADIUS协议报文中的每个Vendor-Specific属性都包含了厂商标识Vendor-ID和厂商扩展的私有子属性。
报文解析插件是由厂商提供的一种微服务，支持识别和解析厂商相关的Vendor-Specific属性。通过RESTFUL接口，它接收vBRAS控制面设备发送的Vendor-Specific属性信息，解析属于本厂商定义的Vendor-Specific属性，并将解析结果作为应答发送给vBRAS控制面设备。
目标设备是vBRAS控制面集中控制和管理的vBRAS转发面设备。通过所述CUSP，vBRAS转发面向vBRAS控制面上报自身的标识信息和接收vBRAS控制面下发的授权信息。
硬件模块部分包括：X86服务器和BRAS设备。
图9为本申请实施例提供的另一种兼容不同厂商的私有格式数据解析的***组网示意图，如图9所示，vBRAS控制面(非厂商)由第三方(非vBRAS转发面设备厂商)提供，vBRAS转发面1(厂商A)和vBRAS转发面2(厂商A)分别表示由厂商A提供的两个vBRAS转发面设备，vBRAS转发面(厂商B)表示由厂商B提供的vBRAS转发面设备；厂商A解析插件1和厂商A解析插件2分别表示厂商A提供的两个报文解析插件，其中，厂商A解析插件1与vBRAS转发面1(厂商A)的标识信息匹配，厂商A解析插件2与vBRAS转发面2(厂商A)的标识信息匹配，厂商B解析插件与vBRAS转发面(厂商B)的标识信息匹配；vBRAS控制面(非厂商)可以分别与vBRAS转发面1(厂商A)、vBRAS转发面2(厂商A)、vBRAS转发面(厂商B)、厂商A解析插件1、厂商A解析插件2、厂商B解析插件和RADIUS服务器进行通信。
BRAS控制面是由第三方(非vBRAS转发面设备厂商)提供，它支持通过 RESTFUL接口和其他厂商提供的解析插件微服务对接。厂商提供的vBRAS转发面设备为了能够和vBRAS控制面对接，除了遵守vBRAS控制面和vBRAS转发面之间的通信协议之外，还需要提供和vBRAS控制面对接的报文解析插件，提供的报文解析插件能够解析RADIUS服务器发送到vBRAS控制面的厂商自定义的私有格式数据。初始部署时，由于同一厂商提供的vBRAS转发面功能相同，对应的报文解析插件功能也相同，因此，同一厂商提供的多个vBRAS转发面可以共享同一个报文解析插件，即每个厂商只需要部署一个报文解析插件和vBRAS控制面对接，vBRAS控制面以厂商标识(Vendor-ID)作为识别vBRAS转发面设备和报文解析插件的标识信息。后期，在现有部署环境上，vBRAS转发面设备扩容升级，原有的报文解析插件不能满足新设备所需的私有格式数据解析，需要提供新报文解析插件和vBRAS控制面对接，vBRAS控制面以厂商标识(Vendor-ID)和vBRAS转发面设备标识信息作为识别新vBRAS转发面设备和新报文解析插件的标识信息，新vBRAS转发面设备扩容升级不影响原设备正常运行。
vBRAS控制面既支持以厂商标识Vendor-ID作为目标设备和解析插件的标识信息，也支持以厂商标识(Vendor-ID)和vBRAS转发面设备标识信息作为目标设备和报文解析插件的标识信息。vBRAS控制面、RADIUS服务器、vBRAS转发面以及报文解析插件之间的工作流程可参考图9。
步骤9010：部署vBRAS控制面设备，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动第三方(非vBRAS转发面设备厂商)提供的vBRAS控制面设备。
步骤9020：部署厂商A解析插件1，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动厂商A解析插件1。
步骤9030：部署厂商B解析插件，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动厂商B解析插件。
步骤9040：配置vBRAS控制面设备和RADIUS服务器的连接，包括配置RADIUS服务器的IP地址和RADIUS协议端口号。
步骤9050：配置vBRAS转发面1(厂商A)和vBRAS转发面(厂商B)连接到vBRAS控制面设备，包括建立vBRAS转发面到vBRAS控制面的VxLAN隧道和建立vBRAS转发面到vBRAS控制面的CUSP连接。
步骤9060：配置厂商A解析插件1向vBRAS控制面注册，通过URI，厂商A解析插件1向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)，本步骤可以参见图9中用字符1d标记的带箭头的线条。
步骤9070：配置厂商B解析插件向vBRAS控制面注册，通过URI，厂商B解析插件向vBRAS控制面提供自身信息，包括通信地址和厂商标识(Vendor-ID)，本步骤可以参见图9中用字符1c标记的带箭头的线条。
步骤9080：通过CUSP，vBRAS转发面1(厂商A)和vBRAS转发面(厂商B)向vBRAS控制面设备主动上报自身的标识信息，即厂商标识Vendor-ID，本步骤可以参见图9中分别用字符1a和1b标记的带箭头的线条。
步骤9090：扩容升级部署厂商A解析插件2，在数据中心的云平台上新建虚机或容器，在虚机或容器内启动厂商A解析插件2。
步骤9100：配置vBRAS转发面2(厂商A)连接到vBRAS控制面设备。包括建立vBRAS转发面到vBRAS控制面的VxLAN隧道和建立vBRAS转发面到vBRAS控制面的CUSP连接。
步骤9110：配置厂商A解析插件2向vBRAS控制面注册，通过URI，厂商A解析插件2向vBRAS控制面设备提供自身信息，包括通信地址、厂商标识(Vendor-ID)和对应的vBRAS转发面设备标识信息，本步骤可以参见图9中用字符1f标记的带箭头的线条。
步骤9120：通过CUSP，vBRAS转发面2(厂商A)向vBRAS控制面设备主动上报自身的标识信息，即设备标识符和厂商标识(Vendor-ID)，本步骤可以参见图9中用字符1e标记的带箭头的线条。
步骤9130：宽带用户开始上线，vBRAS转发面2(厂商A)接收到宽带用户发送的PPPoE接入请求报文，vBRAS转发面通过VxLAN隧道，将所接收到的原始PPPoE接入请求报文和对应的接收接口信息(例如，接口Fei-2/1/0/2)上送到vBRAS控制面，本步骤可以参见图9中用数字2标记的带箭头的线条。
步骤9140：vBRAS控制面设备接收到PPPoE接入请求报文后，根据PPPoE协议，负责完成PPPoE接入请求报文处理和应答。通过PPPoE接入协议报文交互，vBRAS控制面设备获取到宽带用户的用户名信息。vBRAS控制面设备将用户名信息写入RADIUS协议定义的Access-Request认证报文中，向RADIUS服务器发送Access-Request认证请求，本步骤可以参见图9中用数字3标记的带箭头的线条。
步骤9150：RADIUS服务器接收到Access-Request认证请求后，根据认证请求中携带的用户名信息进行认证，如果认证成功，则发送Access-Accept认证响应给vBRAS控制面设备，本步骤可以参见图9中用数字4标记的带箭头的线条。
步骤9160：vBRAS控制面设备接收到Access-Accept认证响应报文后，根 据报文中的Identifier域值，查找到对应的宽带用户接入信息，包括宽带接入接口信息，例如，接口Fei-2/1/0/2。通过宽带接入接口信息，vBRAS控制面设备获取到对应的vBRAS转发面设备及其上报的标识信息，即厂商标识(Vendor-ID)和设备标识信息。vBRAS控制面设备解析Access-Accept认证响应报文中携带的属性(Attributes)信息，如果Access-Accept认证响应报文中携带RADIUS协议定义的Vendor-Specific属性，vBRAS控制面设备则根据上述对应的vBRAS转发面标识信息，即厂商标识(Vendor-ID)和设备标识信息，查找匹配的报文解析插件。如果查找到对应的报文解析插件，vBRAS控制面设备根据报文解析插件注册的通信地址，通过RESTFUL接口，将上述Access-Accept认证响应报文中的所有Vendor-Specific属性发送给对应的报文解析插件做处理，本步骤可以参见图9中用数字5标记的带箭头的线条。
步骤9170：厂商A解析插件2通过RESTFUL接口接收到vBRAS控制面设备发来的Vendor-Specific属性，先判断Vendor-Specific属性中的Vendor-ID值是否与本报文解析插件的厂商标识(Vendor-ID)一致，如果Vendor-ID不一致，则放弃解析，如果Vendor-ID值一致，则按照厂商A的定义，对Vendor-Specific A的厂商标识为4097，当厂商A解析插件2接收到了vBRAS控制面发送的3个Vendor-Specific属性，3个Vendor-Specific属性携带的Vendor-ID值分别为4096，4097和4098，厂商A解析插件2只解析携带的Vendor-ID值为4097的Vendor-Specific属性。根据厂商A定义的私有数据格式，厂商A解析插件2解析出Vendor-ID值为4097的Vendor-Specific属性中包含的所有子属性。当厂商A解析插件2完成所有Vendor-Specific属性及其包含的子属性的解析后，通过响应POST请求方式，将vBRAS控制面需要的子属性，发送给vBRAS控制面设备，本步骤可以参见图9中用数字6标记的带箭头的线条。
步骤9180：vBRAS控制面设备从RESTFUL接口接收到厂商A解析插件2发送的Vendor-Specific属性的解析结果。通过解析插件返回的解析结果和自身对Access-Accept认证响应报文中携带的其他属性的解析，vBRAS控制面设备获取到宽带用户的授权信息。
步骤9190：vBRAS控制面设备将需要下发到vBRAS转发面的授权信息转换成vBRAS控制面和转发面之间通信协议定义的属性后，通过vBRAS转发面(vBRAS转发面2(厂商A))和vBRAS控制面之间建立的CUSP连接，采用TLV方式，将宽带用户的授权信息发送到对应的vBRAS转发面。所述TLV方式，即授权信息中的每个属性值按照属性类型(Type)，属性长度(Length)和属性值(Value)方式传递，本步骤可以参见图9中用数字7标记的带箭头的线条。
步骤9200：根据vBRAS控制面和转发面之间的通信协议定义，vBRAS转发面设备接收到宽带用户授权信息，将授权信息写入用户转发表。vBRAS转发面设备后续根据用户转发表处理和转发宽带用户访问网站的报文。
第六实施例
在本申请前述实施例提出的报文处理方法的基础上，本申请第六实施例提出了一种报文处理装置，可以应用于vBRAS控制面设备中。
图10为本申请实施例提供的一种报文处理装置的组成结构示意图，如图10所示，所述装置包括接收模块1001、第一处理模块1002和第二处理模块1003，其中，
接收模块1001，设置为接收到包含至少一种私有格式数据的报文；
第一处理模块1002，设置为根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述至少一种私有格式数据，接收来自所选择的报文解析插件的解析后数据；所述解析后数据是由所选择的报文解析插件对至少一种私有格式数据进行解析后得出的；
第二处理模块1003，设置为根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。
在一实施方式中，所述第一处理模块1002，还设置为接收多个目标设备上报的标识信息、以及多个报文解析插件上报的标识信息；根据所述多个目标设备上报的标识信息、以及所述多个报文解析插件上报的标识信息，建立目标设备的标识信息与报文解析插件标识信息的对应关系；根据所述对应关系，选择与所确定的目标设备的标识信息匹配的报文解析插件。
在一实施方式中，每个目标设备上报的标识信息包括对应目标设备所属厂商的ID，或者，每个目标设备上报的标识信息包括对应目标设备所属厂商的ID和对应目标设备的ID。
在一实施方式中，每个报文解析插件上报的标识信息包括对应报文解析插件所属厂商的ID，或者，每个报文解析插件上报的标识信息包括对应报文解析插件所属厂商的ID和目标设备的ID。
在一实施方式中，所确定的目标设备的标识信息包括：类别标识信息和唯一标识信息；所述类别标识信息用于标识目标设备的类别、所述唯一标识信息用于唯一标识目标设备。
在一实施方式中，所述类别标识信息包括目标设备所属厂商的ID，所述唯一标识信息包括目标设备的ID。
在一实施方式中，所述第一处理模块1002，是设置为根据所述对应关系，查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件时，选择查找到的报文解析插件；根据所述对应关系，未查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件，且查找到与所确定的目标设备的类别标识信息匹配的报文解析插件时，选择查找到的报文解析插件。
在一实施方式中，所述第一处理模块1002，还设置为在建立目标设备的标识信息与报文解析插件标识信息的对应关系后，接收到新部署的目标设备上报的标识信息、以及新部署的报文解析插件上报的标识信息时，根据所述新部署的目标设备上报的标识信息、以及新部署的报文解析插件上报的标识信息，更新所述对应关系。
在一实施方式中，所述第一处理模块1002，是设置为所述第一报文为针对宽带接入认证请求的认证响应报文时，根据所述第一报文中的Identifier域值，确定目标设备的标识信息。
在一实施方式中，所述第一处理模块1002，是设置为根据所述Identifier域值，查找到对应的宽带用户接入信息；根据所述宽带用户接入信息，确定目标设备的标识信息。
在一实施方式中，所述至少一种私有格式数据包括多个厂商的私有格式数据时，所述解析后数据是由报文解析插件根据自身所属厂商的标识信息，对所述多个厂商的私有格式数据进行过滤处理后，进行解析得出的数据。
在一实施方式中，所述第二处理模块1003，是设置为所述第一报文为针对宽带接入认证请求的认证响应报文时，根据所述解析后数据，得到宽带用户授权信息；将所述宽带用户授权信息发送至目标设备，使目标设备根据所述宽带用户授权信息确定对所述第二报文的处理方式。
实际应用中，上述接收模块1001、第一处理模块1002和第二处理模块1003均可由位于CPU、微处理器(Micro Processor Unit，MPU)、DSP、或FPGA等实现。
另外，在本实施例中的多功能模块可以集成在一个处理单元中，也可以是每个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
所述集成的单元如果以软件功能模块的形式实现并非作为独立的产品进行 销售或使用时，可以存储在一个计算机可读取存储介质中，本实施例的技术方案本质上可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一些指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等多种可以存储程序代码的介质。
本实施例中的一种报文处理方法对应的计算机程序指令可以被存储在光盘，硬盘，通用串行总线闪存盘(Universal Serial Bus flash disk，U盘)等存储介质上，当存储介质中的与一种报文处理方法对应的计算机程序指令被一电子设备读取或被执行时，实现前述实施例的任意一种报文处理方法。
基于前述实施例相同的技术构思，参见图11，图11示出了本申请实施例提供的另一种报文处理装置110，该装置可以包括：存储器111和处理器112；其中，
所述存储器111，设置为存储计算机程序和数据；
所述处理器112，设置为执行所述存储器中存储的计算机程序，以实现前述实施例的任意一种报文处理方法。
在实际应用中，上述存储器111可以是易失性存储器(volatile memory)，例如RAM；或者非易失性存储器(non-volatile memory)，例如ROM，快闪存储器(flash memory)，硬盘(Hard Disk Drive，HDD)或固态硬盘(Solid-State Drive，SSD)；或者上述种类的存储器的组合，并向处理器112提供指令和数据。
上述处理器112可以为ASIC、DSP、DSPD、PLD、FPGA、CPU、控制器、微控制器、微处理器中的至少一种。对于不同的设备，设置为实现上述处理器功能的电子器件还可以为其它，本申请实施例不作限定。
作为一种实施方式，所述报文解析插件的部署方式为：独立于转发面设备进行部署，或者，部署在转发面设备处。
作为一种实施方式，所述目标设备属于转发面设备。
第七实施例
在本申请第七实施例提出了一种控制面设备，包括本申请第六实施例中的任意一种报文处理装置。
本申请的实施例可提供为方法、***、或计算机程序产品。因此，本申请可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本申请的实施例而已，并非用于限定本申请的保护范围。

Claims (18)

  1. 一种报文处理方法，包括：
    接收到包含至少一种私有格式数据的第一报文；
    根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述第一报文，接收来自所选择的报文解析插件的解析后数据；其中，所述解析后数据是由所选择的报文解析插件对所述第一报文中的至少一种私有格式数据进行解析后得出的数据；
    根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。
  2. 根据权利要求1所述的方法，还包括：
    接收多个目标设备上报的标识信息、以及多个报文解析插件上报的标识信息；
    根据所述多个目标设备上报的标识信息、以及所述多个报文解析插件上报的标识信息，建立所述多个目标设备的标识信息与所述多个报文解析插件标识信息的对应关系；
    所述选择与所确定的目标设备的标识信息匹配的报文解析插件，包括：
    根据所述对应关系，选择与所确定的目标设备的标识信息匹配的报文解析插件。
  3. 根据权利要求2所述的方法，其中，每个目标设备上报的标识信息包括对应目标设备所属厂商的身份标识ID，或者，每个目标设备上报的标识信息包括对应目标设备所属厂商的ID和对应目标设备的ID。
  4. 根据权利要求2所述的方法，其中，每个报文解析插件上报的标识信息包括对应报文解析插件所属厂商的ID，或者，每个报文解析插件上报的标识信息包括对应报文解析插件所属厂商的ID和目标设备的ID。
  5. 根据权利要求2所述的方法，其中，所确定的目标设备的标识信息包括：类别标识信息和唯一标识信息；所述类别标识信息用于标识所确定的目标设备的类别、所述唯一标识信息用于唯一标识所确定的目标设备。
  6. 根据权利要求5所述的方法，其中，所述类别标识信息包括所确定的目标设备所属厂商的ID，所述唯一标识信息包括所确定的目标设备的ID。
  7. 根据权利要求5或6所述的方法，其中，所述根据所述对应关系，选择与所确定的目标设备的标识信息匹配的报文解析插件，包括：
    根据所述对应关系，在查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件的情况下，选择查找到的报文解析插件；
    根据所述对应关系，在未查找到与所确定的目标设备的类别标识信息和唯一标识信息均匹配的报文解析插件，且查找到与所确定的目标设备的类别标识信息匹配的报文解析插件的情况下，选择查找到的报文解析插件。
  8. 根据权利要求2所述的方法，在所述建立所述多个目标设备的标识信息与所述多个报文解析插件标识信息的对应关系之后，还包括：
    在接收到新部署的目标设备上报的标识信息、以及新部署的报文解析插件上报的标识信息的情况下，根据所述新部署的目标设备上报的标识信息、以及所述新部署的报文解析插件上报的标识信息，更新所述对应关系。
  9. 根据权利要求1所述的方法，其中，所述根据所述第一报文确定目标设备的标识信息包括：
    在所述第一报文为针对宽带接入认证请求的认证响应报文的情况下，根据所述第一报文中的标识符Identifier域值，确定目标设备的标识信息。
  10. 根据权利要求9所述的方法，其中，所述根据所述第一报文中的Identifier域值，确定目标设备的标识信息，包括：
    根据所述第一报文中的Identifier域值，查找到对应的宽带用户接入信息；
    根据所述宽带用户接入信息，确定目标设备的标识信息。
  11. 根据权利要求1所述的方法，其中，在所述至少一种私有格式数据包括多个厂商的私有格式数据的情况下，所述解析后数据是由所选择的报文解析插件根据自身所属厂商的标识信息，对所述多个厂商的私有格式数据进行过滤处理后，进行解析得出的数据。
  12. 根据权利要求1所述的方法，其中，所述根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式，包括：
    在所述第一报文为针对宽带接入认证请求的认证响应报文的情况下，根据所述解析后数据，得到宽带用户授权信息；
    将所述宽带用户授权信息发送至所述目标设备，使所述目标设备根据所述宽带用户授权信息确定对所述用于访问网站的第二报文的处理方式。
  13. 一种报文处理装置，包括处理器和设置为存储在所述处理器上运行的计算机程序的存储器；其中，所述处理器设置为运行所述计算机程序时，执行权利要求1至12任一项所述的报文处理方法。
  14. 根据权利要求13所述的装置，其中，所述报文解析插件的部署方式为： 独立于转发面设备进行部署，或者，部署在转发面设备处。
  15. 根据权利要求13所述的装置，其中，所述目标设备属于转发面设备。
  16. 一种报文处理装置，包括：
    接收模块，设置为接收到包含至少一种私有格式数据的第一报文；
    第一处理模块，设置为根据所述第一报文确定目标设备的标识信息，选择与所确定的目标设备的标识信息匹配的报文解析插件；向所选择的报文解析插件发送所述第一报文，接收来自所选择的报文解析插件的解析后数据；其中，所述解析后数据是由所选择的报文解析插件对所述第一报文中的至少一种私有格式数据进行解析后得出的数据；
    第二处理模块，设置为根据所述解析后数据，确定所述目标设备对用于访问网站的第二报文的处理方式。
  17. 一种控制面设备，包括权利要求13至16任一项所述的报文处理装置。
  18. 一种计算机存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至12任一项所述的报文处理方法。
PCT/CN2019/128654 2018-12-28 2019-12-26 报文处理方法、装置、控制面设备和计算机存储介质 WO2020135574A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19902328.4A EP3905598B1 (en) 2018-12-28 2019-12-26 Message processing method and apparatus, control plane device, and computer storage medium
US17/271,901 US11575592B2 (en) 2018-12-28 2019-12-26 Message processing method and apparatus, control-plane device, and computer storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811619224.5A CN111385173B (zh) 2018-12-28 2018-12-28 一种报文处理方法、装置、控制面设备和计算机存储介质
CN201811619224.5 2018-12-28

Publications (1)

Publication Number Publication Date
WO2020135574A1 true WO2020135574A1 (zh) 2020-07-02

Family

ID=71128724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128654 WO2020135574A1 (zh) 2018-12-28 2019-12-26 报文处理方法、装置、控制面设备和计算机存储介质

Country Status (4)

Country Link
US (1) US11575592B2 (zh)
EP (1) EP3905598B1 (zh)
CN (1) CN111385173B (zh)
WO (1) WO2020135574A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114168218A (zh) * 2021-11-30 2022-03-11 深圳市名竹科技有限公司 数据处理方法、装置、计算机设备和存储介质
CN114500276A (zh) * 2020-11-13 2022-05-13 中兴通讯股份有限公司 数据处理方法、装置、***和计算机可读存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113055191B (zh) * 2019-12-27 2023-08-01 中兴通讯股份有限公司 一种转发方法、装置、宽带远程接入服务器的转发面
CN112351421B (zh) * 2020-09-14 2024-02-06 深圳Tcl新技术有限公司 数据传输的控制方法、控制设备以及计算机存储介质
CN112491576A (zh) * 2020-09-29 2021-03-12 中兴通讯股份有限公司 网络配置的发送方法及装置、存储介质、电子装置
CN112367197B (zh) * 2020-10-30 2022-08-30 新华三技术有限公司 网络设备的迁移方法及装置
CN114760193A (zh) * 2020-12-29 2022-07-15 华为技术有限公司 一种主备协商方法及设备
CN115706732B (zh) * 2021-08-12 2024-06-11 中移物联网有限公司 一种控制***、方法、电子设备及存储介质
CN114257663A (zh) * 2021-11-30 2022-03-29 神彩科技股份有限公司 数据解析方法、装置、计算机设备、存储介质
CN115002207B (zh) * 2022-05-27 2024-02-23 三一智矿科技有限公司 信息通信方法及***
CN117194075B (zh) * 2023-09-11 2024-05-03 中国人民解放军军事科学院战争研究院 一种适配多模态微应用的消息隔离通信方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103093342A (zh) * 2013-01-11 2013-05-08 北京掌上汇通科技发展有限公司 一种联机交易处理平台及其交易处理方法
WO2014071605A1 (zh) * 2012-11-09 2014-05-15 华为技术有限公司 处理报文的方法、转发面装置及网络设备
WO2018001089A1 (zh) * 2016-06-27 2018-01-04 中兴通讯股份有限公司 业务处理方法及装置、存储介质
CN107770012A (zh) * 2017-10-23 2018-03-06 中国联合网络通信集团有限公司 一种宽带接入方法、装置及虚拟宽带远程接入服务器***

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6728804B1 (en) * 2000-10-27 2004-04-27 Emware, Inc. Remotely reprogrammable communications adapter for providing access to an electronic device
WO2004055659A1 (en) * 2002-12-13 2004-07-01 Bea Systems, Inc. System and method for mobile communication
WO2011029238A1 (zh) * 2009-09-11 2011-03-17 华为技术有限公司 广告投放方法、广告服务器和广告***
EP2472911A1 (en) * 2010-12-29 2012-07-04 British Telecommunications Public Limited Company WLAN device proximity service
US8958439B2 (en) * 2010-08-03 2015-02-17 F5 Networks, Inc. Mediating method and system between signaling network peers
CN102281189B (zh) * 2011-06-28 2015-07-22 杭州华三通信技术有限公司 一种基于第三方设备私有属性的业务实现方法及其装置
CN102868758B (zh) * 2012-09-29 2016-12-21 华为技术有限公司 门户推送的方法和网络设备
CN103905382A (zh) * 2012-12-26 2014-07-02 中国电信股份有限公司 宽带用户拨号认证错误处理方法及***
CN104935677B (zh) * 2014-03-18 2019-10-18 中兴通讯股份有限公司 一种nat64资源获取方法及获取/分配装置
US11165692B2 (en) * 2016-05-25 2021-11-02 Telefonaktiebolaget Lm Ericsson (Publ) Packet forwarding using vendor extension in a software-defined networking (SDN) system
CN107786613B (zh) * 2016-08-30 2020-05-12 新华三技术有限公司 宽带远程接入服务器bras转发实现方法和装置
US20170187577A1 (en) * 2017-03-14 2017-06-29 Nuviso Networks Inc System for configuring network devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014071605A1 (zh) * 2012-11-09 2014-05-15 华为技术有限公司 处理报文的方法、转发面装置及网络设备
CN103093342A (zh) * 2013-01-11 2013-05-08 北京掌上汇通科技发展有限公司 一种联机交易处理平台及其交易处理方法
WO2018001089A1 (zh) * 2016-06-27 2018-01-04 中兴通讯股份有限公司 业务处理方法及装置、存储介质
CN107770012A (zh) * 2017-10-23 2018-03-06 中国联合网络通信集团有限公司 一种宽带接入方法、装置及虚拟宽带远程接入服务器***

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114500276A (zh) * 2020-11-13 2022-05-13 中兴通讯股份有限公司 数据处理方法、装置、***和计算机可读存储介质
CN114168218A (zh) * 2021-11-30 2022-03-11 深圳市名竹科技有限公司 数据处理方法、装置、计算机设备和存储介质
CN114168218B (zh) * 2021-11-30 2024-03-29 深圳市名竹科技有限公司 数据处理方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
US20210194788A1 (en) 2021-06-24
EP3905598A1 (en) 2021-11-03
CN111385173A (zh) 2020-07-07
EP3905598A4 (en) 2022-09-07
CN111385173B (zh) 2023-08-25
US11575592B2 (en) 2023-02-07
EP3905598B1 (en) 2023-06-28

Similar Documents

Publication Publication Date Title
WO2020135574A1 (zh) 报文处理方法、装置、控制面设备和计算机存储介质
US9485147B2 (en) Method and device thereof for automatically finding and configuring virtual network
US11487690B2 (en) Universal host and non-volatile memory express storage domain discovery for non-volatile memory express over fabrics
EP3531634B1 (en) Method for controlling network slices, forwarding device and control device
CN107070691B (zh) Docker容器的跨主机通信方法和***
US9798572B2 (en) Virtual machine migration method, switch, and virtual machine system
US12047287B2 (en) Data transmission method and apparatus, network adapter, and storage medium
US10541877B2 (en) Dynamic reservation protocol for 5G network slicing
US9992104B2 (en) Communication method, communication system, resource pool management system, switch device and control device
CN106452857B (zh) 生成配置信息的方法和网络控制单元
US9325563B2 (en) Overlay tunnel information exchange protocol
EP2843906B1 (en) Method, apparatus, and system for data transmission
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
CN106464534B (zh) 配设和管理用户驻地设备装置的片
US8005083B1 (en) Applying differentiated services within a cable network using customer-aware network router
CN107078974B (zh) 网络交换机、由网络交换机执行的方法以及存储器资源
US9832136B1 (en) Streaming software to multiple virtual machines in different subnets
US20240089165A1 (en) Systems, Methods and Devices for Networked Media Distribution
US9954775B2 (en) Software-defined network (SDN) system using host abstraction, and method for implementing the same
WO2022214019A1 (zh) 一种部署网络设备的方法、装置、设备、***及存储介质
WO2016034006A1 (zh) 一种报文发送方法及接入设备
CN108881178B (zh) 信息发送方法及装置，设备，存储介质和电子装置
CN105577433A (zh) 一种acs集群管理方法、装置和***
KR102385707B1 (ko) 호스트 추상화를 이용한 sdn 네트워크 시스템 및 그 구현방법
CN112887137B (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: 19902328

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019902328

Country of ref document: EP

Effective date: 20210728