Nothing Special   »   [go: up one dir, main page]

WO2020134139A1 - 一种业务数据的转发方法、网络设备及网络系统 - Google Patents

一种业务数据的转发方法、网络设备及网络系统 Download PDF

Info

Publication number
WO2020134139A1
WO2020134139A1 PCT/CN2019/103177 CN2019103177W WO2020134139A1 WO 2020134139 A1 WO2020134139 A1 WO 2020134139A1 CN 2019103177 W CN2019103177 W CN 2019103177W WO 2020134139 A1 WO2020134139 A1 WO 2020134139A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
service data
configuration information
slice
forwarding path
Prior art date
Application number
PCT/CN2019/103177
Other languages
English (en)
French (fr)
Inventor
孙晋松
彭少富
王会来
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US17/299,021 priority Critical patent/US11689452B2/en
Priority to EP19906120.1A priority patent/EP3905609A4/en
Publication of WO2020134139A1 publication Critical patent/WO2020134139A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/50Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/12Shortest path evaluation
    • H04L45/122Shortest path evaluation by minimising distances, e.g. by selecting a route with minimum of number of hops
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/20Hop count for routing purposes, e.g. TTL
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/32Flooding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/66Layer 2 routing, e.g. in Ethernet based MAN's
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/745Address table lookup; Address filtering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/12Shortest path evaluation

Definitions

  • Embodiments of the present application relate to the field of communications, and in particular, to a service data forwarding method, network equipment, and network system.
  • Network slicing is one of the important key technologies of the 5th generation mobile (network for 5G) network. Its purpose is to provide a customized, isolated and reliable end-to-end dedicated network on the bearer network.
  • Technology can divide multiple virtual networks on the same network infrastructure, so that different business traffic is logically isolated on network resources to adapt to the characteristics of various types of services.
  • Embodiments of the present application provide a service data forwarding method, network equipment, and network system to at least solve the problem that network slice service data cannot be forwarded in a bearer network in the related art.
  • a method for forwarding service data includes: the network device determines the above according to network resource configuration information of the designated network and a network slice to which the business data belongs.
  • a forwarding path of service data wherein the network resource configuration information represents a network slice associated with the network resource of the specified network, and the determined network slice associated with the network resource of the forwarding path is related to the network slice to which the service data belongs Matching; the network device forwards the service data according to the forwarding path.
  • a network device including: a memory and a processor, characterized in that the memory stores a computer program, and the processor is configured to execute the computer program to execute:
  • the network resource configuration information of the specified network and the network slice to which the service data belong determine the forwarding path of the service data, wherein the network resource configuration information represents the network slice associated with the network resource of the specified network, and the determined forwarding
  • the network slice associated with the network resource of the path matches the network slice to which the service data belongs; the service data is forwarded according to the forwarding path.
  • a network system including any one of the foregoing network devices.
  • the network device can determine the forwarding path of the service data according to the network resource configuration information of the designated network and the network slice to which the service data belongs, the network resource configuration information represents the network slice associated with the network resource of the designated network.
  • the network slice associated with the network resource of the determined forwarding path matches the network slice to which the service data belongs; the network device forwards the service data according to the forwarding path. Therefore, the problem that the network slice service data cannot be forwarded in the bearer network in the related art can be solved, and the effect that different service data can be forwarded according to the corresponding network slice resources can be achieved.
  • FIG. 1 is a flowchart of a method for forwarding business data according to an embodiment of the present application
  • FIG. 2 is a structural block diagram of a network device according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a routing protocol according to an embodiment of the present application for calculating the optimal route (SR Best-effort LSP, SR-BE for short) based on network slicing;
  • FIG. 4 is a schematic diagram of a SR-BE path calculation based on a layer 2 member interface network slice by a routing protocol according to an embodiment of the present application;
  • FIG. 5 is a schematic diagram of a routing protocol based on network slicing for traffic engineering (Segment Routing Traffic Engineering, SR-TE) calculation according to an optional embodiment of the present application;
  • FIG. 6 is an Intermediate System to Intermediate System (IS-IS) protocol prefix (Prefix) segment ID (a segment identifier (SID)) sub-TLV carrying a slice identifier according to an optional embodiment of the present application.
  • Prefix an Intermediate System to Intermediate System
  • SID segment identifier
  • FIG. 7 is a schematic diagram of a slice-ID information format carried by the IS-IS protocol SID/Label Binding TLV according to an optional embodiment of the present application;
  • FIG. 8 is a schematic diagram of a slice-ID information format carried by the IS-IS protocol Adj-SID sub-TLV according to an optional embodiment of the present application;
  • FIG. 9 is a schematic diagram of a slice-ID information format carried by the IS-IS protocol LAN-Adj-SID sub-TLV according to an optional embodiment of the present application;
  • OSPF Open Shortest Path First
  • FIG. 11 is a schematic diagram of the format of Slice-ID information carried by the OSPF protocol Extended, Prefix, Range, and TLV according to an optional embodiment of the present application;
  • FIG. 12 is a schematic diagram of the format of Slice-ID information carried by the OSdj protocol Adj-SID sub-TLV according to an alternative embodiment of the present application;
  • FIG. 13 is a schematic diagram of the format of Slice-ID information carried by the OSPF protocol LAN Adj-SID sub-TLV according to an optional embodiment of the present application.
  • FIG. 1 is a flowchart of a business data forwarding method according to an embodiment of the present application. As shown in FIG. 1, the method includes:
  • Step S101 The network device determines the forwarding path of the service data according to the network resource configuration information of the designated network and the network slice to which the service data belongs, wherein the network resource configuration information represents the network slice associated with the network resource of the designated network and is determined to be forwarded The network slice associated with the network resource of the path matches the network slice to which the service data belongs;
  • Step S103 The network device forwards the service data according to the forwarding path.
  • the network resource configuration information represents the network slice associated with the network resource of the designated network and is determined
  • the network slice associated with the network resource of the forwarding path matches the network slice to which the service data belongs; the service data is forwarded according to the forwarding path. Therefore, the problem that the network slice service data cannot be forwarded in the bearer network in the related art can be solved, and the effect that different service data can be forwarded according to the corresponding network slice resources can be achieved.
  • determining the forwarding path of the service data according to the network resource configuration information and the network slice to which the service data belongs includes: determining the forwarding path of the service data according to the link resource configuration information, where each of the determined forwarding paths The network slice associated with each link is the same as the network slice to which the service data belongs.
  • the network resource configuration information includes link resource configuration information, which represents the network slice associated with the link in the specified network.
  • the network device determining the forwarding path of the service data according to the link resource configuration information includes: determining the next hop link of the service data according to the link resource configuration information; or, passing the preset according to the link resource configuration information
  • the algorithm determines the forwarding path for forwarding service data to the destination node, where the forwarding path includes multiple links.
  • the network device determines the forwarding path of the service data according to the network resource configuration information and the network slice to which the service data belongs, and further includes: determining the member interface of the link that forwards the service data on the forwarding path according to the link member interface configuration information , Where the network slice associated with the member interface of the link that forwards the service data is the same as the network slice to which the service data belongs, and the link resource configuration information includes the link member interface configuration information, which represents the designated network The network slice associated with the member interface of the link in.
  • the network device determines the forwarding path of the service data according to the network resource configuration information and the network slice to which the service data belongs, and further includes: determining the forwarding path of the service data according to the network node configuration information, wherein the determined forwarding path
  • the network slice associated with each network node is the same as the network slice to which the service data belongs.
  • the network resource configuration information includes network node configuration information.
  • the network node configuration information represents the network slice associated with the network node in the specified network.
  • the network device forwarding the service data according to the forwarding path includes: encapsulating the forwarding path information on the service data, and forwarding the service data according to the encapsulated forwarding path information.
  • the method before the network device determines the forwarding path of the service data according to the network resource configuration information of the designated network and the network slice to which the service data belongs, the method includes: receiving the network resource configuration information, wherein the network resource configuration information is notified to Specify network nodes in the network.
  • the network resource configuration information includes one or more network slice identifiers associated with the network resources of the specified network.
  • the embodiment of the present application can slice and identify the network resources of the device, where the network resources include but are not limited to the prefix address of the device, the layer 3 link, the layer 2 member interface, and the central processing unit (Central Processing Unit, CPU for short) And forwarding queues, etc.; in order to achieve the purpose of forwarding different service traffic according to their corresponding slice resources, it is necessary to perform path calculation based on different slice resources respectively, and establish an association relationship between the forwarding of the service traffic and the slice resources of the bearer network device.
  • the network resources include but are not limited to the prefix address of the device, the layer 3 link, the layer 2 member interface, and the central processing unit (Central Processing Unit, CPU for short) And forwarding queues, etc.; in order to achieve the purpose of forwarding different service traffic according to their corresponding slice resources, it is necessary to perform path calculation based on different slice resources respectively, and establish an association relationship between the forwarding of the service traffic and the slice resources of the bearer network device.
  • different network slices are identified using different Slice-IDs.
  • Slice-ID is a global concept of the network. All devices in the same network have the same awareness of the same Slice-ID. Network resources with the same Slice-ID correspond to the same network slice, otherwise they correspond to different network slices. Different slice-IDs can be assigned to the same network resource to identify that they belong to different network slices. The service can identify the corresponding network slice by associating the Slice-ID, and the traffic will also be forwarded in the corresponding network resource.
  • the network content service provider Internet Content Provider, IGP
  • IGP Internet Content Provider
  • the ingress PE device collects the flood notification information, based on different Slice-ID network resources, based on the algorithm specified by the service, such as Shortest Path First (SPF) or Constrained Shortest Path First (referred to as CSPF) of various strategies, calculate the path forwarding information corresponding to the business, and iteratively associate the underlying network resources required for forwarding, and finally generate device forwarding entries; when ingress (ingress) )
  • SPF Shortest Path First
  • CSPF Constrained Shortest Path First
  • the forwarding entry of the service can continue to be mapped to the corresponding underlying network resource according to the MPLS label and perform label swap (Swap) operation until the packet reaches the egress PE.
  • the service data may carry an identifier to indicate the network slice associated with the service data.
  • the identifier may be an identifier directly indicating the network slice to which the service data belongs, for example, a slice-ID, or another identifier that can indirectly reflect the network slice to which the service data belongs, such as classification information of the service data, etc. .
  • the PE in the network that forwards the service data can map the service data to a specific network slice, for example, through the following two mapping methods: coarse-grained mapping: such as virtual routing forwarding (Virtual RoutingForwarding, referred to as VRF) If the slice-ID information is configured under the service instance, all data packets belonging to the VRF service instance can be forwarded along the network slice corresponding to the corresponding slice-ID; or, fine-grained mapping: you can configure the strategy according to the business report
  • the flow classification information of the document (such as source/destination media access control address (Media Access Control, MAC for short), source/destination Internet protocol address (InternetProtocol, referred to as IP), source/destination port (port), IP priority, etc.) will be Business messages are mapped to different network slices.
  • the IGP protocol on the device needs to support the association of the prefix and the layer 3 link with the corresponding Slice-ID, that is, the prefix and the layer 3 chain
  • One or more Slice-IDs are assigned to the road.
  • Layer 3 links such as Flexible Ethernet (FlexE) or Link Aggregation, abbreviation
  • LAG Link Aggregation, abbreviation
  • the device should also support the allocation of the corresponding Slice-ID for the Layer 2 member interfaces of these Layer 3 links.
  • the Interior Gateway Protocol Interior Gateway Protocol, IGP for short
  • the Slice-ID information will be associated and announced together to identify the network slice information where it is located.
  • the MPLS network can be sliced based on SR technology.
  • Segment routing is a kind of source routing technology, which uses SID to define the topology and services of the network, and can add SID before the business message to identify the message forwarding path information, and then flexibly Control the forwarding of business traffic.
  • the device can assign the corresponding SID to the prefix, layer 3 link, and layer 2 member interface, where the SID assigned to the prefix is called Prefix-SID, and the SID assigned to the neighbor of the device is called Adj-SID, which is The Layer 2 member interface of the Layer 3 link is assigned an Adj-SID for identification, which is called the L2 Link Member Adjacent SID (L2 Bundle Member Adj-SID).
  • the original SR SID can be extended so that it can allocate different slice SIDs according to different Slice-IDs. After slicing SIDs to SR resources based on Slice-ID, the corresponding information will be flooded in the entire routing domain through IGP.
  • other devices on the network receive the above-mentioned announced topology information carrying the Slice-ID field, and will use the service-related algorithm to calculate the corresponding SR based on its dedicated slice network resources.
  • Label path forwarding information provides a basis for flexibly specifying different services to be forwarded in different logical topologies.
  • the device may specify SIDs based on different slice Slice-IDs as prefixes, layer 3 links, and layer 2 member interfaces, respectively, for SR resource identification in different network slices.
  • each SID will be uniquely associated with a Slice-ID.
  • Prefix-SID, Adj-SID and L2 Bundle Member Adj-SID with the same Slice-ID belong to the same network slice.
  • the assigned SID and its corresponding Slice-ID information will be delivered to the local label forwarding table of the device, and a label mapping (IncomingLabelMap, referred to as ILM) entry will be established to associate the business and local hardware resources and guide Local forwarding of business traffic.
  • ILM Label mapping
  • the above-described network resource does not allocate a Slice-ID, it is considered to be in the default slice, and at this time, the prefix, Layer 3 link, Layer 2 member interface, and its location can be considered The specified SID does not have a corresponding Slice-ID, or the Slice-ID is 0.
  • the IGP protocol adds a Prefix-SID notification method, and introduces Slice-ID information into the corresponding notification method, which will be flooded on the network along with the Prefix-SID.
  • a Prefix-SID notification method when performing route redistribution or route leaking operations, it is necessary to support the inherited Slice-ID to be processed together with the Prefix-SID information; for the OSPF protocol, when routing redistribution or regional route summarization is also required, support is also required The inherited Slice-ID is processed together with the Prefix-SID information.
  • the IGP protocol when the device as a mapping server (Mapping Server) announces one or more sets of Prefix-SID prefixes, the IGP protocol will add a SRMS information notification method, and introduce Slice- in the corresponding notification method ID information and flood it with SRMS information on the network.
  • mapping server Mapping Server
  • IGP adds a new announcement method that supports Layer 3 link Adj-SID, and introduces Slice-ID information in the corresponding announcement method, which will be on the network along with the Layer 3 link Adj-SID Flooding.
  • IGP newly added a notification method that supports L2 Bundle Member Adj-SID. Introducing Slice-ID information in the corresponding notification method, it will be carried out on the network together with L2 Bundle Member Adj-SID flood.
  • the above SID carrying Slice-ID information may be considered to be defined as a new TLV to carry to distinguish the current protocol definition SID notification method.
  • the IGP supports receiving and processing all the above related topology resource information and saving it in the topology information database for path calculation.
  • Different services specify the associated Slice-ID, which is used to identify the network slice information where the forwarded traffic is expected, and can specify different path calculation methods according to the characteristics of the service, such as calculating the path according to the shortest path SPF, or based on the traffic engineering topology database (Traffic Engineering Databse, TEDB for short) performs CSPF calculation according to a strategy, such as forwarding along the shortest delay path or forwarding along the link with the maximum bandwidth.
  • Traffic Engineering Databse Traffic Engineering Databse
  • IGP performs topology calculation based on network slices supported by the local device, and does not perform topology calculation on network slices that are not supported by the local device.
  • the path in a corresponding network slice for a certain service when calculating the path in a corresponding network slice for a certain service, it only uses topology resources with the same Slice-ID for calculation, if the prefix or link corresponds to different Slice-ID information , You cannot participate in the path calculation.
  • IGP announces the member interface information of the layer 3 link the relevant information can also participate in the path calculation, but it must also have the same Slice-ID; when IGP performs SR-BE calculation, for the remote The prefix announced by the device is calculated based on a certain network slice.
  • the incoming and outgoing labels are used for this
  • the Prefix-SID corresponding to the slice-ID of the network slice, and the corresponding Slice-ID will also be announced to the forwarding plane as a delivery field.
  • IGP calculates routes based on a certain network slice. For a reachable prefix, if its next hop is a layer 3 link containing a layer 2 member interface, such as a FlexE interface, and The Layer 2 member interface under the FlexE interface is also associated with optional Slice-ID information; then the next hop optionally forwarded can be associated with a Layer 2 member interface with the same Slice-ID.
  • a layer 3 link containing a layer 2 member interface, such as a FlexE interface
  • the Layer 2 member interface under the FlexE interface is also associated with optional Slice-ID information; then the next hop optionally forwarded can be associated with a Layer 2 member interface with the same Slice-ID.
  • IGP is based on TEDB, and when CSPF is calculated for a certain network slice, it uses the Prefix-SID used to identify the node when iterating the optional SID List according to the calculated explicit path.
  • the Adj-SID that identifies the link and the L2 Bundle Member Adj-SID that identifies the Layer 2 member interface must be the SID information corresponding to the network slice, and the corresponding Slice-ID will also be announced to the forwarding plane as a delivery field.
  • FIG. 3 introduces the SR-BE calculation method when different three-layer links on the network are associated with different network slices; in the SR MPLS network shown in FIG. 3, the nodes PE1, PE2, P3, P4 The IGP protocol and the SR function are enabled separately. All devices are configured with the same SR Global Block (SRGB), with a range of [100,200]; two virtual private networks (Virtual Private Network, VPN) services are configured in the network. They are VPN_A and VPN_B. In order to achieve the purpose of different VPN services being forwarded on demand in different network slices, the following steps need to be performed, assuming that the two divided network slices correspond to Slice-ID 1 and Slice-ID 2:
  • SRGB SR Global Block
  • VPN Virtual Private Network
  • Step 1 Associate two VPN services to the corresponding slice, where VPN_A is associated with Slice-ID1 and VPN_B is associated with Slice-ID2; and the VPN_A and VPN_B service forwarding paths are set to use SR-BE method for calculation;
  • Step 2 Configure Layer 3 link Link1, Link2 home slice 1, corresponding to Slice-ID1; configure Layer 3 link Link3, Link4 home slice 2, corresponding to Slice-ID2; for the prefix Prefix_2 announced by the P2 device, assign it
  • the two Prefix-SIDs correspond to Slice-ID1 and Slice-ID2 respectively, with indexes of 1 and 2, and create Information Lifecycle Management (ILM) entries for them, respectively:
  • Step 3 The IGP protocol of the device on the network floods the configured link slicing information and Prefix-SID information of different slices allocated for prefixes in the entire network.
  • the optional notification method will be described in the following embodiment. ;
  • the ingress device PE1 receives the IGP flooding information, and saves the Slice-ID to which the link belongs and the different Prefix-SID information assigned by the prefix to the local topology database.
  • This device supports two slices, Slice-ID 1 and 2, so PE1 attempts to perform path calculation for Slice-ID 1 and Slice-ID 2. Since the path calculation method defined by VPN1 and VPN2 is the default SR-BE method, the device will The shortest path calculation of topology based on SPF. For the path calculation of Slice-ID1, only the link with Slice-ID 1 is used, that is, Link1 and Link2, and the forwarding path is calculated as PE1-P3-PE2; in the same way, the path calculation of Slice-ID2 is performed. Only the link whose Slice-ID is 2, namely Link3 and Link4, is calculated and its forwarding path is PE1-P4-PE2.
  • the next hop sends different information, and the assigned Prefix-SID is also different. Therefore, it is necessary to separately send the corresponding slice forwarding information to the forwarding entry, as follows:
  • Step 5 Repeat the calculation operation similar to step 4 above on the P3 device. Since P3 only supports Slice-ID 1, it only performs SR-BE calculation based on the link of Slice-ID 1, and the calculated SR label forwarding entry It is also based only on Slice-ID 1, the specific entries are as follows:
  • the forwarding entries of the above ⁇ FEC: Prefix_2, Slice-ID: 2> are matched to determine the corresponding forwarding traditional single-layer network (underlay) hardware
  • the exchange is 101, and then forward the message from the interface Link3.
  • Step 6 The operation on the P4 device is similar to step 5, and will not be described in detail here.
  • FIG. 4 introduces the SR-BE calculation method when the layer 2 member interface of the layer 3 link on the network is associated with different network slices.
  • the nodes PE1, PE2, The configuration of P3 is the same as that of Embodiment 1.
  • the two network slices correspond to Slice-ID 1 and Slice-ID 2, respectively, and Link1 and Link2 belong to two network slices at the same time.
  • the difference between this embodiment and the above embodiment lies mainly in SR-BE calculation method for P3 equipment.
  • the two Layer 2 member ports subif1 in the Layer 3 link Link2 belong to the network slice Slice-ID1, and subif2 belongs to the network slice Slice-ID2;
  • the P3 device calculates the SR-BE forwarding path based on the network slice Slice-ID1, it calculates the forwarding next hop of the prefix Prefix_2 according to the SPF calculation is Link2, and since the member port subif1 of Link2 belongs to the network slice Slice-ID1, the actual forwarding The next hop used is subif1, and its SR-MPLS forwarding entries are:
  • FIG. 5 This embodiment is shown in FIG. 5, which introduces a method for the device to perform SR-TE calculation based on different network slices.
  • the nodes PE1, PE2, P3, and P4 respectively enable the IGP protocol and SR function; the network is divided into two network slices corresponding to Slice-ID1 and Slice-ID2; configure two VPN services: VPN_A and VPN_B
  • Step 1 Configure Layer 3 link Link1 home slice 1, corresponding to Slice-ID 1, and assign Adj-SID as 1001; configure Layer 3 link Link3, Link4 home slice 2, corresponding to Slice-ID 2, and assign Adj-SID 3002 respectively , 4002; Among them, there are two Layer 2 member interfaces subif1 and subif2 under Layer 3 link Link2, which belong to slice 1 and slice 2, respectively.
  • the assigned Adj-SIDs are 2001 and 2002. For each Adj-SID, the device is Create an ILM entry as follows:
  • Step 2 The IGP protocol of the device on the network floods the configured link slice information and Adj-SID information of different slices across the entire network.
  • the optional notification method will be described in the following embodiments;
  • Step 3 The ingress device PE1 receives the IGP flooding information, and saves the Slice-ID to which the link belongs and the different Adj-SID information allocated to the local topology database. Since this device supports two slices, Slice-ID 1 and 2, PE1 attempts to perform path calculation for Slice-ID 1 and Slice-ID 2. Since the path calculation method defined by VPN_A and VPN_B is SR-TE, the device will be based on CSPF performs path calculation.
  • the forwarding path of VPN_A is PE1-Link1-P3-subif1-PE2; the forwarding path of VPN_B is PE1-Link3-P4-Link4-P3-subif2-PE2; and the calculated path is iteratively converted to the corresponding one using Adj-SID SID List, for VPN_A, its forwarding SID List A is [1001,2001], VPN_B's forwarding SID List B is [3002,4002,2002];
  • Step 4 When the service traffic of VPN_A reaches the device PE1, it iteratively finds the forwarding entry SID List A according to the configuration, the corresponding SID List on the traffic encapsulation, and finds the local ILM entry according to its outermost label 1001.
  • the outer label POP and according to the corresponding Slice-ID information associated with the traditional single-layer network (underlay) forwarding resources, forward the message from the interface Link1 to the node P3; P3 also searches the local ILM table based on the outermost label of the traffic Item, determine to forward the traditional single-layer network (underlay) forwarding resources associated with Slice-ID and complete the forwarding of traffic; until the traffic reaches the destination node.
  • Step 5 When the service traffic of VPN_B reaches the device PE1, the flow is similar to step 4, which will not be described in detail here.
  • an IS-IS protocol based on the Slice-ID Prefix-ID notification method is considered, considering the device compatibility problem, the Slice Prefix-SID sub-TLV format is added, as shown in FIG. 6, the new The Prefix-SID sub-TLV adds a notice of Slice-ID field information, which is used to identify the Slice-ID information corresponding to the Prefix-SID.
  • an IS-IS protocol is used to announce the SID/Label Binding information based on the Slice-ID.
  • a new format of Slice SID/Label Binding TLV is added. As shown in FIG. 7, Compared with the SID/Label Binding TLV defined by The Internet Engineering Task Force (IETF), the Slice-ID field is added to identify the Slice-ID information corresponding to the Prefix-SID notified by the SID/Label Binding .
  • IETF Internet Engineering Task Force
  • an IS-IS protocol-based Adj-ID notification method based on Slice-ID is shown.
  • new formats of Slice Adj-SID sub-TLV and Slice LAN Adj-SID are added, as shown in the figure
  • two new sub-TLVs add a notice of Slice-ID field information, which is used to identify the Slice-ID information corresponding to the Adj-SID.
  • an IS-IS protocol based on the Slice-ID L2 Bundle Member Adj-ID notification method is considered, considering the device compatibility problem, a new Slice L2 Bundle Member Adj-SID sub-TLV and Slice L2 Bundle are added Member ALAN-AID-SID format, the format is basically the same as shown in Figures 8 and 9, two new sub-TLVs increase the notice of Slice-ID field information, which is used to identify the Slice-corresponding to the Adj-SID ID information.
  • a Prefix-ID notification method based on the Slice-ID of the OSPF protocol is illustrated.
  • a Slice Prefix-SID sub-TLV format is added.
  • the new Prefix-ID SID sub-TLV adds a notice of Slice-ID field information, which is used to identify the Slice-ID information corresponding to the Prefix-SID.
  • an OSPF protocol is shown based on the Slice-ID to announce the Extended Prefix Range information.
  • the Slice Extended Extended Prefix Range TLV format is added.
  • the IETF definition Extended Prefix Range TLV which adds a Slice-ID field, is used to identify the Slice-ID information corresponding to the announced Prefix-SID.
  • an Adj-ID notification method based on the Slice-ID of the OSPF protocol is illustrated.
  • new formats of Slice Adj-SID sub-TLV and Slice LAN Adj-SID are added, as shown in FIG. 12 and As shown in FIG. 13, two new sub-TLVs increase the notice of Slice-ID field information, which is used to identify the Slice-ID information corresponding to the Adj-SID.
  • FIG. 2 is a structural block diagram of the network device according to an embodiment of the present application.
  • the network device includes a memory 202 and a processor 204.
  • a computer program is stored, and the processor is set to run the computer program to execute: determine the forwarding path of the business data according to the network resource configuration information of the designated network and the network slice to which the business data belongs, wherein the network resource configuration information characterizes the network of the designated network
  • the network slice associated with the resource, the network slice associated with the network resource of the determined forwarding path matches the network slice to which the service data belongs; the service data is forwarded according to the forwarding path.
  • the network resource configuration information represents the network slice associated with the network resource of the designated network and is determined
  • the network slice associated with the network resource of the forwarding path matches the network slice to which the service data belongs; the service data is forwarded according to the forwarding path. Therefore, the problem that the network slice service data cannot be forwarded in the bearer network in the related art can be solved, and the effect that different service data can be forwarded according to the corresponding network slice resources can be achieved.
  • the memory 202 may be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the service data forwarding method in the embodiments of the present application, and the processor 204 is stored in the memory 202 by running Computer program to execute various functional applications and data processing, that is, to implement the above method.
  • the memory 202 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the network device determining the forwarding path of the service data according to the network resource configuration information and the network slice to which the service data belongs includes: determining the forwarding path of the service data according to the link resource configuration information, where the determined forwarding path
  • the network slice associated with each link is the same as the network slice to which the service data belongs.
  • the network resource configuration information includes link resource configuration information, which represents the network slice associated with the link in the specified network.
  • the network device determines the forwarding path of the service data according to the link resource configuration information, and further includes: determining the next hop link of the service data according to the link resource configuration information; or, according to the link resource configuration information
  • the set algorithm determines the forwarding path for forwarding service data to the destination node, where the forwarding path includes multiple links.
  • the network device determines the forwarding path of the service data according to the network resource configuration information and the network slice to which the service data belongs, including: determining the member interface of the link that forwards the service data on the forwarding path according to the link member interface configuration information, Among them, the network slice associated with the member interface of the link that forwards the service data is the same as the network slice to which the service data belongs.
  • the link resource configuration information includes the link member interface configuration information.
  • the link member interface configuration information represents the specified The network slice associated with the member interface of the link in the network.
  • the network device determines the forwarding path of the service data according to the network resource configuration information and the network slice to which the service data belongs, and further includes: determining the forwarding path of the service data according to the network node configuration information, wherein the determined forwarding path
  • the network slice associated with each network node is the same as the network slice to which the service data belongs.
  • the network resource configuration information includes network node configuration information.
  • the network node configuration information represents the network slice associated with the network node in the specified network.
  • the network device forwarding the service data according to the forwarding path includes: encapsulating the forwarding path information on the service data, and forwarding the service data according to the encapsulated forwarding path information.
  • before determining the forwarding path of the service data according to the network resource configuration information of the designated network and the network slice to which the service data belongs includes: receiving network resource configuration information, wherein the network resource configuration information is notified to the designated network Network nodes.
  • the network resource configuration information includes one or more network slice identifiers associated with the network resources of the specified network.
  • An embodiment of the present application also provides a network system, including any of the network devices described above.
  • An embodiment of the present application further provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute any of the steps in the above method embodiments during runtime.
  • the above storage medium may include but is not limited to: U disk, read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), mobile hard disk, magnetic Various media that can store computer programs, such as compact discs or optical discs.
  • modules or steps in the embodiments of the present application described above can be implemented by a general-purpose computing device, and they can be concentrated on a single computing device or distributed in multiple computing devices.
  • they can be implemented with program code executable by the computing device, so that they can be stored in the storage device to be executed by the computing device, and in some cases, can be different from here
  • the steps shown or described are performed in the order of, or they are made into individual integrated circuit modules respectively, or multiple modules or steps among them are made into a single integrated circuit module to achieve. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.
  • the network device can determine the forwarding path of the service data according to the network resource configuration information of the designated network and the network slice to which the service data belongs, the network resource configuration information represents the network slice associated with the network resource of the designated network, The network slice associated with the network resource of the determined forwarding path matches the network slice to which the service data belongs; the network device forwards the service data according to the forwarding path. Therefore, the problem that the network slice service data cannot be forwarded in the bearer network in the related art can be solved, and the effect that different service data can be forwarded according to the corresponding network slice resources can be achieved.

Landscapes

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

Abstract

本申请实施例提供了一种业务数据的转发方法、网络设备及网络系统,转发方法包括根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资源所关联的网络切片与业务数据所属的网络切片相匹配;根据转发路径对业务数据进行转发。通过本申请实施例,可以解决相关技术中网络切片业务数据无法在承载网中转发的问题。

Description

一种业务数据的转发方法、网络设备及网络系统
本申请要求于2018年12月29日提交中国专利局、申请号为201811648145.7、发明名称“一种业务数据的转发方法、网络设备及网络系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域,具体而言,涉及一种业务数据的转发方法、网络设备及网络系统。
背景技术
网络切片是第五代移动通信技术(5th generation mobile network,简称5G)网络的重要关键技术之一,其目的是为了在承载网上提供定制化、相互隔离、质量可靠的端到端专属网络,该技术可以在同一个网络基础设施上切分出多个虚拟的网络,使得不同业务流量传输时在网络资源上逻辑隔离,从而适配各种不同类型服务的特征需求。但相关技术中并不存在一种能够在承载网中转发各网络切片业务数据的方案。
发明内容
本申请实施例提供了一种业务数据的转发方法、网络设备及网络系统,以至少解决相关技术中网络切片业务数据无法在承载网中转发的问题。
根据本申请的一个实施例,提供了一种业务数据的转发方法,上述业务数据在指定网络中转发,包括:网络设备根据上述指定网络的网络资源配置信息和上述业务数据所属的网络切片确定上述业务数据的转发路径,其中,上述网络资源配置信息表征了上述指定网络的网络资源所关联的网络切片,被确定的上述转发路径的网络资源所关联的网络切片与上述业务数据所属的网络切片相匹配;网络设备根据上述转发路径对上述业务数据进行转发。
根据本申请的另一个实施例,提供了一种网络设备,包括:包括存储器和处理器,其特征在于,上述存储器中存储有计算机程序,上述处理器被设置为运行上述计算机程序以执行:根据上述指定网络的网络资源配置信息和上述业务数据所属的网络切片确定上述业务数据的转发路径,其中,上述网络资源配置信息表征了上述指定网络的网络资源所关联的网络切片,被确定的上述转发路径的网络资源所关联的网络切片与上述业务数据所属的网络切片相匹配;根据上述转发路径对上述业务数据进行转发。
根据本申请的又一个实施例,还提供了一种网络系统,包括上述任一项上述的网络设备。
根据本申请的又一个实施例,还提供了一种存储介质,上述存储介质中存储有计算机程序,其中,上述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
通过本申请实施例,由于网络设备可以根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资源所关联的网络切片与业务数据所属的网络切片相匹配;网络设备根据转发路径对业务数据进行转发。因此,可以解决相关技术中网络切片业务数据无法在承载网中转发的问题,达到不同业务数据可以按照其对应的网络切片资源进行转发的效果。
附图说明
此处所说明的附图用来提供对本申请实施例的进一步理解,构成本申请实施例的一部分,本申请实施例的示意性实施例及其说明用于解释本申请实施例,并不构成对本申请实施例的不当限定。在附图中:
图1是根据本申请实施例的业务数据的转发方法的流程图;
图2是根据本申请实施例的网络设备的结构框图;
图3是根据本申请实施例的路由协议基于网络切片进行分段路由最优 路径(SR Best-effort LSP,简称SR-BE)算路的示意图;
图4是根据本申请实施例路由协议基于二层成员接口网络切片进行SR-BE算路的示意图;
图5是根据本申请可选实施例的路由协议基于网络切片进行流量工程(Segment Routing Traffic Engineering,简称SR-TE)算路的示意图;
图6是根据本申请可选实施例的中间系统到中间系统(Intermediate system to intermediate system,简称IS-IS)协议前缀(Prefix)段ID(a segment identifier,简称SID)sub-TLV携带切片标识(Slice-Identity document,简称Slice-ID)信息格式示意图;
图7是根据本申请可选实施例的IS-IS协议SID/Label Binding TLV携带Slice-ID信息格式示意图;
图8是根据本申请可选实施例的IS-IS协议Adj-SID sub-TLV携带Slice-ID信息格式示意图;
图9是根据本申请可选实施例的IS-IS协议LAN-Adj-SID sub-TLV携带Slice-ID信息格式示意图;
图10是根据本申请可选实施例的开放式最短路径优先(Open Shortest Path First,简称OSPF)协议Prefix SID sub-TLV携带Slice-ID信息格式示意图;
图11是根据本申请可选实施例的OSPF协议Extended Prefix Range TLV携带Slice-ID信息格式示意图;
图12是根据本申请可选实施例的OSPF协议Adj-SID sub-TLV携带Slice-ID信息格式示意图;
图13是根据本申请可选实施例的OSPF协议LAN Adj-SID sub-TLV携带Slice-ID信息格式示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请实施例。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是,本申请实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
实施例1
本申请的实施例提供了一种业务数据的转发方法,业务数据在指定网络中转发,图1是根据本申请实施例的业务数据的转发方法的流程图,如图1所示,方法包括:
步骤S101,网络设备根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,其中,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资源所关联的网络切片与业务数据所属的网络切片相匹配;
步骤S103,网络设备根据转发路径对业务数据进行转发。
通过本申请的实施例,由于可以根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资源所关联的网络切片与业务数据所属的网络切片相匹配;根据转发路径对业务数据进行转发。因此,可以解决相关技术中网络切片业务数据无法在承载网中转发的问题,达到不同业务数据可以按照其对应的网络切片资源进行转发的效果。
在一个实施方式中,根据网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,包括:根据链路资源配置信息确定业务数据的转发路径,其中,被确定的转发路径上的每个链路所关联的网络切片与业务数据所属的网络切片相同,网络资源配置信息包括链路资源配置信息,链路资源配置信息表征了指定网络中的链路所关联的网络切片。
在一个实施方式中,网络设备根据链路资源配置信息确定业务数据的转发路径,包括:根据链路资源配置信息确定业务数据的下一跳链路;或者,根据链路资源配置信息通过预设的算法确定将业务数据转发至目的节点的转发路径,其中,转发路径包括多条链路。
在一个实施方式中,网络设备根据网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,还包括:根据链路成员接口配置信息确定转发路径上转发业务数据的链路的成员接口,其中,转发业务数据的链路的成员接口所关联的网络切片与业务数据所属的网络切片相同,链路资源配置信息中包括链路成员接口配置信息,链路成员接口配置信息表征了指定网络中的链路的成员接口所关联的网络切片。
在一个实施方式中,网络设备根据网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,还包括:根据网络节点配置信息确定业务数据的转发路径,其中,被确定的转发路径上的每个网络节点所关联的网络切片与业务数据所属的网络切片相同,网络资源配置信息包括网络节点配置信息,网络节点配置信息表征了指定网络中的网络节点所关联的网络切片。
在一个实施方式中,网络设备根据转发路径对业务数据进行转发,包括:将转发路径的信息封装在业务数据上,根据封装的转发路径的信息对业务数据进行转发。
在一个实施方式中,网络设备在根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径之前,方法包括:接收网络资源配置信息,其中,网络资源配置信息被通告给指定网络中的网络节点。
在一个实施方式中,网络资源配置信息中包括指定网络的网络资源所关联的一个或多个网络切片标识。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现,当 然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请实施例的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本申请各个实施例的方法。
以下结合具体实施方式对本申请的实施例进行进一步说明:
本申请实施例可以对设备网络资源进行切片(Slice)和标识,这里网络资源包括但不限于设备的前缀地址、三层链路、二层成员接口,中央处理器(Central Processing Unit,简称CPU)以及转发队列等;为了实现不同业务流量按照其对应的切片资源进行转发的目的,需要分别基于不同的切片资源进行路径计算,并将业务流量的转发与承载网设备的切片资源建立起关联关系。
在一个可选的实施方式中,不同的网络切片使用不同的Slice-ID进行标识。Slice-ID是网络全局概念,同一网络中所有设备对相同的Slice-ID具有相同的认知。具有相同Slice-ID的网络资源对应相同的网络切片,否则对应不同的网络切片。相同的网络资源可以分配不同的Slice-ID,用于标识其属于不同的网络切片。业务可以通过关联Slice-ID来标识对应的网络切片,流量也将在对应的网络资源中进行转发。
在一个可选的实施方式中,考虑多协议标签交换(Multi-Protocol Label Switching,简称MPLS)网络的切片方案,网络内容服务商(Internet Content Provider,简称IGP)协议负责将关联Slice-ID的网络资源信息在全网进行泛洪,入口(ingress)PE设备收集泛洪通告的信息,基于不同的Slice-ID网络资源,根据业务指定的算法,比如最短路径优先(Shortest Path First,简称SPF)或者各种不同策略的约束最短路径优先(Constrained Shortest Path First,简称CSPF),计算得到业务对应的路径转发信息,并迭代关联转发所需要的底层网络资源,最终生成设备转发表项;当入口(ingress) 边缘节点(Provider Edge,简称PE)设备收到业务流量时,则需要根据业务关联的切片信息,封装上对应的MPLS标签进行转发;而对于P设备则同样类似入口(ingress)PE设备生成区分业务的转发表项,并能够根据MPLS标签继续映射到对应的底层网络资源,并进行标签交换(Swap)操作,直到报文到达出口(egress)PE。
在一个可选的方式中,业务数据中可以携带标识,用于表示该业务数据所关联的网络切片。该标识可以是直接表示该业务数据归属的网络切片的标识,例如可以是slice-ID,也可以是其他能够间接反应出该业务数据所归属的网络切片的标识,例如该业务数据的分类信息等。
在一个可选的方式中,转发业务数据的网络中的PE可以将业务数据映射到特定的网络切片,例如可以通过以下两种映射方式:粗粒度映射:比如虚拟路由转发(Virtual Routing Forwarding,简称VRF)业务实例下配置slice-ID信息,则所有归属于该VRF业务实例的数据报文都可以沿相应slice-ID对应的的网络切片转发;或者,细粒度映射:可以配置策略,根据业务报文的流分类信息(如源/目的介质访问控制地址(Media AccessC Control,简称MAC)、源/目的互联网协议地址(InternetProtocol,简称IP)、源/目的端口(port)、IP优先级等)将业务报文映射到不同的网络切片。
在一个可选的实施方式中,为了实现上述基于Slice-ID的网络切片,设备上的IGP协议需要支持将前缀、三层链路与对应的Slice-ID关联起来,即为前缀、三层链路分配一个或者多个Slice-ID,此外,在某些网络应用场景中,可能还需要使用到三层链路(比如弹性以太网(Flexible Ethernet,简称FlexE)、链路聚合(Link Aggregation,简称LAG)等)的成员接口信息,所以设备还应该支持为这些三层链路的二层成员接口分配对应的Slice-ID。内部网关协议(Interior Gateway Protocol,简称IGP)在通告这些拓扑资源信息时,Slice-ID信息将关联一起进行通告,以标识其所在的网络切片信息。
在一个可选的实施方式中,MPLS网络的切片可以基于SR技术实现。段路由(Segment Routing,简称SR)属于源路由技术的一种,其使用SID定义网络的拓扑和服务,并可以通过在业务报文前增加SID List标识该报文转发的路径信息,继而灵活地控制业务流量的转发。在SR MPLS网络中,设备可以为前缀、三层链路、二层成员接口分配对应的SID,其中为前缀分配SID称为Prefix-SID,为设备的邻接分配的SID称为Adj-SID,为三层链路的二层成员接口分配用于标识的Adj-SID,称其为L2链路成员邻接SID(L2 Bundle Member Adj-SID)。
在一个可选的实施方式中,可以对原有的SR SID进行扩展,使得其能够根据不同的Slice-ID分配不同的切片SID。基于Slice-ID对SR资源进行切片SID分配后,对应的信息将通过IGP在整个路由域内进行泛洪。
在一个可选的实施方式中,网络上的其它设备接收上述通告的携带了Slice-ID字段的拓扑信息,将在其专属的切片网络资源基础上,使用业务关联的算法计算得到对应的SR MPLS标签路径转发信息,继而为灵活指定不同业务在不同逻辑拓扑中进行转发提供基础。
在一个可选的实施方式中,设备可以基于不同的切片Slice-ID为前缀、三层链路以及二层成员接口分别指定SID,用于在不同的网络切片进行SR资源标识。
在一个可选的实施方式中,每个SID将唯一关联一个Slice-ID。具有相同Slice-ID的Prefix-SID、Adj-SID以及L2 Bundle Member Adj-SID属于同一个网络切片。分配好的SID以及其对应的Slice-ID信息将下发至设备的本地标签转发表中,建立入标签映射(Incoming Label Map,简称ILM)表项,用于关联业务与本地硬件资源,并指导业务流量的本地转发。
在一个可选的实施方式中,当上述描述的网络资源不分配Slice-ID时,则认为其处于缺省的切片中,此时可以认为前缀、三层链路、二层成员接口以及其所指定的SID没有对应的Slice-ID,或者Slice-ID为0。
在一个可选的实施方式中,IGP协议新增Prefix-SID通告方式,在对 应的通告方式中引入Slice-ID信息,其将随Prefix-SID一起在网络上进行泛洪。对于IS-IS协议,在进行路由重分配或者路由泄漏操作时,需要支持继承Slice-ID随Prefix-SID信息一起进行处理;对于OSPF协议,在进行路由重分配或者区域路由汇总时,同样需要支持继承Slice-ID随Prefix-SID信息一起进行处理。
在一个可选的实施方式中,当设备作为映射服务器(Mapping Server)通告一组或者多组前缀的Prefix-SID时,IGP协议将新增SRMS信息通告方式,在对应的通告方式中引入Slice-ID信息,并将其随SRMS信息一起在网络上进行泛洪。
在一个可选的实施方式中,IGP新增支持三层链路Adj-SID的通告方式,在对应的通告方式中引入Slice-ID信息,其将随三层链路的Adj-SID一起在网络上进行泛洪。
在一个可选的实施方式中,IGP新增支持L2 Bundle Member Adj-SID的通告方式,在对应的通告方式中引入Slice-ID信息,其将随L2 Bundle Member Adj-SID一起在网络上进行泛洪。
在一个可选的实施方式中,为了考虑兼容原有的SID通告方式,防止设备对SID信息解析错误,上述携带Slice-ID信息的SID可以考虑定义新的TLV进行携带,以区分当前协议定义的SID通告方式。
在一个可选的实施方式中,IGP支持接收处理上述相关所有的拓扑资源信息,并保存至拓扑信息库中用于路径计算。不同的业务指定关联的Slice-ID,用于标识转发流量期望所在的网络切片信息,并可以根据业务特点指定不同的路径计算方法,比如按照最短路径SPF进行算路,或者是基于流量工程拓扑数据库(Traffic Engineering Databse,简称TEDB)按照某个策略进行CSPF算路,比如沿着最短时延的路径进行转发、或者沿着最大带宽的链路进行转发等。
在一个可选的实施方式中,IGP基于本地设备支持的网络切片进行拓扑算路,本地设备不支持的网络切片不进行拓扑计算。
在一个可选的实施方式中,为某个业务在对应的网络切片中进行算路时,其仅使用具有相同Slice-ID的拓扑资源进行计算,如果前缀或者链路对应的Slice-ID信息不同,则不能够参与到路径计算中。进行路径计算时,如果IGP通告了三层链路的成员接口信息,则相关信息也可以参与到路径计算中,但也必须具有相同的Slice-ID;IGP进行SR-BE计算时,对于远端设备通告的前缀,基于某个网络切片计算可达后,其在下发该前缀前向纠错码(Forward Error Correction,简称FEC)所对应的SR MPLS标签时,入标签和出标签采用的为该网络切片Slice-ID所对应的Prefix-SID,且对应的Slice-ID也将作为下发字段通告至转发面。
在一个可选的实施方式中,IGP基于某个网络切片进行算路,对于某个可达前缀,如果其直连下一跳为包含二层成员接口的三层链路,比如FlexE接口,且FlexE接口下的二层成员接口也关联了可选地Slice-ID信息;则可选地转发下一跳可以关联到具有相同Slice-ID的二层成员接口。
在一个可选的实施方式中,IGP基于TEDB,为某个网络切片进行CSPF算路时,根据计算得到的显式路径迭代可选地SID List时,采用的用于标识节点的Prefix-SID,标识链路的Adj-SID,以及标识二层成员接口的L2 Bundle Member Adj-SID,都必须是该网络切片所对应的SID信息,对应的Slice-ID也将作为下发字段通告至转发面。
下面对路由各个协议具体实施方式进行说明。
具体实施方式一
本实施例如图3所示,其介绍了网络上不同的三层链路关联不同网络切片时的SR-BE计算方式;在图3所示的SR MPLS网络中,节点PE1、PE2、P3、P4分别使能IGP协议以及SR功能,所有设备配置相同的SR全局块(SR Global Block,简称SRGB),范围为[100,200];网络中配置两个虚拟专用网络(Virtual Private Network,简称VPN)业务,分别为VPN_A和VPN_B。为了实现不同的VPN业务分别在不同的网络切片中按需转发的目的,需要按照如下步骤进行操作,假设划分的两个网络切片 分别对应Slice-ID 1和Slice-ID 2:
步骤1、将两个VPN业务关联至对应的切片中,其中VPN_A关联Slice-ID 1,VPN_B关联Slice-ID 2;且设置VPN_A和VPN_B业务转发路径使用SR-BE方式进行计算;
步骤2、配置三层链路Link1、Link2归属切片1,对应Slice-ID 1;配置三层链路Link3,Link4归属切片2,对应Slice-ID 2;对于P2设备通告的前缀Prefix_2,为其分配两个Prefix-SID分别对应Slice-ID 1和Slice-ID 2,index为1和2,并为其创建信息生命周期管理(Information Lifecycle Management,简称ILM)表项,分别为:
FEC:Prefix_2,Slice-ID:1,入标签:101,操作:POP
FEC:Prefix_2,Slice-ID:2,入标签:102,操作:POP
步骤3、网络上设备的IGP协议将配置的链路切片信息以及为前缀分配的不同切片的Prefix-SID信息在全网进行泛洪转发,可选地通告方式将在下面的实施例中进行说明;
步骤4、入口(ingress)设备PE1接收到IGP泛洪的信息,将其链路所属的Slice-ID,前缀分配的不同Prefix-SID信息保存至本地的拓扑数据库中。本设备支持Slice-ID 1和2两个切片,所以PE1尝试为Slice-ID 1和Slice-ID 2进行路径计算,由于VPN1和VPN2定义的路径计算方式为默认的SR-BE方式,所以设备将基于SPF进行拓扑的最短路径计算。对于Slice-ID 1进行路径计算时,仅采用Slice-ID为1的链路,即Link1和Link2,经计算其转发路径为PE1-P3-PE2;同理,对Slice-ID 2进行路径计算,仅采用Slice-ID为2的链路,即Link3和Link4,经计算其转发路径为PE1-P4-PE2。
对于前缀Prefix_2,其在不同网络切片中,下一跳转发信息不同,分配的Prefix-SID也不同,因此需要分别将其对应的切片转发信息下发至转发表项中,如下所示:
FEC:Prefix_2,Slice-ID:1
出标签:101,下一跳:Link1,操作:PUSH
FEC:Prefix_2,Slice-ID:2
出标签:102,下一跳:Link3,操作:PUSH
当VPN_A的业务流量到达设备PE1时,其根据配置迭代查找至<FEC:Prefix_2,Slice-ID:1>的转发表项,流量封装上MPLS标签101,关联对应的Slice-ID 1的转发传统单层网络(underlay)资源,从接口Link1转发出去;同样地,当VPN_B的业务流量到达设备PE1时,其根据配置迭代查找至<FEC:Prefix_2,Slice-ID:2>的转发表项,流量封装上MPLS标签102,关联对应的Slice-ID 2的转发传统单层网络(underlay)资源,将其从接口Link3转发出去;
步骤5、P3设备上重复上述步骤4类似的计算操作,由于P3仅支持Slice-ID 1,所以其仅基于Slice-ID 1的链路进行SR-BE算路,计算得到的SR标签转发表项也仅基于Slice-ID 1,具体表项如下所示:
FEC:Prefix_2,Slice-ID:1
入标签:101,出标签:101
下一跳:Link3
操作:SWAP
当封装了MPLS标签101的流量转发至设备P3时,根据入标签101,匹配到上述<FEC:Prefix_2,Slice-ID:2>的转发表项,确定对应的转发传统单层网络(underlay)硬件资源,进行标签交换操作,交换为101,然后将报文从接口Link3转发出去。
步骤6、P4设备上的操作类似步骤5,此处不再详述。
具体实施方式二
本实施例如图4所示,其介绍了网络上三层链路的二层成员接口关联不同网络切片时的SR-BE计算方式;在图4所示的SR MPLS网络中,节 点PE1、PE2、P3的配置和实施例1的配置相同,两个网络切片分别对应Slice-ID 1和Slice-ID 2,且Link1和Link2同时属于两个网络切片,该实施例与上述实施例不同的地方主要在于P3设备的SR-BE计算方式。
对于P3设备,其设置三层链路Link2中的两个二层成员端口subif1属于网络切片Slice-ID 1,subif2属于网络切片Slice-ID 2;
P3设备基于网络切片Slice-ID 1计算SR-BE转发路径时,其根据SPF计算得到前缀Prefix_2的转发下一跳为Link2,且由于Link2的成员端口subif1属于网络切片Slice-ID 1,则实际转发使用的下一跳则为subif1,其SR-MPLS的转发表项为:
FEC:Prefix_2,Slice-ID:1
入标签:101,出标签:101
下一跳:subif1
操作:SWAP
同样基于网络切片Slice-ID 2为Prefix_2计算SR-BE转发路径时,由于Link2的成员端口subif2属于网络切片Slice-ID 2,则实际转发使用的下一跳即为subif2,其SR-MPLS的转发表项为:
FEC:Prefix_2,Slice-ID:2
入标签:102,出标签:102
下一跳:subif2
操作:SWAP
具体实施方式三
本实施例如图5所示,其介绍了设备基于不同网络切片进行SR-TE算路的方法;在图5所示的SR MPLS网络中,节点PE1、PE2、P3、P4分别使能IGP协议以及SR功能;网络划分两个网络切片分别对应Slice-ID 1和Slice-ID 2;配置两个VPN业务:VPN_A和VPN_B
其分别关联Slice-ID 1和Slice-ID 2,且设置VPN_A和VPN_B业务转发路径使用基于某个策略(比如最短时延)的CSPF方式进行计算;
步骤1、配置三层链路Link1归属切片1,对应Slice-ID 1,分配Adj-SID为1001;配置三层链路Link3、Link4归属切片2,对应Slice-ID 2,分别分配Adj-SID 3002、4002;其中三层链路Link2下有两个二层成员接口subif1和subif2,其分别属于切片1和切片2,分配的Adj-SID为2001和2002,对于每个Adj-SID,设备为其创建ILM表项,如下所示:
设备PE1:
入标签:1001,Slice-ID:1,下一跳:Link1,操作:POP
入标签:3002,Slice-ID:2,下一跳:Link3,操作:POP
设备P3:
入标签:2001,Slice-ID:1,下一跳:subif1,操作:POP
入标签:2002,Slice-ID:2,下一跳:subif2,操作:POP
设备P4:
入标签:4002,Slice-ID:2,下一跳:Link4,操作:POP
步骤2、网络上设备的IGP协议将配置的链路切片信息以及不同切片的Adj-SID信息在全网进行泛洪转发,可选地通告方式将在后面的实施例中进行说明;
步骤3、入口(ingress)设备PE1接收到IGP泛洪的信息,将其链路所属的Slice-ID,以及分配的不同Adj-SID信息保存至本地的拓扑数据库中。由于本设备支持Slice-ID 1和2两个切片,所以PE1尝试为Slice-ID 1和Slice-ID 2进行路径计算,由于VPN_A和VPN_B定义的路径计算方式为SR-TE方式,所以设备将基于CSPF进行路径计算。经计算,VPN_A的转发路径PE1-Link1-P3-subif1-PE2;VPN_B转发路径为PE1-Link3-P4-Link4-P3-subif2-PE2;并将计算出来的路径使用Adj-SID迭代转换为对应的SID List,对于VPN_A,其转发SID List A为[1001,2001], VPN_B的转发SID List B为[3002,4002,2002];
步骤4、当VPN_A的业务流量到达设备PE1时,其根据配置迭代查找到转发表项SID List A,流量封装上对应的SID List,并根据其最外层标签1001查找本地的ILM表项,将外层标签POP,并根据其对应的Slice-ID信息关联传统单层网络(underlay)转发资源,将报文从接口Link1转发至节点P3;P3同样根据流量的最外层标签查找本地的ILM表项,确定转发Slice-ID关联的传统单层网络(underlay)转发资源并完成流量的转发;直至流量到达目的节点。
步骤5、当VPN_B的业务流量到达设备PE1时,其流程与步骤4类似,此处不再详述。
在本申请的实施例中示意出了一个IS-IS协议基于Slice-ID的Prefix-ID通告方式,考虑设备兼容问题,新增Slice Prefix-SID sub-TLV格式,如图6所示,新的Prefix-SID sub-TLV增加了Slice-ID字段信息的通告,该信息用于标识该Prefix-SID对应的Slice-ID信息。
在本申请的实施例中示意出了一个IS-IS协议基于Slice-ID通告SID/Label Binding信息的方式,考虑设备兼容问题,新增Slice SID/Label Binding TLV格式,如图7所示,相比国际互联网工程任务组(The internet Engineering Task Force,简称IETF)定义的SID/Label Binding TLV,其增加Slice-ID字段,用于标识SID/Label Binding通告的Prefix-SID所对应的Slice-ID信息。
在本申请的实施例中示意出了一个IS-IS协议基于Slice-ID的Adj-ID通告方式,考虑设备兼容问题,新增Slice Adj-SID sub-TLV和Slice LAN Adj-SID格式,如图8和图9所示,两种新的sub-TLV增加了Slice-ID字段信息的通告,该信息用于标识该Adj-SID对应的Slice-ID信息。
在本申请的实施例中示意出了一个IS-IS协议基于Slice-ID的L2 Bundle Member Adj-ID通告方式,考虑设备兼容问题,新增Slice L2 Bundle  Member Adj-SID sub-TLV和Slice L2 Bundle Member LAN Adj-SID格式,其格式与图8和图9所示基本一样,两种新的sub-TLV增加了Slice-ID字段信息的通告,该信息用于标识该Adj-SID对应的Slice-ID信息。
在本申请的实施例中示意出了一个OSPF协议基于Slice-ID的Prefix-ID通告方式,考虑设备兼容问题,新增Slice Prefix-SID sub-TLV格式,如图10所示,新的Prefix-SID sub-TLV增加了Slice-ID字段信息的通告,该信息用于标识该Prefix-SID对应的Slice-ID信息。
在本申请的实施例中示意出了一个OSPF协议基于Slice-ID通告Extended Prefix Range信息的方式,考虑设备兼容问题,新增Slice Extended Prefix Range TLV格式,如图11所示,相比IETF定义的Extended Prefix Range TLV,其增加Slice-ID字段,用于标识通告的Prefix-SID所对应的Slice-ID信息。
在本申请的实施例中示意出了一个OSPF协议基于Slice-ID的Adj-ID通告方式,考虑设备兼容问题,新增Slice Adj-SID sub-TLV和Slice LAN Adj-SID格式,如图12和图13所示,两种新的sub-TLV增加了Slice-ID字段信息的通告,该信息用于标识该Adj-SID对应的Slice-ID信息。
本申请的实施例还提供了一种网络设备,图2是根据本申请实施例的网络设备的结构框图,如图2所示,网络设备包括存储器202和处理器204,其特征在于,存储器中存储有计算机程序,处理器被设置为运行计算机程序以执行:根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,其中,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资源所关联的网络切片与业务数据所属的网络切片相匹配;根据转发路径对业务数据进行转发。
通过本申请的实施例,由于可以根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资 源所关联的网络切片与业务数据所属的网络切片相匹配;根据转发路径对业务数据进行转发。因此,可以解决相关技术中网络切片业务数据无法在承载网中转发的问题,达到不同业务数据可以按照其对应的网络切片资源进行转发的效果。
需要说明的是,存储器202可用于存储计算机程序,例如,应用软件的软件程序以及模块,如本申请实施例中的业务数据的转发方法对应的计算机程序,处理器204通过运行存储在存储器202内的计算机程序,从而执行各种功能应用以及数据处理,即实现上述的方法。存储器202可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。
在一个实施方式中,网络设备根据网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,包括:根据链路资源配置信息确定业务数据的转发路径,其中,被确定的转发路径上的每个链路所关联的网络切片与业务数据所属的网络切片相同,网络资源配置信息包括链路资源配置信息,链路资源配置信息表征了指定网路中的链路所关联的网络切片。
在一个实施方式中,网络设备根据链路资源配置信息确定业务数据的转发路径,还包括:根据链路资源配置信息确定业务数据的下一跳链路;或者,根据链路资源配置信息通过预设的算法确定将业务数据转发至目的节点的转发路径,其中,转发路径包括多条链路。
在一个实施方式中,网络设备根据网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,包括:根据链路成员接口配置信息确定转发路径上转发业务数据的链路的成员接口,其中,转发业务数据的链路的成员接口所关联的网路切片与业务数据所属的网路切片相同,链路资源配置信息中包括链路成员接口配置信息,链路成员接口配置信息表征了指定网络中的链路的成员接口所关联的网络切片。
在一个实施方式中,网络设备根据网络资源配置信息和业务数据所属 的网络切片确定业务数据的转发路径,还包括:根据网络节点配置信息确定业务数据的转发路径,其中,被确定的转发路径上的每个网络节点所关联的网络切片与业务数据所属的网络切片相同,网络资源配置信息包括网络节点配置信息,网络节点配置信息表征了指定网路中的网络节点所关联的网络切片。
在一个实施方式中,网络设备根据转发路径对业务数据进行转发,包括:将转发路径的信息封装在业务数据上,根据封装的转发路径的信息对业务数据进行转发。在一个实施方式中,在根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径之前,包括:接收网络资源配置信息,其中,网络资源配置信息被通告给指定网络中的网络节点。
在一个实施方式中,网络资源配置信息中包括指定网络的网络资源所关联的一个或多个网络切片标识。
本申请的实施例还提供了一种网络系统,包括上述任一项的网络设备。
本申请的实施例还提供了一种存储介质,该存储介质中存储有计算机程序,其中,该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在本实施例中,上述存储介质可以包括但不限于:U盘、只读存储器(Read-Only Memory,简称为ROM)、随机存取存储器(Random Access Memory,简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
显然,本领域的技术人员应该明白,上述的本申请实施例的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出 或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本申请实施例不限制于任何特定的硬件和软件结合。
以上仅为本申请的可选地实施例而已,并不用于限制本申请实施例,对于本领域的技术人员来说,本申请实施例可以有各种更改和变化。凡在本申请实施例的原则之内,所作的任何修改、等同替换、改进等,均应包含在本申请实施例的保护范围之内。
工业实用性
在本申请实施例中,由于网络设备可以根据指定网络的网络资源配置信息和业务数据所属的网络切片确定业务数据的转发路径,网络资源配置信息表征了指定网络的网络资源所关联的网络切片,被确定的转发路径的网络资源所关联的网络切片与业务数据所属的网络切片相匹配;网络设备根据转发路径对业务数据进行转发。因此,可以解决相关技术中网络切片业务数据无法在承载网中转发的问题,达到不同业务数据可以按照其对应的网络切片资源进行转发的效果。

Claims (16)

  1. 一种业务数据的转发方法,所述业务数据在指定网络中转发,包括:
    网络设备根据所述指定网络的网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,其中,所述网络资源配置信息表征了所述指定网络的网络资源所关联的网络切片,被确定的所述转发路径的网络资源所关联的网络切片与所述业务数据所属的网络切片相匹配;
    网络设备根据所述转发路径对所述业务数据进行转发。
  2. 根据权利要求1所述的方法,其中,网络设备根据所述网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,包括:
    网络设备根据链路资源配置信息确定所述业务数据的转发路径,其中,被确定的所述转发路径上的每个链路所关联的网络切片与所述业务数据所属的网络切片相同,所述网络资源配置信息包括所述链路资源配置信息,所述链路资源配置信息表征了所述指定网络中的链路所关联的网络切片。
  3. 根据权利要求2所述的方法,其中,网络设备根据所述链路资源配置信息确定所述业务数据的转发路径,包括:
    网络设备根据所述链路资源配置信息确定所述业务数据的下一跳链路;或者,
    网络设备根据所述链路资源配置信息通过预设的算法确定将所述业务数据转发至目的节点的转发路径,其中,所述转发路径包括多条链路。
  4. 根据权利要求2所述的方法,其中,网络设备根据所述网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,还包括:
    网络设备根据链路成员接口配置信息确定所述转发路径上转发所述业务数据的链路的成员接口,其中,转发所述业务数据的链路的成员接口所关联的网络切片与所述业务数据所属的网络切片相同,所述链路资源配置信息中包括所述链路成员接口配置信息,所述链路成员接口配置信息表征了所述指定网络中的链路的成员接口所关联的网络切片。
  5. 根据权利要求2所述的方法,其中,网络设备根据所述网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,还包括:
    网络设备根据网络节点配置信息确定所述业务数据的转发路径,其中,被确定的所述转发路径上的每个网络节点所关联的网络切片与所述业务数据所属的网络切片相同,所述网络资源配置信息包括所述网络节点配置信息,所述网络节点配置信息表征了所述指定网络中的网络节点所关联的网络切片。
  6. 根据权利要求1至5任一项所述的方法,其中,网络设备根据所述转发路径对所述业务数据进行转发,包括:
    网络设备将所述转发路径的信息封装在所述业务数据上,根据封装的所述转发路径的信息对所述业务数据进行转发。
  7. 根据权利要求1至5任一项所述的方法,其中,网络设备在根据所述指定网络的网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径之前,所述方法包括:
    网络设备接收所述网络资源配置信息,其中,所述网络资源配置信息被通告给所述指定网络中的网络节点。
  8. 根据权利要求1至5任一项所述的方法,其中,所述网络资源配置信息中包括所述指定网络的网络资源所关联的一个或多个网络切片标识。
  9. 一种网络设备,包括存储器和处理器,所述存储器中存储有 计算机程序,所述处理器被设置为运行所述计算机程序以执行:
    根据所述指定网络的网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,其中,所述网络资源配置信息表征了所述指定网络的网络资源所关联的网络切片,被确定的所述转发路径的网络资源所关联的网络切片与所述业务数据所属的网络切片相匹配;
    根据所述转发路径对所述业务数据进行转发。
  10. 根据权利要求9所述的网络设备,其中,根据所述网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,包括:
    根据链路资源配置信息确定所述业务数据的转发路径,其中,被确定的所述转发路径上的每个链路所关联的网络切片与所述业务数据所属的网络切片相同,所述网络资源配置信息包括所述链路资源配置信息,所述链路资源配置信息表征了所述指定网路中的链路所关联的网络切片。
  11. 根据权利要求10所述的网络设备,其中,根据所述链路资源配置信息确定所述业务数据的转发路径,还包括:
    根据所述链路资源配置信息确定所述业务数据的下一跳链路;或者,
    根据所述链路资源配置信息通过预设的算法确定将所述业务数据转发至目的节点的转发路径,其中,所述转发路径包括多条链路。
  12. 根据权利要求10所述的网络设备,其中,根据所述网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,包括:
    根据链路成员接口配置信息确定所述转发路径上转发所述业务数据的链路的成员接口,其中,转发所述业务数据的链路的成员接口所关联的网路切片与所述业务数据所属的网路切片相同,所述链路资源 配置信息中包括所述链路成员接口配置信息,所述链路成员接口配置信息表征了所述指定网络中的链路的成员接口所关联的网络切片。
  13. 根据权利要求10所述的网络设备,其中,根据所述网络资源配置信息和所述业务数据所属的网络切片确定所述业务数据的转发路径,还包括:
    根据网络节点配置信息确定所述业务数据的转发路径,其中,被确定的所述转发路径上的每个网络节点所关联的网络切片与所述业务数据所属的网络切片相同,所述网络资源配置信息包括所述网络节点配置信息,所述网络节点配置信息表征了所述指定网路中的网络节点所关联的网络切片。
  14. 根据权利要求9至13任一项所述的网络设备,其中,根据所述转发路径对所述业务数据进行转发,包括:
    将所述转发路径的信息封装在所述业务数据上,根据封装的所述转发路径的信息对所述业务数据进行转发。
  15. 一种网络系统,其中,包括如所述权利要求9至14任一项所述的网络设备。
  16. 一种存储介质,其中,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行所述权利要求1至8任一项中所述的方法。
PCT/CN2019/103177 2018-12-29 2019-08-29 一种业务数据的转发方法、网络设备及网络系统 WO2020134139A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/299,021 US11689452B2 (en) 2018-12-29 2019-08-29 Method for forwarding service data, network device, and network system
EP19906120.1A EP3905609A4 (en) 2018-12-29 2019-08-29 METHOD OF SERVICE DATA FORWARDING, NETWORK DEVICE AND NETWORK SYSTEM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811648145.7 2018-12-29
CN201811648145.7A CN111385207B (zh) 2018-12-29 2018-12-29 一种业务数据的转发方法、网络设备及网络系统

Publications (1)

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

Family

ID=71128536

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/103177 WO2020134139A1 (zh) 2018-12-29 2019-08-29 一种业务数据的转发方法、网络设备及网络系统

Country Status (4)

Country Link
US (1) US11689452B2 (zh)
EP (1) EP3905609A4 (zh)
CN (1) CN111385207B (zh)
WO (1) WO2020134139A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022152224A1 (zh) * 2021-01-18 2022-07-21 华为技术有限公司 路由消息处理方法、发布方法及装置、通信系统
EP4161002A4 (en) * 2020-07-06 2023-12-20 Huawei Technologies Co., Ltd. MESSAGE PROCESSING METHOD AND NETWORK DEVICE

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114124795A (zh) * 2019-04-15 2022-03-01 华为技术有限公司 一种基于SRv6的数据处理方法及相关网络设备
WO2021047321A1 (zh) * 2019-09-11 2021-03-18 华为技术有限公司 一种数据传输的控制方法及装置
CN113037527B (zh) * 2019-12-25 2024-04-09 中兴通讯股份有限公司 网络切片创建方法、报文转发方法及其装置
CN113055202A (zh) * 2019-12-26 2021-06-29 华为技术有限公司 传输数据报文的方法、装置及系统
CN112134801B (zh) * 2020-08-11 2022-02-15 中盈优创资讯科技有限公司 分段标识sid的处理方法、装置及各节点
CN114157600A (zh) * 2020-09-07 2022-03-08 华为技术有限公司 一种转发报文的方法、设备和系统
CN114268545A (zh) * 2020-09-15 2022-04-01 北京华为数字技术有限公司 业务报文的转发方法、sr策略的发送方法、设备及系统
CN112995030A (zh) * 2021-02-07 2021-06-18 中兴通讯股份有限公司 一种业务处理方法、装置、存储介质及电子装置
CN115190065A (zh) * 2021-03-22 2022-10-14 中兴通讯股份有限公司 路径获取方法、网元及计算机可读存储介质
CN115209482A (zh) * 2021-03-26 2022-10-18 中兴通讯股份有限公司 一种信息传输方法、装置、网络节点、控制器及存储介质
CN115442304A (zh) * 2021-06-04 2022-12-06 中国移动通信有限公司研究院 一种资源确定方法、转发设备、控制器、系统及介质
CN117135643A (zh) * 2022-05-18 2023-11-28 中国移动通信有限公司研究院 资源配置方法、装置及相关设备
CN118158169A (zh) * 2022-12-07 2024-06-07 中兴通讯股份有限公司 数据采集方法、网络设备、服务器、电子设备、介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103650437A (zh) * 2013-06-28 2014-03-19 华为技术有限公司 任播服务注册、实现方法及装置、交换设备和系统
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
CN107277883A (zh) * 2016-04-08 2017-10-20 电信科学技术研究院 在多网络切片的网络中路由消息的方法、设备及系统
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080008202A1 (en) * 2002-10-31 2008-01-10 Terrell William C Router with routing processors and methods for virtualization
US9137590B2 (en) * 2011-11-14 2015-09-15 Infinera Corporation OSPFTE extension to support GMPLS for flexible grid
US9461877B1 (en) * 2013-09-26 2016-10-04 Juniper Networks, Inc. Aggregating network resource allocation information and network resource configuration information
US9363141B1 (en) * 2013-09-30 2016-06-07 Emc Corporation System and method for partitioning a network
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
US10129894B2 (en) * 2016-03-04 2018-11-13 Huawei Technologies Co., Ltd. Systems and methods for performing traffic engineering through network slices
US10608928B2 (en) * 2016-08-05 2020-03-31 Huawei Technologies Co., Ltd. Service-based traffic forwarding in virtual networks
CN107872884A (zh) * 2016-09-26 2018-04-03 电信科学技术研究院 一种随机接入资源分配和随机接入方法、设备
CN107889169B (zh) * 2016-09-29 2021-09-03 华为技术有限公司 网络切片的建立方法和装置
CN108494474A (zh) * 2018-03-23 2018-09-04 烽火通信科技股份有限公司 利用oam报文实现业务叠加保护倒换的方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103650437A (zh) * 2013-06-28 2014-03-19 华为技术有限公司 任播服务注册、实现方法及装置、交换设备和系统
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
CN107277883A (zh) * 2016-04-08 2017-10-20 电信科学技术研究院 在多网络切片的网络中路由消息的方法、设备及系统
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3905609A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4161002A4 (en) * 2020-07-06 2023-12-20 Huawei Technologies Co., Ltd. MESSAGE PROCESSING METHOD AND NETWORK DEVICE
WO2022152224A1 (zh) * 2021-01-18 2022-07-21 华为技术有限公司 路由消息处理方法、发布方法及装置、通信系统

Also Published As

Publication number Publication date
CN111385207A (zh) 2020-07-07
CN111385207B (zh) 2022-08-19
EP3905609A4 (en) 2022-02-23
US20220045944A1 (en) 2022-02-10
US11689452B2 (en) 2023-06-27
EP3905609A1 (en) 2021-11-03

Similar Documents

Publication Publication Date Title
WO2020134139A1 (zh) 一种业务数据的转发方法、网络设备及网络系统
CN111385206B (zh) 报文转发的方法、网络系统、相关设备及计算机存储介质
CN110912795B (zh) 一种传输控制方法、节点、网络系统及存储介质
EP3200402B1 (en) Segment routing information obtainment method and segment routing network establishment method
US10880203B2 (en) Centralized segment routing dataplane based backup path validation
US10581733B2 (en) Methods and devices for constructing label and forwarding label packet
US8665887B2 (en) Number automatic routing method, updating method, withdrawing method, router and device
US11799772B2 (en) Support for multiple virtual networks over an underlay network topology
CN113452610B (zh) 跨城域网的无缝端到端分段路由的方法及区域边界路由器
EP3585012B1 (en) Dynamic tunnel reporting for path computation and traffic engineering within a computer network
US20210367883A1 (en) Bitmask route target in targeted distribution of information using a routing protocol
US11323371B1 (en) Micro SID packet processing with operations, administration, and management
CN112511423A (zh) 报文处理方法、边界设备和计算机可读介质
CN102474451B (zh) 连接内层和外层mpls标签
WO2023274083A1 (zh) 路由发布和转发报文的方法、装置、设备和存储介质
EP3913871B1 (en) Bitmask route target in targeted distribution of information using a routing protocol
EP3942748B1 (en) Seamless multipoint label distribution protocol (mldp) transport over a bit index explicit replication (bier) core
WO2023159975A1 (zh) 网络调度方法及网络设备、可读存储介质
WO2024007762A1 (zh) 一种路由发布方法、通信方法及装置
WO2023050981A1 (zh) 虚拟专用网络业务标识的分配方法、报文处理方法及装置
WO2022042610A1 (zh) 信息处理方法、网络控制器、节点及计算机可读存储介质
WO2014082430A1 (zh) 报文控制方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19906120

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2019906120

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2019906120

Country of ref document: EP

Effective date: 20210729