WO2023197499A1 - 信息采集方法、服务链代理节点、服务链和存储介质 - Google Patents

信息采集方法、服务链代理节点、服务链和存储介质 Download PDF

Info

Publication number
WO2023197499A1
WO2023197499A1 PCT/CN2022/115097 CN2022115097W WO2023197499A1 WO 2023197499 A1 WO2023197499 A1 WO 2023197499A1 CN 2022115097 W CN2022115097 W CN 2022115097W WO 2023197499 A1 WO2023197499 A1 WO 2023197499A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
message
node
oam
information
Prior art date
Application number
PCT/CN2022/115097
Other languages
English (en)
French (fr)
Inventor
黄灿灿
陆立
唐宏
叶何亮
邹洁
范云凌
Original Assignee
中国电信股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国电信股份有限公司 filed Critical 中国电信股份有限公司
Publication of WO2023197499A1 publication Critical patent/WO2023197499A1/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/46—Interconnection of networks
    • 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/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • 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
    • 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/563—Data redirection of data network streams
    • 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/22—Parsing or analysis of headers

Definitions

  • the present disclosure relates to the field of communication technology, particularly an information collection method, a service chain proxy node, a service chain and a storage medium.
  • SF Service Function
  • SFC-unware SF nodes In related technologies, SF (Service Function) nodes on the SFC (Service Function Chain) are deployed at different times, and some older devices (such as firewalls and DPI (Deep Packet Inspection)) are deployed at different times. ), have certain specific business functions, but because there is no upgrade or replacement, these SF nodes (hereinafter referred to as SFC-unware (unaware) SF nodes) do not have the ability to recognize the SFC protocol.
  • SFF Service Function Forwarder
  • One purpose of this disclosure is to improve the comprehensiveness of OAM information collection.
  • an information collection method including: generating a first instruction according to an OAM collection request from the first domain; generating a first message according to the first instruction and the protocol of the second domain; The first message is sent to the node in the second domain, so that the node in the second domain collects OAM information and feeds back according to the first instruction.
  • the information collection method further includes: obtaining OAM information fed back by nodes in the second domain; and encapsulating the OAM information according to the protocol of the first domain.
  • the first instruction is code for the nodes in the second domain to run, and the nodes in the second domain obtain the OAM information by running the first instruction.
  • the first instruction is executable code of OAM requirement information.
  • the OAM collection request is carried through NSH (Network Service Header, Network Service Header) packets.
  • NSH Network Service Header, Network Service Header
  • generating the first message according to the first instruction and the protocol of the second domain includes: adding the first instruction to the payload field of the NSH message; encapsulating the data of the payload field based on the protocol of the second domain, and obtaining the first One message.
  • generating the first message according to the first instruction and the protocol of the second domain includes: using the first instruction as the content of the payload field, encapsulating the data of the payload field based on the protocol of the second domain, and obtaining the first message.
  • the information collection method also includes: encapsulating the user data in the payload field of the NSH message based on the protocol of the second domain to generate a second message, and sending the second message to the node of the second domain.
  • obtaining the OAM information fed back by the node in the second domain includes: obtaining the third message fed back by the node in the second domain; extracting the payload field of the third message to obtain the OAM information.
  • encapsulating the OAM information according to the protocol of the first domain includes: encapsulating the OAM information into a header of the NSH message.
  • the nodes in the first domain have the capability to support the service chain SFC protocol; and the nodes in the second domain do not have the capability to support the SFC protocol.
  • the OAM collection request includes OAM requirement information carried in the received NSH message.
  • generating the first instruction according to the OAM collection request from the first domain includes: enabling the OAM information acquisition function OIAF according to the OAM collection request; and generating the first instruction according to the OAM collection request based on OIAF.
  • the protocol of the second domain includes a protocol for exchanging information between the service chain proxy node and the second domain.
  • a service chain proxy node including: an instruction generation unit configured to generate a first instruction according to an OAM collection request from the first domain; a first message generation unit configured to The first message sending unit is configured to generate a first message according to the first instruction and the protocol of the second domain; the first message sending unit is configured to send the first message to the node of the second domain, so that the node of the second domain can generate the first message according to the first message. Instructs to collect OAM information and provide feedback.
  • the SFC agent node further includes: an information receiving unit configured to obtain OAM information fed back by nodes in the second domain; and an encapsulating unit configured to encapsulate the OAM information according to the protocol of the first domain.
  • a service chain proxy node including: a memory; and a processor coupled to the memory, the processor being configured to execute any of the above information based on instructions stored in the memory Collection method.
  • a non-transitory computer-readable storage medium on which computer program instructions are stored, which when executed by a processor implements the steps of any of the above information collection methods.
  • a service chain including: any SFC agent node mentioned above; a node in the first domain configured to provide a service to a node in the second domain through the SFC agent node Send an operation, maintenance and management OAM collection request; and the node in the second domain is configured to collect OAM information according to the first instruction from the SFC agent node, and feed it back to the SFC agent node, where the SFC agent node is located between the node in the first domain and between nodes in the second domain.
  • the nodes of the first domain include SFF nodes.
  • the node of the second domain is configured to: extract the payload field of the first message from the SFC agent node; obtain the OAM information by running the first instruction carried in the payload field; add the OAM information into the third The payload field of the third message; feeds back the third message to the SFC agent node.
  • the node in the second domain is further configured to: obtain the user data carried in the payload field of the first message, process the user data, and carry the processing result through the payload field of the third message.
  • the node of the second domain is further configured to: obtain a second message from the SFC agent node, the payload field of the second message carries user data; and, process the user data, and pass the processing result through the third message.
  • the payload field of the four messages is carried, and the fourth message is fed back to the SFC agent node.
  • a computer program for causing a processor to execute any of the above information collection methods.
  • Figure 1 is a flow chart of some embodiments of the information collection method of the present disclosure.
  • Figure 2 is a flow chart of other embodiments of the information collection method of the present disclosure.
  • Figure 3A is a schematic diagram of some embodiments of the information collection method of the present disclosure.
  • Figure 3B is a schematic diagram of other embodiments of the information collection method of the present disclosure.
  • FIG. 4 is a schematic diagram of some embodiments of the SFC proxy node of the present disclosure.
  • FIG. 5 is a schematic diagram of other embodiments of the SFC proxy node of the present disclosure.
  • FIG. 6 is a schematic diagram of further embodiments of the SFC proxy node of the present disclosure.
  • FIG. 7 is a schematic diagram of some embodiments of the SFC of the present disclosure.
  • NSH packet headers such as SFF nodes and SFC proxy nodes.
  • SFF nodes and SFC proxy nodes For the SFC unware SF node, since it cannot read the OAM requirement information carried in the NSH packet header, it is difficult to be triggered to collect its own OAM information. This results in the collected SFC OAM information being not comprehensive enough and reducing the reference value.
  • RFC7665 introduces the SFC proxy node.
  • the SFC agent node decapsulates the received SFC message, including separating the NSH message header and the payload part of the NSH, and then passes the payload message through the local circuit (Local Attachment Circuit, including VLAN (Virtual Local Area Network), Virtual LAN), IP-in-IP (IP Encapsulation within IP, IP encapsulation in IP), L2TPv3 (Layer Two Tunneling Protocol-Version 3, Layer Two Tunneling Protocol version 3), GRE (Generic Routing Encapsulation, general routing encapsulation) and VxLAN (Virtual Extensible Local Area Network, virtual extended LAN), etc.) are sent to the SF node for processing.
  • VLAN Virtual Local Area Network
  • Virtual LAN Virtual LAN
  • IP-in-IP IP Encapsulation within IP, IP encapsulation in IP
  • L2TPv3 Layer Two Tunneling Protocol-Version 3, Layer Two Tunneling Protocol version 3
  • GRE Generic Routing Encapsulation, general
  • the SFC agent node After the SF node completes processing, it returns the updated payload to the SFC agent node.
  • the SFC agent node encapsulates the new payload using an NSH header and forwards it to the SFF node, which then forwards it to the next SF node.
  • FIG. 1 A flow chart of some embodiments of the information collection method of the present disclosure is shown in Figure 1.
  • the SFC agent node receives the OAM collection request from the first domain, triggering the operation of generating the first instruction.
  • the nodes in the first domain have the ability to support the SFC protocol and can be called SFC-ware (aware) nodes, and the first domain is the SFC-ware domain; the nodes in the second domain do not have the ability to support SFC.
  • the capabilities of the protocol can be called SFC-unware nodes, and the second domain is the SFC-unware domain.
  • the OAM collection request is carried through an NSH packet, such as being located in the header of the NSH packet.
  • the OAM collection request includes OAM requirement information carried in the NSH message header.
  • the OAM requirement information includes the type of OAM information that needs to be collected.
  • the SFC agent node after receiving the NSH message, parses the NSH message to determine whether it contains an OAM collection request. If it is determined that the NSH message contains an OAM collection request, a first instruction that can be recognized by the node in the second domain is generated. In some embodiments, the first instruction can be generated according to the type of OAM information that needs to be collected, thereby ensuring that nodes in the second domain can obtain the corresponding OAM information.
  • the first instruction is code for the node in the second domain to run. After obtaining the first instruction, the node in the second domain can directly run the first instruction to obtain OAM information.
  • the first instruction is a global code for OAM requirement information in related technologies, thereby ensuring that the nodes in the second domain can correctly run the code without upgrading or changing the nodes in the second domain, and pass Run this code to obtain OAM information.
  • the OAM information obtained by the node in the second domain is the device OAM information of the node.
  • the SFC agent node In step 120, the SFC agent node generates a first message according to the first instruction and the protocol of the second domain.
  • the SFC agent node can add the first instruction to the payload field of the NSH message and based on the protocol of the second domain, such as any of VLAN, IP-in-IP, L2TPv3, GRE or VxLAN protocols, etc.
  • One method is to encapsulate and add the payload field after the first instruction to obtain the first message.
  • the protocol of the second domain includes a protocol for exchanging information between the service chain proxy node and the second domain.
  • the payload field refers to the field in the message from the header to the end of the message.
  • the SFC agent node sends the first message to the node in the second domain.
  • the node in the second domain receives the first message, it extracts the data in the payload field and runs the first instruction code contained therein to collect OAM information.
  • the node in the second domain will feed back the collected OAM information to the SFC agent node through the payload field of the message sent to the SFC agent node.
  • the SFC proxy node can convert the OAM collection request based on the SFC protocol that cannot be recognized by the node in the second domain into one that can be recognized by the node in the second domain and can be executed based on the recognition result.
  • the instructions for collecting OAM information improve the comprehensiveness of the collected OAM information, improve the reference value of the OAM information, and thereby improve the accuracy of the analysis based on the OAM information.
  • the method that can be adopted is to extend the message header used in the SFC-unware domain (such as the above-mentioned VLAN, GRE, etc.) and add it to the SFC agent
  • the node copies the OAM requirement information into the corresponding message header.
  • this method requires all protocols used by the SFC-unware domain to redefine extended message headers. Due to the large number of protocols used by the SFC-unware domain, redefining and updating each protocol will cause high costs. Economic and labor costs, and the development and deployment cycle is too long.
  • the method in this disclosure does not require upgrading devices that do not support the SFC protocol, and can also obtain the OAM information of these devices. Compared with the method of extending the device protocol, this processing method reduces the workload and processing cost, and improves the implementation of SFC. Deployment efficiency of full-chain node OAM collection.
  • the information collection method of the present disclosure may further include step 140.
  • step 140 the SFC agent node obtains the OAM information fed back by the node in the second domain.
  • the SFC agent node can obtain the third message fed back by the node in the second domain, and obtain the OAM information by extracting the payload field of the third message.
  • the payload field also includes user data processed by the node in the second domain, and the SFC agent node identifies the OAM information from the payload field.
  • OAM information may be extracted based on predetermined identification or predetermined field positions.
  • the SFC agent node can obtain the OAM information fed back by the node in the second domain, thereby facilitating subsequent use.
  • the information collection method of the present disclosure may also include step 150: the SFC agent node encapsulates the OAM information according to the protocol of the first domain, and the encapsulated OAM information can be fed back to the node of the first domain as required. In other embodiments, it can also be sent to the server. In some embodiments, the OAM information can be encapsulated into other required formats and forwarded to the corresponding node.
  • the SFC agent node can encapsulate the OAM information into the header of the NSH message, and feed the encapsulated NSH message back to the service function forwarding SFF node located in the first domain.
  • the user data in the third message payload field can be carried through the payload field of the NSH message, thereby ensuring that the interactive function of the user data is not affected.
  • the SFC proxy node may not change the content of the payload field of the third message, but only encapsulate the identified OAM information into the header of the NSH message, so that the payload field includes the OAM of the second domain node. information and user data, thereby avoiding user data damage caused by deleting the OAM information in the payload field.
  • the message containing the OAM information of the second domain node received by the node in the first domain is an NSH message, and the carrying method of the OAM information also complies with the SF protocol, so that the first domain
  • the node is unaware of the packet conversion process, does not affect the OAM information collection process of the existing SFC-ware node, and avoids affecting the processing efficiency of the SFC-ware node.
  • the SFC agent node extracts the information in the message header.
  • the NSH message may come from the SFF node of the first domain.
  • the SFC agent node determines whether the header of the NSH message contains an OAM collection request. If it contains an OAM collection request, the SFC agent node generates the first instruction. In some embodiments, the SFC agent node can pre-store the first instruction and obtain the first instruction by reading the information stored in the memory. In some embodiments, the first instruction may be executable code that instructs the node to collect OAM information.
  • step 221 the SFC agent node adds the first instruction to the payload field of the NSH message.
  • the SFC agent node encapsulates the updated payload field data based on the protocol of the second domain and generates a first message.
  • the first message is a message based on a protocol supported by the first domain.
  • step 231 the SFC agent node sends the first message to the node in the second domain.
  • the node in the first domain When the node in the first domain obtains the first message, it identifies the data in the payload field, discovers and runs the first instruction in it, performs the operation of collecting SF OAM, and generates OAM information. The node in the first domain places the generated OAM information in the payload field and sends it to the SFC agent node through the third message based on the protocol it can support.
  • step 241 the SFC agent node obtains the third message fed back by the node in the second domain.
  • step 242 the SFC agent node extracts the payload field of the third message and obtains the OAM information carried in the payload field.
  • step 251 the SFC agent node encapsulates the extracted OAM information into the header of the NSH message.
  • the SFC agent node may feed back the encapsulated NSH message to the SFF node located in the first domain.
  • the SFC agent node reconstructs the global code of the OAM requirement information in the NSH message header, effectively avoiding the problem that the SFC unaware domain cannot recognize the SF OAM requirement information, and there is no need to modify the SFC unware domain.
  • the equipment was upgraded and transformed, reducing the workload and processing costs, and improving the deployment efficiency of OAM collection of SFC full-chain nodes.
  • the payload field of the first message in steps 221 and 222 may only carry the first instruction, and the original data carried in the payload field of the NSH message obtained in step 211 may be transmitted through the second message.
  • the message is sent to the node in the second domain.
  • the SFC agent node can encapsulate the user data based on the protocol of the second domain and generate a second message, and then send the second message to the node of the second domain, thereby avoiding missing processing of the user data.
  • the payload field of the third message fed back by the node in the second domain may only carry the OAM information obtained by the node in the second domain.
  • the SFC agent node also obtains the fourth message from the node in the second domain, and the payload field of the message carries data processed for the user data in the second message. Based on this method, the data packets carrying data and OAM information can be separated, reducing the probability of data parsing errors.
  • FIG. 3A A schematic diagram of some embodiments of the information collection method of the present disclosure is shown in Figure 3A.
  • the SFF node in the first domain needs to obtain the SF OAM information of the SF node 33, it sends an NSH message to the SF node 33, and the message header carries the OAM collection request.
  • the NSH message is shown as 301.
  • the SFC agent node 32 is located between the SFF node 31 and the SF node 33 and receives the message 301.
  • the SFC agent node 32 reconstructs the code of the telemetry OAM collection request carried in the NSH message header and generates directly executable code (called the first instruction in the figure).
  • the SFC agent node 32 integrates this code with the first payload data Payload1 of the original payload field to form the second payload data Payload2.
  • the SFC proxy node 32 re-encapsulates Payload2 using the protocol of the SFC-unware domain, generates a message 302, and forwards it to the SF node 33.
  • SF node 33 After parsing message 302, SF node 33 directly runs the code of the first instruction in Payload2 to obtain the OAM information of SF.
  • the SF node 33 combines the obtained OAM information together with the processed user data into the third payload data Payload3.
  • SFC node 33 re-encapsulates Payload3 using the protocol of the SFC unware domain, generates message 303, and forwards it to SFC agent node 32.
  • SFC node 32 receives message 303 and parses it, encapsulates the OAM information in Payload3 into the message header of the extended NSH message, generates message 304, and feeds message 304 back to SFF node 31, thereby realizing SFF node 31 Obtain the OAM information of the node in the SFC unware domain.
  • the SFC proxy node 32 can also use the code and the original first payload data Payload1 as Payload2 respectively, and then generate two re-encapsulated messages using the protocol of the SFC-unware domain. 302, sent to SF node 33.
  • the SF node 33 will process the two messages respectively. For the message carrying the code of the first instruction, obtain the OAM information; for the message carrying Payload1, process its user data, and then separate the OAM information and user data. As Payload3, a message is generated and forwarded to the SFC agent node 32.
  • FIG. 4 A schematic diagram of some embodiments of the SFC proxy node 41 of the present disclosure is shown in Figure 4.
  • the instruction generation unit 411 can receive an OAM collection request from the first domain and trigger the operation of generating the first instruction.
  • the first instruction is code for the nodes in the second domain to run.
  • the nodes in the second domain can directly run the first instruction after obtaining the first instruction, and obtain OAM information by running the first instruction.
  • the first message generating unit 412 can generate the first message according to the first instruction and the protocol of the second domain.
  • the first message generation unit 412 can add the first instruction to the payload field of the NSH message and based on the protocol of the second domain, such as VLAN, IP-in-IP, L2TPv3, GRE or VxLAN protocol , encapsulate the payload field after adding the first instruction, and obtain the first message.
  • the first message sending unit 413 can send the first message to the node in the second domain.
  • Such an SFC agent node can convert OAM collection requests based on the SFC protocol that are not recognized by nodes in the second domain into instructions that can be recognized by nodes in the second domain and can execute OAM information collection based on the recognition results, thereby eliminating the need to Upgrading devices that support the SFC protocol can also obtain the OAM information of these devices, which improves the comprehensiveness of the collected SF OAM information, improves the reference value of the OAM information, and thereby improves the accuracy of analysis based on the OAM information.
  • the SFC agent node may also include an information receiving unit 414, which can obtain OAM information fed back by nodes in the second domain.
  • the information receiving unit 414 may obtain the third message fed back by the node in the second domain, and obtain the OAM information by extracting the payload field of the third message.
  • the payload field also includes user data processed by the node of the second domain, and the information receiving unit 414 identifies the OAM information from the payload field.
  • OAM information may be extracted based on predetermined identification or predetermined field positions.
  • Such SFC agent nodes can obtain OAM information fed back by nodes in the second domain, thereby facilitating subsequent use.
  • the SFC proxy node may also include an encapsulation unit 415 capable of encapsulating OAM information according to the protocol of the first domain.
  • the feedback unit 415 may encapsulate the OAM information into the header of the NSH message, and feed back the encapsulated NSH message to the service function forwarding SFF node located in the first domain.
  • the user data in the third message payload field can be carried through the payload field of the NSH message, thereby ensuring that the interactive function of the user data is not affected.
  • the packet encapsulated with OAM information can also be sent to the server.
  • the OAM information can be encapsulated into other required formats and forwarded to the corresponding node.
  • Such an SFC agent node can make the packets containing the OAM information of the second domain node received by the nodes in the first domain be NSH packets.
  • the carrying method of the OAM information also conforms to the SF protocol, so that the nodes in the first domain can handle the packets.
  • the document conversion process is imperceptible, does not affect the existing OAM collection process of SFC ware nodes, and avoids affecting the processing efficiency of SFC ware nodes.
  • the SFC agent node includes a memory 501 and a processor 502.
  • the memory 501 can be a disk, flash memory or any other non-volatile storage medium.
  • the memory is used to store instructions in corresponding embodiments of the above information collection method.
  • Processor 502 is coupled to memory 501 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller.
  • the processor 502 is used to execute instructions stored in the memory, which can improve the comprehensiveness of the collected OAM information, thereby improving the accuracy of analysis based on the OAM information.
  • the SFC agent node 600 includes a memory 601 and a processor 602.
  • Processor 602 is coupled to memory 601 via BUS bus 603 .
  • the SFC agent node 600 can also be connected to the external storage device 605 through the storage interface 604 to call external data, and can also be connected to the network or another computer system (not shown) through the network interface 606. No further details will be given here.
  • the comprehensiveness of the collected OAM information can be improved, thereby improving the accuracy of analysis based on the OAM information.
  • a computer-readable storage medium has computer program instructions stored thereon. When the instructions are executed by a processor, the information collection method implements the steps of the method in the corresponding embodiment.
  • embodiments of the present disclosure may be provided as methods, apparatuses, or computer program products. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. .
  • FIG. 7 A schematic diagram of some embodiments of the SFC of the present disclosure is shown in Figure 7.
  • the SFC agent node 71 is located between the node in the first domain and the node in the second domain, and can be any of the above mentioned ones.
  • the node 72 of the first domain can send an OAM collection request to the node of the second domain through the SFC proxy node.
  • the nodes in the first domain are capable of supporting the SFC protocol.
  • the nodes of the first domain include SFF nodes.
  • the OAM collection request may be carried through an NSH packet, such as being located in the header of the NSH packet.
  • the node 73 of the second domain can collect OAM information according to the first instruction from the SFC agent node and feed it back to the SFC agent node.
  • nodes in the second domain do not have the capability to support the SFC protocol.
  • the node in the second domain can extract the payload field of the first message from the SFC proxy node.
  • the payload field contains the first instruction
  • the information is added to the payload field of the third message, and the third message is fed back to the SFC agent node.
  • the node in the second domain obtains the user data carried in the payload field of the first message, and after processing the user data, carries the processing result through the payload field of the third message, so that the processing result of the data and OAM information can be fed back through the third message.
  • the node in the second domain can also obtain the second message from the SFC proxy node, and the payload field of the second message carries user data.
  • the nodes in the second domain process user data, carry the processing results through the payload field of the fourth message, and feed back the fourth message to the SFC agent node, thereby separating the data packets carrying the data from the data packets carrying OAM information and reducing data parsing. Probability of error.
  • the conversion of OAM collection requests based on the SFC agent node can enable the nodes in the second domain to collect and provide OAM information feedback to the first domain without upgrading the nodes in the second domain, improving the collection SFC
  • the comprehensiveness of OAM information across the entire chain improves the reference value of OAM information and also helps improve the accuracy of analysis based on OAM information.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • the methods and apparatus of the present disclosure may be implemented in many ways.
  • the methods and devices of the present disclosure can be implemented through software, hardware, firmware, or any combination of software, hardware, and firmware.
  • the above order for the steps of the methods is for illustration only, and the steps of the methods of the present disclosure are not limited to the order specifically described above unless otherwise specifically stated.
  • the present disclosure may also be implemented as programs recorded in recording media, and these programs include machine-readable instructions for implementing methods according to the present disclosure.
  • the present disclosure also covers recording media storing programs for executing methods according to the present disclosure.

Landscapes

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

Abstract

本公开提出一种信息采集方法、服务链代理节点、服务链和存储介质，涉及通信技术领域。本公开的一种信息采集方法，包括：根据来自第一域的OAM采集请求生成第一指令；根据第一指令和第二域的协议生成第一报文；将第一报文发送给第二域的节点，以便第二域的节点根据第一指令采集OAM信息并反馈。通过这样的方法，能够提高采集的OAM信息的全面性，进而有助于提高基于OAM信息执行的分析的准确度。

Description

信息采集方法、服务链代理节点、服务链和存储介质
相关申请的交叉引用
本申请是以CN申请号为202210384664.7，申请日为2022年4月13日的申请为基础，并主张其优先权，该CN申请的公开内容在此作为整体引入本申请中。
技术领域
本公开涉及通信技术领域，特别是一种信息采集方法、服务链代理节点、服务链和存储介质。
背景技术
相关技术中，SFC(Service Function Chain，服务链)上的SF(Service Function，服务功能)节点部署于不同时期，有些较早的设备(例如防火墙和DPI(Deep Packet Inspection，深度报文检测)等)，具备某种特定的业务功能，但是由于没有升级和替换，这些SF节点(下文称为SFC-unware(无感知)的SF节点)并不具备识别SFC协议的能力。当SFF(Service Function Forwarder，服务功能转发)节点将报文转发给SFC-unware的SF节点时，SF会因为数据报文解码出无法识别的结果而将报文丢弃。
发明内容
本公开的一个目的在于提高OAM信息采集的全面性。
根据本公开的一些实施例的一个方面，提出一种信息采集方法，包括：根据来自第一域的OAM采集请求生成第一指令；根据第一指令和第二域的协议生成第一报文；将第一报文发送给第二域的节点，以便第二域的节点根据第一指令采集OAM信息并反馈。
在一些实施例中，信息采集方法还包括：获取第二域的节点反馈的OAM信息；根据第一域的协议封装OAM信息。
在一些实施例中，第一指令为供第二域的节点运行的代码，第二域的节点通过运行第一指令获取OAM信息。
在一些实施例中，第一指令为OAM需求信息的可执行代码。
在一些实施例中，OAM采集请求为通过NSH(Network Service Header，网络服务头)报文携带。
在一些实施例中，根据第一指令和第二域的协议生成第一报文包括：将第一指令添加至NSH报文的载荷字段；基于第二域的协议封装载荷字段的数据，获取第一报文。
在一些实施例中，根据第一指令和第二域的协议生成第一报文包括：将第一指令作为载荷字段的内容，并基于第二域的协议封装载荷字段的数据，获取第一报文；信息采集方法还包括：将NSH报文中载荷字段的用户数据基于第二域的协议封装后生成第二报文，将第二报文发送给第二域的节点。
在一些实施例中，获取第二域的节点反馈的OAM信息包括：获取第二域的节点反馈的第三报文；提取第三报文的载荷字段，获取OAM信息。
在一些实施例中，根据第一域的协议封装OAM信息包括：将OAM信息封装至NSH报文的报文头中。
在一些实施例中，第一域中的节点具备支持服务链SFC协议的能力；和第二域中的节点不具备支持SFC协议的能力。
在一些实施例中，OAM采集请求包括收到的NSH报文中携带的OAM需求信息。
在一些实施例中，根据来自第一域的OAM采集请求，生成第一指令包括：根据OAM采集请求开启OAM信息获取功能OIAF；基于OIAF，根据OAM采集请求生成第一指令。
在一些实施例中，第二域的协议包括用于在服务链代理节点与第二域间交换信息的协议。
根据本公开的一些实施例的一个方面，提出一种服务链代理节点，包括：指令生成单元，被配置为根据来自第一域的OAM采集请求生成第一指令；第一报文生成单元，被配置为根据第一指令和第二域的协议生成第一报文；第一报文发送单元，被配置为将第一报文发送给第二域的节点，以便第二域的节点根据第一指令采集OAM信息并反馈。
在一些实施例中，SFC代理节点还包括：信息接收单元，被配置为获取第二域的节点反馈的OAM信息；封装单元，被配置为根据第一域的协议封装OAM信息。
根据本公开的一些实施例的一个方面，提出一种服务链代理节点，包括：存储器； 以及耦接至存储器的处理器，处理器被配置为基于存储在存储器的指令执行上文中任意一种信息采集方法。
根据本公开的一些实施例的一个方面，提出一种非瞬时性计算机可读存储介质，其上存储有计算机程序指令，该指令被处理器执行时实现上文中任意一种信息采集方法的步骤。
根据本公开的一些实施例的一个方面，提出一种服务链，包括：上文中提到的任意一种SFC代理节点；第一域的节点，被配置为通过SFC代理节点向第二域的节点发送操作维护管理OAM采集请求；和第二域的节点，被配置为根据来自SFC代理节点的第一指令采集OAM信息，并反馈给SFC代理节点，其中，SFC代理节点位于第一域的节点与第二域的节点之间。
在一些实施例中，第一域的节点包括SFF节点。
在一些实施例中，第二域的节点被配置为：提取来自SFC代理节点的第一报文的载荷字段；通过运行载荷字段中承载的第一指令，获取OAM信息；将OAM信息添加进第三报文的载荷字段；将第三报文反馈给SFC代理节点。
在一些实施例中，第二域的节点还被配置为：获取第一报文的载荷字段携带的用户数据，处理用户数据后，将处理结果通过第三报文的载荷字段承载。
在一些实施例中，第二域的节点还被配置为：获取来自SFC代理节点的第二报文，第二报文的载荷字段携带用户数据；和，处理用户数据，并将处理结果通过第四报文的载荷字段承载，将第四报文反馈给SFC代理节点。
根据本公开的一些实施例的一个方面，提出一种计算机程序，用于使处理器执行上文中任意一种信息采集方法。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本公开的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1为本公开的信息采集方法的一些实施例的流程图。
图2为本公开的信息采集方法的另一些实施例的流程图。
图3A为本公开的信息采集方法的一些实施例的示意图。
图3B为本公开的信息采集方法的另一些实施例的示意图。
图4为本公开的SFC代理节点的一些实施例的示意图。
图5为本公开的SFC代理节点的另一些实施例的示意图。
图6为本公开的SFC代理节点的又一些实施例的示意图。
图7为本公开的SFC的一些实施例的示意图。
具体实施方式
发明人发现，相关技术中的SFC OAM(Operation Administration and Maintenance，操作维护管理)信息采集方法只适用于采集能够识别NSH报文头的设备(例如SFF节点和SFC proxy(代理)节点)的OAM信息，对于SFC unware的SF节点，由于其无法读取NSH报文头中携带的OAM需求信息，也就难以被触发采集自身的OAM信息，这就导致采集的SFC的OAM信息不够全面，降低了参考价值。
为了解决SFC-unware设备无法识别基于SFC协议的报文的问题，RFC7665引入SFC代理节点。SFC代理节点将收到的SFC报文解封装，包括将NSH报文头以及NSH的payload(载荷)部分分离，再将payload报文通过本地电路(Local Attachment Circuit，包括VLAN(Virtual Local Area Network，虚拟局域网)、IP-in-IP(IP Encapsulation within IP，IP中封装IP)、L2TPv3(Layer Two Tunneling Protocol-Version 3，二层隧道协议第三版)、GRE(Generic Routing Encapsulation，通用路由封装)和VxLAN(Virtual Extensible Local Area Network，虚拟扩展局域网)等)发送给SF节点处理。SF节点处理完之后再将更新后的payload返回到SFC代理节点，SFC代理节点将新的payload使用NSH报头封装后转发给SFF节点，再由SFF再转发给下一个SF节点。
由于在网络设备向SFC过渡期间，大量现有的SF设备都无法升级支持SFC协议，因此在现有的telemetry(遥测)SFC OAM采集机制下大量的SF OAM信息将被遗漏，导致所采集的OAM信息不具有可参考性。
本公开的信息采集方法的一些实施例的流程图如图1所示。
在步骤110中，SFC代理节点接收来自第一域的OAM采集请求，触发其生成第一指令的操作。在一些实施例中，第一域中的节点具备支持SFC协议的能力，可以称为SFC-ware(感知)节点，第一域则为SFC-ware域；第二域中的节点不具备支持SFC协议的能力，可以称为SFC-unware节点，第二域则为SFC-unware域。
在一些实施例中，OAM采集请求通过NSH报文携带，如位于NSH报文的报文 头中。在一些实施例中，OAM采集请求包括NSH报文头中携带的OAM需求信息。在一些实施例中，OAM需求信息中包括需要采集的OAM信息的种类。在一些实施例中，当SFC代理节点收到NSH报文后，解析NSH报文，判断其中是否包含OAM采集请求。若确定NSH报文中包含OAM采集请求，则生成第二域的节点能够识别的第一指令。在一些实施例中，第一指令可以根据需要采集的OAM信息的种类生成，从而确保第二域的节点能够获取对应的OAM信息。
在一些实施例中，第一指令为供第二域的节点运行的代码，第二域的节点在获得第一指令后能够直接运行第一指令，获取OAM信息。
在一些实施例中，第一指令为相关技术中OAM需求信息的全局代码，从而在无需升级、改变第二域的节点的情况下，确保第二域的节点能够正确的运行该代码，并通过运行该代码获取OAM信息。在一些实施例中，第二域的节点获取的OAM信息为节点的设备OAM信息。
在步骤120中，SFC代理节点根据第一指令和第二域的协议生成第一报文。在一些实施例中，SFC代理节点可以将第一指令添加至NSH报文的载荷字段，并基于第二域的协议，如VLAN、IP-in-IP、L2TPv3、GRE或VxLAN协议等中的任意一种，封装添加第一指令后的载荷字段，获取第一报文。在一些实施例中，第二域的协议包括用于在服务链代理节点与第二域间交换信息的协议。在一些实施例中，载荷字段指的是报文中报文头后一直到报文尾部的字段。
在步骤130中，SFC代理节点将第一报文发送给第二域的节点。当第二域的节点收到第一报文后，提取载荷字段的数据，并运行其中包含的第一指令代码，实现采集OAM信息。在一些实施例中，第二域的节点会将采集到的OAM信息通过发送给SFC代理节点的报文的载荷字段反馈给SFC代理节点。
基于上文所示实施例中的方式，能够通过SFC代理节点将第二域中节点无法识别的、基于SFC协议的OAM采集请求，转化为第二域中节点能够识别、并能够根据识别结果执行OAM信息采集的指令，提高了采集的OAM信息的全面性，提高了OAM信息的参考价值，进而提高了基于OAM信息进行的分析的准确度。
另外，基于相关技术中的SFC代理节点的工作逻辑，可以采用的方法是对SFC-unware域中所使用的报文头(例如上述所提到的VLAN，GRE等)进行扩展，并在SFC代理节点上将OAM需求信息拷贝到相应的报文头中。但是这种方法要求SFC-unware域所使用到的所有协议要重新定义扩展的报文头，由于SFC-unware域所使用 的协议的数量众多，针对每种协议进行重新定义并更新会导致高昂的经济和人力成本，且开发部署周期过长。而本公开中的方式无需对不支持SFC协议的设备升级，也能够获取这些设备的OAM信息，这样的处理方式与扩展设备协议的方式相比，降低了工作负担和处理成本，提高了实现SFC全链节点OAM采集的部署效率。
在一些实施例中，如图1所示，本公开的信息采集方法还可以包括步骤140。
在步骤140中，SFC代理节点获取第二域的节点反馈的OAM信息。
在一些实施例中，SFC代理节点可以获取第二域的节点反馈的第三报文，通过提取第三报文的载荷字段，获取OAM信息。在一些实施例中，载荷字段中还包括第二域的节点处理后的用户数据，SFC代理节点从载荷字段识别出OAM信息。在一些实施例中，可以基于预定标识或预定字段位置提取OAM信息。
基于该实施例中的方法，SFC代理节点能够获得第二域的节点反馈的OAM信息，从而便于后续使用。
在一些实施例中，本公开的信息采集方法还可以包括步骤150：SFC代理节点根据第一域的协议封装OAM信息，封装好的OAM信息可以根据需求反馈给第一域的节点。在另一些实施例中，还可以发送给服务器。在一些实施例中，可以将OAM信息封装成其他所需格式并转发给对应的节点。
在一些实施例中，SFC代理节点可以将OAM信息封装至NSH报文的报文头中，并将封装后的NSH报文反馈给位于第一域的服务功能转发SFF节点。在一些实施例中，第三报文载荷字段的用户数据可以通过NSH报文的载荷字段承载，从而确保不影响用户数据的交互功能。在一些实施例中，SFC代理节点可以不改变第三报文的载荷字段的内容，仅将识别出的OAM信息封装至NSH报文的报文头中，使得载荷字段包括第二域节点的OAM信息和用户数据，从而避免删除载荷字段的OAM信息造成用户数据损伤。
基于上文所示实施例中的方式，第一域的节点收到的包含第二域节点OAM信息的报文为NSH报文，OAM信息的携带方式也符合SF协议，从而做到第一域的节点对于报文的转化过程无感知，不影响已有的SFC-ware节点的OAM信息采集流程，避免影响SFC-ware节点的处理效率。
本公开的信息采集方法的另一些实施例的流程图如图2所示。
在步骤211中，SFC代理节点在获取NSH报文后，提取其报文头中的信息。在一些实施例中，NSH报文可以来自于第一域的SFF节点。
在步骤212中，SFC代理节点判断NSH报文的报文头中是否包含OAM采集请求，若包含OAM采集请求，则SFC代理节点生成第一指令。在一些实施例中，SFC代理节点可以预存第一指令，通过读取存储器中存储的信息的方式获取第一指令。在一些实施例中，第一指令可以为指示节点采集OAM信息的可执行代码。
在步骤221中，SFC代理节点将第一指令添加至NSH报文的载荷字段。
在步骤222中，SFC代理节点基于第二域的协议封装更新后的载荷字段的数据，生成第一报文。该第一报文为基于第一域能够支持的协议的报文。
在步骤231中，SFC代理节点将第一报文发送给第二域的节点。
当第一域的节点获得第一报文后，通过识别载荷字段的数据，发现并运行其中的第一指令，执行采集SF OAM的操作，生成OAM信息。第一域的节点将生成的OAM信息放置在载荷字段，通过基于自身能够支持的协议的第三报文发送给SFC代理节点。
在步骤241中，SFC代理节点获取第二域的节点反馈的第三报文。
在步骤242中，SFC代理节点提取第三报文的载荷字段，获取载荷字段携带的OAM信息。
在步骤251中，SFC代理节点将提取出的OAM信息封装至NSH报文的报文头中。在一些实施例中，SFC代理节点可以将封装后的NSH报文反馈给位于第一域的SFF节点。
基于上文实施例中的方式，SFC代理节点将NSH报文头中的OAM需求信息进行的全局代码重构，有效的规避了SFC unaware域无法识别SF OAM需求信息的问题，无需对SFC unware域的设备进行升级改造，降低了工作负担和处理成本，提高了实现SFC全链节点OAM采集的部署效率。
在一些实施例中，上述步骤221、222中的第一报文的载荷字段也可以仅携带第一指令，步骤211中获得的NSH报文中载荷字段所携带的原始数据，可以通过第二报文发送给第二域的节点。在一些实施例中，SFC代理节点可以将这些用户数据基于第二域的协议封装后生成第二报文，进而将第二报文发送给第二域的节点，从而避免用户数据的漏处理。
在一些实施例中，上述步骤241、242中，第二域的节点反馈的第三报文的载荷字段可以仅携带第二域的节点获取的OAM信息。SFC代理节点还获取来自第二域的节点的第四报文，该报文的载荷字段携带有针对于第二报文中用户数据进行处理后的 数据。基于这样的方式，能够使携带数据与携带OAM信息的数据包分离，降低数据解析错误的概率。
本公开的信息采集方法的一些实施例的示意图如图3A所示。
第一域的SFF节点在需要获取SF节点33的SF OAM信息的情况下，向SF节点33发送NSH报文，报文头中携带OAM采集请求。NSH报文如301所示。SFC代理节点32位于SFF节点31与SF节点33之间，收到报文301。SFC代理节点32将NSH报文头中所携带的telemetry OAM采集请求进行代码重构，生成可直接运行的代码(图中称为第一指令)。
SFC代理节点32将此代码与原有的载荷字段的第一载荷数据Payload1进行整合，形成第二载荷数据Payload2。
SFC代理节点32将Payload2使用SFC-unware域的协议进行重新封装，生成报文302，并转发给SF节点33。
SF节点33解析报文302后，直接运行Payload2中的第一指令的代码，实现获得SF的OAM信息。
SF节点33将获取的OAM信息连同处理过的用户数据组合成第三载荷数据Payload3。
SFC节点33将Payload3使用SFC unware域的协议进行重新封装，生成报文303，并转发给SFC代理节点32。
SFC节点32接收报文303并解析，将Payload3中的OAM信息封装至扩展的NSH报文的报文头中，生成报文304，并将报文304反馈给SFF节点31，从而实现SFF节点31获取SFC unware域的节点的OAM信息。
在一些实施例中，如图3B所示，SFC代理节点32也可以将代码和原有的第一载荷数据Payload1分别作为Payload2，进而生成两个使用SFC-unware域的协议进行重新封装的报文302，发送给SF节点33。而SF节点33会分别对于两个报文进行处理，针对携带有第一指令的代码的报文，获取OAM信息；针对携带了Payload1的报文处理其用户数据，进而将OAM信息与用户数据分别作为Payload3，生成报文，并转发给SFC代理节点32。上文所示实施例中，通过将OAM采集请求转化为能够被运行实现采集OAM的代码的方式，有效的规避了由于通信双方需要事先定义SFC OAM字段所导致的、在SFC-unaware域无法识别SF OAM需求信息的问题；用载荷字段携带OAM需求信息规避了SFC-unware域的节点需要修改和扩展大量协议报文 头的问题，有利于低成本、快速的推广应用。
本公开的SFC代理节点41的一些实施例的示意图如图4所示。
指令生成单元411能够接收来自第一域的OAM采集请求，触发其生成第一指令的操作。在一些实施例中，第一指令为供第二域的节点运行的代码，第二域的节点在获得第一指令后能够直接运行第一指令，并通过运行第一指令获取OAM信息。
第一报文生成单元412能够根据第一指令和第二域的协议生成第一报文。在一些实施例中，第一报文生成单元412可以将第一指令添加至NSH报文的载荷字段，并基于第二域的协议，如VLAN、IP-in-IP、L2TPv3、GRE或VxLAN协议，封装添加第一指令后的载荷字段，获取第一报文。
第一报文发送单元413能够将第一报文发送给第二域的节点。
这样的SFC代理节点能够将第二域中节点无法识别的、基于SFC协议的OAM采集请求，转化为第二域中节点能够识别、且能够根据识别结果执行OAM信息采集的指令，从而无需对不支持SFC协议的设备升级，也能够获取这些设备的OAM信息，提高了采集的SF OAM信息的全面性，提高了OAM信息的参考价值，进而提高了基于OAM信息进行的分析的准确度。
在一些实施例中，如图4所示，SFC代理节点还可以包括信息接收单元414，能够获取第二域的节点反馈的OAM信息。在一些实施例中，信息接收单元414可以获取第二域的节点反馈的第三报文，通过提取第三报文的载荷字段，获取OAM信息。在一些实施例中，载荷字段中还包括第二域的节点处理后的用户数据，信息接收单元414从载荷字段识别出OAM信息。在一些实施例中，可以基于预定标识或预定字段位置提取OAM信息。
这样的SFC代理节点能够获得第二域的节点反馈的OAM信息，从而便于后续使用。
在一些实施例中，SFC代理节点还可以包括封装单元415，能够根据第一域的协议封装OAM信息。在一些实施例中，反馈单元415可以将OAM信息封装至NSH报文的报文头中，并将封装后的NSH报文反馈给位于第一域的服务功能转发SFF节点。在一些实施例中，第三报文载荷字段的用户数据可以通过NSH报文的载荷字段承载，从而确保不影响用户数据的交互功能。在另一些实施例中，封装有OAM信息的报文还可以发送给服务器。在一些实施例中，可以将OAM信息封装成其他所需格式并转发给对应的节点。
这样的SFC代理节点能够使第一域的节点收到的包含第二域节点OAM信息的报文为NSH报文，OAM信息的携带方式也符合SF协议，从而做到第一域的节点对于报文的转化过程无感知，不影响已有的SFC ware节点的OAM采集流程，避免影响SFC ware节点的处理效率。
本公开SFC代理节点的一个实施例的结构示意图如图5所示。SFC代理节点包括存储器501和处理器502。其中：存储器501可以是磁盘、闪存或其它任何非易失性存储介质。存储器用于存储上文中信息采集方法的对应实施例中的指令。处理器502耦接至存储器501，可以作为一个或多个集成电路来实施，例如微处理器或微控制器。该处理器502用于执行存储器中存储的指令，能够提高采集的OAM信息的全面性，进而提高了基于OAM信息进行的分析的准确度。
在一个实施例中，还可以如图6所示，SFC代理节点600包括存储器601和处理器602。处理器602通过BUS总线603耦合至存储器601。该SFC代理节点600还可以通过存储接口604连接至外部存储装置605以便调用外部数据，还可以通过网络接口606连接至网络或者另外一台计算机系统(未标出)。此处不再进行详细介绍。
在该实施例中，通过存储器存储数据指令，再通过处理器处理上述指令，能够提高采集的OAM信息的全面性，进而提高了基于OAM信息进行的分析的准确度。
在另一个实施例中，一种计算机可读存储介质，其上存储有计算机程序指令，该指令被处理器执行时实现信息采集方法对应实施例中的方法的步骤。本领域内的技术人员应明白，本公开的实施例可提供为方法、装置、或计算机程序产品。因此，本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用非瞬时性存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开的SFC的一些实施例的示意图如图7所示。
SFC代理节点71位于第一域的节点与第二域的节点之间，可以为上文中提到的任意一种。
第一域的节点72能够通过SFC代理节点向第二域的节点发送OAM采集请求。在一些实施例中，第一域中的节点具备支持SFC协议的能力。在一些实施例中，第一域的节点包括SFF节点。在一些实施例中，OAM采集请求可以通过NSH报文携带，如位于NSH报文的报文头中。
第二域的节点73能够根据来自SFC代理节点的第一指令采集OAM信息，并反馈给SFC代理节点。在一些实施例中，第二域中的节点不具备支持SFC协议的能力。
在一些实施例中，第二域的节点能够提取来自SFC代理节点的第一报文的载荷字段，在发现载荷字段中具备第一指令时，通过运行第一指令，获取OAM信息，并将OAM信息添加进第三报文的载荷字段，将第三报文反馈给SFC代理节点。
在一些实施例中，第二域的节点获取第一报文的载荷字段携带的用户数据，处理用户数据后，将处理结果通过第三报文的载荷字段承载，从而使对于数据的处理结果和OAM信息均能够通过第三报文反馈。
在另一些实施例中，第二域的节点还可以获取来自SFC代理节点的第二报文，该第二报文的载荷字段携带了用户数据。第二域的节点处理用户数据，并将处理结果通过第四报文的载荷字段承载，将第四报文反馈给SFC代理节点，从而使携带数据与携带OAM信息的数据包分离，降低数据解析错误的概率。
这样的SFC中，基于SFC代理节点的OAM采集请求的转化，能够使第二域中的节点采集并提供按OAM信息反馈给第一域，无需对第二域中的节点升级，提高了采集SFC全链的OAM信息的全面性，从而提高了OAM信息的参考价值，也有助于提高基于OAM信息进行的分析的准确度。
本公开是参照根据本公开实施例的方法、设备(系统)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算 机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
至此，已经详细描述了本公开。为了避免遮蔽本公开的构思，没有描述本领域所公知的一些细节。本领域技术人员根据上面的描述，完全可以明白如何实施这里公开的技术方案。
可能以许多方式来实现本公开的方法以及装置。例如，可通过软件、硬件、固件或者软件、硬件、固件的任何组合来实现本公开的方法以及装置。用于所述方法的步骤的上述顺序仅是为了进行说明，本公开的方法的步骤不限于以上具体描述的顺序，除非以其它方式特别说明。此外，在一些实施例中，还可将本公开实施为记录在记录介质中的程序，这些程序包括用于实现根据本公开的方法的机器可读指令。因而，本公开还覆盖存储用于执行根据本公开的方法的程序的记录介质。
最后应当说明的是：以上实施例仅用以说明本公开的技术方案而非对其限制；尽管参照较佳实施例对本公开进行了详细的说明，所属领域的普通技术人员应当理解：依然可以对本公开的具体实施方式进行修改或者对部分技术特征进行等同替换；而不脱离本公开技术方案的精神，其均应涵盖在本公开请求保护的技术方案范围当中。

Claims (23)

  1. 一种信息采集方法，包括：
    根据来自第一域的操作维护管理OAM采集请求，生成第一指令；
    根据所述第一指令和第二域的协议，生成第一报文；
    将所述第一报文发送给第二域的节点，以便所述第二域的节点根据所述第一指令采集OAM信息并反馈。
  2. 根据权利要求1所述的信息采集方法，还包括：
    获取所述第二域的节点反馈的OAM信息；
    根据所述第一域的协议封装所述OAM信息。
  3. 根据权利要求1所述的信息采集方法，其中，所述第一指令为供所述第二域的节点运行的代码，所述第二域的节点通过运行所述第一指令获取所述OAM信息。
  4. 根据权利要求3所述的信息采集方法，其中，所述第一指令为OAM需求信息的可执行代码。
  5. 根据权利要求1所述的信息采集方法，其中，所述OAM采集请求为通过网络服务头NSH报文携带。
  6. 根据权利要求1或5所述的信息采集方法，其中，所述根据所述第一指令和第二域的协议生成第一报文包括：
    将所述第一指令添加至NSH报文的载荷字段，基于第二域的协议封装所述载荷字段的数据，生成所述第一报文。
  7. 根据权利要求1或5所述的信息采集方法，其中，所述根据所述第一指令和第二域的协议生成第一报文包括：
    将所述第一指令作为载荷字段的内容，并基于第二域的协议封装所述载荷字段的数据，获取所述第一报文；
    所述方法还包括：
    将所述NSH报文中载荷字段的用户数据基于第二域的协议封装后生成第二报文，将所述第二报文发送给所述第二域的节点。
  8. 根据权利要求2所述的信息采集方法，其中，所述获取所述第二域的节点反馈的OAM信息包括：
    获取所述第二域的节点反馈的第三报文；
    提取所述第三报文的载荷字段，获取所述OAM信息。
  9. 根据权利要求2或8所述的信息采集方法，其中，所述根据所述第一域的协议封装所述OAM信息包括：将所述OAM信息封装至NSH报文的报文头中。
  10. 根据权利要求1所述的信息采集方法，其中，
    所述第一域中的节点具备支持服务链SFC协议的能力；和
    所述第二域中的节点不具备支持SFC协议的能力。
  11. 根据权利要求1所述的信息采集方法，其中，所述OAM采集请求包括收到的NSH报文中携带的OAM需求信息。
  12. 根据权利要求1所述的信息采集方法，其中，所述根据来自第一域的OAM采集请求，生成第一指令包括：
    根据所述OAM采集请求开启OAM信息获取功能OIAF；
    基于所述OIAF，根据所述OAM采集请求生成第一指令。
  13. 根据权利要求1所述的信息采集方法，其中，所述第二域的协议包括用于在服务链代理节点与所述第二域间交换信息的协议。
  14. 一种服务链代理节点，包括：
    指令生成单元，被配置为根据来自第一域的操作维护管理OAM采集请求生成第一指令；
    第一报文生成单元，被配置为根据所述第一指令和第二域的协议生成第一报文；
    第一报文发送单元，被配置为将所述第一报文发送给第二域的节点，以便所述第二域的节点根据所述第一指令采集OAM信息并反馈。
  15. 根据权利要求14所述的服务链代理节点，还包括：
    信息接收单元，被配置为获取所述第二域的节点反馈的OAM信息；
    封装单元，被配置为根据所述第一域的协议封装所述OAM信息。
  16. 一种服务链代理节点，包括：
    存储器；以及
    耦接至所述存储器的处理器，所述处理器被配置为基于存储在所述存储器的指令执行如权利要求1至13任一项所述的方法。
  17. 一种非瞬时性计算机可读存储介质，其上存储有计算机程序指令，该指令被 处理器执行时实现权利要求1至13任意一项所述的方法的步骤。
  18. 一种服务链，包括：
    权利要求14～16任意一项所述的服务链SFC代理节点；
    第一域的节点，被配置为通过所述SFC代理节点向第二域的节点发送操作维护管理OAM采集请求；和
    第二域的节点，被配置为根据来自所述SFC代理节点的第一指令采集OAM信息，并反馈给所述SFC代理节点，
    其中，所述SFC代理节点位于所述第一域的节点与所述第二域的节点之间。
  19. 根据权利要求18所述的服务链，其中，所述第一域的节点包括服务功能转发SFF节点。
  20. 根据权利要求18所述的服务链，其中，所述第二域的节点被配置为：
    提取来自所述SFC代理节点的第一报文的载荷字段；
    通过运行所述载荷字段中承载的所述第一指令，获取所述OAM信息；
    将所述OAM信息添加进第三报文的载荷字段；
    将所述第三报文反馈给所述SFC代理节点。
  21. 根据权利要求20所述的服务链，其中，所述第二域的节点还被配置为：
    获取所述第一报文的载荷字段携带的用户数据，处理所述用户数据后，将处理结果通过所述第三报文的载荷字段承载。
  22. 根据权利要求20所述的服务链，其中，所述第二域的节点还被配置为：
    获取来自所述SFC代理节点的第二报文，所述第二报文的载荷字段携带用户数据；和
    处理所述用户数据，并将所述处理结果通过第四报文的载荷字段承载，将所述第四报文反馈给所述SFC代理节点。
  23. 一种计算机程序，用于使处理器执行权利要求1至13任意一项所述的信息采集方法。
PCT/CN2022/115097 2022-04-13 2022-08-26 信息采集方法、服务链代理节点、服务链和存储介质 WO2023197499A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210384664.7A CN116962507A (zh) 2022-04-13 2022-04-13 信息采集方法、服务链代理节点、服务链和存储介质
CN202210384664.7 2022-04-13

Publications (1)

Publication Number Publication Date
WO2023197499A1 true WO2023197499A1 (zh) 2023-10-19

Family

ID=88328812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/115097 WO2023197499A1 (zh) 2022-04-13 2022-08-26 信息采集方法、服务链代理节点、服务链和存储介质

Country Status (2)

Country Link
CN (1) CN116962507A (zh)
WO (1) WO2023197499A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105765926A (zh) * 2013-10-14 2016-07-13 思科技术公司 可配置的服务代理映射
CN107078950A (zh) * 2014-10-24 2017-08-18 思科技术公司 透明网络服务报头路径代理
US20200136960A1 (en) * 2018-10-27 2020-04-30 Cisco Technology, Inc. Software version aware networking
CN112956164A (zh) * 2018-11-23 2021-06-11 华为技术有限公司 业务功能链接网络服务
CN113660140A (zh) * 2021-08-17 2021-11-16 北京交通大学 基于数据控制平面混合感知的服务功能链故障检测方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105765926A (zh) * 2013-10-14 2016-07-13 思科技术公司 可配置的服务代理映射
CN107078950A (zh) * 2014-10-24 2017-08-18 思科技术公司 透明网络服务报头路径代理
US20200136960A1 (en) * 2018-10-27 2020-04-30 Cisco Technology, Inc. Software version aware networking
CN112956164A (zh) * 2018-11-23 2021-06-11 华为技术有限公司 业务功能链接网络服务
CN113660140A (zh) * 2021-08-17 2021-11-16 北京交通大学 基于数据控制平面混合感知的服务功能链故障检测方法

Also Published As

Publication number Publication date
CN116962507A (zh) 2023-10-27

Similar Documents

Publication Publication Date Title
US9294302B2 (en) Non-fragmented IP packet tunneling in a network
CN110380970B (zh) 一种适用于异构网络的自适应数据报文转发方法及装置
CN105915427B (zh) 一种报文发送、接收方法及设备
US10404605B2 (en) Packet processing method, device and computer storage medium
CN112787931B (zh) 报文传输方法、代理节点及存储介质
EP3742685B1 (en) Packet processing method and device
CN112751769B (zh) 发送报文的方法、装置及系统
EP4120630A1 (en) Multicast data packet processing method, and apparatus
EP4047888A1 (en) Method for issuing oam configuration information and control node
WO2018188663A1 (zh) 信息通告方法及装置
EP3618365A1 (en) Packet forwarding
EP3618393B1 (en) Packet forwarding
WO2015196923A1 (zh) 一种发送信息的方法和网络装置
WO2019223795A1 (zh) 报文传输方法、通信装置和系统
CN112350934A (zh) 数据传输方法、网络节点和数据传输系统
EP3119046B1 (en) Tunnel type selection method and apparatus
CN112511483A (zh) 一种数据转发方法、设备和存储介质
WO2017193732A1 (zh) 一种伪线数据报文的封装、解封装方法和相关装置
JPWO2015025845A1 (ja) 通信システム、スイッチ、コントローラ、アンシラリデータ管理装置、データ転送方法及びプログラム
EP3965382A1 (en) Method and device for implementing service function processing
US20160134522A1 (en) Data flow processing method, device, and system
WO2023197499A1 (zh) 信息采集方法、服务链代理节点、服务链和存储介质
EP3902204A1 (en) Message sampling method and unpacking method, node, system and storage medium
CN113765762A (zh) 数据传输方法及装置
EP4142422A1 (en) Method and apparatus for session audit for control and user plane separation

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: 22937137

Country of ref document: EP

Kind code of ref document: A1