WO2023165244A1 - 报文的发送方法、装置、存储介质及电子装置 - Google Patents

报文的发送方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2023165244A1
WO2023165244A1 PCT/CN2022/143056 CN2022143056W WO2023165244A1 WO 2023165244 A1 WO2023165244 A1 WO 2023165244A1 CN 2022143056 W CN2022143056 W CN 2022143056W WO 2023165244 A1 WO2023165244 A1 WO 2023165244A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
field
domain
data information
label
Prior art date
Application number
PCT/CN2022/143056
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 WO2023165244A1 publication Critical patent/WO2023165244A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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

Definitions

  • the present disclosure relates to the communication field, and in particular, to a message sending method, device, storage medium, and electronic device.
  • MPLS Multi-Protocol Label Switching
  • edge devices in the MPLS network After receiving the data packets, the edge devices in the MPLS network analyze the contents of the data packets, select appropriate labels for these data packets, and use the obtained fixed-length labels to encapsulate the data packets and send them to the MPLS network. All routers in the MPLS network use this fixed-length label instead of the IP header as the basis for forwarding. When the data packet finally leaves the MPLS network, the fixed-length label is stripped by the edge device in the MPLS network. This method of using the MPLS technology to forward data packets improves the efficiency of data forwarding.
  • IPv6 Internet Protocol version 6, Internet Protocol version 6
  • IPv6 extension header includes Hop-by-Hop Options Header, Routing Header, Destination Options Header, etc.
  • SR Segment Router, segment routing
  • SRv6 segment routing header
  • SR-MPLS label stack
  • IPv6 IPv6 packet header
  • SRv6 network programming network programming
  • SRv6 Segment is a 128-bit number, usually also called SRv6 SID or SID.
  • SRv6 SID is a network instruction (Instruction), including Locator, Function and possible parameter Argument. Locator is mainly responsible for routing functions and is unique in the SR domain. Function can mark any function of the device, such as a certain forwarding behavior, or a certain service, etc. Argument is mainly used to carry parameters related to the function.
  • the structure of the SRv6 SID facilitates programming of the network.
  • MPLS2.0 This new, under-design MPLS architecture solution is called MPLS2.0 hereinafter.
  • Indicator Indicator
  • the indicator is located in the MPLS label stack and is used to indicate the data carried in/behind the stack.
  • One possible scheme is called multi-intent special tags, as shown in Figure 1.
  • This solution includes special label values (the position of Forwarding Actions Indicator shown in Figure 1), and the label corresponding to the special label value can be understood as a multi-intent special label; unlike other MPLS labels, there are no TC and In the TTL part, the corresponding space is used to store the Flag indication bit, and different indication meanings are indicated by setting different Flag positions.
  • bit-A is set to indicate that the indicator carries entropy label information
  • bit-B is set to indicate that the indicator is followed by network slice identification information
  • bit-C is set to indicate that the label stack is followed by auxiliary data information
  • bit-D indicates that the subsequent Also extended 32bit to carry more Flag bits (the Forwarding Actions Header part in the figure) and so on.
  • the data carried. Data is carried in or after the label stack.
  • the identification method of the type of data may include a method of specifying by using an indicator, a method of carrying data type information in the data itself, or a method of carrying the type information indicating the next data in the previous data.
  • Figure 2 illustrates a way of carrying data behind the label stack.
  • Each MPLS extension header carries a type of data, and the extension header contains a next header (NH) field to indicate the type of the next extension header. Before all extension headers, there is a header, in which the NH field is used to indicate the type of the first extension header.
  • MPLS 2.0 mainly changes the data carrying and indication methods, and the basic packet forwarding mechanism is consistent with the original MPLS.
  • the carrying methods are different on different data planes. If a service/auxiliary data information spans multiple data planes, a common solution is to terminate the encapsulation of the previous data plane at the boundary of the two data planes, and for the auxiliary data information carried in it, according to the business A rebuild is required.
  • ECMP Equal Cost Multi-path, equal-cost multi-path routing
  • the MPLS encapsulation (including the entropy label carried in the message) will be terminated, and the value for ECMP will be generated again according to the payload content, and placed in the flow label of the IPv6 header. field. That is, the boundary node does not reuse the entropy label value of the head node, but regenerates it.
  • MPLS2.0 needs to ensure the compatibility of its functions, that is, the existing functions in the original MPLS also need to be available in MPLS2.0, but the form of the indicator and the way of data carrying may be different .
  • Embodiments of the present disclosure provide a message sending method, device, storage medium, and electronic device, so as to at least solve the problem of low message sending efficiency between domains to which different data planes belong.
  • a method for sending a message including: obtaining the feature field in the first message from the first message received by the first domain, wherein the feature field is used Obtaining the auxiliary data information carried in the first message, wherein the auxiliary data information includes at least one of the following: the carrying position of the auxiliary data information, the data type of the auxiliary data information; according to the feature converting the first packet into a second packet conforming to the data plane format of the second domain; and sending the second packet to the second domain.
  • a device for sending a message including: an acquisition module configured to acquire the feature field in the first message from the first message received by the first domain , wherein the characteristic field is used to obtain the auxiliary data information carried in the first message, wherein the auxiliary data information includes at least one of the following: the carrying position of the auxiliary data information, the auxiliary data information The data type; the conversion module is configured to convert the first message into a second message conforming to the data plane format of the second domain according to the characteristic field; the sending module is configured to send the second message to the second domain.
  • a computer-readable storage medium where a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the above message when running. sending method.
  • an electronic device including a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor executes the above-mentioned report through the computer program.
  • the sending method of the text including a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor executes the above-mentioned report through the computer program.
  • the auxiliary data information includes at least one of the following: the carrying position of the auxiliary data information, the data type of the auxiliary data information; according to the characteristic field, the first message is converted into A second message in a data plane format; sending the second message to the second domain solves the problem of low message sending efficiency between domains to which different data planes belong.
  • FIG. 1 is a schematic diagram of a multi-intent special label solution in the related art
  • FIG. 2 is a schematic diagram of data carried behind the tag stack in the related art
  • Fig. 3 is a block diagram of the hardware structure of the computer terminal of the message sending method of the embodiment of the present disclosure
  • FIG. 4 is a flowchart (1) of a method for sending a message according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart (2) of a method for sending a message according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of an interworking topology between MPLS and MPLS2.0 according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a message sent by node 1 according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of a message received by a border node S according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of a message generated by a border node according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a manner of carrying Detnet data in MPLS according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a message received by a border node S from an MPLS domain according to an embodiment of the present disclosure
  • FIG. 12 is a schematic diagram of a message format converted by a node S according to an embodiment of the present disclosure
  • FIG. 13 is a schematic diagram of a message received by a border node S from an MPLS2.0 domain according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram of a message format converted by a node S according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram of an IPv6 and MPLS2.0 interworking scenario according to an embodiment of the present disclosure
  • FIG. 16 is a schematic diagram of an IPv6 message sent by node 1 according to an embodiment of the present disclosure
  • 17 is a schematic diagram of data carried in an HBH header according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic diagram of converted MPLS packets according to an embodiment of the present disclosure.
  • Fig. 19 is a structural block diagram of an apparatus for sending a message according to an embodiment of the disclosure.
  • FIG. 3 is a block diagram of a hardware structure of a computer terminal according to a method for sending a message according to an embodiment of the present disclosure.
  • the computer terminal can include one or more (only one is shown in Figure 3) processor 302 (processor 302 can include but not limited to microprocessor (Microprocessor Unit, MPU for short) or programmable logic A device (Programmable logic device, PLD for short)) and a memory 304 configured to store data.
  • processor 302 can include but not limited to microprocessor (Microprocessor Unit, MPU for short) or programmable logic A device (Programmable logic device, PLD for short)
  • memory 304 configured to store data.
  • the above-mentioned computer terminal may also include a transmission device 306 and an input/output device 308 configured as a communication function.
  • a transmission device 306 and an input/output device 308 configured as a communication function.
  • the structure shown in FIG. 3 is only for illustration, and it does not limit the structure of the above computer terminal.
  • the computer terminal may also include more or less components than those shown in FIG. 3 , or have a different configuration with functions equivalent to those shown in FIG. 3 or more functions than those shown in FIG. 3 .
  • the memory 304 can be set to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the message sending method in the embodiment of the present disclosure, and the processor 302 runs the computer program stored in the memory 304, Thereby executing various functional applications and data processing, that is, realizing the above-mentioned method.
  • the memory 304 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 304 may further include a memory that is remotely located relative to the processor 302, and these remote memories may be connected to a computer terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 306 is configured to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by the communication provider of the computer terminal.
  • the transmission device 306 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 306 may be a radio frequency (Radio Frequency, RF for short) module, which is configured to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 4 is a flow chart (1) of a method for sending a message according to an embodiment of the present disclosure. As shown in FIG. 4 , the steps of the method for sending a message include:
  • Step S402 obtaining the characteristic field in the first packet from the first packet received by the first domain, wherein the characteristic field is used to obtain auxiliary data information carried in the first packet, wherein,
  • the auxiliary data information includes at least one of the following: a carrying position of the auxiliary data information, and a data type of the auxiliary data information.
  • Step S404 converting the first message into a second message conforming to the format of the data plane of the second domain according to the feature field.
  • Step S406 sending the second packet to the second domain.
  • the data plane of the above-mentioned first domain includes MPLS, MPLS2.0, and IPv6, and the data plane of the above-mentioned second domain includes MPLS, MPLS2.0, and IPv6, but is not limited thereto.
  • the sending process of the above-mentioned message is applied to Between MPLS and MPLS2.0, between IPv6 and MPLS2.0, between IPv6 and MPLS.
  • the characteristic field in the first packet is obtained from the first packet received by the first domain, where the characteristic field is used to obtain auxiliary data information carried in the first packet,
  • the auxiliary data information includes at least one of the following: the carrying position of the auxiliary data information, the data type of the auxiliary data information; according to the characteristic field, the first message is converted into A second message in the format of the data plane; sending the second message to the second domain solves the problem of low sending efficiency of messages between domains to which different data planes belong, and improves the efficiency of sending messages between different domains. Transmission efficiency in the data plane.
  • the method further includes: the feature field is carried in one of the following in the first field: a special label SPL located in the MPLS label stack, an extended label located in the MPLS label stack Special label eSPL, ordinary label with non-special label value in MPLS label stack, indicator based on SPL or eSPL label modification, communication classification TC field in IPv6 basic header, flow label Flow Label in IPv6 basic header , the source address in the IPv6 basic header, the destination address in the IPv6 basic header, the triplet TLV field in the IPv6 extension header, and the option field in the IPv6 extension header.
  • auxiliary data information the service/forwarding-related data and non-payload data carried in the message are collectively referred to as auxiliary data information.
  • the carrying positions include:
  • SPL Special Purpose Label
  • eSPL extended special label
  • G-ACH Generic Associated Channel Header
  • RFC5586 the Generic Associated Channel Header
  • G-ACH is only used for end-to-end data carrying. Intermediate nodes do not process G-ACH and cannot be superimposed. A special label needs to be carried at the bottom of the label stack, indicating that G-ACH data is carried after the label stack.
  • the entropy label (Entropy Label, EL)
  • EL itself stores the value used for ECMP, and is located in the MPLS label stack.
  • a special label (Entropy Label Indicator, ELI) is required to indicate that it is followed by an EL.
  • tags and the carried data in the above two methods are in a one-to-one relationship, that is, a tag with a value corresponds to a type of data.
  • the following method can be used to better understand how to obtain the feature field in the first message from the first message received by the first domain in the above step S402.
  • the specific technical solution includes: determining Whether the field in the first message is a required field of a border network node, will be located in the first message, and the field required by the border network node will be used as the characteristic field; obtained from the border network node
  • the first packet carries the position of the characteristic field, and acquires the characteristic field at the position of the characteristic field.
  • a technical solution is proposed after taking the field required by the border network node in the first message as the feature field, and the specific steps include: adding the feature field In the case of having a global meaning, converting the first message into a second message conforming to the data plane format of the second domain according to the feature field; the feature field in the first message does not have a global meaning
  • the feature field is identified by the border network node, wherein the source of the target message includes at least one of the following: the first field , the preset information of the device, the manual configuration message of the device, and the global configuration message.
  • the target message from the first domain may include a notification message and a negotiation message, wherein the notification message refers to a message sent by a network node in the first domain to a border network node in the form of a notification, and the border network node directly receives the notification message That's it.
  • the negotiation message refers to the message that the network nodes in the first domain and the border network nodes agree to after negotiation, and can also be understood as a pre-agreed message between the network nodes in the first domain and the border network nodes. After the negotiation message, it is necessary to reply to the network nodes in the first domain, indicating that the negotiation is successful.
  • the preset information of the device refers to preset related information of the device itself.
  • the specific steps include: the feature field in the second message does not have global In the case of meaning, if it is determined that the network node in the second domain has received the target message, then identify the characteristic field through the border network node in the second domain, wherein the source of the target message at least includes the following One: the border network node, device preset information, device manual configuration message, and global configuration message.
  • the carrying position includes: in the stack of the label stack of the first message, or after the stack of the label stack of the first message; wherein, the carrying position is the In the case of the stack of the label stack of the first message, the carrying form of the auxiliary data information includes at least one of the following: an entropy label, an MPLS control word; the carrying position is the label of the first message In the case of the post-stack of the stack, the carrying form of the auxiliary data information includes at least one of the following: general association channel header, MPLS extension header, and MPLS control word.
  • the MPLS extension header may include the extension header in MPLS2.0
  • IPv6 in addition to carrying a service load (payload) after the IP header, some other service/forwarding-related data may also be carried additionally.
  • the main carrying methods and locations include:
  • the flow label field of the basic IPv6 header is mainly used in ECMP scenarios. There are also plans to use part of the flow label space to carry information such as network slice identifiers or flow identifiers. For example, when the Traffic Class field takes a specific value, flow Which positions in the label field carry the network slice identification information, or determine what information is carried in the flow label field through prior configuration or agreement; but no matter what the solution is, by reading the flow label field separately, or by reading The Traffic Class field and the Flow Label field can identify the type of data carried;
  • SRH Segment Routing Header
  • IPv6 extension header can also be defined, but no matter what form it is carried, generally speaking, the data carried in the IPv6 extension header will carry data
  • the field corresponding to the type can identify what kind of data is carried through the field corresponding to the data type.
  • a technical solution is also proposed, specifically: in the case that the feature field in the first message does not have a global meaning, after the feature field is learned through the target message, carry auxiliary data information; acquire the auxiliary data information carried after the characteristic field, and convert the auxiliary data information carried after the characteristic field according to the data plane format in the second domain, so as to generate the second message .
  • a technical solution for converting the first message into a second message conforming to the data plane format of the second domain according to the feature field and the specific steps include: according to the The feature field obtains the auxiliary data information carried in the label stack of the first message, wherein the auxiliary data information is carried in one of the following: the flow label field of the IPv6 basic header, the communication classification of the IPv6 basic header The TC field, the hop-by-hop option header in the IPv6 extension header, the destination option header in the IPv6 extension header, the routing header in the IPv6 extension header, the source address in the IPv6 basic header, and the destination address in the IPv6 basic header.
  • the auxiliary data information carried in the IPv6 extension header includes a type field for identifying the type of the auxiliary data information, data that needs to be processed hop-by-hop is stored after the label stack, and the extension header after the label stack stores There is in-band operation management and maintenance data; converting the auxiliary data information according to the data plane format in the second domain, and generating the second message according to the converted auxiliary data information.
  • FIG. 5 is a flowchart (2) of a method for sending a message according to an embodiment of the present disclosure, as shown in FIG. 5 , applied to the boundary nodes of different data planes, including the following steps:
  • Step S502 the border node reads the message (equivalent to the first message) received from the first domain, and obtains the feature field.
  • the above feature field refers to the field of the data information carried in the message, including the carrying position of the data, specific data type information, etc.
  • the carrying position of the data may include the stack or the stack of the label stack in MPLS back.
  • the characteristic field is not necessarily an explicit indication information, but may also be implicit in the specific data carrying field, that is, the characteristic field and the carried data can be integrated as a whole, for example, the flow of the IPv6 basic header label field, in the absence of any other instructions, the flow label field carries information for ECMP by default.
  • the feature field may be a field with a global meaning under the standard, or it may be a field with a specific meaning within a limited range through control plane protocol notification/negotiation, configuration, prior agreement, etc. Therefore, the border node It is necessary to receive notification/negotiation information from the control plane, or perform corresponding configuration/agreement to achieve the purpose of identifying the characteristic field.
  • the above-mentioned control plane includes the data plane of the above-mentioned second domain.
  • the feature field can be SPL or eSPL, or a common label with no special label value, but it has a special meaning through global configuration or control plane protocol notification.
  • the feature field is a newly defined indicator, such as a multi-purpose special label.
  • the presence indicator only indicates that data is carried after the label stack. The specific data type needs to be The case of fetching after the label stack.
  • the feature field may include fields such as TC, Flow Label, source address, and destination address in the IPv6 basic header, and may also include fields such as TLV or option in the IPv6 extension header.
  • the position of the auxiliary data information can be obtained from the received first message through the identification field of the border node.
  • the identification field of the border node is used, the received There is also a special case that the first packet may not carry auxiliary data information.
  • the method of obtaining the feature field may be to scan the received message completely, and compare the message one by one whether there is a feature field that the border node cares about, or the border node may have determined in advance Where and what characteristic field will be carried in the message received from the first domain, and information is directly obtained from the corresponding location. For example, through configuration on the border node in advance, it is indicated that only the slice identification field carried in the HBH option in the IPv6 message needs to be converted, then the border node will directly go to the corresponding position to obtain the corresponding field after receiving the message from the first domain .
  • case (1) is applicable to all embodiments below, and case (2) is applicable to embodiment 3 below.
  • Step S504 the border node converts the message to generate a message corresponding to the format of the second domain.
  • step S504 also includes the following steps:
  • Step S5041 according to the characteristic field to the corresponding position of the message, obtain the carried data, and then convert the format of the characteristic field and auxiliary data information according to the data plane format in the second domain;
  • the meaning of the characteristic field needs to be notified/configured/pre-agreed through the protocol, so that the meaning of the characteristic field can be recognized in the second domain.
  • Step S5042 converting the format of the data plane itself. For example, convert the IPv6 data plane to the MPLS data plane, or convert the MPLS data plane to the IPv6 data plane.
  • this embodiment does not limit the execution sequence of S5041 and S5042.
  • auxiliary data information When format conversion is performed between MPLS and MPLS2.0, the location of auxiliary data information is not necessarily the same.
  • the data carried in the label stack of MPLS may be carried in the label stack when converted to MPLS2.0. , and may also be carried after the label stack.
  • Step S506 sending the generated message corresponding to the format of the second domain to the second domain.
  • the conversion may also be realized by carrying an instruction in the message, for example, through SRv6 network programming, assigning a specific SID to a data conversion process when processing the SID.
  • This embodiment specifically illustrates how the MPLS data plane communicates with MPLS2.0 when the indicator has a global meaning.
  • the feature field indicator in MPLS2.0 as an example of a multi-purpose special label, it should be noted that the data format carried at the bottom of the stack is only exemplary.
  • FIG. 6 is a schematic diagram of an interworking topology between MPLS and MPLS2.0 according to an embodiment of the present disclosure.
  • an end-to-end SR-MPLS path 1-2-S-3-4-5 passes through two data planes , the S node is a border node, and supports both MPLS and MPLS2.0 data plane formats.
  • entropy labels need to be carried in the label stack.
  • FIG. 7 is a schematic diagram of a message sent by node 1 according to an embodiment of the present disclosure. As shown in FIG. The positions of ELI and EI in the label stack.
  • Fig. 8 is a schematic diagram of a message received by a border node S according to an embodiment of the present disclosure. As shown in Fig. 8, after the message is forwarded to the S node according to the topmost label, the S node acts as a border node to scan the label stack, It is found that there are two special labels ELI indicating entropy labels in the stack.
  • FIG. 9 is a schematic diagram of a message generated by a border node according to an embodiment of the present disclosure, and the message is shown in FIG. 9 . After the message is generated, according to the forwarding rules of MPLS, it is forwarded according to the topmost label, and the message is sent to node 3 in the MPLS2.0 domain.
  • This embodiment specifically illustrates how the MPLS data plane communicates with MPLS2.0 when the feature field does not have a global meaning.
  • FIG. 10 is a schematic diagram of a manner of carrying Detnet data in MPLS according to an embodiment of the present disclosure.
  • FIG. 10 illustrates a typical manner of carrying Detnet data in MPLS.
  • F-Label forwarding label
  • S-Label A service label
  • Detnet data carried in the form of detnet control word.
  • the value of S-Label is an ordinary MPLS label, and its meaning needs to be notified externally through control plane protocols (such as RSVP-TE, LDP, etc.), or through centralized configuration (such as netconf, YANG, PCEP, etc.) , other nodes can know its special indication meaning.
  • control plane protocols such as RSVP-TE, LDP, etc.
  • centralized configuration such as netconf, YANG, PCEP, etc.
  • FIG. 11 is a schematic diagram of a message received by a border node S from the MPLS domain according to an embodiment of the present disclosure.
  • LabelD indicates the data followed by detnet.
  • Figure 12 is a schematic diagram of the message format converted by node S according to an embodiment of the present disclosure.
  • the Indicator indicates that the data is carried after the stack, and the specific data type needs to read the extended header after reaching the bottom of the stack.
  • EH1 contains The information stored in the detnet control word of the original message is deleted.
  • Figure 13 is a schematic diagram of the message received by the border node S from the MPLS2.0 domain according to an embodiment of the present disclosure .
  • the border node S notifies to read the Indicator, and knows that the label stack carries data, and by reading the data behind the stack, it knows that EH1 carries detnet information.
  • Node S needs to convert the Indicator into the form of S-Label indicating detnet data in the MPLS domain.
  • Label D2 is taken as an example.
  • Label D2 is an ordinary label (not SPL/eSPL with global meaning), Therefore, it is necessary to specify the special meaning of Label D2 through control plane notification or global configuration in the MPLS domain.
  • FIG. 14 is a schematic diagram of the converted message format of the node S according to an embodiment of the present disclosure.
  • boundary nodes in the two directions may not be the same node.
  • This embodiment specifically illustrates the manner in which the MPLS2.0 and IPv6 data planes communicate with each other.
  • Fig. 15 is a schematic diagram of an IPv6 and MPLS2.0 interworking scenario according to an embodiment of the disclosure; as shown in Fig. 15 , an end-to-end path 1-2-S-3-4-5 passes through two data planes, and the S node As a border node, it supports both IPv6 and MPLS2.0 data plane formats.
  • FIG. 17 is a schematic diagram of data carried in the HBH header according to an embodiment of the present disclosure. Different option types correspond to different types of carried data.
  • the SRH carries path information passing through the SRv6 (IPv6) domain.
  • SID-S is a variant of BINDING SID, and its specific function is to strip off the IPv6 header and encapsulate the MPLS label stack ⁇ Label3, Label4, Label5>.
  • node S After node S receives the message, it finds that it needs to convert the message.
  • the possible trigger methods include:
  • SID-S adds another behavior of converting message format.
  • FIG. 18 is a schematic diagram of converted MPLS packets according to an embodiment of the present disclosure.
  • the Indicator indicates that the entropy label and slice identification information are followed, and the data that needs to be processed hop-by-hop is stored after the label stack.
  • the extension header EH1 behind the MPLS label stack stores the data of IOAM (in-band operation management and maintenance).
  • the number and position of the entropy labels in the figure are only for illustration, and may be placed in other positions according to the capabilities of each node's ERLD and MSD.
  • a general-purpose message sending method which can be used for end-to-end transfer of services/data, and is suitable for solving intercommunication and functional compatibility problems of various data planes.
  • the message to be converted can be located according to the feature field in the message, and the format of the message to be converted can be converted to the format of the next data plane.
  • the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
  • the technical solution of the present disclosure can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the method of each embodiment of the present disclosure.
  • a storage medium such as ROM/RAM, disk, CD
  • a device for sending a message is also provided, and the device is used to implement the above embodiments and preferred implementation modes, and what has been explained will not be repeated here.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • Fig. 19 is a structural block diagram of an apparatus for sending a message according to an embodiment of the disclosure.
  • the sending device of message comprises:
  • the acquiring module 1902 is configured to acquire the feature field in the first message from the first message received by the first domain, where the feature field is used to acquire auxiliary data information carried in the first message , wherein the auxiliary data information includes at least one of the following: the carrying position of the auxiliary data information, the data type of the auxiliary data information;
  • a conversion module 1904 configured to convert the first message into a second message conforming to the data plane format of the second domain according to the feature field;
  • a sending module 1906 configured to send the second packet to the second domain.
  • the data plane of the above-mentioned first domain includes MPLS, MPLS2.0, and IPv6, and the data plane of the above-mentioned second domain includes MPLS, MPLS2.0, and IPv6, but is not limited thereto.
  • the sending process of the above-mentioned message is applied to Between MPLS and MPLS2.0, between IPv6 and MPLS2.0, between IPv6 and MPLS.
  • the auxiliary data information includes at least one of the following: the carrying position of the auxiliary data information, the data type of the auxiliary data information; according to the characteristic field, the first message is converted into A second message in the format of the data plane; sending the second message to the second domain solves the problem of low sending efficiency of messages between domains to which different data planes belong, and improves the efficiency of sending messages between different domains. Transmission efficiency in the data plane.
  • the feature field is carried in one of the following in the first field: a special label SPL located in the MPLS label stack, an extended special label eSPL located in the MPLS label stack, an Ordinary labels with non-special label values in the label stack, indicators based on SPL or eSPL label transformation, communication classification TC field in the IPv6 basic header, flow label Flow Label in the IPv6 basic header, and IPv6 basic header
  • a special label SPL located in the MPLS label stack an extended special label eSPL located in the MPLS label stack
  • an Ordinary labels with non-special label values in the label stack indicators based on SPL or eSPL label transformation
  • communication classification TC field in the IPv6 basic header a special label SPL located in the MPLS label stack
  • eSPL located in the MPLS label stack
  • an Ordinary labels with non-special label values in the label stack indicators based on SPL or eSPL label transformation
  • communication classification TC field in the IPv6 basic header a special label SPL
  • the obtaining module is further configured to determine whether the field in the first message is a field required by the border network node, and will be located in the first message, and the border network node needs The field is used as the feature field; the position of the feature field in the first packet is obtained from the border network node, and the feature field is obtained at the position of the feature field.
  • the device for sending the above message further includes a first identification module, configured to convert the first message into a conforming The second message in the data plane format of the second domain; in the case that the characteristic field in the first message does not have a global meaning, if it is determined that the border network node has received the target message, then through the The border network node identifies the feature field, wherein the source of the target message includes at least one of the following: the first field, device preset information, device manual configuration message, and global configuration message.
  • the device for sending the above message further includes a second identification module, which is configured to, if the feature field in the second message does not have a global meaning, if it is determined that the After receiving the target message, the network node identifies the feature field through the network nodes in the second domain, where the source of the target message includes at least one of the following: the border network node, device preset information , the manual configuration message of the device, and the global configuration message.
  • the target message from the first domain may include a notification message and a negotiation message, wherein the notification message refers to a message sent by a network node in the first domain to a border network node in the form of a notification, and the border network node directly receives the notification message That's it.
  • the negotiation message refers to the message that the network nodes in the first domain and the border network nodes agree to after negotiation, and can also be understood as a pre-agreed message between the network nodes in the first domain and the border network nodes. After the negotiation message, it is necessary to reply to the network nodes in the first domain, indicating that the negotiation is successful.
  • the preset information of the device refers to preset related information of the device itself.
  • the conversion module is further configured to obtain the auxiliary data information carried in the first message according to the carrying position indicated by the characteristic field; converting the format of the feature field and the auxiliary data information to obtain the second message, wherein the second message includes: the format-converted feature field and the auxiliary data information.
  • the carrying position includes: in the stack of the label stack of the first message, or after the stack of the label stack of the first message; wherein, the carrying position is the In the case of the stack of the label stack of the first message, the carrying form of the auxiliary data information includes at least one of the following: an entropy label, an MPLS control word; the carrying position is the label of the first message In the case of the post-stack of the stack, the carrying form of the auxiliary data information includes at least one of the following: general association channel header, MPLS extension header, and MPLS control word.
  • the device for sending the above message further includes a message generating module, configured to obtain the Auxiliary data information carried after the feature field; acquiring the auxiliary data information carried after the feature field, converting the auxiliary data information carried after the feature field according to the data plane format in the second domain, to generate the second message.
  • a message generating module configured to obtain the Auxiliary data information carried after the feature field; acquiring the auxiliary data information carried after the feature field, converting the auxiliary data information carried after the feature field according to the data plane format in the second domain, to generate the second message.
  • the conversion module is further configured to acquire auxiliary data information carried in the label stack of the first message according to the characteristic field, wherein the auxiliary data information is carried in one of the following : The flow label field of the IPv6 basic header, the communication classification TC field of the IPv6 basic header, the hop-by-hop option header in the IPv6 extension header, the destination option header in the IPv6 extension header, the routing header in the IPv6 extension header, and the IPv6 extension header.
  • the extension header after the label stack stores in-band operation management and maintenance data; converts the auxiliary data information according to the data plane format in the second domain, and converts the auxiliary data information according to the converted auxiliary data information.
  • the data information generates the second packet.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • Embodiments of the present disclosure also provide an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the above-mentioned processor may be configured to execute the following steps through a computer program:
  • auxiliary data information includes at least one of the following: a carrying position of the auxiliary data information, and a data type of the auxiliary data information.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • each module or each step of the above-mentioned disclosure can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present disclosure is not limited to any specific combination of hardware and software.

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

本公开实施例提出了一种报文的发送方法、装置、存储介质及电子装置，该方法包括：从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；将所述第二报文发送至所述第二域，解决了不同数据面所属的域之间报文的发送效率较低的问题，提高了报文在不同数据面中的发送效率。

Description

报文的发送方法、装置、存储介质及电子装置
本公开要求于2022年03月03日提交中国专利局、申请号为202210211171.3、发明名称“报文的发送方法、装置、存储介质及电子装置”的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
技术领域
本公开涉及通信领域，具体而言，涉及一种报文的发送方法、装置、存储介质及电子装置。
背景技术
MPLS(Multi-Protocol Label Switching，多协议标签交换)技术的关键是引入了标签的概念，将IP(Internet Protocol，网际互联协议)地址映射为具有固定长度的标签，用于不同的包转发和包交换技术。MPLS网络中的边缘设备接收到数据包后，分析数据包的内容，为这些数据包选择合适的标签，并利用得到的具有固定长度的标签封装数据包发送到MPLS网络内。MPLS网络中所有路由器都以这个具有固定长度的标签取代IP头作为转发依据，数据包最终离开MPLS网络时，这个具有固定长度的标签被MPLS网络中的边缘设备剥离。这种利用MPLS技术转发数据包的方法，提高了数据的转发效率。
IPv6(Internet Protocol version 6，网际协议第6版)定义了一组数据包头，包括基本IPv6数据包头和IPv6扩展头。其中，IPv6扩展头包括逐跳选项头(Hop-by-Hop Options Header)、路由头(Routing Header)、目的选项头(Destination Options Header)等。
SR(Segment Router，段路由)是一种基于源地址的路由，通过在现有的MPLS网络的标签栈(SR-MPLS)或者IPv6报文头中携带段路由报文头中(SRv6)，携带有一系列的指示操作(也称为段操作)用于数据在网络中的路由和传输。
SRv6网络编程(network programming)，SRv6 Segment是一个128位数，通常也可以称为SRv6 SID或者SID。SRv6 SID是一种网络指令(Instruction)，包括Locator和Function以及可能携带的参数Argument，Locator主要承担路由功能，在SR域内唯一。Function可以标示设备的任何功能，比如某个转发行为，或者某种业务等，Argument主要用于携带与function相关的参数。SRv6 SID的结构有利于对网络进行编程。
随着网络的演进和新型业务的发展，越来越多的业务要求在MPLS标签栈之中或者之后携带数据。原有MPLS中的数据指示和携带方式，存在各方案不统一，扩展性不佳等缺点。特别是某些场景下，需要多种数据在栈底进行叠加，且不同的节点需要处理的数据不完全相同，原有的MPLS架构已不能很好的满足需求。因此，当前IETF中正在进行的一项工作是，设计一个新的MPLS架构，以更好满足日益增加的、丰富多样的携带数据的需求。下文将这种新的、正在设计中的MPLS架构方案称为MPLS2.0。
无论MPLS2.0方案如何，最终会包括以下组成要素：
1)指示符(Indicator)。指示符位于MPLS标签栈之中，用于说明栈中/栈后携带数据。一种可能的方案被称为多意图特殊标签，如图1所示。该方案中包括特殊标签值(如图1所示的Forwarding Actions Indicator位置)，特殊标签值对应的标签可以理解为多意图特殊标签；与其他的MPLS标签不同，多意图特殊标签中不存在TC和TTL部分，而是将对应的空 间存放Flag指示位，通过不同Flag位置位的方式来表明不同的指示含义。例如bit-A置位表明Indicator后携带了熵标签信息，bit-B置位表明Indicator后携带了网络切片标识信息，bit-C置位代表标签栈之后携带了辅助数据信息，bit-D代表随后还扩展了32bit用以携带更多的Flag位(图中的Forwarding Actions Header部分)等等。
2)携带的数据。数据携带在标签栈中或者标签栈之后。数据的类型的识别方式可以包括使用指示符具体指明的方式，数据本身携带数据类型信息的方式，也可能是前一个数据中携带有指明下一个数据的类型信息的方法。图2示意了一种在标签栈后携带数据的方式。每个MPLS扩展头携带一类数据，扩展头中包含next header(NH)字段，用以指明下一个扩展头的类型。在所有扩展头之前，还存在一个头部，其中的NH字段用以指明第一个扩展头的类型。
需要说明的是，MPLS2.0主要是数据的携带和指示方式发生了变化，基础的报文转发机制与原有MPLS是一致的。对于同一种业务/数据，在不同的数据面中，携带的方式都不尽相同。如果一种业务/辅助数据信息跨越了多个数据面，一种常见的解决方案是，在两个数据面的边界上，终结上一个数据面的封装，对于其中携带的辅助数据信息，根据业务要求重新生成。例如从MPLS到IPv6，从MPLS接收的报文，如果有端到端流量ECMP(Equal Cost Multi-path，等价多路径路由)的需求，报文从MPLS的头节点发出时，会根据payload内容，生成熵标签放置于标签栈中，在边界节点上，会终结MPLS的封装(包括报文中携带的熵标签)，重新根据payload内容，生成用于ECMP的值，放置于IPv6头的flow label字段中。即边界节点没有复用头节点的熵标签值，而是重新生成的。这就要求边界节点和业务头节点对于特定的业务，需要具备同样的能力。如果在报文中，携带了多种数据，则对于边界节点能力的要求也要随之提高。当前也有一些针对特定业务的数据转换方式，但应用范围都较为局限，不是通用的解决方案。
特别是提出MPLS2.0架构之后，MPLS2.0需要保证其功能的兼容性，即原有MPLS中已有的功能，MPLS2.0中也需要具备，只不过指示符的形式和数据携带方式可能不同。
针对相关技术，不同数据面所属的域之间报文的发送效率较低的问题，目前尚未提出有效的解决方案。
因此，有必要对相关技术予以改良以克服相关技术中的所述缺陷。
发明内容
本公开实施例提供了一种报文的发送方法、装置、存储介质及电子装置，以至少解决不同数据面所属的域之间报文的发送效率较低的问题。
根据本公开实施例的一方面，提供一种报文的发送方法，包括：从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；将所述第二报文发送至所述第二域。
根据本公开实施例的又一方面，还提供了一种报文的发送装置，包括：获取模块，设置为从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述 辅助数据信息的携带位置，所述辅助数据信息的数据类型；转换模块，设置为根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；发送模块，设置为将所述第二报文发送至所述第二域。
根据本公开实施例的又一方面，还提供了一种计算机可读的存储介质，该计算机可读的存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述报文的发送方法。
根据本公开实施例的又一方面，还提供了一种电子装置，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，上述处理器通过计算机程序执行上述报文的发送方法。
通过本公开，通过从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；将所述第二报文发送至所述第二域，解决了不同数据面所属的域之间报文的发送效率较低的问题。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本公开的一部分，本公开的示例性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是相关技术中多意图特殊标签方案的示意图；
图2是相关技术中标签栈后携带数据的示意图；
图3是本公开实施例的报文的发送方法的计算机终端的硬件结构框图；
图4是根据本公开实施例的报文的发送方法的流程图(一)；
图5是根据本公开实施例的报文的发送方法的流程图(二)；
图6是根据本公开实施例的MPLS与MPLS2.0互通拓扑的示意图；
图7是根据本公开实施例的节点1发出的报文的示意图；
图8是根据本公开实施例的边界节点S收到的报文的示意图；
图9是根据本公开实施例的边界节点生成的报文的示意图；
图10是根据本公开实施例的MPLS中Detnet数据的携带方式的示意图；
图11是根据本公开实施例的边界节点S从MPLS域收到的报文的示意图；
图12是根据本公开实施例的节点S转换后的报文格式的示意图；
图13是根据本公开实施例的边界节点S从MPLS2.0域收到的报文的示意图；
图14是根据本公开实施例的节点S转换后的报文格式的示意图；
图15是根据本公开实施例的IPv6与MPLS2.0互通场景的示意图；
图16是根据本公开实施例的节点1发出的IPv6报文的示意图；
图17是根据本公开实施例的HBH头中携带的数据的示意图；
图18是根据本公开实施例的转换后的MPLS报文的示意图；
图19是根据本公开实施例的报文的发送装置的结构框图。
具体实施方式
为了使本技术领域的人员更好地理解本公开方案，下面将结合本公开实施例中的附图， 对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分的实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本公开保护的范围。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本公开的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本公开实施例中所提供的方法实施例可以在计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图3是本公开实施例的报文的发送方法的计算机终端的硬件结构框图。如图3所示，计算机终端可以包括一个或多个(图3中仅示出一个)处理器302(处理器302可以包括但不限于微处理器(Microprocessor Unit，简称是MPU)或可编程逻辑器件(Programmable logic device，简称是PLD))和设置为存储数据的存储器304，在一个示例性实施例中，上述计算机终端还可以包括设置为通信功能的传输设备306以及输入输出设备308。本领域普通技术人员可以理解，图3所示的结构仅为示意，其并不对上述计算机终端的结构造成限定。例如，计算机终端还可包括比图3中所示更多或者更少的组件，或者具有与图3所示等同功能或比图3所示功能更多的不同的配置。
存储器304可设置为存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的报文的发送方法对应的计算机程序，处理器302通过运行存储在存储器304内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器304可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器304可进一步包括相对于处理器302远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输设备306设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中，传输设备306包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输设备306可以为射频(Radio Frequency，简称为RF)模块，其设置为通过无线方式与互联网进行通讯。
图4是根据本公开实施例的报文的发送方法的流程图(一)，如图4所示，该报文的发送方法的步骤包括：
步骤S402，从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型。
步骤S404，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报 文。
步骤S406，将所述第二报文发送至所述第二域。
需要说明的是，上述第一域的数据面包括MPLS，MPLS2.0，IPv6，上述第二域的数据面包括MPLS，MPLS2.0，IPv6，但不限于此，上述报文的发送过程应用于MPLS和MPLS2.0之间，IPv6和MPLS2.0，IPv6和MPLS之间。
本公开实施例通过从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；将所述第二报文发送至所述第二域，解决了不同数据面所属的域之间报文的发送效率较低的问题，提高了报文在不同数据面中的发送效率。
在一个示例性实施例中，所述方法还包括：所述特征字段在所述第一域中携带在以下之一中：位于MPLS标签栈中的特殊标签SPL、位于MPLS标签栈中的扩展的特殊标签eSPL、位于MPLS标签栈中的非特殊标签取值的普通标签、基于SPL或eSPL标签改造的指示符、IPv6的基础头中的通信分类TC字段、IPv6的基础头中的流标签Flow Label、IPv6的基础头中的源地址、IPv6的基础头中的目的地址、IPv6的扩展头中的三元组TLV字段和IPv6中扩展头中的选项option字段。
在一个可选的示例性实施例中，将携带在报文中的，与业务/转发相关的数据非负载数据统称为辅助数据信息。
对于某些MPLS/SR-MPLS网络中的业务来说，需要在MPLS的标签栈之中，或者标签栈之后额外携带数据，携带位置包括：
1)特殊标签(Special Purpose Label，SPL)或者扩展的特殊标签(eSPL)指示。无论是SPL还是eSPL方式指示，核心思想是一样的，即不需要其他手段的辅助，通过直接读取标签值，即可获得对应的固定含义。
例如RFC5586中，定义的通用关联通道头(Generic Associated Channel Header，G-ACH)，用于OAM业务。G-ACH仅用于端到端的数据携带，中间节点不处理G-ACH，且无法叠加，在标签栈底的位置，需要携带一个特殊标签，说明标签栈之后携带G-ACH数据。
例如熵标签(Entropy Label，EL)，EL本身存放的是用于ECMP的数值，位于MPLS标签栈之中，需要有一个特殊标签(Entropy Label Indicator，ELI)，指明其后紧跟了一个EL。
2)普通标签，SPL/eSPL以外的标签指示。在用普通标签指示时，需要通过控制面协议通告或者事先配置/约定的方式，约定该取值的普通标签表达了何种指示含义。
需要说明的是，以上两种方式中的标签和携带的数据都是一对一的关系，即一个取值的标签对应指示一种数据。
在一个示例性实施例中，可以通过以下方式更好的理解上述步骤S402中如何从第一域接收的第一报文中获取所述第一报文中的特征字段，具体技术方案包括：确定所述第一报文中 的字段是否为边界网络节点的需要的字段，将位于所述第一报文中，所述边界网络节点需要的字段作为所述特征字段；从所述边界网络节点获取所述第一报文中携带所述特征字段的位置，并在所述特征字段的位置获取所述特征字段。
在一个示例性实施例中，将位于所述第一报文中，所述边界网络节点需要的字段作为所述特征字段之后，还提出了一种技术方案，具体步骤包括：在所述特征字段具备全局含义的情况下，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；在所述第一报文中的特征字段不具备全局含义的情况下，如果确定所述边界网络节点接收到所述目标消息，则通过所述边界网络节点识别所述特征字段，其中，所述目标消息的来源包括以下至少之一：所述第一域，设备的预置信息，设备的人工配置消息，全局配置消息。
需要说明的是，来自第一域的目标消息可以包括通告消息和协商消息，其中，通告消息是指第一域内的网络节点以通告形式向边界网络节点发送的消息，边界网络节点直接接收通告消息即可。协商消息是指第一域内的网络节点与边界网络节点经协商后共同认可的消息，也可以理解为在第一域内的网络节点与边界网络节点之间预先约定的消息，边界网络节点在接收到协商消息后，还需回复第一域内的网络节点，表示协商成功。
需要说明的是，设备的预置信息表示预先设置的设备自身相关信息。
在一个示例性实施例中，将所述第二报文发送至所述第二域之前，还提出了一种技术方案，具体步骤包括：在所述第二报文中的特征字段不具备全局含义的情况下，如果确定所述第二域内的网络节点接收到所述目标消息，则通过所述第二域内的边界网络节点识别所述特征字段，其中，所述目标消息的来源至少包括以下之一：所述边界网络节点，设备的预置信息，设备的人工配置消息，全局配置消息。
在一个示例性实施例中，为了更好的理解上述步骤S404中如何根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文，可以根据所述特征字段指示的所述携带位置获得所述第一报文所携带的辅助数据信息；根据所述第二域内的数据面格式将所述特征字段和所述辅助数据信息的格式进行转换，得到所述第二报文，其中，所述第二报文包括：转换格式后的特征字段和辅助数据信息。
在一个示例性实施例中，所述携带位置包括：所述第一报文的标签栈的栈中，或所述第一报文的标签栈的栈后；其中，在所述携带位置为所述第一报文的标签栈的栈中的情况下，所述辅助数据信息的携带形式至少包括以下之一：熵标签，MPLS控制字；在所述携带位置为所述第一报文的标签栈的栈后的情况下，所述辅助数据信息的携带形式至少包括以下之一：通用关联通道头，MPLS扩展头，MPLS控制字。
需要说明的是，本文中将在标签栈之后不直接携带数据，而是要在数据之前加上特定头部字段的数据携带方式统称为MPLS扩展头方式。其中，MPLS扩展头可以包括MPLS2.0中的扩展头，
在一个可选的示例性实施例中，在IPv6中，除了可以在IP头之后携带业务负载(payload)以外，还可以额外携带一些其他与业务/转发相关的数据。主要的携带方式和位置包括：
1)基本IPv6头的flow label字段，flow label字段主要用于ECMP场景，也有方案使 用部分flow label的空间用于携带网络切片标识或流标识等信息，例如在Traffic Class字段取特定值时，flow label字段中的哪些位置携带了网络切片标识信息，或者通过事先的配置或者约定，决定flow label字段中携带了何种信息；但无论哪种方案，通过单独读取flow label字段，或者通过读取Traffic Class字段和Flow Label字段，可以识别出携带的数据类型；
2)基本IPv6头的Traffic Class字段；
3)HBH及DOH的option，通过option部分中的option Type字段识别出携带的何种数据；
4)在路由头中携带数据，数据格式与路由头类型有关，例如，SRH(Segment Routing Header)中通过SRH TLV携带数据，通过SRH TLV中的类型字段，识别出携带何种数据。
5)在源地址/目的地址中携带，通过在源/目的地址中划分出额外的空间，存放信息，这种方式携带的数据，一般需要事先的约定/配置，例如约定特定地址范围的源地址中，会在地址的哪几位携带网络切片标识信息。
需要说明的是，对于3)、4)两种携带方式，也可以定义新类型的IPv6扩展头，但无论以何种形式携带，一般来说，在IPv6扩展头中携带的数据，会携带数据类型对应的字段，通过数据类型对应的字段，可以识别出携带的为何种数据。
在一个示例性实施例中，还提出了一种技术方案，具体为：在所述第一报文中的特征字段不具备全局含义的情况下，通过所述目标消息获知所述特征字段之后携带的辅助数据信息；获取所述在所述特征字段之后携带的辅助数据信息，根据所述第二域内的数据面格式转换所述特征字段之后携带的辅助数据信息，以生成所述第二报文。
在一个示例性实施例中，还提供了一种根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文的技术方案，具体步骤包括：根据所述特征字段获取所述第一报文的标签栈中携带的辅助数据信息，其中，所述辅助数据信息携带在以下之一中：IPv6基础头的流标签flow label字段，IPv6基础头的通信分类TC字段，IPv6扩展头中的逐跳选项头，IPv6扩展头中的目的选项头，IPv6的扩展头中的路由头，IPv6的基础头中的源地址，IPv6的基础头中的目的地址，其中，所述IPv6扩展头中携带的辅助数据信息包括类型字段，用于识别所述辅助数据信息的类型，所述标签栈之后存放有需要逐跳处理的数据，所述标签栈之后的扩展头存放有带内操作管理和维护数据；根据所述第二域内的数据面格式转换所述辅助数据信息，根据转换后的所述辅助数据信息生成所述第二报文。
接下来结合以下实施例对报文的发送方法进行进一步说明。
在一个可选的示例性实施例中，结合图5提供了一种报文的发送方法，图5是根据本公开实施例的报文的发送方法的流程图(二)，如图5所示，应用于不同数据面的边界节点，包括以下步骤：
步骤S502，边界节点读取从第一域接收的报文(相当于上述第一报文)，获取特征字段。
需要说明的是，上述特征字段是指报文中的携带的数据信息的字段，包含数据的携带位置，具体的数据类型信息等，例如数据的携带位置可以包括MPLS中标签栈的栈中或者栈后。
需要说明的是，特征字段不一定是显式的指示信息，也可能是隐含在具体数据携带字段中的，即特征字段和携带的数据可以是合一的整体，例如，IPv6基础头的flow label字段，在没有任何其他指示的情况下，flow label字段中默认携带的就是用于ECMP的信息。
另外，特征字段可能是在标准规定下的具有全局含义的字段，也可能是通过控制面协议通告/协商、配置、事先约定等方式，只在限定范围内具有特定含义的字段，因此，边界节点需要接收到控制面的通告/协商信息，或者进行相应的配置/约定，达到识别特征字段的目的。其中，上述控制面包括上述第二域的数据面。
其中，在MPLS中，特征字段可以是SPL或者eSPL，也可以是一个非特殊标签取值的普通标签，但其通过全局配置或者控制面协议通告的方式具有了特殊含义。在MPLS2.0中，特征字段是新定义的指示符，例如多用途特殊标签，特征字段为多用途特殊标签时，存在指示符只说明了在标签栈之后携带了数据，具体的数据类型需要到标签栈之后获取的情况。在IPv6数据面中，特征字段可以包括IPv6基础头中的TC、Flow Label、源地址、目的地址等字段，还可以包括IPv6扩展头中的TLV或option等字段。
在一个可选的示例性实施例中，通过边界节点识别特征字段，能够从接收到的第一报文获取辅助数据信息的位置，另外，在通过边界节点识别特征字段时，也具有接收到的第一报文也可能不携带辅助数据信息的特殊情况。
在一个可选的示例性实施例中，获取特征字段的方式，可以是完整扫描接收到的报文，逐个比对报文中是否具有边界节点关心的特征字段，也可以是边界节点事先已经确定从第一域接收到的报文会在哪些位置携带何种特征字段，直接到相应的位置获取信息。例如，事先在边界节点上通过配置等方式，指明需要只需要转换IPv6报文中HBH option中携带的切片标识字段，则边界节点从第一域接收到报文后，直接到相应位置获取对应字段。
为了表述方便，下文将特征字段指示和数据携带分开表述，但包含了以下两个特殊情况：
(1)特征字段和携带字段合一的情况。
(2)不携带数据的情况。
其中，情况(1)适用于下文的全部实施例，情况(2)适用于下文中实施例3。
步骤S504，边界节点将报文进行转换，生成与第二域的格式对应的报文。
其中，步骤S504中对报文的转换还包括以下步骤：
步骤S5041，根据特征字段到报文相应的位置，获得携带的数据，然后根据第二域内的数据面格式，将特征字段和辅助数据信息的格式进行转换；
在边界节点转换后的特征字段不具备标准定义的全局含义时，还需要包括将特征字段的含义通过协议通告/配置/事先约定的方式，使得第二域内能够识别该特征字段的含义。
步骤S5042，本身数据面格式的转换。例如，将IPv6数据面转换为MPLS数据面，或者将MPLS数据面转换为IPv6数据面。
需要说明的是，本实施例不限定S5041和S5042的执行顺序。
在MPLS与MPLS2.0进行格式转换时，辅助数据信息的位置不一定是一样的，例如，在MPLS的标签栈中携带的数据，在转换到MPLS2.0时，数据可能是在标签栈中携带，也可能是在标签栈后携带。
在完成报文格式转换后，进入以下步骤：
步骤S506，将生成的与第二域的格式对应的报文发往第二域内。
在一个实施例中，可以通过在边界节点配置策略的方式确定边界节点是否需要进入上述步骤504中的处理流程，例如对于特定特征(源/目的地址，接收到报文的端口)的报文需要进行转换，也可能通过在报文中携带指示的方式来实现，例如通过SRv6网络编程的方式，给特定SID赋予处理到该SID时需要进入数据转换的流程。
实施例1
本实施例具体说明了指示符具有全局含义时，MPLS数据面与MPLS2.0互通的方式。以MPLS2.0中特征字段indicator为多用途特殊标签为例，需要说明的是，栈底携带的数据格式只是示例性的。
图6是根据本公开实施例的MPLS与MPLS2.0互通拓扑的示意图，如图6所示，一条端到端的SR-MPLS路径1-2-S-3-4-5经过了两个数据平面，S节点为边界节点，同时支持MPLS和MPLS2.0两种数据面格式。为了满足该条路径ECMP需求，需要在标签栈中携带熵标签。
图7是根据本公开实施例的节点1发出的报文的示意图，如图7所示，表示为头节点1发出的报文中MPLS标签栈，控制器或节点1计算出路径，并确定了ELI和EI在标签栈中的位置。图8是根据本公开实施例的边界节点S收到的报文的示意图，如图8所示，报文按最顶层标签转发至S节点后，S节点作为边界节点，对标签栈进行扫描，发现栈中存在两个特殊标签ELI指示熵标签。
边界节点将ELI进行转换，转换为MPLS2.0域中的指示符格式，此外，根据原报文中ELI的指示，将ELI随后的熵标签取出，依次放置于指示符之后，不改变栈中的其他标签，重新生成标签栈，图9是根据本公开实施例的边界节点生成的报文的示意图，报文如图9所示。生成报文后，按照MPLS的转发规则，根据最顶层标签进行转发，将报文发往MPLS2.0域内的节点3。
实施例2
本实施例具体说明了特征字段不具有全局含义时，MPLS数据面与MPLS2.0互通的方式。
图10是根据本公开实施例的MPLS中Detnet数据的携带方式的示意图，图10中示意了在MPLS中Detnet数据的携带的典型方式，在转发标签(forwarding label，F-Label)之后，需要有一个业务标签(S-Label)用以表明，在其之后跟随了Detnet数据(以detnet control word的方式携带)。S-Label的取值是一个普通的MPLS标签，其含义需要通过控制面协议(如，RSVP-TE、LDP等)对外进行通告后，或者通过集中配置的方式(如netconf、YANG、PCEP等)，其他节点才能够获知其特殊指示含义。
在如图6所示的拓扑中，边界节点S从MPLS域收到的报文如图11所示。图11是根据本公开实施例的边界节点S从MPLS域收到的报文的示意图，通过控制面协议通告或者全局配置，节点S获知LabelD指示了其后跟随了detnet的数据。通过扫描标签栈，节点S发现了指示符Label D，并取出了随后存放的detnet control word数据，将其进行格式转换后的报文如图12所示。图12是根据本公开实施例的节点S转换后的报文格式的示意图，Indicator指示了栈后携带了数据，具体数据类型需要到栈底后读取扩展头，在本例中，EH1中包含了原报文detnet control word中存放的信息。
类似的，在反方向，边界节点S从MPLS2.0域收到的报文如图13所示，图13是根据本公开实施例的边界节点S从MPLS2.0域收到的报文的示意图。边界节点S通告读取Indicator，获知标签栈后携带了数据，通过读取栈后的数据，获知EH1中携带了detnet信息。节点S需 要将Indicator转换为MPLS域中以S-Label指示detnet数据的形式，本例中以Label D2为例，同时，因为Label D2是一个普通的标签(非具有全局含义的SPL/eSPL)，因此需要在MPLS域内通过控制面通告或者全局配置的方式，说明Label D2的特殊含义。
另外，需要将EH1中的数据取出，按detnet control word的形式存放。
节点S转换后的数据格式如图14所示，图14是根据本公开实施例的节点S转换后的报文格式的示意图。
需要说明的是，两个方向的边界节点可以不是同一个节点。
实施例3
本实施例具体说明了MPLS2.0与IPv6数据面互通的方式。
图15是根据本公开实施例的IPv6与MPLS2.0互通场景的示意图；如图15所示，一条端到端的路径1-2-S-3-4-5经过了两个数据平面，S节点为边界节点，同时支持IPv6和MPLS2.0两种数据面格式。
节点1发出的报文如图16所示，图16是根据本公开实施例的节点1发出的IPv6报文的示意图；其中在flow label中携带了用于ECMP的信息，在HBH头中用两个option分别携带了切片和IOAM数据信息。HBH中的具体携带的内容示意见图17，图17是根据本公开实施例的HBH头中携带的数据的示意图，不同的option type对应了不同的携带数据类型。
SRH中携带了在SRv6(IPv6)域中途经的路径信息。节点1发出的报文SRH为<SID-2，SID-S，SL＝2>，其中SID-2和SID-S分别为节点2和节点S的SRv6SID。SID-S为一个BINDING SID的变体，具体的功能为剥离IPv6头，封装MPLS标签栈<Label3，Label4，Label5>。
节点S收到报文后，发现需要进行报文转换，可能的触发方式包括：
1)本地配置；
2)通过SRv6网络编程的方式，SID-S除上述功能外，再增加一个将报文格式进行转换的行为。
发现报文需要转换后，节点S对报文进行扫描，根据特征字段识别，取出flow label和HBH option中存放的内容，按MPLS2.0的指示和存放格式进行转换，封装到MPLS报文中，如图18所示，图18是根据本公开实施例的转换后的MPLS报文的示意图。其中Indicator指明，其后跟随了熵标签和切片标识信息，且在标签栈之后存放了需要逐跳处理的数据。MPLS标签栈之后的扩展头EH1，存放了IOAM(带内操作管理和维护)的数据。
图中的熵标签的数量和位置仅为示意，实际可能根据各节点ERLD、MSD能力的情况，放置于其他的位置。
在本实施例中，除了以BSID的方式，关联下一个域需对应的MPLS标签栈以外，还可能的方式是，将MPLS标签栈以payload方式携带在IPv6报文头之后，在边界节点剥离IPv6报文头。
通过上述实施例，提出了一种可通用的报文发送方法，能够用于业务/数据的端到端传递，适用于解决多种数据面的互通和功能兼容性问题，在第二域接收来自第一域的报文时，可以根据报文中的特征字段定位需要转换的报文，将需要转换的报文的格式转换为下一个数据面的格式。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方 法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例的方法。
在本实施例中还提供了报文的发送装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的设备较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图19是根据本公开实施例的报文的发送装置的结构框图。如图19所示，报文的发送装置包括：
获取模块1902，设置为从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；
转换模块1904，设置为根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；
发送模块1906，设置为将所述第二报文发送至所述第二域。
需要说明的是，上述第一域的数据面包括MPLS，MPLS2.0，IPv6，上述第二域的数据面包括MPLS，MPLS2.0，IPv6，但不限于此，上述报文的发送过程应用于MPLS和MPLS2.0之间，IPv6和MPLS2.0，IPv6和MPLS之间。
通过上述装置，通过从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；将所述第二报文发送至所述第二域，解决了不同数据面所属的域之间报文的发送效率较低的问题，提高了报文在不同数据面中的发送效率。
在一个示例性实施例中，所述特征字段在所述第一域中携带在以下之一中：位于MPLS标签栈中的特殊标签SPL、位于MPLS标签栈中的扩展的特殊标签eSPL、位于MPLS标签栈中的非特殊标签取值的普通标签、基于SPL或eSPL标签改造的指示符、IPv6的基础头中的通信分类TC字段、IPv6的基础头中的流标签Flow Label、IPv6的基础头中的源地址、IPv6的基础头中的目的地址、IPv6的扩展头中的三元组TLV字段和IPv6中扩展头中的选项option字段。
在一个示例性实施例中，获取模块还设置为，确定所述第一报文中的字段是否为边界网络节点的需要的字段，将位于所述第一报文中，所述边界网络节点需要的字段作为所述特征字段；从所述边界网络节点获取所述第一报文中携带所述特征字段的位置，并在所述特征字段的位置获取所述特征字段。
在一个示例性实施例中，上述报文的发送装置还包括第一识别模块，设置为在所述特征字段具备全局含义的情况下，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；在所述第一报文中的特征字段不具备全局含义的情况下，如果确定所述边界网络节点接收到所述目标消息，则通过所述边界网络节点识别所述特征字段，其中，所述目标消息的来源包括以下至少之一：所述第一域，设备的预置信息，设备的人工配置消息，全局配置消息。
在一个示例性实施例中，上述报文的发送装置还包括第二识别模块，设置为在所述第二报文中的特征字段不具备全局含义的情况下，如果确定所述第二域内的网络节点接收到所述目标消息，则通过所述第二域内的网络节点识别所述特征字段，其中，所述目标消息的来源至少包括以下之一：所述边界网络节点，设备的预置信息，设备的人工配置消息，全局配置消息。
需要说明的是，来自第一域的目标消息可以包括通告消息和协商消息，其中，通告消息是指第一域内的网络节点以通告形式向边界网络节点发送的消息，边界网络节点直接接收通告消息即可。协商消息是指第一域内的网络节点与边界网络节点经协商后共同认可的消息，也可以理解为在第一域内的网络节点与边界网络节点之间预先约定的消息，边界网络节点在接收到协商消息后，还需回复第一域内的网络节点，表示协商成功。
需要说明的是，设备的预置信息表示预先设置的设备自身相关信息。
在一个示例性实施例中，转换模块还设置为根据所述特征字段指示的所述携带位置获得所述第一报文所携带的辅助数据信息；根据所述第二域内的数据面格式将所述特征字段和所述辅助数据信息的格式进行转换，得到所述第二报文，其中，所述第二报文包括：转换格式后的特征字段和辅助数据信息。
在一个示例性实施例中，所述携带位置包括：所述第一报文的标签栈的栈中，或所述第一报文的标签栈的栈后；其中，在所述携带位置为所述第一报文的标签栈的栈中的情况下，所述辅助数据信息的携带形式至少包括以下之一：熵标签，MPLS控制字；在所述携带位置为所述第一报文的标签栈的栈后的情况下，所述辅助数据信息的携带形式至少包括以下之一：通用关联通道头，MPLS扩展头，MPLS控制字。
在一个示例性实施例中，上述报文的发送装置还包括报文生成模块，设置为在所述第一报文中的特征字段不具备全局含义的情况下，通过所述目标消息获知所述特征字段之后携带的辅助数据信息；获取所述在所述特征字段之后携带的辅助数据信息，根据所述第二域内的数据面格式转换所述特征字段之后携带的辅助数据信息，以生成所述第二报文。
在一个示例性实施例中，上述转换模块还设置为，根据所述特征字段获取所述第一报文的标签栈中携带的辅助数据信息，其中，所述辅助数据信息携带在以下之一中：IPv6基础头的流标签flow label字段，IPv6基础头的通信分类TC字段，IPv6扩展头中的逐跳选项头，IPv6扩展头中的目的选项头，IPv6的扩展头中的路由头，IPv6的基础头中的源地址，IPv6的基础头中的目的地址，其中，所述IPv6扩展头中携带的辅助数据信息包括类型字段，用于识别所述辅助数据信息的类型，所述标签栈之后存放有需要逐跳处理的数据，所述标签栈之 后的扩展头存放有带内操作管理和维护数据；根据所述第二域内的数据面格式转换所述辅助数据信息，根据转换后的所述辅助数据信息生成所述第二报文。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型。
S2，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文。
S3，将所述第二报文发送至所述第二域。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (12)

  1. 一种报文的发送方法，包括：
    从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型；
    根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；
    将所述第二报文发送至所述第二域。
  2. 根据权利要求1所述的报文的发送方法，其中，所述方法还包括：
    所述特征字段在所述第一域中携带在以下之一中：位于MPLS标签栈中的特殊标签SPL、位于MPLS标签栈中的扩展的特殊标签eSPL、位于MPLS标签栈中的非特殊标签取值的普通标签、基于SPL或eSPL标签改造的指示符、IPv6的基础头中的通信分类TC字段、IPv6的基础头中的流标签Flow Label、IPv6的基础头中的源地址、IPv6的基础头中的目的地址、IPv6的扩展头中的三元组TLV字段和IPv6中扩展头中的选项option字段。
  3. 根据权利要求1所述的报文的发送方法，其中，从第一域接收的第一报文中获取所述第一报文中的特征字段，至少包括以下之一：
    确定所述第一报文中的字段是否为边界网络节点的需要的字段，将位于所述第一报文中，所述边界网络节点需要的字段作为所述特征字段；
    从所述边界网络节点获取所述第一报文中携带所述特征字段的位置，并在所述特征字段的位置获取所述特征字段。
  4. 根据权利要求3所述的报文的发送方法，其中，将位于所述第一报文中，所述边界网络节点需要的字段作为所述特征字段之后，所述方法还包括：
    在所述特征字段具备全局含义的情况下，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；
    在所述第一报文中的特征字段不具备全局含义的情况下，如果确定所述边界网络节点接收到目标消息，则通过所述边界网络节点识别所述特征字段，其中，所述目标消息的来源包括以下至少之一：所述第一域，设备的预置信息，设备的人工配置消息，全局配置消息。
  5. 根据权利要求3所述的报文的发送方法，其中，将所述第二报文发送至所述第二域之前，所述方法还包括：
    在所述第二报文中的特征字段不具备全局含义的情况下，如果确定所述第二域内的网络节点接收到目标消息，通过所述第二域内的网络节点识别所述特征字段，其中，所述目标消息的来源至少包括以下之一：所述边界网络节点，设备的预置信息，设备的人工配置消息，全局配置消息。
  6. 根据权利要求1所述的报文的发送方法，其中，根据所述特征字段将所述第一报文转 换成符合第二域的数据面格式的第二报文，包括：
    根据所述特征字段指示的所述携带位置获得所述第一报文所携带的辅助数据信息；
    根据所述第二域内的数据面格式将所述特征字段和所述辅助数据信息的格式进行转换，得到所述第二报文，其中，所述第二报文包括：转换格式后的特征字段和辅助数据信息。
  7. 根据权利要求1所述的报文的发送方法，其中，所述携带位置包括：所述第一报文的标签栈的栈中，或所述第一报文的标签栈的栈后；
    其中，在所述携带位置为所述第一报文的标签栈的栈中的情况下，所述辅助数据信息的携带形式至少包括以下之一：熵标签，MPLS控制字；在所述携带位置为所述第一报文的标签栈的栈后的情况下，所述辅助数据信息的携带形式至少包括以下之一：通用关联通道头，MPLS扩展头，MPLS控制字。
  8. 根据权利要求4所述的报文的发送方法，其中，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文包括：
    在所述第一报文中的特征字段具备全局含义的情况下，通过所述目标消息获知所述特征字段之后携带的辅助数据信息；
    获取所述在所述特征字段之后携带的辅助数据信息，根据所述第二域内的数据面格式转换所述特征字段之后携带的辅助数据信息，以生成所述第二报文。
  9. 根据权利要求1所述的报文的发送方法，其中，根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文，包括：
    根据所述特征字段获取所述第一报文的中携带的辅助数据信息，其中，所述辅助数据信息携带在以下之一中：IPv6基础头的流标签flow label字段，IPv6基础头的通信分类TC字段，IPv6扩展头中的逐跳选项头，IPv6扩展头中的目的选项头，IPv6的扩展头中的路由头，IPv6的基础头中的源地址，IPv6的基础头中的目的地址；
    根据所述第二域内的数据面格式转换所述辅助数据信息，根据转换后的所述辅助数据信息生成所述第二报文。
  10. 一种报文的发送装置，包括：
    获取模块，设置为从第一域接收的第一报文中获取所述第一报文中的特征字段，其中，所述特征字段用于获取所述第一报文中携带的辅助数据信息，其中，所述辅助数据信息包含以下至少之一：所述辅助数据信息的携带位置，所述辅助数据信息的数据类型
    转换模块，设置为根据所述特征字段将所述第一报文转换成符合第二域的数据面格式的第二报文；
    发送模块，设置为将所述第二报文发送至所述第二域。
  11. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至9任一项中所述的方法。
  12. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为通过所述计算机程序执行所述权利要求1至9任一项中所述的方法。
PCT/CN2022/143056 2022-03-03 2022-12-28 报文的发送方法、装置、存储介质及电子装置 WO2023165244A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210211171.3A CN116743733A (zh) 2022-03-03 2022-03-03 报文的发送方法、装置、存储介质及电子装置
CN202210211171.3 2022-03-03

Publications (1)

Publication Number Publication Date
WO2023165244A1 true WO2023165244A1 (zh) 2023-09-07

Family

ID=87883014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/143056 WO2023165244A1 (zh) 2022-03-03 2022-12-28 报文的发送方法、装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN116743733A (zh)
WO (1) WO2023165244A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102136995A (zh) * 2010-08-09 2011-07-27 华为技术有限公司 Mpls与mpls-tp之间oam转换的方法及装置
CN110266592A (zh) * 2019-06-21 2019-09-20 Ut斯达康通讯有限公司 Srv6网络与ip mpls网络的通信方法及装置
WO2020233192A1 (zh) * 2019-05-17 2020-11-26 华为技术有限公司 一种为业务流提供业务服务的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102136995A (zh) * 2010-08-09 2011-07-27 华为技术有限公司 Mpls与mpls-tp之间oam转换的方法及装置
WO2020233192A1 (zh) * 2019-05-17 2020-11-26 华为技术有限公司 一种为业务流提供业务服务的方法和装置
CN110266592A (zh) * 2019-06-21 2019-09-20 Ut斯达康通讯有限公司 Srv6网络与ip mpls网络的通信方法及装置

Also Published As

Publication number Publication date
CN116743733A (zh) 2023-09-12

Similar Documents

Publication Publication Date Title
US11700198B2 (en) Transmission control method, node, network system and storage medium
KR102447132B1 (ko) 멀티 캐스트 데이터 전송 방법, 관련 장치 및 시스템
US20210266189A1 (en) Packet forwarding method, packet sending apparatus, and packet receiving apparatus
US8743879B2 (en) Label switched routing to connect low power network domains
US20220078114A1 (en) Method and Apparatus for Providing Service for Traffic Flow
US7499445B2 (en) System and method for routing ISIS traffic through unidirectional links of a computer network
US8125914B2 (en) Scaled Ethernet OAM for mesh and hub-and-spoke networks
WO2019214589A1 (zh) 组播数据传输方法、相关装置及系统
US20230370298A1 (en) Message header processing method and apparatus, storage medium and electronic device
WO2017141076A1 (en) Stateless multicast protocol for low-power and lossy networks
JP4248546B2 (ja) イーサネットを介したｍｐｌｓマルチキャストパケットの転送装置及び方法
US8891551B2 (en) IPv6 over IPv4 transition method and apparatus for improving performance of control server
WO2022184169A1 (zh) 报文转发方法、系统、存储介质及电子装置
EP4191966A1 (en) Method and device for processing data message, storage medium, and electronic device
CN112261054A (zh) 基于应用业务服务质量的Ethernet/IP与IPv6协议转换系统及方法
WO2023024663A1 (zh) 路由和云资源注册方法及装置、存储介质和电子装置
WO2023165244A1 (zh) 报文的发送方法、装置、存储介质及电子装置
CN114520762B (zh) BIERv6报文的发送方法以及第一网络设备
WO2023050981A1 (zh) 虚拟专用网络业务标识的分配方法、报文处理方法及装置
WO2023078144A1 (zh) 报文处理方法、装置及系统
WO2023193511A1 (zh) 一种报文转发方法、装置、存储介质及电子装置
US20240056392A1 (en) Communication method and apparatus
WO2021238699A1 (zh) 一种配置网络设备ip地址的方法及相关设备
WO2022222582A1 (zh) 一种报文处理方法、装置、存储介质及电子装置
CN114978975A (zh) 以太网虚拟私有网络中的bum业务的快速重路由

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

Country of ref document: EP

Kind code of ref document: A1