WO2023241037A1 - 报文封装方法及装置、存储介质及电子装置 - Google Patents

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

Info

Publication number
WO2023241037A1
WO2023241037A1 PCT/CN2023/071740 CN2023071740W WO2023241037A1 WO 2023241037 A1 WO2023241037 A1 WO 2023241037A1 CN 2023071740 W CN2023071740 W CN 2023071740W WO 2023241037 A1 WO2023241037 A1 WO 2023241037A1
Authority
WO
WIPO (PCT)
Prior art keywords
deterministic
message
level
hierarchical
qos
Prior art date
Application number
PCT/CN2023/071740
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 WO2023241037A1 publication Critical patent/WO2023241037A1/zh

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]

Definitions

  • Embodiments of the present disclosure relate to the field of communications, specifically, to a message encapsulation method and device, a storage medium and an electronic device.
  • Deterministic network refers to the forwarding capability that can provide deterministic SLA guarantee in the network.
  • the main goal at the current stage is to support deterministic low packet loss rate, deterministic forwarding delay boundary and deterministic jitter upper limit.
  • Deterministic Networking (DetNet) technology.
  • RFC8655 defines the DetNet-related technology architecture, which is the second-layer bridge and the third-layer Routing networks provide deterministic services.
  • Quality of Service (QoS) requirements include deterministic upper limit of delay, low packet loss rate, reduced jitter and high reliability.
  • DetNet only defines the goals of DetNet QoS, including bounded end-to-end delay, jitter and extremely low packet loss, but does not define specific SLA indicators, nor does it classify DetNet QoS according to business needs, and currently
  • the standard lacks the message encapsulation method related to deterministic hierarchical QoS information, which cannot meet the deterministic forwarding requirements of diverse services in large-scale networks.
  • the current IETF standard lacks a message encapsulation method related to deterministic hierarchical QoS information.
  • Embodiments of the present disclosure provide a message encapsulation method and device, a storage medium and an electronic device to at least solve the problem in related technologies that the current IETF standard lacks a message encapsulation method related to deterministic hierarchical QoS information. question.
  • a message encapsulation method including: encapsulating deterministic hierarchical Qos information in a message, wherein the deterministic hierarchical Qos information includes at least one of the following: a deterministic flow identifier or Classification mark, deterministic business requirement classification, deterministic QoS level and SLA indicator information of the deterministic QoS level.
  • a message encapsulation device including: an encapsulation module configured to encapsulate deterministic hierarchical Qos information in a message, wherein the deterministic hierarchical Qos information includes at least one of the following: 1: Deterministic flow identification or classification mark, deterministic business requirement classification, deterministic QoS level and SLA indicator information of the deterministic QoS level.
  • a computer-readable storage medium is also provided.
  • a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any of the above methods when running. Steps in Examples.
  • an electronic device including a memory and a processor.
  • a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above. Steps in method embodiments.
  • the deterministic hierarchical QoS information is encapsulated in the message, the problem of the lack of a message encapsulation method related to the deterministic hierarchical QoS information in the current IETF standard can be solved, thereby providing a A message encapsulation method that meets the deterministic forwarding requirements of diverse services in large-scale networks.
  • Figure 1 is a hardware structure block diagram of a mobile terminal of a message encapsulation method according to an embodiment of the present disclosure
  • Figure 2 is a flow chart of a message encapsulation method according to an embodiment of the present disclosure
  • Figure 3 is a schematic diagram of the DetNet QoS Option format according to an embodiment of the present disclosure
  • Figure 4 is a schematic diagram of the Deterministic Time sub-TLV format according to an embodiment of the present disclosure
  • Figure 5 is a schematic diagram of the Deterministic Route sub-TLV format according to an embodiment of the present disclosure
  • Figure 6 is a schematic diagram of the Deterministic Bandwidth sub-TLV format according to an embodiment of the present disclosure
  • Figure 7 is a schematic diagram of the DetNet Flow Option format according to an embodiment of the present disclosure.
  • Figure 8 is a schematic diagram of the DetNet QoS TLV format according to an embodiment of the present disclosure.
  • Figure 9 is a schematic diagram of deterministic business classification and its SLA key indicators according to an embodiment of the present disclosure.
  • Figure 10 is a flow chart of deterministic QoS information encapsulation and forwarding processing according to an embodiment of the present disclosure
  • Figure 11 is a structural block diagram (1) of a message encapsulation device according to an embodiment of the present disclosure.
  • Figure 12 is a structural block diagram (2) of a message encapsulation device according to an embodiment of the present disclosure.
  • FIG. 1 is a hardware structure block diagram of a mobile terminal using a message encapsulation method according to an embodiment of the present disclosure.
  • the mobile terminal may include one or more (only one is shown in Figure 1) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 configured to store data, wherein the above-mentioned mobile terminal may also include a transmission device 106 configured as a communication function and an input and output device 108.
  • the structure shown in Figure 1 is only illustrative, and it does not limit the structure of the above-mentioned mobile terminal.
  • the mobile terminal may also include more or fewer components than shown in FIG. 1 , or have a different configuration than shown in FIG. 1 .
  • the memory 104 may be configured to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the message encapsulation method in the embodiment of the present disclosure.
  • the processor 102 executes the computer program stored in the memory 104, Thereby executing various functional applications and data processing, that is, realizing the above method.
  • Memory 104 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 104 may further include memory located remotely relative to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.
  • the transmission device 106 is configured to receive or send data via a network.
  • Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is configured to communicate with the Internet wirelessly.
  • NIC Network Interface Controller
  • FIG. 2 is a flow chart of a message encapsulation method according to an embodiment of the present disclosure. As shown in Figure 2, the process includes the following steps:
  • Step S102 Encapsulate deterministic hierarchical Qos information in the message, where the deterministic hierarchical Qos information includes at least one of the following: a deterministic flow identifier or hierarchical mark, a deterministic business requirement classification, a deterministic QoS level and the SLA indicator information for deterministic QoS levels.
  • the deterministic hierarchical QoS information is encapsulated in the message, it can solve the problem that is missing in the current IETF standard.
  • the current standard is missing the message encapsulation method related to the deterministic hierarchical QoS information, which cannot meet the needs of large-scale networks. This problem solves the problem of deterministic forwarding requirements for diversified services, thereby meeting the deterministic forwarding requirements for diversified services in large-scale networks.
  • the execution subject of the above steps may be a base station, a mobile terminal, etc., but is not limited thereto.
  • the above-mentioned step S102 can be implemented in the following manner: when the message does not extend the message format, by defining new DSCP and MPLS TC mark values to pass all the messages in the message.
  • the new DSCP and MPLS TC maps described deterministic hierarchical QoS information.
  • this embodiment proposes to map DetNet hierarchical QoS information to relevant resources and routes through IP DSCP and MPLS TC marking.
  • Different deterministic QoS levels are marked by different IP DSCP and MPLS TC values, and can currently be divided into 5 levels based on deterministic classification. Proceed as follows:
  • S11 Encapsulate IP DSCP and MPLS TC values in the message according to business requirements
  • the device nodes in the deterministic network After the device nodes in the deterministic network identify the IP DSCP and MPLS TC fields, they map the services to different deterministic QoS levels through classification, and map the services to different resources and routes for forwarding.
  • step S102 can also be implemented in the following manner: when the message is an IPv6 message, the deterministic network QoS Option is carried in the message extension header, wherein in the message The deterministic hierarchical Qos information is carried in the hop-by-hop option header HBH or destination option header DOH.
  • the IPv6 extension header can carry relevant extension information and be placed between the IPv6 header and the upper layer header in the data packet.
  • An IPv6 data packet supports carrying zero, one or more extension headers, each extension header is identified by the header field next to the previous header.
  • the IPv6 extension header includes a hop-by-hop option header HBH (Hop-by-Hop Option Header), which is used to carry optional information. It will not be inserted or deleted. This information can be used by each packet transmission path.
  • HBH Hop-by-Hop Option Header
  • the IPv6 extension header also includes a DOH (Destination Option Header), which is used to carry optional information. This information will be checked or processed at the destination node.
  • Options is a variable-length field whose length is such that the complete hop-by-hop options header is an integer multiple of octets.
  • this embodiment proposes to carry deterministic hierarchical QoS information in the IPv6 extension header for use in IPv6 and SRv6 networks.
  • the extended DetNet QoS Option is carried through the IPv6 HBH method, and the QoS of the service flow can be carried hop by hop.
  • Information and SLA grading indicator requirements indicate the reserved resources of hop-by-hop devices in the path. They can also be carried through IPv6 DOH.
  • the QoS information and SLA grading indicators of the business flow can be processed at the border node and mapped to the routes and resources of the deterministic network. .
  • FIG. 3 is a schematic diagram of the DetNet QoS Option format according to an embodiment of the present disclosure, where,
  • Option Type 8 bits, used to indicate the type of the DetNet QoS Option.
  • Opt Data Len 8 bits, used to indicate the length of the DetNet QoS Option.
  • DetNet Class 8 bits, used to indicate the deterministic service level of the service flow, with a value of 1 to 5.
  • Flag 8 bits, QoS type flag bit, bit T is set, indicating a time deterministic type, and will subsequently carry a deterministic time sub-TLV; bit R is set, indicating a route protection deterministic type, and will subsequently carry a deterministic route sub-TLV; bit B is set, indicating a bandwidth deterministic type, and subsequently carries a deterministic bandwidth sub-TLV.
  • QoS Parameters sub-TLV variable length, optional, used to carry deterministic QoS related information parameters.
  • Figure 4 is a schematic diagram of the Deterministic Time sub-TLV format according to an embodiment of the present disclosure, wherein,
  • Type 16 bits, indicating the deterministic time sub-TLV type.
  • Length 16 bits, indicating the deterministic time sub-TLV length.
  • Precision 16 bits, indicating the accuracy of deterministic delay and jitter, with values ranging from 1 to 100%.
  • EDL 8 bits, indicating the length of the maximum end-to-end delay and jitter.
  • TU 8 bits, indicating the unit of maximum end-to-end delay and jitter.
  • Maximum End-to-end Delay variable length, indicating the maximum end-to-end delay requirement of the business.
  • Maximum End-to-end Delay variation variable length, indicating the maximum end-to-end jitter requirement of the business.
  • Figure 5 is a schematic diagram of the Deterministic Route sub-TLV format according to an embodiment of the present disclosure, wherein,
  • Type 16 bits, indicating the deterministic routing sub-TLV type.
  • Length 16 bits, indicating the length of the deterministic routing sub-TLV.
  • Routes Number 16 bits, indicating the number of deterministic routes.
  • Node Resource Usage 16 bits, indicating the node resource utilization, the value is 1 ⁇ 100%.
  • PU 8 bits, indicating the unit of packet loss.
  • Packet Loss 32 bits, indicating the end-to-end packet loss rate requirements of the service.
  • Availability 32 bits, indicating the end-to-end reliability requirements of the service.
  • Figure 6 is a schematic diagram of the Deterministic Bandwidth sub-TLV format according to an embodiment of the present disclosure, wherein,
  • Type 16 bits, indicating the deterministic bandwidth sub-TLV type.
  • Length 16 bits, indicating the deterministic bandwidth sub-TLV length.
  • Efficiency 16 bits, indicating the efficiency of deterministic guaranteed bandwidth, the value is 1 to 100%.
  • Maximum Guaranteed Bandwidth 32 bits, indicating the end-to-end deterministic maximum guaranteed bandwidth of the business.
  • Step S21 Encapsulate IPv6 DetNet QoS Option in the message according to business requirements
  • Step S22 After obtaining DetNet QoS, the device node in the deterministic network maps the business to different resources and routes for forwarding.
  • the above step S102 can also be implemented in the following manner: when the message is an IPv6 message, the deterministic network Flow Option is carried in the message extension header, wherein the deterministic network flow option
  • the Flow Option carries a deterministic flow identifier FLow-ID, and the deterministic flow identifier FLow-ID is used to map the deterministic hierarchical Qos information.
  • this embodiment proposes to map DetNet hierarchical QoS information in the flow identification ID (equivalent to the above-mentioned deterministic flow identification FLow-ID).
  • the DetNet Flow Option is extended in the IPv6 network.
  • the Flow-ID configuration is bound to the DetNet hierarchical QoS information.
  • Flow-ID 32 bits, used to indicate the flow ID of this service flow.
  • Step S31 Configure and bind DetNet hierarchical QoS information to the flow identification ID according to business requirements.
  • Step S32 The device node in the deterministic network identifies the flow ID, maps it to DetNet QoS, and maps the service to different resources and routes for forwarding.
  • step S102 can also be implemented in the following manner: when the packet is an MPLS packet, using the deterministic flow identifier S-Label to map the deterministic hierarchical Qos information.
  • this embodiment uses S-Label configuration to bind DetNet hierarchical QoS information in the MPLS network.
  • the above step S102 can also be implemented in the following manner: when the message is an MPLS message, the deterministic hierarchical QoS information is carried in an MPLS label, where the MPLS label includes : Basic special purpose label bSPL, entropy label Entropy Label; among them, the deterministic hierarchical TLV is extended to carry the deterministic hierarchical QoS information.
  • the MPLS label includes : Basic special purpose label bSPL, entropy label Entropy Label; among them, the deterministic hierarchical TLV is extended to carry the deterministic hierarchical QoS information.
  • this embodiment proposes DetNet hierarchical QoS information as auxiliary information, which is placed at the bottom of the MPLS stack for processing. It can be carried through the base Special Purpose Label (bSPL for short) or through the entropy label (Entropy Label) Carrying, including hierarchical QoS and SLA hierarchical indicators, etc.
  • bSPL base Special Purpose Label
  • Entropy Label Entropy Label
  • FIG 8 is a schematic diagram of the DetNet QoS TLV format according to an embodiment of the present disclosure. The relevant data is shown in Figure 3, and the carrying sub-TLV is shown in Figures 4, 5, and 6.
  • the steps for deterministic hierarchical QoS encapsulation and forwarding in MPLS or SR-MPLS networks are as follows:
  • Step S41 Encapsulate MPLS auxiliary information DetNet QoS TLV, etc. in the message according to business requirements;
  • Step S42 After obtaining DetNet QoS, the device node in the deterministic network maps the business to different resources and routes for forwarding.
  • step S102 can also be implemented in the following manner: when the message is an SRv6 message, carrying the deterministic classification in the SRH message header by extending the deterministic classification Qos TLV Qos information.
  • this embodiment proposes to carry deterministic hierarchical QoS information in the SRH header of IPv6 for use in SRv6 networks.
  • the DetNet QoS TLV is extended in the Optional TLV to carry the QoS information of the service flow and SLA classification indicator requirements, indicating the reserved resources of the devices in the path.
  • the DetNet QoS TLV format is shown in Figure 3, and the carrying sub-TLV is shown in Figure 4, Figure 5 and Figure 6.
  • the steps for deterministic hierarchical QoS encapsulation and forwarding in the SRv6 network are as follows:
  • Step S51 Encapsulate the DetNet QoS information of the IPv6 SRH header in the message according to business requirements;
  • Step S52 After obtaining DetNet QoS, the device node in the deterministic network maps the business to different resources and routes for forwarding.
  • the demand type of the deterministic service may also be determined, QoS classification is performed on the deterministic flow, and SLA indicator information for each deterministic QoS level is defined.
  • the service demand of the deterministic network may also be classified, wherein the service demand includes at least one of the following: bandwidth deterministic demand, Routing protection deterministic requirements, time deterministic requirements.
  • the demand type of the deterministic service can be determined by at least one of the following: SLA indicator information for determining the deterministic demand for bandwidth includes at least one of the following: ensuring rate, accuracy, efficiency; determining The SLA indicator information that determines the deterministic requirement for route protection includes at least one of the following: number of route protections, node resource utilization, packet loss rate, and reliability; the SLA indicator information that determines the time deterministic requirement includes at least one of the following: Delay, jitter, accuracy.
  • FIG. 9 is a schematic diagram of deterministic service classification and its SLA key indicators according to an embodiment of the present disclosure.
  • deterministic requirements in the network can be classified, including: deterministic requirements for bandwidth, deterministic requirements for routing protection, time Deterministic requirements: Divide each deterministic requirement into 5 levels, specify the SLA key indicators for each level, and define the SLA key indicators hierarchically.
  • Qos grading of deterministic services can be implemented in the following manner: for the time deterministic requirements, the deterministic services are classified into the following levels: Level 1: No time deterministic requirements ; Level 2: Jitter Guaranteed; Level 3: Delay Guaranteed; Level 4: Low Latency; Level 5: Ultra-Low Latency.
  • DetNet QoS is divided into 5 levels, as follows:
  • Level-1 (equivalent to the first level above): No time deterministic requirements, basic bandwidth guarantee and a certain tolerance for packet loss are required. There are no requirements for the upper limit of delay and no requirements for delay jitter. Typical services include downloads, such as FTP wait;
  • Level-2 (equivalent to the above-mentioned second level): jitter guarantee type, the indicator requirements include jitter ⁇ 50ms, delay ⁇ 300ms, accuracy ⁇ 10%, typical services include synchronous voice, such as voice calls, etc.;
  • Level-3 (equivalent to the third level above): Delay guarantee category. Indicator requirements include delay ⁇ 50ms, jitter ⁇ 50ms, accuracy ⁇ 10%. Typical services include real-time communication, such as video, production monitoring, communications, etc. ;
  • Level-4 (equivalent to the fourth level above): low latency, low jitter guarantee category.
  • Indicator requirements include latency ⁇ 20ms, jitter ⁇ 5ms, and accuracy ⁇ 10%.
  • Typical services include video interaction, such as AR/VR , holographic communication, cloud video, cloud games, etc.;
  • Qos grading of deterministic services can be implemented in the following manner: for the routing protection deterministic requirement, the deterministic services are classified into the following levels: Level 1: No routing determinism Requirements; Level 2: There is a requirement for routing determinism; Level 3: There is a requirement for route protection; Level 4: There is a requirement for the first multiple routes to be protected; Level 5: There is a requirement for the second multiple routes to be protected.
  • DetNet QoS is divided into 5 levels, as follows:
  • Level-1 (equivalent to the first level above): There is no requirement for routing certainty, and basic bandwidth guarantee and a certain tolerance for packet loss are required.
  • Level-2 (equivalent to the second level above): There are deterministic routing requirements, no routing protection requirements, no node resource utilization requirements, packet loss rate ⁇ 10 ⁇ -3, and reliability of 99.9%.
  • Level-3 (equivalent to the third level above): There are routing protection requirements, deterministic routing guarantee and protection recovery requirements, the routing protection number is 1, no node resource utilization requirements, packet loss rate ⁇ 10 ⁇ -5, reliability 99.99%.
  • Level-4 (equivalent to the fourth level above): multiple routing protection requirements, deterministic routing guarantee and multiple routing protection requirements, the number of route protections ⁇ 2, the resource utilization rate of the entire network node ⁇ 80%, and the packet loss rate ⁇ 10 ⁇ -6, 99.999% reliability.
  • Level-5 (equivalent to the fifth level above): multiple route protection requirements, deterministic routing guarantee and multiple route protection requirements, the number of route protections is ⁇ 2, the resource utilization rate of the entire network node is ⁇ 90%, and the packet loss rate is 10 ⁇ -6 ⁇ 10 ⁇ -9, reliability 99.9999%.
  • Qos grading of deterministic services can be implemented in the following manner: for the deterministic bandwidth requirements, the deterministic services are classified into the following levels: Level 1: No deterministic bandwidth requirements ; Level 2: Ensure average data rate; Level 3: Ensure data rate and enhanced data rate; Level 4: First ensure data rate; Level 5: Second ensure data rate.
  • DetNet QoS DetNet QoS is divided into 5 levels, as follows:
  • Level-1 (equivalent to the first level above): No bandwidth deterministic requirements.
  • Level-2 (equivalent to the second level above): Ensures average rate, accuracy ⁇ 10%, and efficiency of 80%.
  • Level-3 (equivalent to the third level above): Ensures data rate (for the non-discardable part) and enhanced data rate (statistical multiplexing, for the discardable part) accuracy of ⁇ 10% and efficiency of 80%.
  • Level-4 (equivalent to the fourth level above): Ensure data rate (not statistically multiplexable) accuracy ⁇ 10% and efficiency 80%.
  • Level-5 (equivalent to the fifth level above): Ensure data rate (not statistically multiplexable) accuracy ⁇ 5% and efficiency 90%.
  • deterministic hierarchical QoS information is encapsulated in the message header, including deterministic flow identifiers and deterministic SLA hierarchical indicators.
  • the message header can be divided into MPLS/SR-MPLS/IPv4/IPv6/SRv6 according to different network types.
  • the deterministic types of deterministic hierarchical QoS can be divided into time deterministic, route protection deterministic and bandwidth deterministic. Each type is divided into 5 levels and carries different SLA indicator parameters. Deterministic QoS information is as follows:
  • DetNet QoS Type 1 Bit T is set, indicating a time deterministic type, with levels 1 to 5. SLA indicator parameters carry delay, jitter and accuracy, etc.
  • DetNet QoS Type 2 Bit R is set, indicating a deterministic type of route protection, with levels 1 to 5.
  • the SLA indicator parameters carry the number of route protections, node utilization, packet loss rate and reliability, etc.
  • DetNet QoS Type 3 Bit B is set, indicating a bandwidth deterministic type, with levels 1 to 5. SLA indicator parameters are carried to ensure speed, accuracy and efficiency, etc.
  • step S102 after performing the above step S102, it is also necessary to forward the message according to the deterministic hierarchical Qos information encapsulated in the message.
  • a method of deterministic service classification and deterministic QoS classification is proposed to meet the deterministic QoS requirements of different levels of various services, including end-to-end delay, jitter, packet loss, bandwidth, reliability Sexual and other deterministic needs.
  • the QoS information corresponding to each service flow can be carried implicitly or explicitly in forwarding plane messages. If it is carried implicitly, you can use existing fields in the message (such as flow identification fields, etc.) to configure relevant QoS information.
  • the forwarding plane can use the integrated service model (IntServ Model) to implement flow-by-flow deterministic forwarding to meet a variety of deterministic requirements. Sexual QoS requirements.
  • the forwarding plane can use the differential service model (DiffServ model) to achieve different levels of deterministic QoS requirements. There is no need to notify the network to reserve resources for each service, and the implementation is simple. , with better scalability.
  • DiffServ model differential service model
  • this embodiment proposes to summarize business characteristics, classify requirements, classify each type of requirements, define key SLA indicators for each type of requirements, and define SLA indicators from different dimensions.
  • deterministic requirements in the network can be classified, including bandwidth deterministic requirements, routing protection deterministic requirements, and time deterministic requirements.
  • Each deterministic requirement is divided into 5 levels, and the SLA key indicators of each level are specified. , define hierarchical SLA key indicators.
  • DetNet QoS is divided into 5 levels, as follows:
  • Level-1 No time certainty requirements, basic bandwidth guarantee and certain packet loss tolerance are required. There is no requirement for upper limit of delay and no requirement for delay jitter. Typical services include downloads, such as FTP, etc.;
  • Level-2 Jitter guarantee category, the indicator requirements include jitter ⁇ 50ms, delay ⁇ 300ms, accuracy ⁇ 10%, typical services include synchronous voice, such as voice calls, etc.;
  • Level-3 Delay guarantee category.
  • the indicator requirements include delay ⁇ 50ms, jitter ⁇ 50ms, and accuracy ⁇ 10%.
  • Typical services include real-time communication, such as video, production monitoring, communications, etc.;
  • Level-4 Low latency, low jitter guarantee category. Indicator requirements include: latency ⁇ 20ms, jitter ⁇ 5ms, accuracy ⁇ 10%. Typical services include video interaction, such as AR/VR, holographic communication, cloud video, cloud Games, etc.;
  • Level-5 Ultra-low latency, ultra-low jitter guarantee category. Indicator requirements include latency ⁇ 10ms, jitter ⁇ 100us, and accuracy ⁇ 5%. Typical services include production control, such as power protection, remote control, etc.
  • DetNet QoS The key SLA indicators of route protection certainty are the number of route protections, node utilization, packet loss rate and reliability.
  • DetNet QoS is divided into 5 levels, as follows:
  • Level-1 No routing determinism requirement, basic bandwidth guarantee and certain packet loss tolerance are required.
  • Level-2 There are deterministic routing requirements, no routing protection requirements, no node resource utilization requirements, packet loss rate ⁇ 10 ⁇ -3, and reliability of 99.9%.
  • Level-3 There are requirements for route protection, deterministic routing guarantee and protection recovery requirements, the number of route protections is 1, there is no node resource utilization requirement, the packet loss rate is ⁇ 10 ⁇ -5, and the reliability is 99.99%.
  • Level-4 Multiple route protection requirements, deterministic routing guarantee and multi-route protection requirements, the number of route protections ⁇ 2, the resource utilization rate of the entire network node ⁇ 80%, the packet loss rate ⁇ 10 ⁇ -6, and the reliability 99.999% .
  • Level-5 Multiple route protection requirements, deterministic routing guarantee and multiple route protection requirements, the number of route protections is ⁇ 2, the resource utilization rate of the entire network node is ⁇ 90%, and the packet loss rate is 10 ⁇ -6 ⁇ 10 ⁇ -9. 99.9999% reliability.
  • DetNet QoS The key SLA indicators for bandwidth deterministic requirements are guaranteed speed, accuracy and efficiency.
  • DetNet QoS is divided into 5 levels, as follows:
  • Level-1 No bandwidth deterministic requirement.
  • Level-2 Ensures average rate, accuracy ⁇ 10%, and efficiency of 80%.
  • Level-3 Ensures data rate (for the non-discardable part) and enhanced data rate (statistical multiplexing, for the discardable part) accuracy of ⁇ 10% and efficiency of 80%.
  • Level-4 Ensure data rate (not statistically multiplexable) accuracy ⁇ 10%, efficiency 80%.
  • Level-5 Ensure data rate (not statistically multiplexable) accuracy ⁇ 5%, efficiency 90%.
  • deterministic hierarchical QoS information is encapsulated in the message header, including deterministic flow identifiers and deterministic SLA hierarchical indicators.
  • the message header can be divided into MPLS/SR-MPLS/IPv4/IPv6/SRv6 according to different network types.
  • the deterministic types of deterministic hierarchical QoS can be divided into time deterministic, route protection deterministic and bandwidth deterministic. Each type is divided into 5 levels and carries different SLA indicator parameters. Deterministic QoS information is as follows:
  • DetNet QoS Type 1 Bit T is set, indicating a time deterministic type, with levels 1 to 5. SLA indicator parameters carry delay, jitter and accuracy, etc.
  • DetNet QoS Type 2 Bit R is set, indicating a deterministic type of route protection, with levels 1 to 5.
  • the SLA indicator parameters carry the number of route protections, node utilization, packet loss rate and reliability, etc.
  • DetNet QoS Type 3 Bit B is set, indicating a bandwidth deterministic type, with levels 1 to 5. SLA indicator parameters are carried to ensure speed, accuracy and efficiency, etc.
  • the node forwards the message according to the deterministic hierarchical QoS information encapsulated in the message header.
  • this embodiment proposes classifying and grading deterministic services, and also proposes a qualitative and graded QoS message encapsulation and forwarding method.
  • Deterministic hierarchical QoS information including flow identification, demand classification, SLA indicator parameters, etc., realize hierarchical deterministic forwarding and meet the deterministic needs of diverse services in large-scale networks.
  • Figure 10 is a flow chart of deterministic QoS information encapsulation and forwarding processing according to an embodiment of the present disclosure. The specific steps are as follows:
  • Step S1 From the perspective of deterministic business requirements, perform QoS classification and SLA indicator definition for deterministic flows;
  • Step S2 Encapsulate deterministic hierarchical QoS information in the message header, including flow identification, demand classification, SLA indicator parameters, etc.;
  • Step S3 The node forwards the message according to the deterministic hierarchical QoS information encapsulated in the message header.
  • Embodiment 1 IPv6 HBH/DOH carries DetNet hierarchical QoS information
  • the IPv6 extension header can carry relevant extension information and is placed between the IPv6 header and the upper layer header in the data packet.
  • An IPv6 data packet supports carrying zero, one or more extension headers, each extension header is identified by the header field next to the previous header.
  • the extension header of IPv6 includes a hop-by-hop option header HBH (Hop-by-Hop Option Header), which is used to carry optional information. It will not be inserted or deleted. This information can be used by each node on the data packet transmission path. Each node inspects or processes the packet until the packet reaches the node identified in the destination address field of the IPv6 header (or in the case of multicast, each of a group of nodes).
  • HBH Hop-by-Hop Option Header
  • the IPv6 extension header also includes a DOH (Destination Option Header), which is used to carry optional information. This information will be checked or processed at the destination node.
  • Options is a variable-length field whose length is such that the complete hop-by-hop options header is an integer multiple of octets.
  • This embodiment proposes to carry deterministic hierarchical QoS information in the IPv6 extension header, which is used in IPv6 and SRv6 networks.
  • the DetNet QoS Option is extended and carried in the IPv6 HBH mode, which can carry the QoS information of the service flow hop by hop.
  • SLA grading index requirements indicating the reserved resources of hop-by-hop devices in the path, which can also be carried through IPv6 DOH.
  • the QoS information and SLA grading indicators of the business flow can be processed at the border node, and mapped to the routes and resources of the deterministic network.
  • the steps of deterministic hierarchical QoS encapsulation and forwarding in the IPv6 or SRv6 network are as above-mentioned steps S21 to S22.
  • Embodiment 2 MPLS labels carry DetNet hierarchical QoS information
  • This embodiment proposes DetNet hierarchical QoS information as auxiliary information, which is placed at the bottom of the MPLS stack for processing. It can be carried by bSPL (base Special Purpose Label) or entropy label (Entropy Label), which includes hierarchical QoS and SLA classification indicators, etc. The details are shown in Figure 8.
  • the steps of deterministic hierarchical QoS encapsulation and forwarding in the MPLS or SR-MPLS network are as above-mentioned steps S41 to S42.
  • Embodiment 3 IP DSCP and MPLS TC carry DetNet hierarchical QoS information
  • This embodiment proposes that DetNet hierarchical QoS information is mapped to relevant resources and routes through IP DSCP and MPLS TC markings. Different deterministic QoS levels are marked by different IP DSCP and MPLS TC values, and can currently be divided into 5 levels based on deterministic classification.
  • the steps are as above-mentioned step S11-step S12.
  • Embodiment 4 IPv6 SRH carries DetNet hierarchical QoS information
  • This embodiment proposes to carry deterministic hierarchical QoS information in the SRH header of IPv6 for use in SRv6 networks.
  • the DetNet QoS TLV is extended in the Optional TLV to carry the QoS information of the business flow and SLA hierarchical index requirements. , indicating the reserved resources of the device in the path.
  • the DetNet QoS TLV format is shown in Figure 3, and the carrying sub-TLV is shown in Figure 4, Figure 5 and Figure 6.
  • the steps of deterministic hierarchical QoS encapsulation and forwarding in the SRv6 network are steps S51 to S52.
  • Embodiment 5 Flow identification ID mapping DetNet hierarchical QoS information
  • This embodiment proposes mapping DetNet hierarchical QoS information in the flow identification ID.
  • the DetNet Flow Option is extended in the IPv6 network.
  • the Flow-ID configuration is bound to the DetNet hierarchical QoS information.
  • Use S-Label configuration to bind DetNet hierarchical QoS information in the MPLS network.
  • steps S31 to S32 are as described above, steps S31 to S32.
  • this embodiment proposes a method for classifying and grading deterministic services, and also proposes a method for encapsulating and forwarding qualitative graded QoS messages.
  • deterministic graded QoS information including flow identifiers, in the packets, the requirements Classification and SLA indicator parameters, etc.
  • This embodiment proposes that deterministic hierarchical QoS information can be carried in various message headers, as follows:
  • the DetNet QoS Option can be extended and carried in the IPv6 HBH or DOH header to carry deterministic hierarchical QoS information in IPv6 or SRv6 networks, including demand classification and SLA indicator parameters, etc. , to achieve hierarchical deterministic forwarding.
  • the DetNet QoS TLV can be extended and carried in the optional TLV to carry deterministic hierarchical QoS information in the SRv6 network, including demand classification and SLA indicator parameters, etc., to achieve hierarchical certainty Forward.
  • the method according to the above embodiments 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 can be embodied in the form of a software product in essence or that contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD), including several instructions to cause a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present disclosure.
  • This embodiment also provides a message encapsulation device, which is configured to implement the above-mentioned embodiments and preferred implementations. What has already been described will not be described again.
  • the term "module” may be a combination of software and/or hardware that implements a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
  • Figure 11 is a structural block diagram (1) of a message encapsulation device according to an embodiment of the present disclosure. As shown in Figure 11, the device includes
  • the encapsulation module 112 is configured to encapsulate deterministic hierarchical Qos information in the message, wherein the deterministic hierarchical Qos information includes at least one of the following: deterministic flow identification or hierarchical mark, deterministic business requirement classification, deterministic QoS level and SLA indicator information of the deterministic QoS level.
  • the problem of the lack of a message encapsulation method related to the deterministic hierarchical QoS information in the current IETF standard can be solved, thereby providing a A message encapsulation method that meets the deterministic forwarding requirements of diverse services in large-scale networks.
  • Figure 12 is a structural block diagram (2) of a message encapsulation device according to an embodiment of the present disclosure. As shown in Figure 12, in addition to all the modules shown in Figure 11, the device also includes: a processing module 114, a sending module 116, Classification module 118.
  • the processing module 114 is configured to determine the demand type of the deterministic service, perform QoS classification on the deterministic flow, and define each deterministic type before encapsulating the deterministic hierarchical QoS information in the message.
  • QoS level SLA indicator information is configured to determine the demand type of the deterministic service, perform QoS classification on the deterministic flow, and define each deterministic type before encapsulating the deterministic hierarchical QoS information in the message.
  • the sending module 116 is configured to, after encapsulating the deterministic hierarchical Qos information in the message, forward the message according to the deterministic hierarchical Qos information encapsulated in the message.
  • the above-mentioned encapsulation module 112 is also configured to pass the message in the message by defining new DSCP and MPLS TC mark values when the message does not extend the message format.
  • the new DSCP and MPLS TC maps the deterministic hierarchical QoS information.
  • the above-mentioned encapsulation module 112 is also configured to carry a deterministic network QoS Option in the message extension header when the message is an IPv6 message.
  • the deterministic hierarchical Qos information is carried in the hop option header HBH or the destination option header DOH.
  • the above-mentioned encapsulation module 112 is also configured to carry a deterministic network Flow Option in the message extension header when the message is an IPv6 message, wherein the deterministic network Flow Option carries the deterministic flow identifier FLow-ID, and the deterministic flow identifier FLow-ID is used to map the deterministic hierarchical Qos information.
  • the above-mentioned encapsulation module 112 is further configured to carry the deterministic hierarchical QoS information in an MPLS label when the message is an MPLS message, where the MPLS label includes: basic Special purpose label bSPL, entropy label Entropy Label; among them, the deterministic hierarchical TLV is extended to carry the deterministic hierarchical QoS information.
  • the MPLS label includes: basic Special purpose label bSPL, entropy label Entropy Label; among them, the deterministic hierarchical TLV is extended to carry the deterministic hierarchical QoS information.
  • the above-mentioned encapsulation module 112 is further configured to use the deterministic flow identifier S-Label to map the deterministic hierarchical Qos information when the packet is an MPLS packet.
  • the above-mentioned encapsulation module 112 is also configured to carry the deterministic hierarchical Qos information in the SRH message header by extending the deterministic hierarchical Qos TLV when the message is an SRv6 message. .
  • the above-mentioned classification module 118 is also configured to classify the service requirements of the deterministic network before determining the demand type of the deterministic service, wherein the service requirements include at least one of the following : Deterministic requirements for bandwidth, deterministic requirements for route protection, and deterministic requirements for time.
  • the above-mentioned processing module 114 is further configured to determine the demand type of the deterministic service through at least one of the following: Determining the SLA indicator information of the deterministic bandwidth demand includes at least one of the following: ensuring Rate, accuracy, efficiency; SLA indicator information that determines the deterministic requirement for route protection includes at least one of the following: number of route protections, node resource utilization, packet loss rate, reliability; SLA indicator information that determines the deterministic requirement for time The information includes at least one of the following: delay, jitter, accuracy.
  • the above-mentioned processing module 114 is also configured to classify the deterministic service into the following levels for the time deterministic requirement: Level 1: No time deterministic requirement; Level 2: Jitter Guaranteed category; Level 3: Delay guaranteed category; Level 4: Low latency; Level 5: Ultra-low latency.
  • the above-mentioned processing module 114 is also configured to classify the deterministic service into the following levels for the routing protection deterministic requirement: Level 1: No routing deterministic requirement; Level 2: There is a requirement for routing certainty; Level 3: There is a requirement for route protection; Level 4: There is a requirement for the first number of route protections; Level 5: There is a requirement for the second number of route protections.
  • the above-mentioned processing module 114 is also configured to classify the deterministic service into the following levels for the deterministic demand for bandwidth: Level 1: No deterministic demand for bandwidth; Level 2: Ensure Average data rate; Level 3: guaranteed data rate and enhanced data rate; Level 4: first guaranteed data rate; Level 5: second guaranteed data rate.
  • each of the above modules can be implemented through software or hardware.
  • it can be implemented in the following ways, but is not limited to this: the above modules are all located in the same processor; or the above modules can be implemented in any combination.
  • the forms are located in different processors.
  • Embodiments of the present disclosure also provide a computer-readable storage medium that stores a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.
  • the computer-readable storage medium may include but is 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.
  • a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • modules or steps of the present disclosure can be implemented using general-purpose computing devices, and they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices. They may be implemented in program code executable by a computing device, such that they may be stored in a storage device for execution by the computing device, and in some cases may be executed in a sequence different from that shown herein. Or the described steps can be implemented by making them into individual integrated circuit modules respectively, or by making multiple modules or steps among them into a single integrated circuit module. As such, the present disclosure is not limited to any specific combination of hardware and software.

Abstract

本公开实施例提供了一种报文封装方法及装置、存储介质及电子装置，该报文封装方法包括：在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。

Description

报文封装方法及装置、存储介质及电子装置
本公开要求于2022年6月13日提交中国专利局、申请号为202210663399.6、发明名称“报文封装方法及装置、存储介质及电子装置”的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
技术领域
本公开实施例涉及通信领域，具体而言，涉及一种报文封装方法及装置、存储介质及电子装置。
背景技术
确定性网络是指在网络中可提供确定性SLA保障的转发能力，当前阶段的主要目标是支持确定性低丢包率、确定性转发时延边界和确定性抖动上限。为了满足确定性服务的业务需求，为了在L3层实现确定性技术，IETF标准组织提出确定性网络(Deterministic Networking，简称为DetNet)技术，其中RFC8655定义DetNet相关技术架构，为二层桥和三层路由网络提供确定性服务，服务等级(Quality of Service，简称为QoS)要求包括确定性时延上限，低丢包率，降低抖动和高可靠性等。
目前DetNet只定义了DetNet QoS的目标，包括有界的端到端时延，抖动及极低丢包，但并未定义具体的SLA指标，也并未按照业务需求对DetNet QoS进行分级，而且目前标准中缺失了与确定性分级QoS信息相关的报文封装方法，无法满足大规模网络中多样化业务的确定性转发要求。
针对相关技术中，目前IETF标准中缺失目前标准中缺失了与确定性分级QoS信息相关的报文封装方法的问题。
发明内容
本公开实施例提供了一种报文封装方法及装置、存储介质及电子装置，以至少解决相关技术中目前IETF标准中缺失目前标准中缺失了与确定性分级QoS信息相关的报文封装方法的问题。
根据本公开的一个实施例，提供了一种报文封装方法，包括：在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。
根据本公开的另一个实施例，提供了一种报文封装装置，包括：封装模块，被设置为在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。
根据本公开的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施 例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开，由于在报文中封装确定性分级Qos信息，因此，可以解决目前I ETF标准中缺失目前标准中缺失了与确定性分级QoS信息相关的报文封装方法的问题，进而提供了一种满足了大规模网络中多样化业务的确定性转发要求的报文封装方法。
附图说明
图1是本公开实施例的一种报文封装方法的移动终端的硬件结构框图；
图2是根据本公开实施例的报文封装方法的流程图；
图3是根据本公开实施例的DetNet QoS Option格式示意图；
图4是根据本公开实施例的Deterministic Time sub-TLV格式示意图；
图5是根据本公开实施例的Deterministic Route sub-TLV格式示意图；
图6是根据本公开实施例的Deterministic Bandwidth sub-TLV格式示意图；
图7是根据本公开实施例的DetNet Flow Option格式示意图；
图8是根据本公开实施例的DetNet QoS TLV格式示意图；
图9是根据本公开实施例的确定性业务分类及其SLA关键指标示意图；
图10是根据本公开实施例的确定性QoS信息封装及转发处理流程图；
图11是根据本公开实施例的报文封装装置的结构框图(一)；
图12是根据本公开实施例的报文封装装置的结构框图(二)。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本公开实施例中所提供的方法实施例可以在移动终端、网络侧设备或者类似的报文发送端中执行。以运行在移动终端上为例，图1是本公开实施例的一种报文封装方法的移动终端的硬件结构框图。如图1所示，移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和被设置为存储数据的存储器104，其中，上述移动终端还可以包括被设置为通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可被设置为存储计算机程序，例如，应用软件的软件程序以及模块，如本公 开实施例中的报文封装方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输设备106被设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中，传输设备106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输设备106可以为射频(Radio Frequency，简称为RF)模块，其被设置为通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端的报文封装方法，图2是根据本公开实施例的报文封装方法的流程图，如图2所示，该流程包括如下步骤：
步骤S102，在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。
通过上述步骤，由于在报文中封装确定性分级Qos信息，因此，可以解决目前IETF标准中缺失目前标准中缺失了与确定性分级QoS信息相关的报文封装方法，进而无法满足大规模网络中多样化业务的确定性转发要求的问题，进而满足了大规模网络中多样化业务的确定性转发要求。
其中，上述步骤的执行主体可以为基站、移动终端等，但不限于此。
在一个示例性的实施例中，上述步骤S102可以通过以下方式实现：在所述报文不扩展报文格式时，通过定义新的DSCP及MPLS TC标记值，以在所述报文中通过所述新的DSCP及MPLS TC映射所述确定性分级QoS信息。
也就是说，本实施例提出将DetNet分级QoS信息通过IP DSCP及MPLS TC标记，映射到相关的资源及路由。不同的确定性QoS等级通过不同的IP DSCP及MPLS TC值标记，目前可根据确定性分类分级分成5级。步骤如下：
S11：根据业务需求在报文中封装IP DSCP及MPLS TC值；
S12：确定性网络中设备节点识别IP DSCP及MPLS TC字段后，通过分类映射到不同的确定性QoS等级，将业务映射到不同的资源及路由进行转发。
在一个示例性的实施例中，上述步骤S102还可以通过以下方式实现：当所述报文为IPv6报文时，在报文扩展头中携带确定性网络QoS Option，其中，在所述报文的逐跳选项头HBH或目的选项头DOH中携带所述确定性分级Qos信息。
也就是说，在IPv6头中，IPv6扩展头(Extension header)可以携带相关扩展信息，放在数据包中的IPv6头和上层头之间。一个IPv6数据包支持携带零个、一个或多个扩展头，每个扩展头都由前面的头的下一个头字段识别。IPv6的扩展头中包括一种逐跳选项头HBH (Hop-by-Hop Option Header)，用于携带可选的信息，它不会被插入或删除，这些信息能够被数据包传输路径上的每个节点检查或处理，直到数据包到达IPv6头的目标地址字段中确定的节点(或在组播情况下，一组节点中的每一个)。IPv6的扩展头中还包括一种目的选项头DOH(Destination Option Header)，用于携带可选的信息，这些信息会在目的节点检查或处理。Options是一个可变长度的字段，其长度使得完整的逐跳选项头是八位组的整数倍。
即本实施例提出在IPv6扩展头中携带确定性分级QoS信息，用于IPv6及SRv6网络中，如图3所示，扩展DetNet QoS Option，通过IPv6 HBH方式携带，可以逐跳携带业务流的QoS信息和SLA分级指标需求，指示路径中逐跳设备的预留资源，也可以通过IPv6 DOH方式携带，可以在边界节点处理业务流的QoS信息和SLA分级指标，映射到确定性网络的路由和资源。
图3是根据本公开实施例的DetNet QoS Option格式示意图，其中，
Option Type：8比特，用于指示该DetNet QoS Option的类型。
Opt Data Len：8比特，用于指示该DetNet QoS Option的长度。
DetNet Class：8比特，用于指示该业务流的确定性服务等级，数值为1到5。
Flag：8比特，QoS类型标记位，比特T置位，表明为时间确定性类型，后续携带确定性时间的sub-TLV；比特R置位，表明为路由保护确定性类型，后续携带确定性路由sub-TLV；比特B置位，表明为带宽确定性类型，后续携带确定性带宽sub-TLV。这些比特位可以同时置位，表明需要同时满足确定性时间，路由或带宽的需求。
QoS Parameters sub-TLV：可变长，可选，用于携带确定性QoS相关信息参数。
如图4、图5、图6所示，目前已定义确定性时间，确定性路由及确定性带宽相关sub-TLV。
图4是根据本公开实施例的Deterministic Time sub-TLV格式示意图，其中，
Type：16比特，表明确定性时间sub-TLV类型。
Length：16比特，表明确定性时间sub-TLV长度。
Precision：16比特，表明确定性时延及抖动的精度，数值为1～100％。
EDL：8比特，表明最大端到端时延及抖动的长度。
TU：8比特，表明最大端到端时延及抖动的单位。
Maximum End-to-end Delay：可变长，表明业务最大端到端时延需求。
Maximum End-to-end Delay variation：可变长，表明业务最大端到端抖动需求。
图5是根据本公开实施例的Deterministic Route sub-TLV格式示意图，其中，
Type：16比特，表明确定性路由sub-TLV类型。
Length：16比特，表明确定性路由sub-TLV长度。
Routes Number：16比特，表明确定性路由数目。
Node Resource Usage：16比特，表明节点资源利用率，数值为1～100％。
PU：8比特，表明丢包的单位。
Packet Loss：32比特，表明业务端到端丢包率要求。
Availability：32比特，表明业务端到端的可靠性要求。
图6是根据本公开实施例的Deterministic Bandwidth sub-TLV格式示意图，其中，
Type：16比特，表明确定性带宽sub-TLV类型。
Length：16比特，表明确定性带宽sub-TLV长度。
Precision：16比特，表明确定性保障带宽的精度，数值为1～100％。
Efficiency：16比特，表明确定性保障带宽的效率，数值为1～100％。
Maximum Guaranteed Bandwidth：32比特，表明业务端到端确定性最大保障带宽。
在本实例中，IPv6或SRv6网络中确定性分级QoS封装及转发的步骤如下：
步骤S21：根据业务需求在报文中封装IPv6 DetNet QoS Option；
步骤S22：确定性网络中设备节点获取DetNet QoS后，将业务映射到不同的资源及路由进行转发。
在一个示例性的实施例中，上述步骤S102还可以通过以下方式实现：当所述报文为IPv6报文时，在报文扩展头中携带确定性网络Flow Option，其中，所述确定性网络Flow Option中携带确定性流标识FLow-ID，所述确定性流标识FLow-ID用于映射所述确定性分级Qos信息。
也就是说，本实施例提出在流识别ID(相当于上述确定性流标识FLow-ID)中映射DetNet分级QoS信息。具体的，在IPv6网络中扩展DetNet Flow Option，如图7所示，Flow-ID配置绑定DetNet分级QoS信息。
图7是根据本公开实施例的DetNet Flow Option格式示意图，其中，
Flow-ID：32比特，用于指示该该业务流的流标识。
在本实施例中，确定性分级QoS封装及转发的步骤如下：
步骤S31：根据业务需求配置绑定DetNet分级QoS信息到流识别ID。
步骤S32：确定性网络中设备节点识别流ID，映射到DetNet QoS后，将业务映射到不同的资源及路由进行转发。
在一个示例性的实施例中，上述步骤S102还可以通过以下方式实现：当所述报文为MPLS报文时，使用确定性流标识S-Label映射所述确定性分级Qos信息。
也就是说，本实施例在MPLS网络中使用S-Label配置绑定DetNet分级QoS信息。
在一个示例性的实施例中，上述步骤S102还可以通过以下方式实现：当所述报文为MPLS报文时，在MPLS标签中携带所述确定性分级QoS信息，其中，所述MPLS标签包括：基础特殊用途标签bSPL，熵标签Entropy Label；其中，通过扩展确定性分级TLV以携带所述确定 性分级QoS信息。
也就是说，本实施例提出DetNet分级QoS信息作为辅助信息，放在MPLS栈底处理，可以通过基础特殊用途标签(base Special Purpose Label，简称为bSPL)携带，也可以通过熵标签(Entropy Label)携带，其中包括分级QoS及SLA分级指标等。
图8是根据本公开实施例的DetNet QoS TLV格式示意图，其中，相关数据见图3所示，携带sub-TLV见图4、图5、图6。
在本实施例中，MPLS或SR-MPLS网络中确定性分级QoS封装及转发的步骤如下：
步骤S41：根据业务需求在报文中封装MPLS的辅助信息DetNet QoS TLV等；
步骤S42：确定性网络中设备节点获取DetNet QoS后，将业务映射到不同的资源及路由进行转发。
在一个示例性的实施例中，上述步骤S102还可以通过以下方式实现：当所述报文为SRv6报文时，通过扩展确定性分级Qos TLV，在SRH报文头中携带所述确定性分级Qos信息。
也就是说，本实施例提出在IPv6的SRH头中携带确定性分级QoS信息，用于SRv6网络中，如图7所示，在Optional TLV中扩展DetNet QoS TLV，可以携带业务流的QoS信息和SLA分级指标需求，指示路径中设备的预留资源。DetNet QoS TLV格式见图3所示，携带sub-TLV见图4，图5和图6。
在本实施例中，SRv6网络中确定性分级QoS封装及转发的步骤如下：
步骤S51：根据业务需求在报文中封装IPv6 SRH头的DetNet QoS信息等；
步骤S52：确定性网络中设备节点获取DetNet QoS后，将业务映射到不同的资源及路由进行转发。
在一个示例性的实施例中，在执行上述步骤S102之前，还可以确定所述确定性业务的需求类型，对确定性流进行QoS分级，定义每种确定性QoS级别的SLA指标信息。
在一个示例性的实施例中，在确定所述确定性业务的需求类型之前，还可以对确定性网络的业务需求进行分类，其中，所述业务需求包括以下至少之一：带宽确定性需求，路由保护确定性需求，时间确定性需求。
在一个示例性的实施例中，可以通过以下至少之一确定所述确定性业务的需求类型：确定所述带宽确定性需求的SLA指标信息包括以下至少之一：确保速率，精度，效率；确定所述路由保护确定性需求的SLA指标信息包括以下至少之一：路由保护数、节点资源利用率、丢包率、可靠性；确定所述时间确定性需求的SLA指标信息包括以下至少之一：时延，抖动，精度。
在本实施例中，为了满足多样化业务的确定性需求，提出从确定性业务需求的角度，对确定性流进行QoS分级及SLA指标定义的方法。具体的，提出对业务特征进行归纳分类，对需求进行分类，对每类需求进行分级，定义每类需求的关键SLA指标，从不同纬度定义SLA指标。图9是根据本公开实施例的确定性业务分类及其SLA关键指标示意图，如图9所示， 可对网络中确定性需求进行分类，包括：带宽确定性需求，路由保护确定性需求，时间确定性需求；将每种确定性需求分成5级，指定每级的SLA关键指标，对SLA关键指标进行分级定义。
在一个示例性的实施例中，对确定性业务进行Qos分级，可以通过以下方式实现：对于所述时间确定性需求，将所述确定性业务分级以下级别：第一级：无时间确定性需求；第二级：抖动保证类；第三级：时延保证类；第四级：低时延；第五级：超低时延。
也就是说，时间确定性需求的关键指标是时延，抖动及精度。将DetNet QoS分成5级，如下：
Level-1(相当于上述第一级)：无时间确定性要求，需要基本带宽保障及一定的丢包容忍度，时延上限无要求，时延抖动无要求，典型业务包括下载类，如FTP等；
Level-2(相当于上述第二级)：抖动保证类，指标要求包括，抖动＜50ms，时延＜300ms，精度±10％，典型业务包括同步语音类，如语音电话等；
Level-3(相当于上述第三级)：时延保证类，指标要求包括，时延＜50ms，抖动＜50ms，精度±10％，典型业务包括实时通信类，如视频、生产监控、通信等；
Level-4(相当于上述第四级)：低时延，低抖动保证类，指标要求包括，时延＜20ms，抖动＜5ms，精度±10％，典型业务包括视频交互类，如AR/VR，全息通信，云视频，云游戏等；
Level-5(相当于上述第五级)：超低时延，超低抖动保证类，指标要求包括，时延＜10ms，抖动＜100us，精度±5％，典型业务包括生产控制类，如电力保护、远程控制等。
在一个示例性的实施例中，对确定性业务进行Qos分级，可以通过以下方式实现：对于所述路由保护确定性需求，将所述确定性业务分级以下级别：第一级：无路由确定性要求；第二级：有路由确定性要求；第三级：有路由保护需求；第四级：有第一多路由保护需求；第五级：有第二多路由保护需求。
也就是说，路由保护确定性的SLA关键指标是路由保护数，节点利用率，丢包率和可靠性。将DetNet QoS分成5级，如下：
Level-1(相当于上述第一级)：无路由确定性要求，需要基本带宽保障及一定的丢包容忍度。
Level-2(相当于上述第二级)：有确定性路由要求，无路由保护要求，无节点资源利用率要求，丢包率＜10～-3，可靠性99.9％。
Level-3(相当于上述第三级)：有路由保护需求，确定性路由保障及保护恢复要求，路由保护数为1，无节点资源利用率要求，丢包率＜10^-5，可靠性99.99％。
Level-4(相当于上述第四级)：有多路由保护需求，确定性路由保障及多路由保护要求，路由保护数≥2，全网节点的资源利用率≥80％，丢包率＜10^-6，可靠性99.999％。
Level-5(相当于上述第五级)：有多路由保护需求，确定性路由保障及多路由保护要求，路由保护数≥2，全网节点的资源利用率≥90％，丢包率10^-6～10^-9，可靠性99.9999％。
在一个示例性的实施例中，对确定性业务进行Qos分级，可以通过以下方式实现：对于所述带宽确定性需求，将所述确定性业务分级以下级别：第一级：无带宽确定性需求；第二级：确保平均数率；第三级：确保数据速率和增强数据速率；第四级：第一确保数据速率；第五级：第二确保数据速率。
也就是说，带宽确定性需求的SLA关键指标是确保速率，精度和效率。将DetNet QoS分成5级，如下：
Level-1(相当于上述第一级)：无带宽确定性要求。
Level-2(相当于上述第二级)：确保平均数率，精度±10％，效率为80％。
Level-3(相当于上述第三级)：确保数据速率(用于不可丢弃部分)和增强数据速率(统计复用，用于可丢弃部分)精度±10％，效率为80％。
Level-4(相当于上述第四级)：确保数据速率(不可统计复用)精度±10％，效率80％。
Level-5(相当于上述第五级)：确保数据速率(不可统计复用)精度±5％，效率90％。
进一步的，在报文头中封装确定性分级QoS信息，包括确定性流标识及确定性SLA分级指标等。报文头按照网络类型不同可分为MPLS/SR-MPLS/IPv4/IPv6/SRv6等。具体的，确定性分级QoS的确定性类型可分为时间确定性，路由保护确定性和带宽确定性等类型，每种类型分为5级，携带不同的SLA指标参数。确定性QoS信息如下：
DetNet QoS Type 1：比特T置位，表明为时间确定性类型，级别为1～5级，SLA指标参数携带时延，抖动及精度等。
DetNet QoS Type 2：比特R置位，表明为路由保护确定性类型，级别为1～5级，SLA指标参数携带路由保护数，节点利用率，丢包率和可靠性等。
DetNet QoS Type 3：比特B置位，表明为带宽确定性类型，级别为1～5级，SLA指标参数携带确保速率，精度和效率等。
在一个示例性的实施例中，在执行上述步骤S102之后，还需要根据报文中封装的所述确定性分级Qos信息转发所述报文。
为了更好理解上述报文封装方法，以下结合可选实施例对上述技术方案进行解释说明，但不用于限定本公开实施例的技术方案。
在一个完整的实施例中，提出一种确定性业务分类和确定性QoS分级的方法，满足各类业务不同等级的确定性QoS需求，包括端到端时延，抖动，丢包，带宽，可靠性等确定性需求。对确定性业务进行需求分类及QoS分级后，每个业务流对应的QoS信息在转发面报文中可以隐式携带，也可以显式携带。如果隐式携带，可以利用报文中已有字段(例如流识别字段等)配置相关QoS信息，此时转发面可以利用集成服务模型(IntServ Model)实现逐流的确定性转发，满足多种确定性QoS需求。如果显式携带，需要在报文中封装QoS信息，此时转发面可以利用差分服务模型(DiffServ model)实现不同级别的确定性QoS需求，不需要通知网络为每个业务预留资源，实现简单，扩展性较好。本实施例同时提出在报文中携带确 定性分级QoS信息并转发的方法。
首先，为了满足多样化业务的确定性需求，提出从确定性业务需求的角度，对确定性流进行QoS分级及SLA指标定义的方法。具体的，本实施例提出对业务特征进行归纳分，对需求进行分类，对每类需求进行分级，定义每类需求的关键SLA指标，从不同纬度定义SLA指标。如图9所示，可对网络中确定性需求进行分类，包括带宽确定性需求，路由保护确定性需求，时间确定性需求，将每种确定性需求分成5级，指定每级的SLA关键指标，对SLA关键指标进行分级定义。
其中，时间确定性需求的关键指标是时延，抖动及精度。将DetNet QoS分成5级，如下：
Level-1：无时间确定性要求，需要基本带宽保障及一定的丢包容忍度，时延上限无要求，时延抖动无要求，典型业务包括下载类，如FTP等；
Level-2：抖动保证类，指标要求包括，抖动＜50ms，时延＜300ms，精度±10％，典型业务包括同步语音类，如语音电话等；
Level-3：时延保证类，指标要求包括，时延＜50ms，抖动＜50ms，精度±10％，典型业务包括实时通信类，如视频、生产监控、通信等；
Level-4：低时延，低抖动保证类，指标要求包括，时延＜20ms，抖动＜5ms，精度±10％，典型业务包括视频交互类，如AR/VR，全息通信，云视频，云游戏等；
Level-5：超低时延，超低抖动保证类，指标要求包括，时延＜10ms，抖动＜100us，精度±5％，典型业务包括生产控制类，如电力保护、远程控制等。
路由保护确定性的SLA关键指标是路由保护数，节点利用率，丢包率和可靠性。将DetNet QoS分成5级，如下：
Level-1：无路由确定性要求，需要基本带宽保障及一定的丢包容忍度。
Level-2：有确定性路由要求，无路由保护要求，无节点资源利用率要求，丢包率＜10^-3，可靠性99.9％。
Level-3：有路由保护需求，确定性路由保障及保护恢复要求，路由保护数为1，无节点资源利用率要求，丢包率＜10^-5，可靠性99.99％。
Level-4：有多路由保护需求，确定性路由保障及多路由保护要求，路由保护数≥2，全网节点的资源利用率≥80％，丢包率＜10^-6，可靠性99.999％。
Level-5：有多路由保护需求，确定性路由保障及多路由保护要求，路由保护数≥2，全网节点的资源利用率≥90％，丢包率10^-6～10^-9，可靠性99.9999％。
带宽确定性需求的SLA关键指标是确保速率，精度和效率。将DetNet QoS分成5级，如下：
Level-1：无带宽确定性要求。
Level-2：确保平均数率，精度±10％，效率为80％。
Level-3：确保数据速率(用于不可丢弃部分)和增强数据速率(统计复用，用于可丢弃部分)精度±10％，效率为80％。
Level-4：确保数据速率(不可统计复用)精度±10％，效率80％。
Level-5：确保数据速率(不可统计复用)精度±5％，效率90％。
进一步的，在报文头中封装确定性分级QoS信息，包括确定性流标识及确定性SLA分级指标等。报文头按照网络类型不同可分为MPLS/SR-MPLS/IPv4/IPv6/SRv6等。具体的，确定 性分级QoS的确定性类型可分为时间确定性，路由保护确定性和带宽确定性等类型，每种类型分为5级，携带不同的SLA指标参数。确定性QoS信息如下：
DetNet QoS Type 1：比特T置位，表明为时间确定性类型，级别为1～5级，SLA指标参数携带时延，抖动及精度等。
DetNet QoS Type 2：比特R置位，表明为路由保护确定性类型，级别为1～5级，SLA指标参数携带路由保护数，节点利用率，丢包率和可靠性等。
DetNet QoS Type 3：比特B置位，表明为带宽确定性类型，级别为1～5级，SLA指标参数携带确保速率，精度和效率等。
进一步的，节点根据报文头中封装的确定性分级QoS信息转发报文。
为了更好的理解，以下结合具体实施例方式进行说明，具体的，本实施例提出对确定性业务进行分类分级，同时提出一种定性分级QoS报文封装及转发方法，通过在报文中携带确定性分级QoS信息，包括流标识，需求分类和SLA指标参数等，实现分级确定性转发，满足大规模网络中多样化业务的确定性需求。图10是根据本公开实施例的确定性QoS信息封装及转发处理流程图，具体步骤如下：
步骤S1：从确定性业务需求的角度，对确定性流进行QoS分级及SLA指标定义；
步骤S2：在报文头中封装确定性分级QoS信息，包括流标识，需求分类和SLA指标参数等；
步骤S3：节点根据报文头中封装的确定性分级QoS信息转发报文。
实施例一：IPv6 HBH/DOH携带DetNet分级QoS信息
在IPv6头中，IPv6扩展头(extension header)可以携带相关扩展信息，放在数据包中IPv6头和上层头之间。一个IPv6数据包支持携带零个、一个或多个扩展头，每个扩展头都由前面的头的下一个头字段识别。IPv6的扩展头中包括一种逐跳选项头HBH(Hop-by-Hop Option Header)，用于携带可选的信息，它不会被插入或删除，这些信息能够被数据包传输路径上的每个节点检查或处理，直到数据包到达IPv6头的目标地址字段中确定的节点(或在组播情况下，一组节点中的每一个)。IPv6的扩展头中还包括一种目的选项头DOH(Destination Option Header)，用于携带可选的信息，这些信息会在目的节点检查或处理。Options是一个可变长度的字段，其长度使得完整的逐跳选项头是八位组的整数倍。
本实施例提出在IPv6扩展头中携带确定性分级QoS信息，用于IPv6及SRv6网络中，如图3所示，扩展DetNet QoS Option，通过IPv6 HBH方式携带，可以逐跳携带业务流的QoS信息和SLA分级指标需求，指示路径中逐跳设备的预留资源，也可以通过IPv6 DOH方式携带，可以在边界节点处理业务流的QoS信息和SLA分级指标，映射到确定性网络的路由和资源。
在本实例中，IPv6或SRv6网络中确定性分级QoS封装及转发的步骤如上述步骤S21-步骤S22。
实施例二：MPLS标签携带DetNet分级QoS信息
本实施例提出DetNet分级QoS信息作为辅助信息，放在MPLS栈底处理，可以通过bSPL(base Special Purpose Label)基础特殊用途标签携带，也可以通过熵标签(Entropy Label) 携带，其中包括分级QoS及SLA分级指标等。具体如图8所示。
本实施例中，MPLS或SR-MPLS网络中确定性分级QoS封装及转发的步骤如上述步骤S41-步骤S42。
实施例三：IP DSCP及MPLS TC携带DetNet分级QoS信息
本实施例提出DetNet分级QoS信息通过IP DSCP及MPLS TC标记，映射到相关的资源及路由。不同的确定性QoS等级通过不同的IP DSCP及MPLS TC值标记，目前可根据确定性分类分级分成5级。步骤如上述步骤S11-步骤S12。
实施例四：IPv6 SRH携带DetNet分级QoS信息
本实施例提出在IPv6的SRH头中携带确定性分级QoS信息，用于SRv6网络中，如图7所示，在Optional TLV中扩展DetNet QoS TLV，可以携带业务流的QoS信息和SLA分级指标需求，指示路径中设备的预留资源。DetNet QoS TLV格式见图3所示，携带sub-TLV见图4，图5和图6。
在本实施例中，SRv6网络中确定性分级QoS封装及转发的步骤上述步骤S51-步骤S52。
实施例五：流识别ID映射DetNet分级QoS信息
本实施例提出在流识别ID中映射DetNet分级QoS信息。具体的，在IPv6网络中扩展DetNet Flow Option，如图7所示，Flow-ID配置绑定DetNet分级QoS信息。在MPLS网络中使用S-Label配置绑定DetNet分级QoS信息。
在本实施例中，确定性分级QoS封装及转发的步骤如上述步骤S31步骤-S32。
需要说明的是，本实施例提出对确定性业务进行分类分级的方法，同时提出一种定性分级QoS报文封装及转发方法，通过在报文中携带确定性分级QoS信息，包括流标识，需求分类和SLA指标参数等，实现分级确定性转发，满足大规模网络中多样化业务的确定性需求。本实施例提出可以在多种报文头中携带确定性分级QoS信息，如下：
(1)在IPv6报文扩展头中携带，可以扩展DetNet QoS Option，携带于IPv6 HBH或DOH头中，用于在IPv6或SRv6网络中携带确定性分级QoS信息，包括需求分类和SLA指标参数等，实现分级确定性转发。
(2)在MPLS Metadata中携带DetNet分级QoS信息，包括bSPL及Entropy Label携带方式，可以扩展DetNet QoS TLV，携带确定性分级QoS信息，包括需求分类和SLA指标参数等，实现分级确定性转发。
(3)在IP DSCP及MPLS TC携带DetNet分级QoS信息，定义相应的DSCP及TC值，用于映射DetNet分级QoS等级，实现分级确定性转发。
(4)在IPv6 SRH报文头中携带，可以扩展DetNet QoS TLV，携带于optional TLV中，用于在SRv6网络中携带确定性分级QoS信息，包括需求分类和SLA指标参数等，实现分级确定性转发。
(5)在流识别ID中映射DetNet分级QoS信息，在IPv6报文扩展头中扩展DetNet Flow Option，携带FLow-ID，在MPLS中使用S-Label，配置绑定DetNet分级QoS信息，包括需求 分类和SLA指标参数等，实现分级确定性转发。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
在本实施例中还提供了一种报文封装装置，该装置被设置为实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图11是根据本公开实施例的报文封装装置的结构框图(一)，如图11所示，该装置包括
封装模块112，被设置为在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。
通过上述装置，由于在报文中封装确定性分级Qos信息，因此，可以解决目前IETF标准中缺失目前标准中缺失了与确定性分级QoS信息相关的报文封装方法的问题，进而提供了一种满足了大规模网络中多样化业务的确定性转发要求的报文封装方法。
图12是根据本公开实施例的报文封装装置的结构框图(二)，如图12所示，该装置除包括图11所示的所有模块外，还包括：处理模块114，发送模块116，分类模块118。
在一个示例性的实例中，处理模块114，被设置为在报文中封装确定性分级Qos信息之前，确定所述确定性业务的需求类型，对确定性流进行QoS分级，定义每种确定性QoS级别的SLA指标信息。
在一个示例性的实例中，发送模块116，被设置为在报文中封装确定性分级Qos信息之后，根据报文中封装的所述确定性分级Qos信息转发所述报文。
在一个示例性的实例中，上述封装模块112，还被设置为在所述报文不扩展报文格式时，通过定义新的DSCP及MPLS TC标记值，以在所述报文中通过所述新的DSCP及MPLS TC映射所述确定性分级QoS信息。
在一个示例性的实例中，上述封装模块112，还被设置为当所述报文为IPv6报文时，在报文扩展头中携带确定性网络QoS Option，其中，在所述报文的逐跳选项头HBH或目的选项头DOH中携带所述确定性分级Qos信息。
在一个示例性的实例中，上述封装模块112，还被设置为当所述报文为IPv6报文时，在报文扩展头中携带确定性网络Flow Option，其中，所述确定性网络Flow Option中携带确定性流标识FLow-ID，所述确定性流标识FLow-ID用于映射所述确定性分级Qos信息。
在一个示例性的实例中，上述封装模块112，还被设置为当所述报文为MPLS报文时，在MPLS标签中携带所述确定性分级QoS信息，其中，所述MPLS标签包括：基础特殊用途标签 bSPL，熵标签Entropy Label；其中，通过扩展确定性分级TLV以携带所述确定性分级QoS信息。
在一个示例性的实例中，上述封装模块112，还被设置为当所述报文为MPLS报文时，使用确定性流标识S-Label映射所述确定性分级Qos信息。
在一个示例性的实例中，上述封装模块112，还被设置为当所述报文为SRv6报文时，通过扩展确定性分级Qos TLV，在SRH报文头中携带所述确定性分级Qos信息。
在一个示例性的实例中，上述分类模块118，还被设置为在确定所述确定性业务的需求类型之前，对确定性网络的业务需求进行分类，其中，所述业务需求包括以下至少之一：带宽确定性需求，路由保护确定性需求，时间确定性需求。
在一个示例性的实例中，上述处理模块114，还被设置为通过以下至少之一确定所述确定性业务的需求类型：确定所述带宽确定性需求的SLA指标信息包括以下至少之一：确保速率，精度，效率；确定所述路由保护确定性需求的SLA指标信息包括以下至少之一：路由保护数、节点资源利用率、丢包率、可靠性；确定所述时间确定性需求的SLA指标信息包括以下至少之一：时延，抖动，精度。
在一个示例性的实例中，上述处理模块114，还被设置为对于所述时间确定性需求，将所述确定性业务分级以下级别：第一级：无时间确定性需求；第二级：抖动保证类；第三级：时延保证类；第四级：低时延；第五级：超低时延。
在一个示例性的实例中，上述处理模块114，还被设置为对于所述路由保护确定性需求，将所述确定性业务分级以下级别：第一级：无路由确定性要求；第二级：有路由确定性要求；第三级：有路由保护需求；第四级：有第一多路由保护需求；第五级：有第二多路由保护需求。
在一个示例性的实例中，上述处理模块114，还被设置为对于所述带宽确定性需求，将所述确定性业务分级以下级别：第一级：无带宽确定性需求；第二级：确保平均数率；第三级：确保数据速率和增强数据速率；第四级：第一确保数据速率；第五级：第二确保数据速率。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (17)

  1. 一种报文封装方法，包括：
    在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。
  2. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息之前，所述方法还包括：
    确定所述确定性业务的需求类型，对确定性流进行QoS分级，定义每种确定性QoS级别的SLA指标信息。
  3. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息之后，所述方法还包括：
    根据报文中封装的所述确定性分级Qos信息转发所述报文。
  4. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息，包括：
    在所述报文不扩展报文格式时，通过定义新的DSCP及MPLS TC标记值，以在所述报文中通过所述新的DSCP及MPLS TC映射所述确定性分级QoS信息。
  5. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息，包括：
    当所述报文为IPv6报文时，在报文扩展头中携带确定性网络QoS Option，其中，在所述报文的逐跳选项头HBH或目的选项头DOH中携带所述确定性分级Qos信息。
  6. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息，包括：
    当所述报文为IPv6报文时，在报文扩展头中携带确定性网络Flow Option，其中，所述确定性网络Flow Option中携带确定性流标识FLow-ID，所述确定性流标识FLow-ID用于映射所述确定性分级Qos信息。
  7. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息，包括：
    当所述报文为MPLS报文时，在MPLS标签中携带所述确定性分级QoS信息，其中，所述MPLS标签包括：基础特殊用途标签bSPL，熵标签Entropy Label；其中，
    通过扩展确定性分级TLV以携带所述确定性分级QoS信息。
  8. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息，包括：
    当所述报文为MPLS报文时，使用确定性流标识S-Label映射所述确定性分级Qos信息。
  9. 根据权利要求1所述的报文封装方法，其中，在报文中封装确定性分级Qos信息，包括：
    当所述报文为SRv6报文时，通过扩展确定性分级Qos TLV，在SRH报文头中携带所述确定性分级Qos信息。
  10. 根据权利要求2所述的报文封装方法，其中，确定所述确定性业务的需求类型之前，包括：
    对确定性网络的业务需求进行分类，其中，所述业务需求包括以下至少之一：带宽确定性需求，路由保护确定性需求，时间确定性需求。
  11. 根据权利要求10所述的报文封装方法，其中，确定所述确定性业务的需求类型，包括以下至少之一：
    确定所述带宽确定性需求的SLA指标信息包括以下至少之一：确保速率，精度，效率；
    确定所述路由保护确定性需求的SLA指标信息包括以下至少之一：路由保护数、节点资源利用率、丢包率、可靠性；
    确定所述时间确定性需求的SLA指标信息包括以下至少之一：时延，抖动，精度。
  12. 根据权利要求10所述的报文封装方法，其中，对确定性业务进行Qos分级，包括：
    对于所述时间确定性需求，将所述确定性业务分级以下级别：
    第一级：无时间确定性需求；
    第二级：抖动保证类；
    第三级：时延保证类；
    第四级：低时延；
    第五级：超低时延。
  13. 根据权利要求10所述的报文封装方法，其中，对确定性业务进行Qos分级，包括：
    对于所述路由保护确定性需求，将所述确定性业务分级以下级别：
    第一级：无路由确定性要求；
    第二级：有路由确定性要求；
    第三级：有路由保护需求；
    第四级：有第一多路由保护需求；
    第五级：有第二多路由保护需求。
  14. 根据权利要求10所述的报文封装方法，其中，对确定性业务进行Qos分级，包括：
    对于所述带宽确定性需求，将所述确定性业务分级以下级别：
    第一级：无带宽确定性需求；
    第二级：确保平均数率；
    第三级：确保数据速率和增强数据速率；
    第四级：第一确保数据速率；
    第五级：第二确保数据速率。
  15. 一种报文封装装置，包括：
    封装模块，被设置为在报文中封装确定性分级Qos信息，其中，所述确定性分级Qos信息至少包括以下之一：确定性流标识或分级标记，确定性业务需求分类，确定性QoS级别及所述确定性QoS级别的SLA指标信息。
  16. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至14任一项中所述的方法。
  17. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至14任一项中所述的方法。
PCT/CN2023/071740 2022-06-13 2023-01-10 报文封装方法及装置、存储介质及电子装置 WO2023241037A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210663399.6 2022-06-13
CN202210663399.6A CN117278645A (zh) 2022-06-13 2022-06-13 报文封装方法及装置、存储介质及电子装置

Publications (1)

Publication Number Publication Date
WO2023241037A1 true WO2023241037A1 (zh) 2023-12-21

Family

ID=89193071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/071740 WO2023241037A1 (zh) 2022-06-13 2023-01-10 报文封装方法及装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN117278645A (zh)
WO (1) WO2023241037A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112787902A (zh) * 2019-11-08 2021-05-11 中兴通讯股份有限公司 报文封装方法及装置、报文解封装方法及装置
US20210243641A1 (en) * 2018-08-14 2021-08-05 Huawei Technologies Co., Ltd. Time-aware quality-of-service in communication systems
CN114189905A (zh) * 2020-09-15 2022-03-15 华为技术有限公司 一种报文处理方法及相关设备
CN114205866A (zh) * 2021-12-10 2022-03-18 中国电信股份有限公司 确定性信息上报、下发方法、装置、存储介质及电子设备
CN114363182A (zh) * 2020-09-29 2022-04-15 中国移动通信有限公司研究院 确定性网络系统及确定性业务的传输方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210243641A1 (en) * 2018-08-14 2021-08-05 Huawei Technologies Co., Ltd. Time-aware quality-of-service in communication systems
CN112787902A (zh) * 2019-11-08 2021-05-11 中兴通讯股份有限公司 报文封装方法及装置、报文解封装方法及装置
CN114189905A (zh) * 2020-09-15 2022-03-15 华为技术有限公司 一种报文处理方法及相关设备
CN114363182A (zh) * 2020-09-29 2022-04-15 中国移动通信有限公司研究院 确定性网络系统及确定性业务的传输方法
CN114205866A (zh) * 2021-12-10 2022-03-18 中国电信股份有限公司 确定性信息上报、下发方法、装置、存储介质及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KORHONEN J., ANDERSSON L, JIANG Y, FINN N, VARGA B, FARKAS J, BERNARDOS C J, MIZRAHI T, BERGER L, : "DetNet Data Plane Encapsulation draft-ietf-detnet-dp-sol-04", IETF, 22 March 2018 (2018-03-22), pages 1 - 77, XP093118188, Retrieved from the Internet <URL:https://datatracker.ietf.org/doc/draft-ietf-detnet-dp-sol/04/> [retrieved on 20240111] *

Also Published As

Publication number Publication date
CN117278645A (zh) 2023-12-22

Similar Documents

Publication Publication Date Title
CN109743340B (zh) 报文处理的方法和网络装置
CN103346922B (zh) 基于sdn的确定网络状态的控制器及其确定方法
CN107181663A (zh) 一种报文处理方法、相关设备及计算机可读存储介质
WO2019228318A1 (zh) 一种报文处理方法和装置
WO2021017930A1 (zh) 报文转发
CN113328902B (zh) 网络性能检测方法、装置及网络设备
CN105024985A (zh) 一种报文处理方法及装置
CN112994961A (zh) 传输质量检测方法及装置、系统、存储介质
US11165716B2 (en) Data flow processing method and device
CN112511995B (zh) 消息交互方法、装置、设备和存储介质
EP2928128A1 (en) Ip data package transmitting method and label switching router
WO2015101066A1 (zh) 建立服务质量预留的方法及节点
CN105429882A (zh) 基于传统交换芯片查找方式的报文编辑实现方法及装置
TW202002596A (zh) 運算裝置中預測封包壽命之佇列系統
CN107104898A (zh) 报文传输的方法、设备及系统
WO2016150020A1 (zh) 基于调度流标识的报文调度方法和装置
CN112769738A (zh) DetNet数据包处理方法及装置
CN113949667A (zh) 分段网络中的报文处理方法及节点设备
WO2023241037A1 (zh) 报文封装方法及装置、存储介质及电子装置
CN115242892B (zh) 一种流标识获取方法、装置、设备及介质
CN104052741B (zh) 一种IPv6数据流的传输方法及装置
WO2023024663A1 (zh) 路由和云资源注册方法及装置、存储介质和电子装置
CN110351202A (zh) 5g核心网流量分组方法、装置、设备和计算机存储介质
CN110830373B (zh) 一种实现sdn网络中业务的qos服务质量区分的方法和装置
CN103973590B (zh) 一种QoS调度方法和装置

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

Country of ref document: EP

Kind code of ref document: A1