WO2021088629A1 - DetNet数据包处理方法及装置 - Google Patents

DetNet数据包处理方法及装置 Download PDF

Info

Publication number
WO2021088629A1
WO2021088629A1 PCT/CN2020/121947 CN2020121947W WO2021088629A1 WO 2021088629 A1 WO2021088629 A1 WO 2021088629A1 CN 2020121947 W CN2020121947 W CN 2020121947W WO 2021088629 A1 WO2021088629 A1 WO 2021088629A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
detnet
value
data packet
mpls
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/121947
Other languages
English (en)
French (fr)
Inventor
喻敬海
高陈强
戎立锋
刘爱华
熊泉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP20884778.0A priority Critical patent/EP4044529B1/en
Priority to US17/769,025 priority patent/US12199867B2/en
Publication of WO2021088629A1 publication Critical patent/WO2021088629A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/38—Flow based routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • the present disclosure relates to the field of network communication, and in particular, to a DetNet data packet processing method and device.
  • the DetNet architecture divides the data plane functions related to DetNet into two sublayers: the service sublayer and the forwarding sublayer.
  • the service sublayer is used to provide DetNet service functions, such as protection and reordering, including the DetNet control word (d-CW) and identification service label (S-Label);
  • the forwarding sublayer is used to provide forwarding guarantees (low loss, guaranteed Delay and limited reordering).
  • the IETF draft stipulates the MPLS network-based DetNet data plane operation and the encapsulation of DetNet service flow in its architecture model.
  • DetNet's MPLS-based encapsulation format is shown in Figure 1, where the DetNet control word (d-CW) contains sequence information (Sequence Number) for data packet duplication and deduplication purposes, and is also used for OAM indicators.
  • the format of the DetNet control word is shown in Figure 2. The first 4 bits are set to 0, and the last 28 bits are the Sequence Number value.
  • the application flow identification of the DetNet service sub-layer is realized by the service label (S-Label).
  • MPLS-aware DetNet terminal systems and edge nodes (defined as MPLS ingress and egress nodes) must add and delete application-specific d-CW and S-Label, and relay nodes can exchange S-Label when processing application streams.
  • the S-Label value must be provided for each application stream through configuration, for example, through the control plane configuration.
  • S-Label provides application flow identification at the downstream DetNet service sub-layer receiver (rather than the sender). Therefore, the S-Label must be allocated by the control service sublayer to receive the physical allocation of the node label space, and can be allocated from the platform label space. Since S-Label is a local label of each node, not a global identifier in the domain, it must be advertised to its upstream DetNet service-aware peer node (for example, DetNet MPLS terminal system or DetNet relay or edge node ).
  • each message must be parsed and matched whether the MPLS encapsulated DetNet application flow is time-consuming and inefficient.
  • the embodiments of the present disclosure provide a DetNet data packet processing method and device, so as to at least solve the problem that when a DetNet application flow message arrives at a DetNet node device in the related art, each message must be parsed and matched to determine whether the MPLS encapsulated DetNet application flow , Resulting in time-consuming and inefficient problems.
  • a DetNet data packet processing method which includes: when the DetNet application flow passes through the MPLS network, the DetNet node performs format encapsulation on the data packet of the DetNet application flow, wherein the encapsulated data
  • the packet includes a guide label and a flow indication; the encapsulated data packet is forwarded in the MPLS network.
  • a DetNet data packet processing method including: receiving a DetNet application stream data packet; determining whether the data packet is DetNet MPLS according to the label value Label of the boot label in the data packet An encapsulation format, wherein the data packet includes a boot label and a flow indication; if it is, the data packet is parsed and processed.
  • a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • an electronic device including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute any of the above Steps in the method embodiment.
  • Figure 1 is the MPLS-based encapsulation format of DetNet in the IETF draft
  • Figure 2 is the DetNet control word format in the IETF draft
  • Fig. 3 is a flowchart of a DetNet data packet processing method according to an embodiment of the present disclosure
  • Figure 4 is a DetNet MPLS-based encapsulation format according to an embodiment of the present disclosure
  • Figure 5 is a message encapsulation format according to an embodiment of the present disclosure.
  • Fig. 6 is an L2VPN message encapsulation format according to an embodiment of the present disclosure
  • Fig. 7 is an L2VPN message encapsulation format according to another embodiment of the present disclosure.
  • Fig. 8 is an encapsulation format using a Label value of 8 according to an embodiment of the present disclosure
  • FIG. 9 is an encapsulation format using an extended tag value of 15 according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of DetNet's MPLS network according to an embodiment of the present disclosure.
  • FIG. 11 is a processing flowchart of the Service layer of an edge ingress node according to an embodiment of the present disclosure
  • Fig. 12 is a flowchart of processing at the Service layer of an intermediate node according to an embodiment of the present disclosure
  • FIG. 13 is a processing flowchart of the Service layer of an edge out node according to an embodiment of the present disclosure
  • Fig. 14 is a schematic diagram of a DetNet data packet encapsulation format according to the first embodiment of the present disclosure
  • FIG. 15 is a schematic diagram of a DetNet data packet encapsulation format according to the second embodiment of the present disclosure.
  • Fig. 16 is a schematic diagram of a DetNet data packet encapsulation format according to the third embodiment of the present disclosure.
  • Fig. 17 is a schematic diagram of a DetNet data packet encapsulation format according to the fourth embodiment of the present disclosure.
  • a DetNet data packet processing method is provided.
  • Fig. 3 is a flow chart of the method according to the disclosed embodiment. As shown in Fig. 3, the process includes the following steps:
  • Step S302 When the DetNet application flow passes through the MPLS network, the DetNet node performs format encapsulation on the data packet of the DetNet application flow, wherein the encapsulated data packet includes a guide label and a flow indication.
  • Step S304 The encapsulated data packet is forwarded in the MPLS network.
  • an mpls-based DetNet data plane encapsulation is provided.
  • the encapsulation format is shown in Figure 4a and Figure 4b. It has two formats, consisting of three parts: a label (Label indication), a flow indication (FlowID header, or command header), and a sequence number (Sequence Number).
  • the boot label and flow indication are required, and the serial number is optional.
  • the new packaging format replaces the two fields of d-CW and S-Label in Figure 1, and the overall packaging format after replacement is shown in Figure 5.
  • there is a special L2VPN data whose encapsulation format is shown in Figure 6.
  • a new encapsulation label is inserted in the encapsulation format, and the overall encapsulation format after replacement is shown in Figure 7.
  • the boot label is a standard MPLS label stack code, and the label value (0-15) is reserved for MPLS.
  • the first 20 bits are the label value Label, values 0-3, 7, 13-15 have been used, and the value 15 is extensible.
  • the last 3bit Exp is a reserved bit.
  • the S bit indicates whether it is the bottom of the stack. When the value is 1, it is the bottom of the stack, and 0 is other label stack entries.
  • TTL is the time to live of 8bit.
  • the format complies with the RFC 3032 standard.
  • the boot label can also be a specific value specified by the system, and it may not be in the range of 0-15.
  • the first 20 bits of the flow indication are FlowID, that is, the S-Label value.
  • the last three digits of the reserved value take the last SN flag, indicating whether there is a Sequence number value, 0 means no, 1 means yes, the default is 1, and the first two digits are still reserved.
  • Next Header occupies 8 bits and indicates the encapsulation type after Sequence number. 0 means no subsequent encapsulation, 1 means OAM data, and 2 means PW (pseudo wire) encapsulation.
  • the sequence number is the Sequence Number value, which occupies 32 bits, and is used for data packet replication and deduplication.
  • the guide label can also have two formats:
  • Label value can apply to reserve the unused value in the value, such as the value 8.
  • the encapsulation format is shown in Figure 8.
  • the other is to use an extended label value of 15, which means that the data after the boot label is expandable. Insert a new boot label after the boot label, use only the DetNet-Label value in it, and assign a new default value, such as 15, The rest can be set to a fixed value of 0 or 1 (not used in practice). Use the extended boot label to indicate that this encapsulation is DetNet's MPLS encapsulation. After the new DetNet-Label field is still the stream indication and serial number. The encapsulation format is shown in Figure 9.
  • the DetNet device when the message reaches the DetNet device, it only needs to parse whether the Label in the boot label is 8 or 15, and determine whether it is DetNet MPLS encapsulation. If it is 15, continue to determine whether the DetNet-Label value is 15.
  • the Sequence Number and S-label are analyzed, which greatly simplifies the complexity of recognition.
  • the Service layer of each node recognizes and forwards it.
  • the application flow passes from the IP DetNet terminal on the left through the DetNet MPLS network to the IP DetNet terminal on the right.
  • the Service layer of each node performs DetNet-related encapsulation and operations.
  • These nodes include the ingress node of the edge node, the egress node of the edge node, and the intermediate forwarding node.
  • the three types of nodes are as follows:
  • the IP DetNet terminal on the left is the ingress node of the edge node, and the Service layer within it encapsulates the message, including the generation of FlowID and Sequence Number, and encapsulates it according to the encapsulation format described above in this embodiment.
  • the flow chart is As shown in Figure 11, the processing steps are as follows:
  • Step S1101 Whether the node is a DetNet ingress node, if yes, continue processing, otherwise go to step S1105;
  • Step S1102 Generate FlowID and Sequence Number, and encapsulate the message according to the encapsulation format described above in this embodiment;
  • Step S1103 whether to perform a packet copy operation, if yes, continue processing, otherwise go to step S1105;
  • Step S1104 Perform a packet copy operation according to FlowID and Sequence Number
  • Step S1105 subsequent functional operations
  • the intermediate network node performs a series of functional operations such as packet forwarding and packet duplication elimination according to the parsed FlowID and Sequence Number, and the FlowID is variable or unchanged during the forwarding process.
  • the flowchart is shown in Figure 12, and the processing steps are as follows:
  • Step S1201 Whether the packet has DetNet MPLS encapsulation, if yes, go to step S1203, otherwise continue processing;
  • Step S1202 Generate FlowID and Sequence Number, and encapsulate the message according to the encapsulation format of this embodiment
  • Step S1203 whether to perform packet copy and delete operations, if yes, continue processing, otherwise go to step S1205;
  • Step S1204 Perform packet copy and delete operations according to FlowID and Sequence Number
  • Step S1205 subsequent functional operations
  • IP DetNet terminal on the right is the outgoing node of the edge node, and the Service layer within it decapsulates the message.
  • the flowchart is shown in Figure 13, and the processing steps are as follows:
  • Step S1301 Whether the node is an outgoing node of DetNet, if yes, continue processing, otherwise go to step S1305;
  • Step S1302 whether to perform packet elimination operation, if yes, continue processing, otherwise go to step S1304;
  • Step S1303 Eliminate duplicate packets according to FlowID and Sequence Number
  • Step S1304 Decapsulate the message
  • Step S1305 subsequent functional operations
  • the guide label is effectively used, which greatly simplifies the identification complexity of the MPLS encapsulation of the DetNet message.
  • the first method is used for the boot tag, and it has a Sequence Number value.
  • the encapsulation format is shown in Figure 14.
  • the DetNet device node receives the application flow data packet, it judges whether the Label value is 8. If it is, it is the DetNet MPLS encapsulation format, and the FlowID and Sequence Number are parsed for subsequent processing.
  • the first method is used for the boot tag, and there is no Sequence Number value.
  • the encapsulation format is shown in Figure 15.
  • Set the source address of the DetNet flow to 10.1.1.2, the destination address to 10.2.2.2, the Label value to 8, the Exp value after the FlowID is 0, the Next Header value is 0, and the FlowID generated by the application is 2. .
  • the DetNet device node receives the application flow data packet, it judges whether the Label value is 8. If it is, it is the DetNet MPLS encapsulation format, and the FlowID is parsed for subsequent processing.
  • the guide label uses the second method, and has a Sequence Number value.
  • the encapsulation format is shown in Figure 16.
  • Set the source address of the DetNet flow to 10.1.1.3, the destination address to 10.2.2.3, the Label value is 15, the Exp value after FlowID is 1, the DetNet-Label value is 15, and the NextHeader value is 0 , The FlowID and Sequence Number generated by the application are 3 and 101 respectively.
  • the DetNet device node receives the application flow data packet, it judges whether the Label value is 15. If it is, continue to judge whether the DetNet-Label value is 15. If it is, it is the DetNet MPLS encapsulation format, and the FlowID and Sequence Number are parsed out Do follow-up processing.
  • the second method is used for the boot tag, and there is a Sequence Number value, and there is encapsulation data after the Sequence Number.
  • the encapsulation format is shown in Figure 17.
  • the subsequent encapsulation is PW, and the FlowID and Sequence Number generated by the application are 4 and 102, respectively.
  • the DetNet device node receives the application flow data packet, it judges whether the Label value is 15. If it is, continue to judge whether the DetNet-Label value is 15. If it is, it is the DetNet MPLS encapsulation format, and the FlowID and Sequence Number are parsed out Do follow-up processing.
  • the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of the present disclosure essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the methods described in the various embodiments of the present disclosure.
  • the embodiment of the present disclosure also provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • the foregoing storage medium may include, but is not limited to: U disk, Read-Only Memory (Read-Only Memory, ROM for short), Random Access Memory (Random Access Memory, RAM for short), Various media that can store computer programs, such as mobile hard disks, magnetic disks, or optical disks.
  • An embodiment of the present disclosure also provides an electronic device, including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute the steps in any of the foregoing method embodiments.
  • the aforementioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the aforementioned processor, and the input-output device is connected to the aforementioned processor.
  • a guide label is added to the MPLS encapsulation, and the d-CW and S-Label in the original encapsulation format are changed at the same time, which simplifies the identification of the label, so that the application can send it directly after the Sequence Number and S-Label are generated.
  • the relay node does not need to change and exchange S-Label, thus shortening the forwarding time and improving the forwarding efficiency.
  • modules or steps of the present disclosure can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
  • they can be implemented with program codes executable by the computing device, so that they can be stored in the storage device for execution by the computing device, and in some cases, can be executed in a different order than here.

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

本公开提供了一种DetNet数据包处理方法和装置，该方法包括：当DetNet应用流经过MPLS网络时，DetNet节点对所述DetNet应用流的数据包进行格式封装，其中，所述封装的数据包中包括引导标签和流指示；将封装后的所述数据包在所述MPLS网络中进行转发。在本公开中，通过在MPLS封装中加入引导标签，大大简化了DetNet报文MPLS封装的识别复杂度。中继节点不需要改变和交换S-Label，从而缩短了转发时间，提高了转发效率。

Description

DetNet数据包处理方法及装置 技术领域
本公开涉及网络通信领域，具体而言，涉及一种DetNet数据包处理方法及装置。
背景技术
在MPLS分组交换网络上运行确定性业务流时，其数据平面由IETF的草案DetNet Data Plane:MPLS draft-ietf-detnet-mpls-01指定。
DetNet架构将与DetNet相关的数据平面功能分为两个子层：服务子层和转发子层。服务子层用于提供DetNet服务功能，如保护和重新排序，包含DetNet控制字(d-CW)和识别服务标签(S-Label)；转发子层用于提供转发保证(低损耗、有保证的延迟和有限的重新排序)。IETF草案中规定了其架构模型中，基于MPLS网络的DetNet数据平面操作和DetNet业务流的封装。
DetNet基于MPLS的封装格式如图1所示，其中DetNet控制字(d-CW)包含序列信息(Sequence Number)用于数据包复制和重复消除目的，另外用于OAM指示器。DetNet控制字格式如图2所示，前4bit置为0，后28bit是Sequence Number值。DetNet服务子层的应用流标识是通过服务标签(S-Label)实现的。MPLS感知的DetNet终端系统和边缘节点(定义为MPLS入口和出口节点)，必须添加和删除特定于应用流的d-CW和S-Label，中继节点在处理应用流时可以交换S-Label。必须通过配置为每个应用流提供S-Label值，例如可以通过控制平面配置。S-Label在下游DetNet服务子层接收器(而不是发送器)提供应用流标识。因此，S-Label必须由控制服务子层接收节点标签空间的实体分配，并且可以从平台标签空间分配。由于S-Label是每个节点的本地标签，而不是域中的全局标识符，因此必须将其通告到其上游的DetNet服务感知对等节点(例如，DetNet MPLS终端系统或DetNet中继或边缘节点)。
由于S-Label的分配及其通告过程复杂，并且在报文到达DetNet节点设备时，每个报文都要解析并匹配是否MPLS封装的DetNet应用流，耗时且效率低下。
发明内容
本公开实施例提供了一种DetNet数据包处理方法及装置，以至少解决相关技术中在DetNet应用流报文到达DetNet节点设备时，每个报文都要解析并匹配是否MPLS封装的DetNet应用流，从而导致耗时且效率低下的问题。
根据本公开的实施例，提供了一种DetNet数据包处理方法，包括：当DetNet应用流经过MPLS网络时，DetNet节点对所述DetNet应用流的数据包进行格式封装，其中，所述封装的数据包中包括引导标签和流指示；将封装后的所述数据包在所述MPLS网络中进行转发。
根据本公开的实施例，还提供了一种DetNet数据包处理方法，包括：接收DetNet应用流数据包；根据所述数据包中的引导标签的标签值Label确定所述数据包是否为DetNet的MPLS封装格式，其中，所述数据包中包括引导标签和流指示；如果是，则对所述数据包进行解析和处理。
根据本公开的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是IETF草案中DetNet基于MPLS的封装格式；
图2是IETF草案中的DetNet控制字格式；
图3是根据本公开实施例的DetNet数据包处理方法的流程图；
图4是根据本公开实施例的DetNet基于MPLS的封装格式；
图5是根据本公开实施例的报文封装格式；
图6是根据本公开实施例的L2VPN报文封装格式；
图7是根据本公开另一实施例的L2VPN报文封装格式；
图8是根据本公开实施例的使用Label值8的封装格式；
图9是根据本公开实施例的使用扩展标签值15的封装格式；
图10是根据本公开实施例的DetNet的MPLS网络示意图；
图11是根据本公开实施例的边缘入节点Service层处理流程图；
图12是根据本公开实施例的中间节点Service层处理流程图；
图13是根据本公开实施例的边缘出节点Service层处理流程图；
图14是根据本公开实施例一的DetNet数据包封装格式示意图；
图15是根据本公开实施例二的DetNet数据包封装格式示意图；
图16是根据本公开实施例三的DetNet数据包封装格式示意图；
图17是根据本公开实施例四的DetNet数据包封装格式示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种DetNet数据包处理方法，图3是根据本公 开实施例的方法流程图，如图3所示，该流程包括如下步骤：
步骤S302，当DetNet应用流经过MPLS网络时，DetNet节点对所述DetNet应用流的数据包进行格式封装，其中，所述封装的数据包中包括引导标签和流指示。
步骤S304，将封装后的所述数据包在所述MPLS网络中进行转发。
在本实施例中，提供了一种基于mpls的DetNet数据平面封装。其封装格式如图4a和图4b所示，其有两种格式，由引导标签(Label indication)、流指示(FlowID header，或称为指令头)和序列号(Sequence Number)三部分组成。引导标签和流指示是必须的，序列号是可选的。新的封装格式取代图1中的d-CW和S-Label两个字段，取代后的整体封装格式如图5所示。另外有一种特殊的L2VPN数据，其封装格式如图6所示，在其封装格式中插入新的封装标签，取代后的整体封装格式如图7所示。
在本实施例的DetNet数据平面封装格式中，引导标签是标准的MPLS标签栈编码，为MPLS保留标签值(0-15)。前20bit是标签值Label，值0-3、7、13-15已经被使用，其中值15是可扩展的。后3bit的Exp是保留位。S位指示是否是栈底，值为1时是栈底，为0是其他标签栈表项。TTL是8bit的生存时间。格式符合RFC 3032标准。另外，这个引导标签也可以是系统指定的特定值，可以不在0-15范围内。
在本实施例的DetNet数据平面封装格式中，流指示的前20bit是FlowID，即S-Label值。后三位的保留值取最后一位SN flag，指示是否有Sequence number值，0表示没有，1表示有，默认是1，前两位仍保留。Next Header占8bit，指示Sequence number后的封装类型，0表示没有后续封装，1表示有OAM数据，2表示有PW(伪线)封装。
在本实施例的DetNet数据平面封装格式中，序列号中是Sequence Number值，占32bit，用于数据包复制和重复消除。
在本实施例的DetNet数据平面封装格式中，引导标签也可以有两种格式：
一种是Label值可以申请保留值中未被使用的值，例如值8。则其封装格式如图8所示。
另一种是使用扩展标签值15，表示引导标签后数据是可扩展的，在引导标签后插入新的引导标签，只使用其中的DetNet-Label值，并分配一个新的默认值，如15，其余的可以置为固定值0或1(实际中不使用)。用扩展的引导标签指示此封装是DetNet的MPLS封装。新的DetNet-Label字段后仍然是流指示和序列号。其封装格式如图9所示。
按照本实施例提供的新的报文封装格式，当报文到达DetNet设备时，只需要解析引导标签中的Label是否是8或者15，判断是否为DetNet的MPLS封装。如果是15，则需继续判断DetNet-Label值是否为15。通过引导标签识别，从而解析Sequence Number和S-label，大大简化了识别的复杂度。
如图10所示，DetNet应用流经过MPLS网络时，各节点的Service层进行识别并转发，应用流从左侧的IP DetNet终端经过DetNet MPLS网络，并到达右侧的IP DetNet终端。各节点的Service层进行DetNet相关的封装和操作，这些节点包括边缘节点的入节点、边缘节点的出节点和中间转发节点，三种类型节点如下：
1)左侧的IP DetNet终端是边缘节点的入节点，其内的Service层进行报文的封装，包括FlowID和Sequence Number的生成，并根据本实施例上述描述的封装格式进行封装，其流程图如图11所示，处理步骤如下：
步骤S1101：节点是否是DetNet入节点，若是，继续处理，否则转步骤S1105；
步骤S1102：生成FlowID和Sequence Number，并根据本实施例上述描述的的封装格式进行报文的封装；
步骤S1103：是否进行包复制操作，若是，继续处理，否则转步骤S1105；
步骤S1104：根据FlowID和Sequence Number进行包复制操作；
步骤S1105：后续功能操作；
2)中间网络节点根据解析的FlowID和Sequence Number进行报文的转发和包复制消除等一系列功能操作，转发过程中FlowID可变可不变。其流程图如图12所示，处理步骤如下：
步骤S1201：报文是否有DetNet的MPLS封装，若是，转步骤S1203，否则继续处理；
步骤S1202：生成FlowID和Sequence Number，并根据本实施例的封装格式进行报文的封装；
步骤S1203：是否进行包复制和消除操作，若是，继续处理，否则转步骤S1205；
步骤S1204：根据FlowID和Sequence Number进行包复制和消除操作；
步骤S1205：后续功能操作；
3)右侧的IP DetNet终端是边缘节点的出节点，其内的Service层进行报文的解封装。其流程图如图13所示，处理步骤如下：
步骤S1301：节点是否是DetNet出节点，若是，继续处理，否则转步骤S1305；
步骤S1302：是否进行包消除操作，若是，继续处理，否则转步骤S1304；
步骤S1303：根据FlowID和Sequence Number进行重复包消除；
步骤S1304：报文解封装；
步骤S1305：后续功能操作；
在本公开的上述实施例中，有效利用了引导标签，大大简化了DetNet报文MPLS封装的识别复杂度。
为了便于对本公开实施例所提供的技术方案的理解，下面将结合具体应用场景实施例进行详细描述。
实施例一：
在本实施例中，引导标签使用第一种方式，且有Sequence Number值。
其封装格式如图14所示，设DetNet流的源地址10.1.1.1，目的地址10.2.2.1，Label值为8，FlowID后的Exp值为1，Next Header值为0，应用产生的FlowID和Sequence Number分别为1和100。当DetNet设备节点接收到应用流数据包时，判断Label值是否为8，如果是，则是DetNet的MPLS封装格式，通过解析出FlowID和Sequence Number做后续处理。
实施例二：
在本实施例中，引导标签使用第一种方式，且无Sequence Number值。
其封装格式如图15所示，设DetNet流的源地址10.1.1.2，目的地址10.2.2.2，Label值为8，FlowID后的Exp值为0，Next Header值为0，应用产生的FlowID为2。当DetNet设备节点接收到应用流数据包时，判断Label值是否为8，如果是，则是DetNet的MPLS封装格式，通过解析出FlowID做后续处理。
实施例三：
在本实施例中，引导标签使用第二种方式，且有Sequence Number值。
其封装格式如图16所示，设DetNet流的源地址10.1.1.3，目的地址10.2.2.3，Label值为15，FlowID后的Exp值为1，DetNet-Label值为15，Next Header值为0，应用产生的FlowID和Sequence Number分别为3和101。当DetNet设备节点接收到应用流数据包时，判断Label值是否为15，如果是，继续判断DetNet-Label值是否为15，如果是，则是DetNet的MPLS封装格式，通过解析出FlowID和Sequence Number做后续处理。
实施例四：
在本实施例中，引导标签使用第二种方式，且有Sequence Number值，Sequence Number后有封装数据。
其封装格式如图17所示，设DetNet流的源地址10.1.1.4，目的地址10.2.2.4，Label值为16，FlowID后的Exp值为1，DetNet-Label值为15， Next Header值为2，后续封装为PW，应用产生的FlowID和Sequence Number分别为4和102。当DetNet设备节点接收到应用流数据包时，判断Label值是否为15，如果是，继续判断DetNet-Label值是否为15，如果是，则是DetNet的MPLS封装格式，通过解析出FlowID和Sequence Number做后续处理。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
本公开的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
通过本公开实施例，在MPLS封装中加入引导标签，同时改变原封装格式中的d-CW和S-Label，简化了标签的识别，使得应用生成Sequence  Number和S-Label后，可直接发送，中继节点不需要改变和交换S-Label，从而缩短了转发时间，提高了转发效率。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (16)

  1. 一种DetNet数据包处理方法，包括：
    当DetNet应用流经过MPLS网络时，DetNet节点对所述DetNet应用流的数据包进行格式封装，其中，所述封装的数据包中包括引导标签和流指示；
    将封装后的所述数据包在所述MPLS网络中进行转发。
  2. 根据权利要求1所述的方法，其中，其中，所述封装的数据包中还包括序列号Sequence number，所述序列号为可选。
  3. 根据权利要求1所述的方法，其中，所述引导标签为标准的MPLS标签栈编码，依次包括：20bit的标签值Label，3bit的Exp保留位，1bit的S位指示是否为栈底，8bit的TTL生存时间。
  4. 根据权利要求1所述的方法，其中，所述引导标签值为标准的MPLS标签栈编码的保留值中未被使用的值或扩展标签值，或系统指定的特定值。
  5. 根据权利要求1所述的方法，其中，其中，所述流指示依次包括20bit的FlowID、3bit的保留值，1bit的S位指示是否为栈底，8bit的Next Header；其中，所述保留值的最后一位SN flag指示是否有Sequence number值，所述Next Header用于指示Sequence number后的封装类型。
  6. 根据权利要求1所述的方法，其中，其中，所述序列号Sequence Number值占32bit，用于数据包复制和重复消除。
  7. 根据权利要求4所述的方法，其中，当所述引导标签-的标签值为扩展标签值时，表示所述引导标签后的数据是可扩展的，在所述引导标签后插入扩展的引导标签，其中，在所述扩展的引导标签中，仅使用其中的DetNet-Label值，并为所述DetNet-Label分配有一个新 的默认值。
  8. 一种DetNet数据包处理方法，包括：
    接收DetNet应用流数据包；
    根据所述数据包中的引导标签的标签值Label确定所述数据包是否为DetNet的MPLS封装格式，其中，所述数据包中包括引导标签和流指示；
    如果是，则对所述数据包进行解析和处理。
  9. 根据权利要求8所述的方法，其中，其中，所述数据包中还包括序列号，所述序列号为可选。
  10. 根据权利要求8所述的方法，其中，所述引导标签为标准的MPLS标签栈编码，依次为：20bit的标签值Label，3bit的Exp保留位，1bit的S位指示是否为栈底，8bit的TTL生存时间。
  11. 根据权利要求8所述的方法，其中，所述引导标签值为标准的MPLS标签栈编码的保留值中未被使用的值或扩展标签值，或系统指定的特定值。
  12. 根据权利要求11所述的方法，其中，当所述引导标签的标签值为扩展标签值时，表示所述引导标签后的数据是可扩展的，在所述引导标签后插入扩展的引导标签，其中，在所述扩展的引导标签中，仅使用其中的DetNet-Label值，并为所述DetNet-Label分配有一个默认值。
  13. 根据权利要求11所述的方法，其中，根据所述数据包中的引导标签的标签值确定所述数据包是否为DetNet的MPLS封装格式包括：
    判断所述引导标签的标签值是否为约定值，其中所述约定值为所述保留值中未被使用的值；
    如果是，则确定所述数据包为DetNet的MPLS封装格式。
  14. 根据权利要求12所述的方法，其中，根据所述数据包中的引导标签的标签值确定所述数据包是否为DetNet的MPLS封装格式包括：
    判断所述引导标签的标签值是否为扩展标签值，如果是，则继续判断扩展的引导标签中的DetNet-Label值是否为约定的默认值，如果是，则确定所述数据包为DetNet的MPLS封装格式。
  15. 一种计算机可读存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至14任一项中所述的方法。
  16. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至14任一项中所述的方法。
PCT/CN2020/121947 2019-11-05 2020-10-19 DetNet数据包处理方法及装置 Ceased WO2021088629A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20884778.0A EP4044529B1 (en) 2019-11-05 2020-10-19 Detnet data packet processing method and apparatus
US17/769,025 US12199867B2 (en) 2019-11-05 2020-10-19 Method and apparatus for processing DetNet data packet

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911072282.5 2019-11-05
CN201911072282.5A CN112769738B (zh) 2019-11-05 2019-11-05 DetNet数据包处理方法及装置

Publications (1)

Publication Number Publication Date
WO2021088629A1 true WO2021088629A1 (zh) 2021-05-14

Family

ID=75692875

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/121947 Ceased WO2021088629A1 (zh) 2019-11-05 2020-10-19 DetNet数据包处理方法及装置

Country Status (4)

Country Link
US (1) US12199867B2 (zh)
EP (1) EP4044529B1 (zh)
CN (1) CN112769738B (zh)
WO (1) WO2021088629A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023241053A1 (zh) * 2022-06-15 2023-12-21 中兴通讯股份有限公司 信息处理方法、设备和存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12519735B2 (en) * 2021-06-04 2026-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Deterministic networking operations administration and maintenance for deterministic network service sub-layer
CN113507414B (zh) * 2021-06-30 2023-09-19 新华三信息安全技术有限公司 一种报文处理方法及装置
CN117221412A (zh) * 2022-06-02 2023-12-12 中兴通讯股份有限公司 一种IPv4报文的封装方法、电子设备和计算机存储介质
CN116781611A (zh) * 2022-11-23 2023-09-19 国网江苏省电力有限公司信息通信分公司 一种基于灵活以太网和确定性网络的数据交换设备和方法
CN116319400A (zh) * 2022-12-30 2023-06-23 南京江岳环保科技有限公司 一种环保管家监测服务系统及方法
CN119135641A (zh) * 2023-06-13 2024-12-13 中兴通讯股份有限公司 报文传输方法、电子设备、计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109561021A (zh) * 2017-09-25 2019-04-02 华为技术有限公司 一种报文转发的方法及网络设备
CN110324242A (zh) * 2018-03-29 2019-10-11 华为技术有限公司 一种报文发送的方法、网络节点和系统
WO2019205756A1 (zh) * 2018-04-27 2019-10-31 中兴通讯股份有限公司 数据发送保护方法、装置、系统及计算机可读存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9088519B2 (en) * 2012-06-15 2015-07-21 Juniper Networks, Inc. Allocating and distributing labels for packet encapsulation
CN104506433B (zh) * 2014-12-30 2018-07-06 盛科网络（苏州）有限公司 一种mpls网络中识别ptp报文的方法和装置
CN108259338B (zh) * 2017-06-20 2021-06-29 新华三技术有限公司 一种私网应用识别方法及装置
CN108111416B (zh) * 2017-12-15 2020-10-23 盛科网络（苏州）有限公司 直接识别mpls内部封装报文的方法
CN110224934B (zh) * 2018-03-01 2021-11-09 中兴通讯股份有限公司 一种利用统一sr标签栈进行报文处理的方法及装置
WO2019210769A1 (en) * 2018-05-03 2019-11-07 Huawei Technologies Co., Ltd. Explicit routing with network function encoding
CN111953604B (zh) * 2019-05-17 2023-07-18 华为技术有限公司 一种为业务流提供业务服务的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109561021A (zh) * 2017-09-25 2019-04-02 华为技术有限公司 一种报文转发的方法及网络设备
CN110324242A (zh) * 2018-03-29 2019-10-11 华为技术有限公司 一种报文发送的方法、网络节点和系统
WO2019205756A1 (zh) * 2018-04-27 2019-10-31 中兴通讯股份有限公司 数据发送保护方法、装置、系统及计算机可读存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
BRYANT S., CHEN M.: "Operation of Deterministic Networks over MPLS draft-bryant-detnet-mpls-dp-00", DETNET WORKING GROUP, INTERNET-DRAFT, INTENDED STATUS: STANDARDS TRACK, 5 March 2018 (2018-03-05), XP055809919, Retrieved from the Internet <URL:https://tools.ietf.org/pdf/draft-bryant-detnet-mpls-dp-00.pdf> [retrieved on 20210602] *
J. KORHONEN, ED. B. VARGA, ED. ERICSSON: "DetNet MPLS Data Plane Encapsulation; draft-ietf-detnet-dp-sol-mpls-00.txt", DETNET MPLS DATA PLANE ENCAPSULATION; DRAFT-IETF-DETNET-DP-SOL-MPLS-00.TXT; INTERNET-DRAFT: DETNET, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, no. 00, 1 July 2018 (2018-07-01), Internet Society (ISOC) 4, rue des Falaises CH- 1205 Geneva, Switzerland, pages 1 - 46, XP015127291 *
See also references of EP4044529A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023241053A1 (zh) * 2022-06-15 2023-12-21 中兴通讯股份有限公司 信息处理方法、设备和存储介质

Also Published As

Publication number Publication date
EP4044529B1 (en) 2026-04-29
EP4044529A4 (en) 2022-11-23
EP4044529A1 (en) 2022-08-17
CN112769738A (zh) 2021-05-07
CN112769738B (zh) 2023-09-12
US12199867B2 (en) 2025-01-14
US20240106751A1 (en) 2024-03-28

Similar Documents

Publication Publication Date Title
CN112769738B (zh) DetNet数据包处理方法及装置
KR102753139B1 (ko) Sr 네트워크에서 패킷을 전달하는 방법, 장치 및 시스템
CN109039919B (zh) 转发路径确定方法、装置、系统、计算机设备及存储介质
CN105684382A (zh) 报文的控制方法、交换机及控制器
CN112787902B (zh) 报文封装方法及装置、报文解封装方法及装置
WO2021088433A1 (zh) 一种报文的处理方法，装置和系统
US12537760B2 (en) Packet forwarding method and apparatus, network device, and storage medium
CN110224934A (zh) 一种利用统一sr标签栈进行报文处理的方法及装置
WO2021057683A1 (zh) 一种报文处理方法及装置
CN108429652A (zh) 基于sdn的远端流镜像控制方法、实现方法及相关设备
CN107547346B (zh) 一种报文传输方法和装置
CN106878181A (zh) 一种报文传输方法和装置
CN107968749A (zh) 实现QinQ路由终结的方法、交换芯片及交换机
CN105099919B (zh) 报文处理方法及装置
WO2023088145A1 (zh) 一种报文处理方法、装置及设备
KR102815947B1 (ko) 서비스 처리 방법, 장치, 설비 및 저장 매체
CN112350957B (zh) 一种网络报文发送的方法、装置和网络处理器
CN111447131B (zh) 报文解封装方法及装置、报文封装方法及装置
CN111371909B (zh) 实现4in6 DS Lite数据流转发方法、系统
CN107645401A (zh) 多协议标签交换的检测、处理方法、装置及系统
CN117041142A (zh) 报文转发方法、装置、设备、介质和程序产品
CN116455810A (zh) 报文转发方法、装置、可读存储介质以及电子设备
CN109474527B (zh) 一种报文转发方法及装置
CN114697160A (zh) 一种隧道报文的处理方法和装置
CN113765794B (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: 20884778

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 17769025

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2020884778

Country of ref document: EP

Effective date: 20220413

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2020884778

Country of ref document: EP