WO2024027378A1 - Procédé et appareil de transmission de données, et dispositif de réseau et support de stockage - Google Patents

Procédé et appareil de transmission de données, et dispositif de réseau et support de stockage Download PDF

Info

Publication number
WO2024027378A1
WO2024027378A1 PCT/CN2023/102953 CN2023102953W WO2024027378A1 WO 2024027378 A1 WO2024027378 A1 WO 2024027378A1 CN 2023102953 W CN2023102953 W CN 2023102953W WO 2024027378 A1 WO2024027378 A1 WO 2024027378A1
Authority
WO
WIPO (PCT)
Prior art keywords
srv6
indication information
bandwidth control
tenant
transmission service
Prior art date
Application number
PCT/CN2023/102953
Other languages
English (en)
Chinese (zh)
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 WO2024027378A1 publication Critical patent/WO2024027378A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing

Definitions

  • the present application relates to the field of communications, and in particular, to a data transmission method, device, network equipment and storage medium.
  • the operator's edge (English: Provider Edge, PE) device introduces the user's traffic to the operator's network-based network in accordance with the agreement between the operator and the user.
  • the Segment Routing over Internet Protocol version 6 (English: Segment Routing over Internet Protocol version 6, referred to as: SRv6) tunnel, the traffic is forwarded through the SRv6 tunnel.
  • the operator's network provides differentiated transmission capabilities to meet users' different needs for network transmission services (for example: path overhead requirements, delay requirements, bandwidth requirements, link jitter requirements, bit error requirements, fiber to be allocated (wavelength or time slot requirements, etc.), operators cannot operate different types of network transmission services in different ways based on SRv6 technology.
  • Embodiments of the present application provide a data transmission method, device, network equipment and storage medium, which can solve the problem that operators are unable to operate different types of network transmission services in different ways based on SRv6 technology.
  • a data transmission method is provided.
  • the data transmission method is applied to a first PE device.
  • the method includes: the first PE device obtains a first SRv6 message, and the first SRv6 message contains first indication information.
  • the first indication information is used to indicate the first transmission service type of the first tenant to the operator network.
  • the first PE device then processes the first SRv6 message according to the associated first bandwidth control policy indicated by the first indication information.
  • the operator can use the PE equipment in the operator's network to control the bandwidth of the tenant's transmission traffic using different transmission service types, thereby realizing the operator's billing operation for different transmission service types.
  • the manner in which the first SRv6 message carries the first indication information is not limited, so as to improve the format flexibility of the first SRv6 message carrying the first indication information, so that the first SRv6 message can be configured according to the scenario requirements.
  • the first indication information may be set in the IPv6 extension header of the IPv6 header of the first SRv6 message.
  • the outer destination IP address field of the first SRv6 message may be used to carry the first indication information.
  • the first bandwidth control policy may include a committed access rate (English: Committed Access Rate, referred to as: CAR), and the committed access rate may include a committed rate (English: Committed Information Rate, referred to as: CIR) and/or a peak rate (English: Peak Information Rate (PIR), that is, the first bandwidth control policy selects the processing method for the first SRv6 packet based on the committed rate and/or peak rate agreed between the first tenant and the operator, such as forwarding the packet or discarding the packet. .
  • CAR Committed Access Rate
  • CIR Committed Information Rate
  • PIR Peak Information Rate
  • the above-mentioned first indication information is an SRv6 segment identifier (English: segment id, abbreviation: SID).
  • the first indication information may be the first SRv6 SID assigned by the first PE device to the first tenant in a per-tenant-per-service manner, and the destination address field of the first SRv6 message carries the first SRv6 SID.
  • the per-tenant-per-service approach refers to allocating different SRv6SIDs to different transmission service types of different tenants.
  • the above-mentioned first indication information may also be a partial field of the first SRv6SID, such as a function (English: Function) field or an argument (English: Argument) field of the first SRv6SID.
  • the first PE device can also determine the first transmission path of the first SRv6 message according to the first indication information.
  • the first indication information is SRv6SID
  • the first PE device determines the first transmission service according to the SRv6SID. the first transmission path corresponding to the type, and then process the first SRv6 message according to the first transmission path.
  • the first PE device stores a corresponding relationship between the first indication information and the first bandwidth control policy, so that the first PE device determines the first SRv6 based on the first indication information carried in the first SRv6 message.
  • the first bandwidth control policy for packets.
  • the correlation between the first indication information and the first bandwidth control policy may be a direct correspondence or an indirect correspondence.
  • the first PE device determines the first bandwidth control policy based on the correspondence between the first indication information and the first bandwidth control policy.
  • the first PE device may also determine the first transmission service type based on the corresponding relationship between the first indication information and the first transmission service type, and then determine the first bandwidth based on the corresponding relationship between the first transmission service type and the first bandwidth control policy. Control Strategy.
  • the association relationship between the above-mentioned first indication information and the first bandwidth control policy is stored in the first PE device in the form of an association relationship table.
  • the association relationship table is the first PE device's first PE device before processing the tenant's business. configured in the device. For example, when the resources of the built-in access control list (English: Access Control Lists, ACL for short) of the first PE device are relatively sufficient, the first PE device can use the access control list as the association table.
  • the first PE device may use the local SID table or the forwarding information base table as the association table.
  • FIB Forward Information dataBase
  • RIB Routing Information dataBase
  • the first PE device when the first PE device stores an association table, after receiving the first SRv6 message, the first PE device determines the association table according to the first indication information carried in the first SRv6 message.
  • the first bandwidth control policy corresponding to the first transmission service type to which the first SRv6 message belongs is determined in the table. For example, the first PE device inputs the first indication information into the access control list, local segment identification SID table, forwarding information database table or routing information database table, and matches the first bandwidth policy corresponding to the first indication information. This ensures rapid matching between the first indication information and the first bandwidth policy, and improves packet forwarding and transmission efficiency.
  • the first PE device when the first PE device processes the first SRv6 message based on the first bandwidth control policy, it first determines the effective length of the first SRv6 message, and then uses the first SRv6 message based on the effective length of the first SRv6 message.
  • the bandwidth control policy controls the processing of the first SRv6 packet.
  • the embodiment of the present application does not limit the method of determining the effective length of the first SRv6.
  • the segment routing header (English: Segment Routing Header, SRH) of the first SRv6 message usually does not carry the data required by the tenant.
  • the first PE device strips off the segment routing header of the first SRv6 message to obtain the first
  • the payload of the SRv6 message is used as the effective length of the first SRv6 message, so that the first bandwidth control policy calculates the traffic used by the tenant to transmit the first SRv6 message based on the message content that is valid for the tenant, which improves Bandwidth control accuracy.
  • the first PE device uses the length of the first SRv6 message containing the segment routing header as the effective length of the first SRv6 message, which reduces the operation of stripping the segment routing header and ensures the overall efficiency of message transmission.
  • the first PE device discards the first SRv6 message when the value of the segment remaining (English: Segment Left, SL) of the first SRv6 message is greater than 1. When the remaining value of the segment is equal to 1, the first SRv6 message is forwarded.
  • the tenant's packets can be restricted from carrying, in addition to the SID used to indicate the bandwidth control policy, a SID used to indicate the destination customer premises equipment (English: Customer-premises equipment, CPE) of the packet, thereby reducing
  • the packet transmission overhead of the tenant prevents the tenant from sending packets with a long forwarding path to the first PE device and occupying additional user bandwidth quota.
  • the first PE device may also use different bandwidth control policies to process packets of different tenants.
  • the first PE device obtains the second SRv6 message, determines the second bandwidth control policy associated with the second instruction information according to the second indication information contained in the second SRv6 message, and processes the second SRv6 message.
  • the first PE The device provides different billing operation methods for different transmission type services of the same tenant. If the second tenant and the first tenant are different tenants, the second transmission service type and the first transmission service type are the same transmission service type, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies, then the first PE The device provides different billing operation methods for different transmission type services of the same tenant. If the second tenant and the first tenant are different tenants, the second transmission service type and the first transmission service type are the same transmission service type, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies, then the first PE For the same transmission service type, the equipment can provide different billing operation methods for different tenants.
  • a second aspect provides a data transmission device, which includes various modules for executing the data transmission method in the first aspect or any possible implementation of the first aspect.
  • the data transmission device described in the second aspect may be a terminal device or a network device, or may be a chip (system) or other component or component that can be installed in the terminal device or network device, or may include a terminal device.
  • Equipment or network equipment this application does not limit this.
  • a network device including a memory and a processor.
  • the memory is used to store instructions.
  • the processor executes the instructions, it is used to perform any of the possible designs in the first aspect. Operational steps of the data transfer method.
  • a computer-readable storage medium including: computer software instructions; when the computer software instructions are run in a processor, the method described in any possible implementation manner in the first aspect is executed.
  • a computer program product is provided.
  • the computer program product When the computer program product is run on a processor, it executes the method described in any possible implementation manner in the first aspect.
  • Figure 1 is a schematic diagram of the network framework involved in an application scenario provided by the embodiment of the present application.
  • Figure 2 is a schematic diagram of message processing when providing bearer services in an operator network provided by an embodiment of the present application
  • Figure 3 is a schematic structural diagram of a transmission network in an operator network provided by an embodiment of the present application.
  • Figure 4a is a schematic diagram of an SRv6 message 1 provided by an embodiment of the present application.
  • Figure 4b is a schematic diagram of a message 2 provided by the embodiment of the present application.
  • Figure 4c is a schematic diagram of a message 3 provided by the embodiment of the present application.
  • Figure 4d is a schematic diagram of an SRv6 message 4 provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a network framework involved in another application scenario provided by the embodiment of the present application.
  • Figure 6 is a schematic flow chart of a data transmission method provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a data transmission system provided by an embodiment of the present application.
  • a, b or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b and c can be single or multiple.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as “first” and “second” do not limit the number and execution order.
  • the "first” in the first message and the "second” in the second message are only used to distinguish different messages.
  • the first, second, etc. descriptions appearing in the embodiments of the present application are only for illustration and to distinguish the description objects, and there is no order. They do not represent special limitations on the number of devices in the embodiments of the present application, and cannot constitute a limitation of the present application. Any limitations of the embodiments.
  • a tenant's traffic is sent from one user-side device to another user-side device of the tenant, it needs to be forwarded through the operator's network, which provides bearer services for the tenant's traffic.
  • tenants and operator networks agree on transmission service types by signing contracts and other forms, and operator networks provide corresponding services to tenants according to the agreed transmission service types.
  • an SRv6 tunnel is established in the operator's network. After the tenant's traffic reaches the PE equipment of the operator's network, the PE equipment can introduce the traffic into the SRv6 tunnel corresponding to the pre-agreed transmission service type. The traffic can be forwarded through the SRv6 tunnel. This enables the operator network to provide tenants with services that comply with the pre-agreed transmission service type.
  • tenants require the operator network to provide different transmission service types for some traffic.
  • the above-mentioned operator network provides at least one bearer service method for the tenant's traffic according to the agreement.
  • the service is operated by transmitting traffic. For example, if an operator and a tenant sign a service agreement to determine the traffic limit for a certain transmission service type, the operation method corresponding to the transmission service type includes controlling the traffic of the tenant to access the bearer network so as not to exceed the traffic upper limit determined by the above service agreement. Avoid mutual congestion of bandwidth in the case of multi-tenants and multiple services.
  • Operators will provide at least one transmission service type to the same tenant or different tenants, and operators have different billing plans for different transmission service types. Operators need to use different billing operations for tenants using different transmission service types. Traffic is billed for operation. However, when the operator network uses the SRv6 tunnel to determine the tenant's transmission service type, it cannot conduct different charging operations for the traffic transmitted by the tenant using different transmission service types.
  • the PE equipment of the bearer network can obtain SRv6 messages including different indication information.
  • the different indication information is used to indicate the first transmission service of the first tenant to the operator network. type, and the PE device processes SRv6 messages according to the bandwidth control policy associated with the indication information.
  • the operator network provides tenants with different transmission service types, it can provide the transmission service type required by the tenant according to the instruction information to transmit SRv6 messages, and use the bandwidth control policy indicated by the instruction information to process the SRv6 messages.
  • Bandwidth control Therefore, the operator can control the bandwidth of the transmission traffic of tenants using different transmission service types, thereby realizing the operator's billing operation for different transmission service types.
  • transmission service types can be divided according to different quality of service (English: Quality of Service, QoS for short) requirements, such as path overhead requirements, delay requirements, bandwidth requirements, link jitter requirements, bit error requirements, and waiting requirements. Assigned fiber wavelength or time slot requirements.
  • QoS Quality of Service
  • the operator network can divide paths corresponding to different transmission service types based on different topologies, slicing, routing algorithms, and Differentiated Services Code Points (DSCP).
  • Bandwidth control policies include committed access rates, such as committed rate control, peak rate control, etc.
  • the operator network 10 may include: PE equipment 1, PE equipment 2, and transmission network 3.
  • PE equipment 1 is connected to the user-side equipment 11 of tenant 1 through interface 1, and through interface 2
  • the user-side equipment 21 of tenant 2 is connected, and PE equipment 1 is connected to PE equipment 2 through transmission network 3.
  • PE device 2 is connected to the user-side device 12 of tenant 1 through interface 3, and is connected to the user-side device 22 of combination 2 through interface 4.
  • the transmission network 3 may include one or more operator (English: Provider, abbreviated as: P) equipment (which may also be called core layer equipment).
  • P Operator
  • the embodiment of this application only takes PE equipment as an example for description.
  • operator network 10 can agree with tenant 1 on transmission service type 1 and establish SRv6 tunnel 1 that meets transmission service type 1.
  • This SRv6 tunnel 1 passes through PE equipment 1, transmission network 3 and PE equipment 2 in sequence.
  • User-side device 11 receives message 1 and sends message 1 from interface 1 to PE device 1;
  • PE device 1 receives message 1 from tenant 1 and forwards message 1 using SRv6 tunnel 1, for example,
  • PE device 1 Strip the segment routing header of message 1 and then encapsulate the transmission network header to obtain message 2.
  • PE device 2 receives message 2.
  • PE device 2 decapsulates message 2 and obtains message 3.
  • the schematic diagram can be seen in Figure 2; thus, PE device 2 sends message 3 from interface 3 to the user-side device 12 of tenant 1.
  • the operator network 10 provides tenant 1 with services corresponding to the pre-agreed transmission service type 1. If tenant 1 needs operator network 10 to provide transmission service type 2 services for traffic with certain characteristics, and transmission service type 2 is different from transmission service type 1, operator network 10 needs to agree with tenant 1 on transmission service type 2 and establish a transmission service type that meets the requirements of SRv6 tunnel 2 of service type 2 passes through PE device 1, transmission network 3 and PE device 2 in sequence.
  • the traffic includes, for example, message 1'.
  • user-side device 11 receives message 1' and sends message 1' from interface 1 to PE device 1; PE device 1 receives message 1',' from tenant 1.
  • the PE equipment in the operator network 10 and the user-side equipment of each tenant support SRv6.
  • the operator network 10 provides multiple different types of paths, such as: Label Switched Path (LSP) for forwarding based on Multi-Protocol Label Switching (MPLS). , IPv6 tunnel, SRv6 tunnel or optical fiber physical link. Different types of paths correspond to different transmission service types.
  • LSP Label Switched Path
  • MPLS Multi-Protocol Label Switching
  • IPv6 tunnel IPv6 tunnel
  • SRv6 tunnel or optical fiber physical link.
  • Different types of paths correspond to different transmission service types.
  • the transmission network 3 can also provide multiple different types of paths such as label switching paths, IPv6 tunnels, SRv6 tunnels or optical fiber physical links.
  • the network transmission header encapsulated by PE device 1 for message 1 or message 1' conforms to the protocol of the path provided by transmission network 3, such as IP header, IPv6 header, multi-protocol label switching (English: Multi-Protocol Label Switching, Abbreviation: MPLS) header, etc.
  • transmission network 3 includes PE equipment 3 and PE equipment 4.
  • PE equipment 1 is connected to PE equipment 2 through PE equipment 3 and PE equipment 4 respectively.
  • the path 1 included in transmission network 3 is PE equipment 1->PE.
  • path 2 is PE device 1—>PE equipment 4—>PE equipment 2.
  • Path 1 and path 2 are different types of paths in transmission network 3. For example, path 1 corresponds to transmission service type 1, and path 2 corresponds to transmission service type 2.
  • the operator network 10 is able to provide tenant 1 with services corresponding to the pre-agreed transmission service type 1 and transmission service type 2.
  • the operator network 10 cannot provide services for different transmission service types separately.
  • To perform billing operations that is, the operator network 10 cannot control the traffic sent and received by the tenant using different transmission service types to comply with the traffic range defined in the service agreement signed between the tenant and the operator.
  • the tenant's user-side equipment and the PE equipment connected to the operator network 10 can obtain the transmission service information.
  • the transmission service information is used to indicate bandwidth control policies corresponding to different indication information.
  • the PE device connected to the tenant's user-side device in the operator network 10 can configure relevant transmission service information for the tenant connected to the PE device, and send the transmission service information of each tenant to the tenant's user-side device. on the user side device.
  • the PE device sends transmission service information to the user-side device.
  • the PE device can directly send the transmission service information to the user-side device, or the PE device can indirectly send the transmission service information to the user-side device through the operator management equipment and business management equipment to which the PE equipment belongs. Send the transmission service information to the user-side device.
  • the operator management device or service management device can configure relevant transmission service information for the tenant, and send the transmission service information to the tenant's user-side equipment and the PE equipment connected to the tenant's user-side equipment.
  • the tenant's user-side device and the PE device connected to the user-side device can obtain relevant transmission service information through static configuration, as long as the same transmission service information indicates the same content. The following description takes the example of configuring relevant transmission service information on the PE device and sending the transmission service information directly to the user-side device.
  • the transmission service information may include the corresponding relationship between indication information, paths in the operator's network, and bandwidth control policies. Different paths meet different transmission service types, and different transmission service types correspond to different bandwidths. Control Strategy.
  • the transmission service information may include correspondence between indication information, transmission service type, and bandwidth control policy.
  • the indication information can be the IPv6 address in the exclusive IPv6 address set allocated to the tenant (which can also be called IPv6 address block or IPv6 network segment); it can also be based on the exclusive IPv6 address set allocated to the tenant, through Function The bandwidth control policy carried by the field or Argument field; it can also be a bandwidth control policy that is not related to the exclusive IPv6 address set assigned to the tenant.
  • the bandwidth control policy can be defined in the traffic-behavior object, and then the traffic-behavior object is associated with the indication information, thereby realizing the association between the bandwidth control policy and the indication information.
  • the PE device can also configure a corresponding bandwidth control policy for each indication information, or associate the bandwidth control policy with the indication information through other objects instead of the traffic-behavior object.
  • the PE equipment in the operator's network can parse the packets sent by the user-side device when the transmission service information is known, obtain the indication information, and determine the path and bandwidth control policy based on the transmission service type corresponding to the indication information. Based on the bandwidth The control policy encapsulates the SRv6 packet according to the determined path type and forwards it along the path. In this way, the operator network can provide the tenant's packets with the transmission service type required by the tenant, and perform bandwidth control on the traffic of different transmission service types, realizing the operator's planning of services of different transmission service types. Free operation.
  • PE device 1 can pre-configure the IPv6 address set for tenant 1: 2001:db8:A1::/48, and pre-configure the IPv6 address set for tenant 2: 2001:db8:A2::/48. .
  • the indication information is an IPv6 address in the tenant's IPv6 address set
  • the transmission service information includes indication information and transmission service type.
  • the transmission service information on PE device 1 may include:
  • a specific example of configuring the above transmission service information on PE device 1 can be:
  • the transmission service information on the PE device 1 can be sent to the user-side device of the corresponding tenant in an offline manner or in a protocol message.
  • the IPv6 address set configured on the above PE device 1 that needs to be advertised to each tenant can be sent through a protocol message (such as an intermediate system to intermediate system (English: Intermediate system to intermediate system, abbreviation: ISIS) message)
  • a protocol message such as an intermediate system to intermediate system (English: Intermediate system to intermediate system, abbreviation: ISIS) message
  • ISIS Intermediate system to intermediate system
  • the PE device 1 can send the above-mentioned transmission service information 1-3 to the user-side device 11, and send the transmission service information 4 and 5 to the user-side device 12.
  • the transmission service information in the PE device 1 also includes a bandwidth control policy associated with the indication information, such as the committed access rate (English: Committed Access Rate (CAR) bandwidth control information.
  • a bandwidth control policy associated with the indication information such as the committed access rate (English: Committed Access Rate (CAR) bandwidth control information.
  • a specific example of configuring the bandwidth control policy in the above transmission service information on PE device 1 can be:
  • the user-side device 11 can determine to fill in the SRv6 message 1 to be sent based on the transmission service information 1.
  • the destination IP address is IPv6 address 11 (that is, 2001:db8:A1::1).
  • PE device 1 When PE device 1 receives SRv6 message 1 including 2001:db8:A1::1 from interface 1 connected to tenant 1, it can use the destination IP address 2001:db8 of the SRv6 message 1 as shown in the above example 1: A1::1 determines the transmission service type 11 required for the SRv6 message 1, selects the path 1 with the smallest cost, and passes through PE device 1, PE device 3 and PE device 2 in sequence, and determines the SRv6 message based on the transmission service type 11.
  • transmission service type 11 corresponds to path 1
  • transmission service type 12 corresponds to path 2; or, for tenant 1
  • the paths determined by SRv6 packets of different transmission service types can pass through the same network device, but the path types are different.
  • transmission service type 11 and transmission service type 12 both correspond to path 1, but the path 1 corresponding to transmission service type 11 is For LSPs forwarded based on MPLS, path 1 corresponding to transmission service type 12 is an SRv6 tunnel.
  • the user-side device 12 can forward the service based on the transmission service type 22.
  • Information 5 confirm that the destination IP address in the SRv6 message 5 to be sent is IPv6 address 22 (that is, 2001:db8:A2::2).
  • PE device 1 When PE device 1 receives SRv6 packet 5 including 2001:db8:A2::2 from interface 2 connected to tenant 2, it can use the destination IP address 2001:db8:A2 of the SRv6 packet 5 as shown in the above example 2: :2 Determine that the transmission service type 22 required for the SRv6 message 5 is path 2 with the smallest link jitter, and the bandwidth control policy qt5 corresponding to the SRv6 message 5.
  • Path 2 passes through PE device 1, PE device 4 and PE device in sequence 2; Therefore, PE device 1 can process SRv6 message 5 according to path 2 corresponding to this transmission service type 22 to obtain message 6, and send message 6 to PE device 2 according to path 2 based on bandwidth control policy qt5, and then use PE device 2 processes the received message 6 to obtain SRv6 message 7, and sends SRv6 message 7 from interface 4 to user-side device 22.
  • SRv6 message 1 and SRv6 message 5 can also specify the destination address of the user-side device in the SID list of SRH.
  • SRv6 message 1 can also include the address of user-side device 12.
  • the SRv6 message 5 may also include the address of the user-side device 22 .
  • the address of the user-side device can be carried in the segment identifier list (English: Segment Identifier list, abbreviation: SID list) field of the segment routing header in the SRv6 message.
  • the user-side device 12 may be a destination host, a user edge device, or a user premises device.
  • the destination address of the user-side device specified in the SRv6 message 1 may be the address of the CE device or CPE, for example, it may be a 128-bit SRv6 SID, or it may be A compressed SRv6 SID or IPv6 address less than 128 bits, for example, it can be compressed using draft-cl-spring-generalized-srv6-for-cmpr-03; if the user-side device 12 is the destination host, then the SRv6 report
  • the destination address of the user-side device specified in Document 1 may be the address of the destination host, for example, it may be the IPv6 address of the destination host.
  • the host 11 can generate an SRv6 message as shown in Figure 4a for service 1.
  • 1 (actually a native (English: native) IPv6 message with SRH added as an IPv6 extension header).
  • SRv6 message 1 uses the non-simplified (English: reduced) SRH message encapsulation method, and when the destination address in the IPv6 header of SRv6 message 1 is 2001:db8:A1::1, SRH The SID list does not need to include 2001:db8:A1::1.
  • This method is called the reduced SRH packet encapsulation method.
  • the embodiment of this application takes an SRv6 packet in the non-reduced SRH packet encapsulation mode as an example for explanation.
  • PE device 1 determines the transmission service type 11 and bandwidth control policy qt1 corresponding to message 1 based on the destination IP address field in message 1.
  • the message 2 processed by PE device 1 can be seen in Figure 4b.
  • this message 2 also adds the MPLS label stack corresponding to path 1 that meets the transmission service type 11.
  • the above MPLS label stack is that PE device 1 searches the routing table entry to determine that the next hop to host 12 is PE device 3, and determines that path 1 between PE device 1 and PE device 2 that meets the transmission service type 11 is forwarded based on MPLS. LSP, thereby obtaining the MPLS label stack corresponding to path 1.
  • PE device 1 forwards message 2 to PE device 2 through path 1 based on the MPLS label stack of message 2 in a forwarding manner that complies with bandwidth control policy qt1.
  • PE device 2 receives message 3 corresponding to message 2.
  • the difference compared with Figure 4b is that the MPLS label stack only includes the MPLS label of PE device 2.
  • PE device 2 can peel off the MPLS label of PE device 2 (that is, peel off the MPLS label stack) Obtain SRv6 message 4, as shown in Figure 4d.
  • This SRv6 message 4 includes an IPv6 header, SRH and payload.
  • the SL field 0, and the SID list includes the address of host 12 and 2001:db8:A1::1.
  • PE device 2 can send the SRv6 message 4 to host 12.
  • host 11 can be directly connected to PE device 1, or can be connected to PE device 1 through other network devices such as switches or routers.
  • host 11 is connected to PE device 1 through other network devices, then other networks The device only performs IPv6 forwarding processing on SRv6 message 1 without changing the destination address and SRH of the SRv6 message 1.
  • host 12 can be directly connected to PE device 2, or can be connected to PE device 2 through other network devices. If host 12 is connected to PE device 2 through other network devices, then other network devices will only forward SRv6 packet 4 through IPv6. to the host 12 for processing without changing the destination address and SRH of the SRv6 message 4.
  • the remaining value in the segment routing header of the packets shown in Figure 4b, Figure 4c and Figure 4d is 0, and the segment routing header can be stripped off, that is, the packets shown in Figure 4b, Figure 4c and Figure 4d
  • the document may not contain a segment routing header.
  • the segment routing header may be stripped when message 2, message 3 or message 4 is generated.
  • the operator network may refer to the service provider network, and the tenant may be an individual tenant.
  • the service provider network for enterprise tenants, not only the service provider network can be used, but also the virtual private cloud (English: Virtual Private Cloud, VPC for short) service provided by the cloud provider.
  • VPC Virtual Private Cloud
  • the scenario shown in Figure 5 includes the campus network 20 of Enterprise , the operator network 31 includes PE equipment 31 and PE equipment 31', the operator network 32 includes PE equipment 32 and PE equipment 32', and the cloud provider network 40 may include an access point (English: Point of Presence, abbreviation: PoP) 41.
  • the host 21 is connected to the CPE 23 through the switch 22.
  • the CPE 23 is connected to the operator network 31 and the operator network 32 through the PE equipment 31 and PE equipment 32 respectively.
  • the operator network 31 is connected to the cloud provider network 40 through the PE equipment 31'.
  • PoP 41 the operator network 32 is connected to the PoP 41 of the cloud provider network 40 through the PE device 32', and the PoP 41 is connected to the server 43 through the server 42.
  • the server 42 can be regarded as a cloud PE device
  • the server 43 can be regarded as a cloud CE device.
  • the cloud provider network 40 can provide VPC services for enterprise X.
  • the devices in the cloud provider network 40 can be virtualized into virtual hosts, switches, routers, gateways, etc.
  • the server 42 is virtualized into a virtual gateway (English: Virtual Gateway, abbreviation: VGW) and a virtual router rt0
  • the server 43 is virtualized into a virtual switch (English: Virtual Switch, abbreviation: VSW) and a virtual machine (English: Virtual Machine, abbreviation: VM) .
  • VM can be regarded as a virtual host
  • VGW can be regarded as a virtual CPE.
  • enterprise X it can be considered that it has an end-to-end connection from the host 21 to the VM.
  • the carrier network 31 and the carrier network provide corresponding services for enterprise X to transmit traffic between the campus network 20 and VPC services. From the perspective of enterprise For the virtual router rt1-rt4. For operators In addition to the tenant Enterprise X, the network 31 and the operator network 32 may also include other individual and enterprise tenants, which are not limited in the embodiment of this application.
  • this scenario may also include: the operator management device 31" of the operator network 31, the operator management device 32" of the operator network 32, and the cloud management device 40 of the cloud provider network 40, where,
  • the operator management device 31" is used to manage and control the equipment in the operator network 31, and is also used to provide a management interface to enterprise X through the Web portal; similarly, the operator management equipment 32" is used to manage and control the equipment in the operator network 32, It is also used to provide a management interface to Enterprise
  • This scenario may also include a service management device (or service orchestrator) 20.
  • the service management device 20 is used to manage and control its own physical devices (such as host 21, switch 22 or CPE 23); on the other hand, The service management device 20 is used to manage virtual routers rt1-rt4 through the management interface provided by the operator management device; on the other hand, the service management device 20 is used to manage VM, VSW, rt0 and rt0 through the management interface provided by the cloud management device 40. VGW.
  • the operator network 31 configures three IPv6 addresses for enterprise X.
  • the corresponding transmission service information may include:
  • the transmission service information of the operator network 31 for enterprise X also includes the bandwidth control policy:
  • operator network 32 configures two IPv6 addresses for enterprise X, and the corresponding transmission service information can be:
  • the transmission service information of the operator network 32 for enterprise X also includes the bandwidth control policy:
  • the transmission service information may be statically configured on the operator management device 31" and the operator management device 32" or obtained from the PE equipment in the corresponding operator network. Then, the service management device 20 may obtain the information from the operator management device 31" and the operator management device 32". The device 31" and the operator management device 32" obtain the transmission service information and send the transmission service information to the host 21 and/or CPE 23 in the campus network 10.
  • the service management device 20 can obtain the transmission service information from the operator management device 31" and the operator management device 32" obtain the transmission service information, and send the transmission service information to the VM and/or VGW in the cloud provider network 40; alternatively, the service management device 20 can obtain the transmission service information from the operator management device 31" and the operator The management device 32" obtains the transmission service information and sends the transmission service information to the VM and/or VGW through the cloud management device 40 of the cloud provider network 40.
  • the service management device 20 or the service management device 20 sends the corresponding transmission service information to the VM (or VGW) through the cloud management device 40, instructing the VM (or VGW) to encapsulate the transmission service information in the packet of the specific service. IPv6 address.
  • the cloud management device 40 can also deliver all transmission service information to the VM (or VGW), and the VM (or VGW) selects one of the transmission service types according to the actual needs of the business, and encapsulates the corresponding IPv6 address in the message. .
  • the service management device 20 can deliver corresponding transmission service information to the host 21 (or CPE 23) for a specific service, and instruct the host 21 (or CPE 23) to encapsulate the IPv6 in the transmission service information for the message of the specific service. address.
  • the service management device 20 can also deliver all transmission service information to the host 21 (or CPE 23), and the host 21 (or CPE 23) selects one of the transmission service types according to the actual needs of the business and encapsulates it in the message. The corresponding IPv6 address.
  • PE device 31 or PE device 32 When PE device 31 or PE device 32 receives the message sent by host 21, it determines the transmission service type and bandwidth control policy corresponding to the message according to the transmission service information, and determines the transmission service type and bandwidth control policy corresponding to the message in the path corresponding to the transmission service type according to the bandwidth control policy corresponding to the message. Forward the message.
  • enterprise tenants and cloud providers can independently select different transmission service types provided by the operator's network, and use bandwidth control policies corresponding to different transmission service types to control packet transmission, achieving Operators' billing operations for traffic of different transmission service types.
  • the granularity of selecting the transmission service type is not limited in the embodiments of this application.
  • the granularity of selecting the transmission service type can be selected for different services.
  • Different transmission service types can also be selected for different traffic types.
  • the PE device in the embodiment of this application may be a network device such as a switch, router, or firewall.
  • CE devices can be devices with private network access functions, such as switches, routers, Internet of Things (English: Internet of Things, abbreviated as: IoT) terminals, hosts and other devices.
  • IoT Internet of Things
  • the transmission service information in the embodiment of this application can be a set of correspondences between multiple pieces of information.
  • the transmission service information on the PE device can be: the tenant's identity, interface, indication information, and transmission service type. , the correspondence between paths and bandwidth control strategies.
  • the transmission service information may also include the correspondence between multiple sets of partial information.
  • the transmission service information on the PE device includes: the correspondence 1 between the indication information and the transmission service type, and the correspondence between the indication information and the path. Relationship 2, correspondence relationship 3 between tenant identification and interface, correspondence relationship 4 between tenant identification and indication information, and correspondence relationship 4 between transmission service type and bandwidth control policy.
  • the tenant's identifier is used to uniquely identify the tenant, for example, it may be the tenant's VPN identifier or the tenant's corresponding VNI. It should be noted that the specific embodiment of the transmission service information is not limited in the embodiments of this application, as long as it can ensure that the operator network provides the required services for tenants.
  • Figure 6 is a schematic flowchart of a data transmission method provided by an embodiment of the present application. This method is described with the interaction between the first user-side device of the first tenant and the first PE device.
  • the first user-side device in this method is the user-side device 11 in Figure 1
  • the first PE device can is PE equipment 1 in Figure 1
  • the first user-side equipment in this method is the host 21 or CPE 23 in Figure 5
  • the first PE equipment can be the PE equipment 31 or PE equipment 32 in Figure 5 ( Corresponding to rt3 or rt4 for enterprise '(Corresponding to rt1 or rt2 for enterprise X).
  • the method may include steps 601 to 604:
  • Step 601 The first user-side device of the first tenant obtains a first SRv6 message.
  • the first SRv6 message includes first indication information.
  • the first indication information is used to indicate the first transmission service of the first tenant to the operator network. type.
  • the first SRv6 message may be an SRv6-encapsulated message of the first tenant's service message, or may be a message generated (English: originating) by the first tenant's host.
  • the device that encapsulates the first tenant's service packets with SRv6 may be a network device such as a switch or router connected to the first tenant's host.
  • the first indication information in the first SRv6 message is the indication information determined by the first tenant according to the QoS requirements of the service packet to indicate the first bandwidth control policy of the operator network.
  • the first indication information is carried in In the first SRv6 message, the first PE device that receives the first SRv6 message can determine the first bandwidth control policy according to the first indication information, thereby enabling the operator to perform bandwidth control on traffic of different transmission service types.
  • the destination host of the first tenant or the CE device or CPE connected to the destination host that the first SRv6 packet reaches can be recorded as the second user-side device.
  • the second user-side device is connected to the operator network through the second PE device.
  • the second PE device is the egress node of the first SRv6 message in the operator's network, and the first PE device and the second PE device belong to the operator's network.
  • the first SRv6 message may include the address of the second user-side device, indicating that the first SRv6 message passes through or reaches the second user-side device.
  • the first transmission service type is used to indicate the transmission service to be provided by the first tenant for the operator's network to process the first SRv6 message.
  • different path types are set up between PE devices to meet the different transmission service needs of each tenant.
  • the path type and specific path used are used.
  • the path affects the services provided by the operator's network for tenants' SRv6 packets.
  • the paths between PE devices in the operator network may include but are not limited to: LSPs, IPv6 tunnels, SRv6 tunnels or physical links for forwarding based on MPLS.
  • Bearing technologies for physical links may include: link layer encapsulation based on a single physical link, link layer encapsulation based on the first wavelength or time slot of a single optical fiber physical link.
  • the first transmission service type may be, but is not limited to, transmission services with large path overhead, low-latency transmission services, large-bandwidth transmission services, low-link jitter transmission services, transmission services with few bit errors, and optical fiber wavelengths to be allocated. or time slot transmission service.
  • the first path that satisfies the first transmission service type may be, for example, LSP 1 for forwarding based on MPLS.
  • LSP 1 may be the path from PE device 1 to PE device 2 via PE device 3.
  • the first indication information may be any information that can be carried in the first SRv6 message and sensed and recognized by the first PE device.
  • the first indication information may be the first IPv6 address in the exclusive IPv6 address set allocated by the first PE device to the first tenant, and the first IPv6 address is used to carry the first indication information.
  • the IPv6 address set may be an IPv6 network segment allocated by the first PE device to the first tenant, such as 2001:db8:A1::/48.
  • the IPv6 address set may include multiple IPv6 addresses.
  • Each IPv6 address in the IPv6 address can correspond to a transmission service type of the first tenant. For example, the transmission service type corresponding to 2001:db8:A1::1 is the path with the minimum cost, and the transmission service type corresponding to 2001:db8:A1::2 The service type is the path with the smallest delay.
  • the first IPv6 address as a whole may carry the first indication information.
  • 2001:db8:A1::1 is the first indication information.
  • some fields in the first IPv6 address (such as the Function field or the Argument field) are used to carry the first indication information.
  • the value of the Function field is "1" This is the first instruction information.
  • the value of the outer destination IP address field in the first SRv6 message is the first IPv6 address.
  • the first PE device parses the first SRv6 message and obtains the value from its outer layer.
  • the first IPv6 address is obtained from the destination IP address field, so that the first transmission service type is determined according to the value of the first IPv6 address or the field used to carry the first indication information in the first IPv6 address.
  • the first indication information may also be set in the IPv6 extension header of the first SRv6 message.
  • both the first PE device and the first user-side device need to obtain transmission service information, where the transmission service information includes an association relationship between the indication information and the transmission service type.
  • the association between the indication information and the transmission service type may include, but is not limited to, the association between the first indication information and the first transmission service type.
  • the association between the first indication information and the first transmission service type can be configured on the first PE device, and the first PE device not only saves it locally
  • the association between the first indication information and the first transmission service type can also be sent directly or indirectly to the first user-side device in the form of an offline or protocol message. .
  • the association between the first indication information and the first transmission service type can also be configured on the operator management device. Then, the operator management device can send the association between the first indication information and the first transmission service type. To the first PE device, the association relationship between the first indication information and the first transmission service type may also be sent to the first user-side device through the service management device.
  • the specific form of the transmission service information stored locally by the first PE device is not limited, as long as the first PE device can determine based on the transmission service information stored locally and the first indication information in the first SRv6 message. It is sufficient to satisfy the first path of the first transmission service type corresponding to the first indication information, thereby providing services to the first tenant based on the first path.
  • Step 602 The first user-side device sends the first SRv6 message to the first PE device.
  • Step 603 The first PE device receives the first SRv6 message sent by the first user-side device belonging to the first tenant.
  • the first PE device can also save the matching relationship between each interface and the indication information. After receiving the SRv6 message, the first PE device can determine the interface that received the SRv6 message, thereby determining the interface and the indication in the SRv6 message. Whether the information satisfies the matching relationship. If so, it is considered that the SRv6 message needs to be processed, and the following step 604 is performed on the SRv6 message; otherwise, the SRv6 message is deemed not to meet the conditions for continued processing, and the SRv6 message is discarded. text, the following step 604 is not performed.
  • Step 604 The first PE device processes the first SRv6 message and obtains the second SRv6 message.
  • the first PE device decrements the value of the SL field by one, and updates the value of the outer destination IP address field in the IPv6 header according to the SID in the SID list indicated by the SL field.
  • Step 605 The first PE device selects the first path corresponding to the first transmission service type and forwards the second SRv6 message based on the first indication information and the first bandwidth control policy.
  • the first PE device can decrement the value of the SL field in the SRH of the first SRv6 message by one, so that the SID of the next hop of the first PE device is in the SID list indicated by the SL field; and, the first PE device will In the first SRv6 message, the value of the outer destination IP address field in the IPv6 header is updated. Specifically, the value of the outer destination IP address field in the IPv6 header can be updated according to the SID in the SID list indicated by SL in the SRH.
  • the first PE device may select a first path that satisfies the first transmission service type based on the first indication information, so as to correspondingly encapsulate the first SRv6 message according to the first path.
  • the first path is based on
  • the first SRv6 packet is encapsulated according to the first path, which may be based on the first SRv6 packet.
  • the MPLS label stack corresponding to the first path is encapsulated; for another example, the first path is an SRv6 tunnel.
  • encapsulating the first SRv6 message according to the first path may be based on the first SRv6 message and then performing SRv6 encapsulation; for another example, the first path is an IPv6 tunnel, then encapsulating the first SRv6 message according to the first path
  • the SRv6 message encapsulation may include encapsulating the IPv6 header corresponding to the first path based on the first SRv6 message.
  • the ingress node of the first path is the first PE device
  • the egress node of the first path is the second PE device
  • the destination host of the first SRv6 message accesses the operator network through the second PE device.
  • the first PE device stores an association relationship between the first indication information, the first transmission service type and the first bandwidth control policy.
  • Step 605 may include: the first PE device obtains the first indication information from the first SRv6 message, and searches for the first transmission service corresponding to the first indication information in the first SRv6 message from the locally saved association relationship. type, and determine the first path starting from the first PE device and meeting the first transmission service type in the operator network. Then, the first PE device saves the association from the local In the relationship, search for the first bandwidth control policy corresponding to the first indication information in the first SRv6 message. The first PE device then forwards the first SRv6 packet to the second PE device according to the first path based on the first bandwidth control policy.
  • the first PE device uses the access control list to store the bandwidth control policy.
  • Step 605 may include: the first PE device receives the first SRv6 message, the first PE device obtains the first indication information from the destination IP field of the first SRv6 message, and searches for the first indication information from the locally saved association relationship.
  • a first transmission service type corresponding to the first indication information in an SRv6 message, and a first path starting from the first PE device and meeting the first transmission service type is determined in the operator network.
  • the first PE device uses the access control list to match the first bandwidth control policy corresponding to the first indication information, and forwards the first SRv6 message to the second PE along the first path according to the traffic behavior of the first bandwidth control policy. equipment.
  • the above implementation requires the first PE device to have ACL resources. If the ACL resource specifications of the first PE device are larger, the indication information that can support the selection function of the bandwidth control policy stored in the first PE device in the above implementation is relatively large. many.
  • the first PE device uses a SID list, a routing information database table, or a forwarding information database table to store the bandwidth control policy.
  • Step 605 may include: the first PE device receives the first SRv6 message, the first PE device obtains the first indication information from the destination IP field of the first SRv6 message, and searches for the first indication information from the locally saved association relationship.
  • a first transmission service type corresponding to the first indication information in an SRv6 message, and a first path starting from the first PE device and meeting the first transmission service type is determined in the operator network.
  • the first PE device uses the SID list, routing information database table or forwarding information database table to match the first bandwidth control policy corresponding to the first indication information, and according to the traffic behavior of the first bandwidth control policy, follow the first path Forward the first SRv6 packet to the second PE device.
  • the above implementation requires that the first PE device has a SID list or FIB resource. If the SID list or FIB resource of the first PE device has a larger specification, then the first PE device in the above implementation can support the bandwidth control policy. There are more instructions for selecting functions.
  • the method provided by the embodiment of the present application can use the access control list, SID list, routing information database table or forwarding information database table as the association table for storing the association between the indication information and the bandwidth control policy, and can be based on the PE equipment.
  • ACL resources, SID list resources or FIB resources you can flexibly choose to use access control lists, SID lists, routing information base tables or forwarding information base tables to store bandwidth control policies corresponding to indication information, as well as indication information and bandwidth control. Strategy relationships.
  • the first PE device forwards the second SRv6 message based on the first bandwidth control policy.
  • the first PE device may determine the effective length of the first SRv6 message. If the effective length of the first SRv6 message meets the first bandwidth Control policy: Send the first SRv6 message to the next-hop device. If the effective length of the first SRv6 message does not comply with the first bandwidth control policy, discard the first SRv6 message.
  • the first method is to determine the effective length of the first SRv6 message.
  • the effective length of the first SRv6 message is the length of the message including the segment routing header.
  • the length of the first SRv6 message is 1500 bytes.
  • the transmission rate of the first SRv6 message is 416 packets per second (English: Packets per Second). , abbreviation: pps) and 500pps.
  • the second method is to determine the effective length of the first SRv6 message.
  • the effective length of the first SRv6 message is the length of the message with the segment routing header stripped off.
  • the length of the first SRv6 message is 1500 bytes, and the length of the message after stripping off the 24-byte segment routing header is 1476 bytes.
  • the transmission rates of the messages are 423pps and 508pps respectively.
  • the SRv6 SID in this embodiment can conform to the Delete On Demand style and the Only One Segment Left style.
  • Delete On Demand style means that when the PE device receives an SRv6 message whose outer destination IP address is SRv6SID and the next SID is the last SID in the SID list (the value of the SL field is 1), the PE device will The outer destination IP address of the message is updated to the last SID in the SID list, and the segment routing header will be stripped off.
  • the Only One Segment Left style means that the PE device only processes SRv6 packets with an SL field value equal to 1 and discards SRv6 packets with an SL field value greater than 1.
  • the tenant's first SRv6 message can be restricted to carry only an additional SID used to indicate the bandwidth control policy of the first SRv6 message to send messages on behalf of the tenant.
  • the SID of the destination device thereby preventing the tenant from sending packets with an SL field value greater than 1 to the first PE device, resulting in the inability to perform operations corresponding to the Delete On Demand style, and at the same time reducing the user's packet transmission overhead and avoiding occupying more tenants.
  • Bandwidth limit ensures the actual available bandwidth of tenants.
  • the first PE device processes the first SRv6 message of the first tenant.
  • the first PE device can also process packets of other tenants.
  • the first PE device obtains the SRv6 message, and the second indication information contained in the SRv6 message is used to indicate the second transmission service type of the second tenant, then the first PE device controls the bandwidth based on the second bandwidth associated with the second indication information.
  • the policy processes the second SRv6 packet.
  • the second tenant and the first tenant may be the same tenant or different tenants, the second transmission service type may be the same transmission service type or different transmission service types, and the second bandwidth control policy and the first bandwidth control policy may be different bandwidth control policies. Or the same bandwidth control policy, so that billing operations can be flexibly performed for different transmission services of different tenants.
  • FIG. 7 is a schematic structural diagram of a data transmission device 700 provided by an embodiment of the present application.
  • the data transmission device 700 is applied to the first user-side device belonging to the first tenant.
  • the device 700 may include: an acquisition module 701 and a forwarding module 702.
  • the device 700 can be used to perform the methods in the above embodiments, such as steps 601 to 605.
  • the acquisition module 701 is configured to acquire a first SRv6 message, where the first SRv6 message includes first indication information, and the first indication information indicates a first transmission service type of the first tenant to the operator network.
  • the forwarding module 702 is configured to process the first SRv6 message based on the first bandwidth control policy associated with the first indication information.
  • the destination address of the first SRv6 message is the first indication information.
  • the first indication information is set in an IPv6 extension header.
  • the first indication information is the first SRv6SID
  • the first SRv6SID is the destination address of the first SRv6 message
  • the first SRv6SID is assigned by the first PE device to the first tenant in a per-tenant-per-service manner. SID.
  • the forwarding module 702 before acquiring the first SRv6 message, is also configured to: determine the first bandwidth control policy based on the association between the first indication information and the first bandwidth control policy.
  • the association includes a correspondence between the first indication information and the first transmission service type, and a correspondence between the first transmission service type and the first bandwidth control policy.
  • the association relationship table includes an access control list, a local SID table, a routing information database table or a forwarding information database table of the first PE device.
  • the forwarding module 702 before forwarding the first SRv6 message based on the first bandwidth control policy, is also configured to query the first bandwidth control policy in the association table according to the first indication information.
  • the first bandwidth control policy includes a committed access rate
  • the committed access rate includes a committed rate and/or a peak rate profile.
  • the first bandwidth control is performed based on the length of the payload of the first SRv6 message.
  • the forwarding module 702 is specifically configured to: determine the first transmission path corresponding to the first transmission service type according to the first indication information; forward the first SRv6 message based on the first bandwidth control policy and the first transmission path,
  • the ingress node of the first transmission path is the first PE device
  • the egress node of the first transmission path is the second PE device
  • the destination node of the second first SRv6 message accesses the operator network through the second PE device.
  • the remaining segment value of the first SRv6 message is greater than 1, and the forwarding module 702 is specifically configured to discard the first SRv6 message.
  • the remaining value of the segment of the first SRv6 message is equal to 1, and the forwarding module 702 is specifically configured to: forward the first SRv6 message.
  • the obtaining module 701 is further configured to: obtain a second SRv6 message, the second SRv6 message includes second indication information, and the second indication information is used to indicate the third transmission service type of the second SRv6 message. Second bandwidth control policy; the forwarding module is also used to: forward the second SRv6 message based on the second bandwidth control policy.
  • the second tenant and the first tenant are the same tenant, the second transmission service type and the first transmission service type are different transmission service types, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies.
  • the second indication information is the second SRv6SID
  • the second SRv6SID is the destination address of the second SRv6 message
  • the second SRv6SID is the SID allocated by the first PE device to the second tenant in a per-tenant-per-service manner.
  • the acquisition module 701 is further specifically configured to determine the second bandwidth control policy according to the association between the second indication information and the second bandwidth control policy.
  • the first PE device stores an association between the second indication information and the second bandwidth control policy.
  • FIG. 8 is a schematic structural diagram of a network device 800 provided by an embodiment of the present application.
  • the network device 800 can be used to perform the data transmission method in the above embodiment.
  • the network device 800 may include a processor 810 and a memory 820 coupled to the processor 810 .
  • the processor 810 may be a central processing unit (English: central processing unit, abbreviation: CPU), a network processor (English: network processor, abbreviation: NP) or a combination of CPU and NP.
  • the processor can also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), a field-programmable logic gate array (English: field-programmable gate array, abbreviation: FPGA), a general array logic (English: generic array logic, abbreviation: GAL) or any combination thereof.
  • the processor 810 may refer to one processor or may include multiple processors.
  • the memory 820 may include volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory) , such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid-state drive (English: solid-state drive , abbreviation: SSD); the memory 820 may also include a combination of the above types of memories.
  • the memory 820 may refer to one memory or may include multiple memories. In one embodiment, computer readable instructions are stored in the memory 820.
  • the computer readable instructions include a plurality of software modules, such as a first processing module 821 and a second processing module 822, which may respectively correspond to the above-mentioned data transmission device 700.
  • the processor 810 can perform corresponding operations according to the instructions of each software module.
  • the operations performed by a software module actually refer to operations performed by the processor 810 according to the instructions of the software module.
  • "obtaining the first SRv6 message" executed by the first processing module 821 may actually refer to "acquiring the first SRv6 message” executed by the processor 810 according to the instruction of the first processing module 821.
  • the The first processing module 821 may correspond to the acquisition module 701 in the data transmission device 700.
  • the network device 800 can perform the data transmission method as shown in FIG. 6 in the above embodiment.
  • the processor 810 is used to perform the data transmission method. All processing related operations.
  • the processor 810 is configured to process the first SRv6 message to obtain the second SRv6 message, and select the first path corresponding to the first transmission service type to forward the second SRv6 message based on the first indication information and the first bandwidth control policy. 2. SRv6 packets.
  • FIG. 9 is a schematic structural diagram of a data transmission system 900 provided by an embodiment of the present application.
  • the data transmission system 900 may include a first PE device 901 and a first user-side device 902.
  • the first PE device 901 may be, for example, the PE device 1 in FIG. 1 , or the PE device 31 or the PE device 32 in FIG. 5 , and is used to perform operations performed by the first PE device.
  • the first user-side device 90 can be the user-side device 11 in Figure 1, or can be the host 21 or CPE 23 in Figure 5, used to perform the operations performed by the first user-side device in the method.
  • the present application also provides a computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When run on a computer, the computer is caused to execute the method described in any of the foregoing embodiments. any one or more operations.
  • This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform any one or more operations in the method described in any of the preceding embodiments.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical service division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each business unit in various embodiments of this application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software business units.
  • Integrated units may be stored in a computer-readable storage medium when implemented in the form of software business units and sold or used as independent products.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

La présente demande concerne un procédé et un appareil de transmission de données, ainsi qu'un dispositif de réseau et un support de stockage. Lorsqu'un fournisseur effectue une transmission de trafic pour différents types de service de transmission sélectionnés par un locataire, un dispositif PE d'un réseau de fournisseur analyse des informations d'indication qui sont contenues dans un message SRv6 reçu en provenance d'un dispositif côté utilisateur du locataire et sont utilisées pour indiquer un type de service de transmission du locataire relativement au réseau de fournisseur, puis traite le message SRv6 selon une politique de commande de bande passante associée aux informations d'indication. Par conséquent, le fournisseur peut effectuer une commande de bande passante sur du trafic de transmission de services de différents types de service de transmission qui sont utilisés par le locataire, ce qui permet de réaliser la tarification et le fonctionnement du fournisseur pour différents types de service de transmission.
PCT/CN2023/102953 2022-07-30 2023-06-27 Procédé et appareil de transmission de données, et dispositif de réseau et support de stockage WO2024027378A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210912439.6 2022-07-30
CN202210912439.6A CN117527668A (zh) 2022-07-30 2022-07-30 数据传输方法、装置、网络设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024027378A1 true WO2024027378A1 (fr) 2024-02-08

Family

ID=89744415

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/102953 WO2024027378A1 (fr) 2022-07-30 2023-06-27 Procédé et appareil de transmission de données, et dispositif de réseau et support de stockage

Country Status (2)

Country Link
CN (1) CN117527668A (fr)
WO (1) WO2024027378A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105337894A (zh) * 2014-06-24 2016-02-17 华为技术有限公司 一种为业务报文提供服务质量QoS的装置、***和方法
CN113949645A (zh) * 2020-07-15 2022-01-18 华为技术有限公司 一种业务处理方法、装置、设备及***
US20220159505A1 (en) * 2019-07-31 2022-05-19 Huawei Technologies Co., Ltd. Transporting mtnc-id over srv6-header for 5g transport

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105337894A (zh) * 2014-06-24 2016-02-17 华为技术有限公司 一种为业务报文提供服务质量QoS的装置、***和方法
US20220159505A1 (en) * 2019-07-31 2022-05-19 Huawei Technologies Co., Ltd. Transporting mtnc-id over srv6-header for 5g transport
CN113949645A (zh) * 2020-07-15 2022-01-18 华为技术有限公司 一种业务处理方法、装置、设备及***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LEE YOUNG; JOHN KAIPPALLIMALIL; VILALTA RICARD: "Extended ACTN Architecture to Enable End-To-End 5G Transport Service Assurance", 2019 21ST INTERNATIONAL CONFERENCE ON TRANSPARENT OPTICAL NETWORKS (ICTON), IEEE, 9 July 2019 (2019-07-09), pages 1 - 3, XP033618028, DOI: 10.1109/ICTON.2019.8840270 *

Also Published As

Publication number Publication date
CN117527668A (zh) 2024-02-06

Similar Documents

Publication Publication Date Title
US10757008B2 (en) Flow specification protocol-based communications method, device, and system
EP4102785A1 (fr) Procédé et appareil de traitement de message, et dispositif de réseau et support de stockage
CN111865796B (zh) 用于网络业务的路径计算单元中央控制器（pcecc）
EP3866414A1 (fr) Procédé, appareil, dispositif et système de traitement de message
US7486674B2 (en) Data mirroring in a service
US20140351812A1 (en) Recording medium, management device, and network system
EP4024783A1 (fr) Procédé et appareil de commande destinés à la transmission de données
US11799688B2 (en) Method for managing virtual private network, and device
US20240098019A1 (en) Packet Processing Method and Related Device
Shvedov et al. Segment routing in data transmission networks
CN114128228A (zh) 通过SRv6头传输MTNC-ID以实现5G传输
US20230086487A1 (en) Method for Determining Processing Capability, Node, and System
CN113055293B (zh) 软件定义广域网中的选路方法及装置、通信***
WO2022057810A1 (fr) Procédé de transfert de paquet de services, procédé d'envoi de politique sr, dispositif et système
US20240056392A1 (en) Communication method and apparatus
US20230412508A1 (en) Packet processing method and related apparatus
CN114128227B (zh) 在支持SRv6的数据面上传输MTNC-ID以实现5G传输
WO2020114083A1 (fr) Procédé et appareil de traitement d'informations ioam
CN114710975B (zh) 一种用于多域间传输多传输网络上下文标识的方法、基站、网元及装置
WO2024027378A1 (fr) Procédé et appareil de transmission de données, et dispositif de réseau et support de stockage
WO2023231438A1 (fr) Procédé d'envoi de messages, dispositif de réseau et système
WO2024007762A1 (fr) Procédé de publication de voie d'acheminement, et procédé et appareil de communication
CN110838965B (zh) 一种隧道建立方法以及接收节点
WO2024002101A1 (fr) Procédé et appareil de transmission de paquets, dispositif associé, et support de stockage
CN117411822A (zh) 基于位索引显式复制的转发路由器brf的管理方法

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

Country of ref document: EP

Kind code of ref document: A1