CN117527668A - Data transmission method, device, network equipment and storage medium - Google Patents
Data transmission method, device, network equipment and storage medium Download PDFInfo
- Publication number
- CN117527668A CN117527668A CN202210912439.6A CN202210912439A CN117527668A CN 117527668 A CN117527668 A CN 117527668A CN 202210912439 A CN202210912439 A CN 202210912439A CN 117527668 A CN117527668 A CN 117527668A
- Authority
- CN
- China
- Prior art keywords
- srv
- message
- bandwidth control
- indication information
- tenant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 218
- 238000000034 method Methods 0.000 title claims abstract description 90
- 238000011217 control strategy Methods 0.000 claims abstract description 25
- 230000008569 process Effects 0.000 claims abstract description 23
- 238000012545 processing Methods 0.000 claims description 22
- 230000015654 memory Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 6
- 229920006235 chlorinated polyethylene elastomer Polymers 0.000 description 15
- 238000010586 diagram Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 10
- 238000005538 encapsulation Methods 0.000 description 9
- 239000010410 layer Substances 0.000 description 9
- 230000000694 effects Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 5
- 239000000835 fiber Substances 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 3
- 101100256916 Caenorhabditis elegans sid-1 gene Proteins 0.000 description 2
- 101100256918 Caenorhabditis elegans sid-2 gene Proteins 0.000 description 2
- 101100256922 Caenorhabditis elegans sid-3 gene Proteins 0.000 description 2
- 101100365746 Caenorhabditis elegans sid-5 gene Proteins 0.000 description 2
- 101000984710 Homo sapiens Lymphocyte-specific protein 1 Proteins 0.000 description 2
- 102100027105 Lymphocyte-specific protein 1 Human genes 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 238000000136 cloud-point extraction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- ABEXEQSGABRUHS-UHFFFAOYSA-N 16-methylheptadecyl 16-methylheptadecanoate Chemical compound CC(C)CCCCCCCCCCCCCCCOC(=O)CCCCCCCCCCCCCCC(C)C ABEXEQSGABRUHS-UHFFFAOYSA-N 0.000 description 1
- 241000764238 Isis Species 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 239000012792 core layer Substances 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005417 image-selected in vivo spectroscopy Methods 0.000 description 1
- 238000012739 integrated shape imaging system Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- HRULVFRXEOZUMJ-UHFFFAOYSA-K potassium;disodium;2-(4-chloro-2-methylphenoxy)propanoate;methyl-dioxido-oxo-$l^{5}-arsane Chemical compound [Na+].[Na+].[K+].C[As]([O-])([O-])=O.[O-]C(=O)C(C)OC1=CC=C(Cl)C=C1C HRULVFRXEOZUMJ-UHFFFAOYSA-K 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- 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
- 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
Abstract
The application provides a data transmission method, a device, network equipment and a storage medium, when an operator performs traffic transmission aiming at different transmission service types selected by a tenant, PE equipment of the operator network analyzes indication information which is contained in SRv message received from user side equipment of the tenant and is used for indicating the transmission service type of the tenant to the operator network, and then processes SRv message according to bandwidth control strategy associated with the indication information. Therefore, the operator can control the bandwidth of the transmission flow of the service of which the tenant uses different transmission service types, so that the operator can realize the charging operation of the different transmission service types.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a data transmission method, apparatus, network device, and storage medium.
Background
When the traffic of the user needs to provide the bearer service by the operator network, the operator Edge (PE) device introduces the traffic of the user into a sixth-edition internet protocol-based segment routing (English: segment Routing over Internet Protocol version 6, SRv) tunnel established in the operator network according to the agreement of the operator and the user, and forwards the traffic through the SRv6 tunnel.
However, in the case where the operator network provides differentiated transmission capability to meet different requirements (such as a path overhead requirement, a delay requirement, a bandwidth requirement, a link jitter requirement, an error code requirement, a requirement of an optical fiber wavelength or a time slot to be allocated, etc.) of the network transmission service, the operator cannot respectively operate different types of network transmission services in different manners based on the SRv technology.
Disclosure of Invention
The embodiment of the application provides a data transmission method, a data transmission device, network equipment and a storage medium, which can solve the problem that operators cannot respectively operate different types of network transmission services in different modes based on SRv technology.
In order to achieve the above purpose, the present application adopts the following technical scheme:
in a first aspect, a data transmission method is provided, where the data transmission method is applied to a first PE device, and the method includes: the first PE device obtains a first SRv6 message, and the first SRv6 message includes first indication information. The first indication information is used for indicating a first transmission service type of the first tenant to the operator network. The first PE device further indicates the associated first bandwidth control policy to process the first SRv6 message according to the first indication information. Therefore, the operator can control the bandwidth of the transmission flow of the service of which the tenant uses different transmission service types through the PE equipment in the operator network, so that the charging operation of the operator on the different transmission service types is realized.
In the embodiment of the application, the mode of carrying the first indication information by the first SRv message is not limited, so that the format flexibility of carrying the first indication information by the first SRv message is improved, the first SRv6 message can carry the first indication information in different modes according to scene requirements, and the applicability of the data transmission method is improved. For example, the first indication information may be set in an IPv6 extension header of an IPv6 header of the first SRv message. As another example, 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, abbreviated as CAR), and the committed access rate may include a committed rate (english: committed Information Rate, abbreviated as CIR) and/or a peak rate (english: peak Information Rate, abbreviated as PIR), that is, the first bandwidth control policy selects a processing manner of the first SRv6 packet, for example, forwarding the packet or discarding the packet, according to the committed rate and/or the peak rate agreed by the first tenant and the operator.
Optionally, since the method provided in the embodiment of the present application is applied in the SRv scene, the first indication information is SRv segment id (english: segment id, abbreviated as SID).
The first indication information may be a first SRv SID allocated to the first tenant by the first PE device according to a per-tenant per-service manner, and the destination address field of the first SRv6 packet carries the first SRv SID. The per-tenant per-service mode refers to respectively allocating different SRv SIDs to different transmission service types of different tenants.
Alternatively, the first indication information may also be a partial field of the first SRv SID, for example, a Function (english: function) field or a parameter (english: area) field of the first SRv SID.
As a possible implementation manner, the first PE device may further determine a first transmission path of the first SRv packet according to the first indication information, for example, the first indication information is SRv SID, and the first PE device determines a first transmission path corresponding to the first transmission service type according to SRv SID, and processes the first SRv packet according to the first transmission path.
As a possible implementation manner, the first PE device stores a correspondence between the first indication information and the first bandwidth control policy, so that the first PE device determines the first bandwidth control policy of the first SRv packet based on the first indication information carried by the first SRv packet.
The association relationship between the first indication information and the first bandwidth control policy may be a direct correspondence relationship or an indirect correspondence relationship. For example, the first PE device determines the first bandwidth control policy based on a correspondence between the first indication information and the first bandwidth control policy. In another example, the first PE device may further determine the first transport service type based on a correspondence between the first indication information and the first transport service type, and determine the first bandwidth control policy based on a correspondence between the first transport service type and the first bandwidth control policy.
Optionally, the association between the first indication information and the first bandwidth control policy is stored in the first PE device in an association table, where the association table is configured in the first PE device before the first PE device processes the service of the tenant. For example, when the resources of the access control list (english: access Control Lists, abbreviated ACL) built in the first PE device are sufficient, the first PE device may use the access control list as the association table. For another example, when the resources of the local SID table, the forwarding information base table (english: forward Information dataBase, abbreviated as FIB) or the routing information base table (english: routing Information dataBase, abbreviated as RIB) built in the first PE device are sufficient, the first PE device may use the local SID table or the forwarding information base table as the association table.
As a possible implementation manner, when the association table is stored in the first PE device, the first PE device determines, in the association table, a first bandwidth control policy corresponding to a first transmission service type to which the first SRv6 packet belongs according to first indication information carried by the first SRv6 packet after receiving the first SRv packet. For example, the first PE device inputs the first indication information into an access control list, a local segment identification SID table, a forwarding information base table, or a routing information base table, and matches the first indication information to a first bandwidth policy corresponding to the first indication information. Therefore, the rapid matching of the first indication information and the first bandwidth policy is ensured, and the message forwarding and transmitting efficiency is improved.
As a possible implementation manner, when the first PE device processes the first SRv6 packet based on the first bandwidth control policy, the effective length of the first SRv6 packet is first determined, and then the processing of the first SRv6 packet is controlled using the first bandwidth control policy according to the effective length of the first SRv6 packet.
The embodiment of the present application does not limit the manner in which the effective length of the first SRv6 is determined.
For example, the segment routing header (English: segment Routing Header, abbreviated as SRH) of the first SRv message does not generally carry data required by the tenant, the first PE device strips the segment routing header of the first SRv6 message to obtain a load of the first SRv6 message, and the length of the load is used as the effective length of the first SRv6 message, so that the first bandwidth control strategy calculates the traffic used by the tenant for transmitting the first SRv message based on the message content effective to the tenant, and the accuracy of bandwidth control is improved.
For another example, the first PE device uses the length of the first SRv message including the segment routing header as the effective length of the first SRv message, so as to reduce the operation of stripping the segment routing header and ensure the overall efficiency of message transmission.
As a possible implementation manner, the first PE device discards the first SRv6 packet when the value of the Segment residual (english: segment Left, abbreviated: SL) of the first SRv6 packet is greater than 1, and forwards the first SRv6 packet when the value of the Segment residual of the first SRv6 packet is equal to 1. Therefore, the message of the tenant can be limited to carry the SID (service identifier) for indicating the destination Customer premises equipment (English: customer-premises equipment, CPE for short) of the message besides the SID for indicating the bandwidth control strategy, so that the message transmission overhead of the tenant is reduced, and the fact that the tenant sends the message with a longer forwarding path to the first PE equipment to occupy additional user bandwidth allowance is avoided.
The first PE device may process the first SRv packet of the first tenant by using a first bandwidth control policy, and may also process the packet of a different tenant by using a different bandwidth control policy.
For example, the first PE device obtains the second SRv6 packet, determines, according to the second indication information included in the second SRv packet, that the second bandwidth control policy associated with the second indication information processes the second SRv6 packet.
If 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 first PE device provides different charging operation modes 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, the first PE device can provide different charging operation modes for different tenants aiming at the same transmission service type.
The two cases are two examples provided in this embodiment, where the second tenant, the second transmission service type and the second bandwidth control policy are not limited in this embodiment, so as to implement more flexible bandwidth control on the packet of the tenant.
In a second aspect, a data transmission apparatus is provided, the apparatus comprising respective modules for performing the data transmission method of the first aspect or any one of the possible implementations of the first aspect.
The data transmission apparatus according to the second aspect may be a terminal device or a network device, or may be a chip (system) or other components or assemblies that may be disposed in the terminal device or the network device, or may be an apparatus including the terminal device or the network device, which is not limited in this application.
In addition, the technical effects of the data transmission device according to the second aspect may refer to the technical effects of the data transmission method according to the first aspect, which are not described herein.
In a third aspect, there is provided a network device comprising a memory and a processor, the memory for storing instructions which, when executed by the processor, are operative to perform the operational steps of the data transmission method in any one of the possible designs of the first aspect.
In addition, the technical effects of the network device described in the third aspect may refer to the technical effects of the data transmission method described in the first aspect, which are not described herein.
In a fourth aspect, there is provided a computer-readable storage medium comprising: computer software instructions; when the computer software instructions are run in a processor, the method as described in any one of the possible implementations of the first aspect is performed.
In a fifth aspect, there is provided a computer program product for performing a method as described in any one of the possible implementations of the first aspect when the computer program product is run on a processor.
Further combinations of the present application may be made to provide further implementations based on the implementations provided in the above aspects.
Drawings
Fig. 1 is a schematic diagram of a network framework related to an application scenario provided in an embodiment of the present application;
fig. 2 is a schematic processing diagram of a message when a bearer service is provided in an operator network according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a transmission network in an operator network according to an embodiment of the present application;
fig. 4a is a schematic diagram of a SRv message 1 provided in an embodiment of the present application;
fig. 4b is a schematic diagram of a message 2 provided in an embodiment of the present application;
fig. 4c is a schematic diagram of a message 3 provided in an embodiment of the present application;
fig. 4d is a schematic diagram of a SRv message 4 provided in an embodiment of the present application;
fig. 5 is a schematic diagram of a network framework related to another application scenario provided in an embodiment of the present application;
fig. 6 is a flow chart of a data transmission method according to an embodiment of the present application;
Fig. 7 is a schematic structural diagram of a data transmission device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a data transmission system according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In this application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, a and b, a and c, b and c, or a and b and c, wherein a, b and c may be single or plural. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect, and those skilled in the art will understand that the terms "first", "second", and the like do not limit the number and execution order. For example, in the embodiment of the present application, "first" of the first message and "second" of the second message are only used to distinguish different messages. The first, second, etc. descriptions in the embodiments of the present application are only used for illustrating and distinguishing the description objects, and no order division is used, nor does it indicate that the number of the devices in the embodiments of the present application is particularly limited, and no limitation on the embodiments of the present application should be construed.
In this application, the terms "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
Typically, when the traffic of a tenant is sent from one user side device to another user side device of the tenant, the traffic needs to be forwarded through an operator network, where the operator network provides a bearer service for the traffic of the tenant. Currently, the tenant and the operator network agree on a transmission service type by signing an agreement, and the operator network provides corresponding services for the tenant according to the agreed transmission service type. Specifically, a SRv tunnel is established in the operator network, after the traffic of the tenant reaches the PE device of the operator network, the PE device may introduce the traffic into the SRv tunnel corresponding to the predefined transmission service type, and forwarding the traffic through the SRv tunnel may enable the operator network to provide the service conforming to the predefined transmission service type for the tenant.
However, in many scenarios, the tenant needs an operator network to provide services of different transport service types for a part of the traffic, and then the operator network provides at least one bearer service for the traffic of the tenant according to a contract. The cost difference exists in the services of different transmission service types provided by the operators for the tenants, so the operators need to operate the traffic transmitted by the tenants by using the services of different transmission service types by adopting different operation modes. For example, when the operator and the tenant sign a service protocol to determine the flow limit of a service of a certain transmission service type, the operation mode corresponding to the transmission service type includes controlling the flow of the tenant accessing the bearer network not to exceed the flow upper limit determined by the service protocol, so as to avoid the bandwidth occupation under the conditions of multiple tenants and multiple services. An operator can provide at least one transmission service type for the same tenant or different tenants, and the operator has a difference in charging formulated for different transmission service types, so that the operator needs to use different charging operation modes to perform charging operation on the traffic transmitted by the tenants using different transmission service types. However, when the carrier network determines the transmission service type of the tenant by using the SRv tunnel, the carrier network cannot perform charging operation in different manners on the traffic transmitted by the tenant using the services of different transmission service types.
Based on this, the embodiment of the application provides a data transmission method, where a PE device carrying a network can obtain a SRv packet including different indication information, where the different indication information is used to indicate a first transmission service type of a first tenant to an operator network, and the PE device processes SRv the packet according to a bandwidth control policy associated with the indication information. In this way, when providing services of different transmission service types for the tenant, the operator network can transmit SRv messages according to the transmission service types required by the tenant provided with the indication information, and perform bandwidth control on the processing of SRv messages by adopting the bandwidth control policy indicated by the indication information. Therefore, the operator can control the bandwidth of the transmission flow of the service of which the tenant uses different transmission service types, so that the operator can realize the charging operation of the different transmission service types.
The transmission service types may be divided according to different requirements of quality of service (english: quality of Service, abbreviated: qoS), such as a path overhead requirement, a delay requirement, a bandwidth requirement, a link jitter requirement, an error code requirement, and a requirement of a fiber wavelength or a slot to be allocated. Alternatively, the operator network may divide paths corresponding to different transport service types based on different topologies, slices, routing algorithms and differentiated services code points (english: differentiated Services Code Point, abbreviated: DSCP). Bandwidth control policies include committed access rates, such as committed rate control, peak rate control, etc.
For example, in the scenario shown in fig. 1, the operator network 10 may include: PE device 1, PE device 2 and transport network 3, PE device 1 connects user side device 11 of tenant 1 through interface 1, connects user side device 21 of tenant 2 through interface 2, PE device 1 connects PE device 2 through transport network 3. The PE device 2 is connected to the user side device 12 of the tenant 1 via the interface 3 and to the user side device 22 of the combination 2 via the interface 4. Alternatively, the transport network 3 may include one or more operator (P) devices (also referred to as core layer devices), and the embodiment of the present application is only illustrated by taking a PE device as an example.
Taking tenant 1 as an example, the operator network 10 may agree on the transport service type 1 with tenant 1, and establish a SRv tunnel 1 satisfying the transport service type 1, where the SRv tunnel 1 passes through the PE device 1, the transport network 3, and the PE device 2 in order. The user side device 11 receives the message 1 and sends the message 1 from the interface 1 to the PE device 1; PE device 1 receives message 1 of tenant 1, forwards the message 1 by using SRv tunnel 1, for example, PE device 1 peels off the segment routing header of message 1 and encapsulates the transmission network header to obtain message 2, forwards message 2 by transmission network 3, PE device 2 receives message 2, and PE device 2 decapsulates message 2 to obtain message 3, and the schematic diagram can be seen in FIG. 2; thus, the PE device 2 sends the message 3 from the interface 3 to the user side device 12 of the tenant 1. In this way, the operator network 10 provides the tenant 1 with a service corresponding to the predefined transport service type 1. If tenant 1 needs operator network 10 to provide a service of transport service type 2 for traffic of a certain feature, transport service type 2 is different from transport service type 1, operator network 10 needs to agree on transport service type 2 with tenant 1, and establishes SRv tunnel 2 satisfying transport service type 2, and SRv tunnel 2 passes through PE device 1, transport network 3, and PE device 2 in order. The traffic includes, for example, a message 1', and then the user side device 11 receives the message 1', and sends the message 1' from the interface 1 to the PE device 1; PE equipment 1 receives a message 1 'of tenant 1, encapsulates a transmission network header for the message 1' to obtain a message 2', forwards the message 2' through a transmission network 3, and decapsulates the message 2 'by PE equipment 2 to obtain a message 3'; thus, the PE device 2 sends the message 3' from the interface 3 to the user side device 12 of the tenant 1.
According to the technical solution provided in the embodiment of the present application, in the scenario shown in fig. 1, both the PE device in the operator network 10 and the user side device of each tenant support SRv. A plurality of different types of paths are provided in the carrier network 10, for example: label switching paths (English: label Switched Path, abbreviated: LSP), IPv6 tunnels, SRv6 tunnels or optical fiber physical links for forwarding based on multiprotocol label switching (English: multi-Protocol Label Switching, abbreviated: MPLS), wherein different types of paths respectively correspond to different transmission service types.
The transport network 3 may also provide a plurality of different types of paths, such as label switched paths, IPv6 tunnels, SRv tunnels or fibre optic physical links, as part of the carrier network 10. The network transmission header of the packet 1 or the packet 1' encapsulated by the PE device 1 conforms to the protocol of the path provided by the transmission network 3, such as an IP header, an IPv6 header, a multiprotocol label switching (english: multi-Protocol Label Switching, abbreviated: MPLS) header, and the like.
Taking fig. 3 as an example, the transport network 3 includes a PE device 3 and a PE device 4, and the PE device 1 is connected to the PE device 2 through the PE device 3 and the PE device 4, respectively, and then the transport network 3 includes a path 1 that is PE device 1- > PE device 3- > PE device 2, a path 2 that is PE device 1- > PE device 4- > PE device 2, and a path 1 and a path 2 that are different types of paths in the transport network 3. For example, path 1 corresponds to transport service type 1 and path 2 corresponds to transport service type 2.
In this way, according to the target technical solution, the operator network 10 provides the service corresponding to the transmission service type 1 and the transmission service type 2 agreed in advance for the tenant 1, but the operator network 10 cannot respectively perform charging operation on the services of different transmission service types, that is, the operator network 10 cannot control the traffic of the tenant for receiving and transmitting the service using the different transmission service types to conform to the traffic range defined in the service protocol signed by the tenant and the operator.
Before the message processing, the user side device of the tenant and the PE device of the user side device accessed to the operator network 10 may acquire transmission service information, where the transmission service information is used to indicate bandwidth control policies corresponding to different indication information. As an example, the PE device connected to the user side device of the tenant in the operator network 10 may configure transport service information related to the tenant connected to the PE device, and send the transport service information of each tenant to the user side device of the tenant. The PE device may directly send the transmission service information to the user side device, or the PE device may indirectly send the transmission service information to the user side device through an operator management device, a service management device, and the like to which the PE device belongs. As another example, the carrier management device or the service management device may configure related transport service information for the tenant, and send the transport service information to the user side device of the tenant and the PE device connected to the user side device of the tenant. As yet another example, the user side device of the tenant and the PE device connected to the user side device may both obtain relevant transport service information by means of static configuration, as long as it is ensured that the same transport service information indicates the same content. In the following, the PE device is used to configure related transport service information and send the transport service information directly to the user device.
For the transmission service information, in one case, the transmission service information may include the correspondence between the indication information, the paths in the operator network, and the bandwidth control policies, where different paths satisfy different transmission service types, and different transmission service types correspond to different bandwidth control policies. In another case, the transmission service information may include correspondence of indication information, transmission service type, and bandwidth control policy. The indication information may be an IPv6 address in a dedicated IPv6 address set (may also be referred to as an IPv6 address block or an IPv6 network segment) allocated for the tenant; or on the basis of the exclusive IPv6 address set allocated to the tenant, carrying out a bandwidth control strategy through a Function field or an figure field; but may also be a bandwidth control policy that is not related to the set of proprietary IPv6 addresses allocated for the tenant.
As a possible implementation manner, the bandwidth control policy may be defined in the traffic-behavir object, and then the traffic-behavir object is associated with the indication information, so as to implement association between the bandwidth control policy and the indication information. As another possible implementation manner, the PE device may also configure a corresponding bandwidth control policy for each indication information, or perform association between the bandwidth control policy and the indication information through other objects instead of the traffic-behavir object, etc.
PE equipment in an operator network can analyze a message sent by user side equipment under the condition of knowing transmission service information to obtain indication information, determine a path and a bandwidth control strategy according to a transmission service type corresponding to the indication information, package the SRv message according to the determined path type based on the bandwidth control strategy, and forward the path. In this way, the operator network can provide the service of the transmission service type required by the tenant for the message of the tenant, and bandwidth control the flow of the service of different transmission service types, so as to realize the charging operation of the operator on the service of different transmission service types.
In the scenario shown in fig. 1, PE device 1 may pre-configure an IPv6 address set for tenant 1: 2001:db8:A 1::48, pre-configuration of IPv6 address set for tenant 2: 2001:db8:A2:: 48.
In some possible implementations, the indication information is an IPv6 address in an IPv6 address set of the tenant, the transport service information includes the indication information and a transport service type, and the transport service information on the PE device 1 may include:
transmission service information 1: (tenant 1, ipv6 address 11=2001:db8:a1:1, transport service type 11< transport path=path with minimal overhead >)
Transmission service information 2: (tenant 1, ipv6 address 12=2001:db8:a1:2, transport service type 12< transport path=path with minimum delay >)
Transmission service information 3: (tenant 1, ipv6 address 13=2001:db8:a1:3, transport service type 13< transport path=path of exclusive fiber wavelength or slot >)
Transmission service information 4: (tenant 2, ipv6 address 21=2001:db8:a2:1, transport service type 21< transport path=path with minimum latency >)
Transmission service information 5: (tenant 2, ipv6 address 22=2001:db8:a2:2, transport service type 22< transport path=path with minimal link jitter >)
Specific examples of configuring the above transmission service information on the PE device 1 may be:
optionally, the transmission service information on the PE device 1 may be sent to the user side device of the corresponding tenant in an offline manner or in a protocol packet manner.
Optionally, the IPv6 address set configured on the PE device 1 and required to be advertised to each tenant may be sent to a user side device of the corresponding tenant through a protocol packet (such as an intermediate system to intermediate system (english: intermediate system to intermediate system, abbreviated as ISIS) packet), so as to achieve reachable routing between the user side device and the PE device 1.
The PE device 1 may send the above-mentioned transport service information 1-3 to the user side device 11 and the transport service information 4 and 5 to the user side device 12.
In the embodiment of the present application, in order to implement bandwidth control of the carrier network 10 for traffic of different transport service types, the transport service information in the PE device 1 further includes bandwidth control policy associated with the indication information, such as bandwidth control information of a committed access rate (english: committed Access Rate, abbreviated: CAR).
Specific examples of configuring the bandwidth control policy in the above-mentioned transport service information on the PE device 1 may be:
as an example, when the service 1 of the tenant 1 (such as the Web file transmission service) has a QoS requirement corresponding to the transmission service type 11, the user side device 11 may determine, based on the transmission service information 1, that the destination IP address is the IPv6 address 11 filled in the SRv message 1 to be sent (i.e. 2001:db8:a1:: 1). When PE device 1 receives SRv message 1 including 2001:db8:1:1:1 from interface 1 connected to tenant 1, it may determine, according to the IP address 2001:db8:1:1 of SRv6 message 1, as shown in the above example one, a transmission service type 11 required by SRv message 1, select path 1 with minimum overhead, where path 1 sequentially passes through PE device 1, PE device 3 and PE device 2, and determine, according to the transmission service type 11, bandwidth control policy qt1 corresponding to SRv message 1; therefore, the PE device 1 may process SRv the packet 1 according to the path 1 corresponding to the transport service type 11 to obtain the packet 2, send the packet 2 to the PE device 2 according to the path 1 based on the bandwidth control policy qt1, process the received packet 3 corresponding to the packet 2 by the PE device 2 to obtain SRv the packet 4, and send SRv the packet 4 from the interface 3 to the user side device 12. It should be noted that, network devices through which paths determined by SRv6 packets of different transmission service types for tenant 1 may pass are different, for example, transmission service type 11 corresponds to path 1 and transmission service type 12 corresponds to path 2; alternatively, paths determined by SRv packets of different transport service types for tenant 1 may pass through the same network device, but the path types are different, for example, transport service type 11 and transport service type 12 each correspond to path 1, but path 1 corresponding to transport service type 11 is an LSP forwarded based on MPLS, and path 1 corresponding to transport service type 12 is a SRv tunnel.
As another example, when the service 2 of the tenant 2 (such as a voice or video call service) has a QoS requirement corresponding to the transport service type 22 (i.e. selects a path with minimum link jitter for forwarding), the user side device 12 may determine, based on the transport service information 5, to fill in the to-be-sent SRv message 5 with the destination IP address being the IPv6 address 22 (i.e. 2001: db8: a2:: 2). When the PE device 1 receives a SRv packet 5 including 2001:db8:a2:1:2 from the interface 2 connected to the tenant 2, it may determine, according to the IP address 2001:db8:a2:2 of the SRv packet 5 destination IP address, that the transmission service type 22 required by the SRv packet 5 is the path 2 with the minimum link jitter, and a bandwidth control policy qt5 corresponding to the SRv packet 5, where the path 2 passes through the PE device 1, the PE device 4, and the PE device 2 in sequence, as in the example two above; thus, the PE device 1 may process SRv the packet 5 according to the path 2 corresponding to the transport service type 22 to obtain the packet 6, send the packet 6 to the PE device 2 according to the path 2 based on the bandwidth control policy qt5, process the received packet 6 with the PE device 2 to obtain SRv the packet 7, and send SRv the packet 7 from the interface 4 to the user side device 22.
In the above two examples, the destination address of the user side device may also be specified in the SID list of the SRH in the SRv6 packet 1 and SRv6 packet 5, for example, the address of the user side device 12 may also be included in the SRv6 packet 1, and the address of the user side device 22 may also be included in the SRv6 packet 5. The address of the user side device may be carried in a segment identification list (english: segment Identifier list, abbreviated SID list) field of the segment routing header in the SRv message, for example. Taking the example of the customer premise equipment 12, the customer premise equipment 12 may be a destination host, customer edge equipment, or customer premise equipment. If the customer side device 12 is a CE device or CPE, the destination address of the customer side device specified in SRv message 1 may be the address of the CE device or CPE, for example, a 128-bit SRv SID, or a compressed SRv SID or IPv6 address of less than 128 bits, for example, as compressed by the driver-cl-spring-customized-srv 6-for-cmpr-03; if the user side device 12 is a destination host, the destination address of the user side device specified in SRv message 1 may be an address of the destination host, for example, may be an IPv6 address of the destination host.
As an example, if the user side device 11 is the host 11 connected to the PE device 1 and the user side device 12 is the host 12 connected to the PE device 2, the host 11 may generate a SRv message 1 (actually a native (english: active) IPv6 message with an SRH added as an IPv6 extension header) as shown in fig. 4a for the service 1, where the SRv message 1 includes an IPv6 header, an SRH, and a payload (english: payload), where the source IP address field=the address of the host 11 in the IPv6 header, the destination IP address field=2001:db8:a 1::1, the SRH includes a remaining segment field and a SID list field, and the SL field=1, and the SID list includes the address of the host 12 and 2001:db8:a 1::. It should be noted that, the foregoing SRv message 1 adopts a non-simplified (english: reduced) SRH message encapsulation mode, and when the destination address in the IPv6 header of the SRv message 1 is 2001:db8:a1::1, the SID list in the SRH may not include 2001:db8:a1::1, and this mode is called reduced SRH message encapsulation mode. The embodiment of the application is described by taking SRv message in a message encapsulation mode of non-reduced SRH as an example.
When SRv message 1 is sent to PE device 1, PE device 1 determines, according to the destination IP address field in message 1, the transport service type 11 and bandwidth control policy qt1 corresponding to message 1. As shown in fig. 4b, the packet 2 obtained by processing the PE device 1 may include, in addition to the IPv6 header, the SRH and the payload, an MPLS label stack corresponding to the path 1 satisfying the transport service type 11. The MPLS label stack is an MPLS label stack corresponding to the path 1 obtained by the PE device 1 searching the routing table entry to determine that the next hop reaching the host 12 is the PE device 3, and determining that the path 1 between the PE device 1 and the PE device 2 satisfying the transport service type 11 is an LSP forwarding based on MPLS. The MPLS label stack may include an MPLS label of PE device 3 and an MPLS label of PE device 2, where a source IP address field=address of host 11, a destination IP address field=address of host 12, an SL field=0 in SRH, and a sid list includes an address of host 12 and 2001:db8:a 1:1. In this way, based on the MPLS label stack of the packet 2, the PE device 1 forwards the packet 2 to the PE device 2 through the path 1 in a forwarding manner conforming to the bandwidth control policy qt1, and the PE device 2 receives the packet 3 corresponding to the packet 2 as shown in fig. 4c, which is different from fig. 4b in that: the MPLS label stack only includes MPLS labels of the PE device 2, where the PE device 2 may strip off (i.e. strip the MPLS label stack) the MPLS label of the PE device 2 to obtain a SRv packet 4, as shown in fig. 4d, where the SRv packet 4 includes an IPv6 header, an SRH, and a payload, a source IP address field=an address of the host 11 in the IPv6 header, a destination IP address field=an address of the host 12, an SL field=0 in the SRH, and an sid list includes an address of the host 12 and 2001:db8:a 1:1. Then PE device 2 may send the SRv message 4 to host 12. It should be noted that, in this example, the host 11 may be directly connected to the PE device 1, or may be connected to the PE device 1 through a network device such as another switch or a router, and if the host 11 is connected to the PE device 1 through another network device, the other network device only performs IPv6 forwarding processing on the SRv message 1 without changing the destination address and SRH of the SRv message 1. Similarly, the host 12 may be directly connected to the PE device 2, or may be connected to the PE device 2 through another network device, and if the host 12 is connected to the PE device 2 through another network device, the other network device only performs the processing of forwarding the SRv message 4 to the host 12 by using IPv6 without changing the destination address and SRH of the SRv message 4.
Alternatively, the messages shown in fig. 4b, 4c and 4d have a value of 0 remaining in the segment of the segment routing header, and the segment routing header may be stripped, i.e., the messages shown in fig. 4b, 4c and 4d may not contain the segment routing header. The segment routing header may be stripped off at the time of message 2, message 3, or message 4 generation.
In the scenario example illustrated in fig. 1 above, the operator network may refer to a service provider network and the tenant may be a personal tenant. In the embodiment of the application, for enterprise tenants, not only a service provider network but also virtual private cloud (English: virtual Private Cloud, simply: VPC) services provided by a cloud provider can be used. Embodiments of the present application are described below in the context of the scenario illustrated in fig. 5.
As in the scenario shown in fig. 5, including the campus network 20 of enterprise X, the carrier network 31, the carrier network 32, and the cloud provider network 40, where the campus network 20 may include hosts 21, switches 22, and customer premises devices 23, the carrier network 31 includes PE devices 31 and 31', the carrier network 32 includes PE devices 32 and 32', and the cloud provider network 40 may include access points (english: point of Presence, abbreviated: poP) 41, servers 42, and servers 43. The host 21 is connected to the CPE 23 through the switch 22, the CPE 23 accesses the carrier network 31 and the carrier network 32 through the PE device 31 and the PE device 32, the carrier network 31 is connected to the PoP 41 of the cloud provider network 40 through the PE device 31', the carrier 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. Wherein server 42 may be considered a cloud PE device and server 43 may be considered a cloud CE device.
The cloud provider network 40 may provide VPC services for the enterprise X, and from the perspective of the enterprise X, devices in the cloud provider network 40 may be virtualized as Virtual hosts, switches, routers, gateways, etc., for example, the server 42 is virtualized as Virtual Gateway (in english: virtual Gateway; in short: VGW) and the Virtual router rt0, and the server 43 is virtualized as Virtual Switch (in english: virtual Switch; in short: VSW) and Virtual Machine (in english: virtual Machine; in short: VM). Wherein, the VM can be regarded as a virtual host, and the VGW can be regarded as a virtual CPE. For enterprise X, it can be considered to have an end-to-end connection from host 21 to VM.
The carrier network 31 and carrier network provide corresponding services for enterprise X to conduct traffic between the campus network 20 and VPC traffic. From the perspective of enterprise X, the devices in carrier network 31 and carrier network 32 may be virtualized as virtual routers, e.g., PE devices 31', PE devices 32', PE devices 31, and PE devices 32 are virtualized as virtual routers rt1-rt4. The operator network 31 and the operator network 32 may include other individuals and enterprise tenants besides the tenant of the enterprise X, and are not limited in the embodiment of the present application.
As shown in fig. 5, the scene may further 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, wherein the operator management device 31 "is configured to manage devices in the operator network 31, and further configured to provide a management interface to the enterprise X through the Web portal; similarly, the operator management device 32″ is configured to manage devices in the operator network 32, and further configured to provide a management interface to the enterprise X through the Web portal; cloud management device 40 is used to manage devices (e.g., servers 42) in cloud provider network 40 and also to provide a management interface to enterprise X via a Web portal. A service management device (or service orchestrator) 20 may also be included in the scenario, where, on the one hand, the service management device 20 is configured to regulate its own physical devices (e.g., hosts 21, switches 22, or CPEs 23); on the other hand, the service management device 20 is configured to manage the virtual routers rt1 to rt4 through a management interface provided by the operator management device; in yet another aspect, the service management device 20 is configured to manage VM, VSW, rt and VGW through a management interface provided by the cloud management device 40.
As an example, taking the example that the indication information is carried through an IPv6 address, the operator network 31 configures 3 IPv6 addresses for the enterprise X, and the corresponding transport service information may include:
(tenant=enterprise X, IPv6 address=sid 1, transport service type < transport path=path with minimal overhead >)
(tenant=enterprise X, IPv6 address=sid 2, transport service type < transport path=path with minimum delay >)
(tenant=enterprise X, IPv6 address=sid 3, transport service type < transport path=path of exclusive fiber wavelength or slot >)
The carrier network 31 also includes a bandwidth control policy for the transport service information of enterprise X:
(tenant=enterprise X, IPv6 address=sid 1, bandwidth control policy < QoS-local-id qt1 >)
(tenant=enterprise X, IPv6 address=sid 2, bandwidth control policy < QoS-local-id qt2 >)
(tenant=enterprise X, IPv6 address=sid 3, bandwidth control policy < QoS-local-id qt3 >)
Similarly, the operator network 32 configures 2 IPv6 addresses for the enterprise X, and the corresponding transport service information may be:
(tenant=enterprise X, IPv6 address=sid 4, transport service type < transport path=path with minimum delay >)
(tenant=enterprise X, IPv6 address=sid 5, transport service type < transport path=path with minimal link jitter >)
The carrier network 32 also includes bandwidth control policies for the transport services information of enterprise X:
(tenant=enterprise X, IPv6 address=sid 4, bandwidth control policy < QoS-local-id qt4 >)
(tenant=enterprise X, IPv6 address=sid 5, bandwidth control policy < QoS-local-id qt5 >)
Wherein the transport service information may be statically configured on the carrier management device 31 "and the carrier management device 32" or obtained from PE devices in the corresponding carrier network, then the traffic management device 20 may obtain the transport service information from the carrier management device 31 "and the carrier management device 32" and send the transport service information to the hosts 21 and/or CPEs 23 in the campus network 10, and likewise the traffic management device 20 may obtain the transport service information from the carrier management device 31 "and the carrier management device 32" and send the transport service information to the VMs and/or VGWs in the cloud provider network 40; still alternatively, the traffic management device 20 may obtain the transmission service information from the carrier management device 31 "and the carrier management device 32" and send the transmission service information to the VM and/or VGW via the cloud management device 40 of the cloud provider network 40.
For a specific service, the service management device 20 or the service management device 20 sends corresponding transmission service information to the VM (or VGW) through the cloud management device 40, and instructs the VM (or VGW) to package the IPv6 address in the transmission service information for a message of the specific service. Alternatively, the cloud management device 40 may also issue all the transmission service information to the VM (or VGW), and the VM (or VGW) selects one of the transmission service types according to the actual requirement of the service, and encapsulates the corresponding IPv6 address in the message.
Similarly, the service management device 20 may issue corresponding transport service information to the host 21 (or CPE 23) for a specific service, and instruct the host 21 (or CPE 23) to package the IPv6 address in the transport service information for the packet of the specific service. Alternatively, the service management device 20 may also issue all the transmission service information to the host 21 (or CPE 23), where the host 21 (or CPE 23) selects one of the transmission service types according to the actual service requirement, and encapsulates the corresponding IPv6 address in the message. When the PE device 31 or the PE device 32 receives the message sent by the host 21, the transmission service type and the bandwidth control policy corresponding to the message are determined according to the transmission service information, and the message is forwarded in the path corresponding to the transmission service type according to the bandwidth control policy corresponding to the message.
Therefore, by the method provided by the embodiment of the application, enterprise tenants and cloud providers can independently select different transmission service types provided by the operator network, and the message transmission is controlled by adopting the bandwidth control strategies corresponding to the different transmission service types, so that the charging operation of the operators on the flow of the different transmission service types is realized.
Optionally, the granularity of selecting the transmission service type is not limited in the embodiments of the present application, for example, different transmission service types may be selected for different services, and different transmission service types may also be selected for different traffic.
Optionally, in the embodiment of the present application, the PE device may be a network device such as a switch, a router, or a firewall. The CE device may be a device having a private network access function, for example, a switch, a router, an internet of things (english: internet of Things, abbreviated: ioT) terminal, a host, or the like.
Optionally, the transmission service information in the embodiment of the present application may be a correspondence between a set of multiple pieces of information, for example, the transmission service information on the PE device may be: the identity of the tenant, the interface, the indication information, the transmission service type, the path and the corresponding relation between the bandwidth control strategies. In another case, the transport service information may also include a correspondence between multiple sets of part information, for example, the transport service information on the PE device includes: the method comprises the steps of indicating a corresponding relation 1 of information and transmission service types, indicating a corresponding relation 2 of information and paths, identifying a tenant and a corresponding relation 3 of interfaces, identifying the tenant and indicating a corresponding relation 4 of information, and transmitting a corresponding relation 4 of the service types and bandwidth control strategies. The identity of the tenant is used to uniquely identify the tenant, and may be, for example, a VPN identity of the tenant or a VNI corresponding to the tenant. It should be noted that, in the embodiment of the present application, the specific embodiment of the transmission service information is not limited, so long as the network of the operator can be ensured to provide the needed service for the tenant.
The above description takes the scenario shown in fig. 1 and fig. 5 as an example, and describes the application of the technical solution of the embodiment of the present application in different scenarios, which are only examples of the scenarios provided in the embodiment of the present application, and the application is not limited to the embodiment of the present application.
The following describes a data transmission method provided in the embodiments of the present application with reference to the accompanying drawings.
Fig. 6 is a flow chart of a data transmission method according to an embodiment of the present application. The method is described in terms of interaction between a first user side device of a first tenant and a first PE device, for example, the first user side device in the method is the user side device 11 in fig. 1, and the first PE device may be the PE device 1 in fig. 1; as another example, the first user side device in the method is the host 21 or CPE 23 in fig. 5, and the first PE device may be the PE device 31 or PE device 32 in fig. 5 (corresponding to rt3 or rt4 for enterprise X); for another example, the first user side device in the method is VM or VGW in fig. 5, and the first PE device may be PE device 31 'or PE device 32' in fig. 5 (corresponding to rt1 or rt2 for enterprise X). Referring to fig. 6, the method may include steps 601 to 604:
in step 601, a first user side device of a first tenant acquires a first SRv6 packet, where the first SRv packet includes first indication information, where the first indication information is used to indicate a first transmission service type of the first tenant to an operator network.
The first SRv message may be a message obtained by SRv packaging a service message of the first tenant, or may be a message generated by a host of the first tenant (english). The device for SRv encapsulation of the service packet of the first tenant may be a network device such as a switch, a router, etc. connected to the host of the first tenant. The first indication information in the first SRv message is indication information, which is determined by the first tenant according to the QoS requirement of the service message and is used for indicating the first bandwidth control policy of the operator network, and the first indication information is carried in the first SRv message, so that the first PE device that receives the first SRv6 message can determine the first bandwidth control policy according to the first indication information, thereby implementing bandwidth control on the traffic of different transmission service types by the operator.
The destination host of the first tenant, or the CE device or CPE connected to the destination host, to which the first SRv packet arrives, may be denoted as a second user side device, where the second user side device accesses to the operator network through a second PE device, where the second PE device is an egress node of the first SRv6 packet in the operator network, where the first PE device and the second PE device belong to the operator network. The first SRv message may include an address of the second user side device, indicating that the first SRv message passes through or reaches the second user side device.
The first transport service type is used for indicating transport services to be provided by the first tenant for the operator network to process the first SRv message. In the operator network, different transmission service requirements of each tenant are met by setting paths with different path types between PE devices, and when the first PE device forwards SRv messages of each tenant, the path types and the specific paths used influence the service provided by the operator network for SRv messages of the tenant. Wherein the path between PE devices of the operator network may include, but is not limited to: MPLS-based forwarding LSPs, IPv6 tunnels, SRv tunnels or physical links. Bearer techniques for a physical link may include: link layer encapsulation based on the link layer encapsulation corresponding to the individual physical links, link layer encapsulation corresponding to the first wavelength or time slot based on one individual fiber physical link, etc. The first transmission service type may be, but is not limited to, a transmission service with a large path overhead, a transmission service with a low delay, a transmission service with a large bandwidth, a transmission service with a low link jitter, a transmission service with a small error, a transmission service with a wavelength or a time slot of an optical fiber to be allocated. The first path satisfying the first transport service type may be, for example, LSP1 forwarded based on MPLS, and LSP1 may be a path of PE device 1 through PE device 3 to PE device 2, corresponding to the scenario shown in fig. 1.
The first indication information may be any information that can be carried in the first SRv message and perceived and identified by the first PE device.
As an example, the first indication information may be a first IPv6 address in a set of private IPv6 addresses allocated by the first PE device for the first tenant, where the first IPv6 address is used to carry the first indication information. The IPv6 address set may be one IPv6 network segment allocated by the first PE device for the first tenant, for example 2001:db8:a1:/48, where the IPv6 address set may include a plurality of IPv6 addresses, and each IPv6 address in the plurality of IPv6 addresses may correspond to one transport service type of the first tenant, for example 2001:db8:a1::1 corresponds to a transport service type that is the path with the minimum overhead, and 2001:db8:a1::2 corresponds to the transport service type that is the path with the minimum delay. In one case, the first IPv6 address may carry the first indication information as a whole, e.g., 2001:db8:A 1:1 is the first indication information. In another case, a part of the fields (such as the Function field or the area field) in the first IPv6 address is used to carry the first indication information, for example, in 2001:db8:a 1:1, the value "1" of the Function field is the first indication information. In this example, the value of the outer layer destination IP address field in the first SRv6 packet is the first IPv6 address, and after the first PE device receives the first SRv packet, the first IPv6 address is obtained from the outer layer destination IP address field by parsing the first SRv6 packet, so as to determine the first transport service type according to the first IPv6 address or the value of the field for carrying the first indication information in the first IPv6 address. In another example, the first indication information may be set in the IPv6 extension header of the first SRv6 packet, in addition to the outer layer destination IP address field of the first SRv6 packet.
Optionally, before step 601, 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 indication information and a transmission service type. The association relationship between the indication information and the transmission service type may include, but is not limited to, an association relationship between the first indication information and the first transmission service type. Taking the association relationship between the first indication information and the first transmission service type as an example, the association relationship between the first indication information and the first transmission service type may be configured on the first PE device, where the first PE device not only locally stores the association relationship between the first indication information and the first transmission service type, but also may directly or indirectly send the association relationship between the first indication information and the first transmission service type to the first user side device in an offline or protocol packet form. As another example, the association relationship between the first indication information and the first transmission service type may also be configured on the operator management device, and then the operator management device may send the association relationship between the first indication information and the first transmission service type to the first PE device, and may also send the association relationship between the first indication information and the first transmission service type to the first user side device through the service management device.
In the embodiment of the present application, the specific form of the locally stored transmission service information of the first PE device is not limited, so long as the first PE device can determine, based on the locally stored transmission service information and the first indication information in the first SRv message, a first path that satisfies the first transmission service type corresponding to the first indication information, so that services are provided for the first tenant based on the first path.
In step 602, the first user side device sends a first SRv message to the first PE device.
In step 603, the first PE device receives a first SRv6 packet sent by a first user side device belonging to the first tenant.
The first PE device may also store the matching relationship between each interface and the indication information, and after the first PE device receives the SRv packet, the first PE device may determine the interface that receives the SRv packet, so as to determine whether the matching relationship is satisfied by the interface and the indication information in the SRv6 packet, and if so, consider that the SRv packet needs to be processed, so as to execute the following step 604 on the SRv6 packet; otherwise, the SRv message is deemed not to meet the condition for continued processing, and the SRv message is discarded, and step 604 described below is not performed.
In step 604, the first PE device processes the first SRv message to obtain a second SRv6 message.
The first PE device subtracts one from the value of the SL field, and updates the value of the outer layer 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, according to the first indication information, a first path corresponding to the first transmission service type to forward the second SRv message based on the first bandwidth control policy.
In one aspect, the first PE device may subtract one from the value of the SL field in the SRH of the first SRv packet, so that the SID of the next hop of the first PE device in the SID list indicated by the SL field; in addition, the first PE device updates the value of the outer layer destination IP address field in the IPv6 header in the first SRv message, and specifically may update the value of the outer layer destination IP address field in the IPv6 header according to the SID in the SID list indicated by SL in the SRH. On the other hand, the first PE device may select, based on the first indication information, a first path that meets the first transport service type, so as to perform corresponding encapsulation on the first SRv packet according to the first path, for example, if the first path is an LSP that performs forwarding based on MPLS, then the first SRv6 packet may be encapsulated according to the first path, and may be an MPLS label stack that encapsulates the first path on the basis of the first SRv6 packet; for another example, if the first path is a SRv6 tunnel, the first SRv6 packet may be encapsulated according to the first path, and SRv encapsulation may be performed on the basis of the first SRv6 packet; for another example, if the first path is an IPv6 tunnel, the first SRv6 packet may be encapsulated according to the first path, and the IPv6 header corresponding to the first path may be encapsulated on the basis of the first SRv6 packet.
The ingress node of the first path is a first PE device, the egress node of the first path is a second PE device, and the destination host of the first SRv packet accesses the operator network through the second PE device.
As an example, the association relationship between the first indication information, the first transmission service type and the first bandwidth control policy is stored on the first PE device. Step 605 may include: the first PE device obtains first indication information from the first SRv6 message, searches a first transmission service type corresponding to the first indication information in the first SRv6 message from the locally stored association relationship, and determines a first path which starts from the first PE device and satisfies the first transmission service type in the operator network. Then, the first PE device searches for a first bandwidth control policy corresponding to the first indication information in the first SRv message from the locally stored association relationship. The first PE device forwards the first SRv message to the second PE device according to the first path based on the first bandwidth control policy.
In one possible implementation, the first PE device stores the bandwidth control policy using an access control list. Step 605 may include: the first PE device receives the first SRv message, the first PE device obtains first indication information from a destination IP field of the first SRv message, searches a first transmission service type corresponding to the first indication information in the first SRv message from a locally stored association relationship, and determines a first path which starts from the first PE device and meets the first transmission service type in an operator network. Then, the first PE device matches the first bandwidth control policy corresponding to the first indication information by using the access control list, and forwards the first SRv message to the second PE device according to the first path according to the traffic behavior of the first bandwidth control policy.
In the above implementation manner, the first PE device needs to have ACL resources, and if the specification of the ACL resources of the first PE device is larger, the indication information stored in the first PE device in the above implementation manner, which can support the selection function of the bandwidth control policy, is more.
In another possible implementation, the first PE device stores the bandwidth control policy using SID list, routing information base table, or forwarding information base table. Step 605 may include: the first PE device receives the first SRv message, the first PE device obtains first indication information from a destination IP field of the first SRv message, searches a first transmission service type corresponding to the first indication information in the first SRv message from a locally stored association relationship, and determines a first path which starts from the first PE device and meets the first transmission service type in an operator network. Then, the first PE device matches the first bandwidth control policy corresponding to the first indication information by using the SID list, the routing information base table or the forwarding information base table, and forwards the first SRv6 message to the second PE device according to the first path according to the traffic behavior of the first bandwidth control policy.
In the above implementation manner, the first PE device needs to have SID list or FIB resources, and if the specification of the SID list or FIB resources of the first PE device is large, the indication information stored in the first PE device and capable of supporting the selection function of the bandwidth control policy in the above implementation manner is more.
Therefore, the access control list, the SID list, the routing information base table or the forwarding information base table can be used as an association relation table for storing the association relation between the indication information and the bandwidth control policy, and the bandwidth control policy corresponding to the indication information and the association relation between the indication information and the bandwidth control policy can be flexibly selected and used according to the size of ACL resources, SID list resources or FIB resources of the PE equipment.
For step 605, the first PE device forwards the second SRv packet based on the first bandwidth control policy, which may be that the first PE device determines an effective length of the first SRv6 packet, if the effective length of the first SRv6 packet conforms to the first bandwidth control policy, sends the first SRv packet to the next hop device, and if the effective length of the first SRv6 packet does not conform to the first bandwidth control policy, discards the first SRv6 packet.
The first way to determine the effective length of the first SRv message is that of the first SRv message, which is the length of the message containing the segment routing header. For example, the length of the first SRv6 packet is 1500 bytes, and the transmission rate of the first SRv6 packet is 416 packets per second (english: packets per Second, abbreviated: pps) and 500pps, respectively, according to cir=5000 kbps and qir=6000 kbps in the bandwidth control policy qt 1.
The second way to determine the effective length of the first SRv message is to strip the segment routing header from the first SRv message. For example, the length of the first SRv message is 1500 bytes, the length of the message after stripping the 24-byte segment routing header is 1476 bytes, and the transmission rate of the first SRv message is 423pps and 508pps according to cir=5000 kbps and qir=6000 kbps in the bandwidth control policy qt 1.
Alternatively, in an implementation where the indication information is a SID, the SRv SID in this embodiment may conform to the Delete On Demand style and the Only One Segment Left style. The Delete On Demand style refers to the case that the PE device updates the outer destination IP address of the packet to the last SID in the SID list and strips the segment routing header when the outer destination IP address of the received SRv packet is SRv SID and the next SID is the last SID in the SID list (the value of the SL field is 1). Only One Segment Left style means that the PE device processes only SRv messages with SL field value equal to 1, and discards SRv messages with SL field value greater than 1.
If SRv SID in this embodiment is Only One Segment Left style, it may be restricted that the first SRv6 packet of the tenant only carries an SID representing the destination device of the packet sent by the tenant in addition to the SID for indicating the bandwidth control policy of the first SRv packet, so as to avoid that the operation corresponding to the Delete On Demand style cannot be executed due to the fact that the packet with a value of SL field greater than 1 is sent by the tenant to the first PE device, and reduce the packet transmission overhead of the user, avoid occupying more bandwidth limits of the tenant, and ensure the actual available bandwidth of the tenant.
In the foregoing embodiment, the processing of the first SRv6 packet of the first tenant by the first PE device is only an example provided in the embodiment of the present application, and in another implementation manner, the first PE device may also process packets of other tenants. For example, the first PE device obtains SRv6 packet, and the second indication information included in SRv6 packet is used to indicate the second transport service type of the second tenant, so that the first PE device processes the second SRv6 packet based on the second bandwidth control policy associated with the second indication information. 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 are different bandwidth control policies or the same bandwidth control policy, so that charging operation can be flexibly performed for different transmission services of different tenants.
In addition, the embodiment of the application further provides a data transmission device 700, which is shown in fig. 7. Fig. 7 is a schematic structural diagram of a data transmission device 700 according to an embodiment of the present application. The data transmission apparatus 700 is applied to a first user side device belonging to a first tenant, and the apparatus 700 may include: an acquisition module 701 and a forwarding module 702. The apparatus 700 may be used to perform the methods of the above embodiments, e.g., steps 601-605.
The obtaining module 701 is configured to obtain a first SRv6 packet, where the first SRv6 packet includes first indication information, and the first indication information indicates a first transmission service type of a first tenant to an operator network.
The forwarding module 702 is configured to process the first SRv6 packet based on a first bandwidth control policy associated with the first indication information.
In one implementation, the destination address of the first SRv message is the first indication.
In one implementation, the first indication information is provided in an IPv6 extension header.
In one implementation, the first indication information is a first SRv SID, the first SRv SID is a destination address of the first SRv6 message, and the first SRv SID is a SID allocated by the first PE device for the first tenant in a per-tenant per-service manner.
In one implementation, before acquiring the first SRv6 packet, the forwarding module 702 is further configured to: determining a first bandwidth control strategy according to the association relation between the first indication information and the first bandwidth control strategy
In one implementation, the association relationship 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.
In one implementation, the association table includes an access control list, a local SID table, a routing information base table, or a forwarding information base table of the first PE device.
In one implementation, the forwarding module 702 is further configured to, prior to forwarding the first SRv6 packet based on the first bandwidth control policy: inquiring a first bandwidth control strategy in the association relation table according to the first indication information.
In one implementation, the first bandwidth control policy includes a committed access rate, the committed access rate including a committed rate and/or a peak rate text.
In one implementation, the first bandwidth control is based on a length of a payload of the first SRv message.
In one implementation, the forwarding module 702 is specifically configured to: determining a first transmission path corresponding to the first transmission service type according to the first indication information; based on a first bandwidth control strategy and a first transmission path, forwarding a first SRv message, wherein an input node of the first transmission path is a first PE device, an output node of the first transmission path is a second PE device, and a destination node of the second first SRv message is accessed to an operator network through the second PE device.
In one implementation, the value of the segment remainder of the first SRv message is greater than 1, and the forwarding module 702 is specifically configured to: the first SRv message is discarded.
In one implementation, the value of the segment remainder of the first SRv message is equal to 1, and the forwarding module 702 is specifically configured to: forwarding the first SRv message.
In one implementation, the obtaining module 701 is further configured to: acquiring a second SRv message, wherein the second SRv message includes second indication information for indicating a second bandwidth control policy of a transmission service type of the second SRv6 message; the forwarding module is further configured to: forwarding the second SRv message based on the second bandwidth control policy.
For example, the second tenant and the first tenant are the same tenant, the second transport service type and the first transport service type are different transport service types, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies.
For another example, the second indication information is a second SRv SID, the second SRv SID is a destination address of the second SRv6 packet, and the second SRv SID is a SID allocated by the first PE device to the second tenant according to a per-tenant service manner.
Optionally, the obtaining module 701 is further specifically configured to: and determining a second bandwidth control strategy according to the association relation between the second indication information and the second bandwidth control strategy.
In one implementation, the first PE device stores an association of the second indication information and the second bandwidth control policy.
The specific implementation manner and the achieved effect of the data transmission device 700 provided in the embodiment of the present application may be refer to fig. 6 and the related description, which are not repeated here.
In addition, the embodiment of the application further provides a network device 800, and referring to fig. 8, fig. 8 is a schematic structural diagram of the network device 800 provided in the embodiment of the application. The network device 800 may be used to perform the data transmission method in the above embodiments.
As shown in fig. 8, 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 processor (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of CPU and NP. The processor may also be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD) or a combination thereof (English: programmable logic device). The PLD may be a complex programmable logic device (English: complex programmable logic device, abbreviated: CPLD), a field programmable gate array (English: field-programmable gate array, abbreviated: FPGA), a general-purpose array logic (English: generic array logic, abbreviated: GAL), or any combination thereof. Processor 810 may refer to one processor or may include multiple processors. Memory 820 may include volatile memory (English) such as random-access memory (RAM); the memory may also include a nonvolatile memory (english: non-volatile memory), such as a read-only memory (ROM), a flash memory (english: flash memory), a hard disk (HDD) or a Solid State Disk (SSD); memory 820 may also include a combination of the above types of memory. The memory 820 may refer to one memory or may include a plurality of memories. In one embodiment, the memory 820 stores computer readable instructions, where the computer readable instructions include a plurality of software modules, for example, the first processing module 821 and the second processing module 822, and may correspond to one of the function modules of the acquisition module 701 and the forwarding module 702 in the data transmission device 700. The processor 810, upon execution of the various software modules, may perform the corresponding operations as directed by the various software modules. In this embodiment, the operations performed by one software module actually refer to operations performed by the processor 810 according to instructions of the software module. For example, the "acquire first SRv message" executed by the first processing module 821 may actually refer to "acquire first SRv message" executed by the processor 810 according to the instruction of the first processing module 821, and at this time, the first processing module 821 may correspond to the acquisition module 701 in the data transmission apparatus 700.
In one example, the network device 800 may perform the data transmission method as shown in fig. 6 in the above embodiment, when the network device 800 is used to perform the data transmission method in the above embodiment: the processor 810 is configured to perform all processing related operations in the data transmission method. For example, the processor 810 is configured to process the first SRv6 packet to obtain a second SRv6 packet, and select, according to the first indication information, a first path corresponding to the first transport service type to forward the second SRv6 packet based on the first bandwidth control policy.
In addition, the embodiment of the application further provides a data transmission system 900, which is shown in fig. 9. Fig. 9 is a schematic structural diagram of a data transmission system 900 according to 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 configured to perform an operation implemented by the first PE device.
The first user side device 902 may be, for example, the user side device 11 in fig. 1, or the host 21 or the CPE 23 in fig. 5, for performing the operations performed by the first user side device.
The specific implementation and effects achieved by the communication system 900 can be seen from the above description of the data transmission method.
The present application also provides a computer-readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform any one or more of the operations of the method of any one of the preceding embodiments.
The present application also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform any one or more of the operations of the method of any one of the preceding embodiments.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, e.g., the division of units is merely a logical service division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each service unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software business units.
The integrated units, if implemented in the form of software business units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product 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 perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Those of skill in the art will appreciate that in one or more of the examples described above, the services described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the services may be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The foregoing embodiments have been provided for the purpose of illustrating the objects, technical solutions and advantageous effects of the present application in further detail, and it should be understood that the foregoing embodiments are merely exemplary embodiments of the present application.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims (42)
1. A data transmission method, applied to a first provider edge PE device, comprising:
acquiring a first segment routing SRv message based on a sixth version of internet protocol, wherein the first SRv message comprises first indication information indicating a first transmission service type of a first tenant to an operator network;
the first SRv message is processed based on a first bandwidth control policy associated with the first indication information.
2. The method of claim 1, wherein the destination address of the first SRv message carries the first indication information.
3. The method of claim 1, wherein the first indication information is set in an IPv6 extension header of the first SRv message.
4. The method of claim 1, wherein the first indication information is a first SRv6 SID, the first SRv SID is a destination address of the first SRv6 message, and the first SRv SID is a SID allocated by the first PE device per tenant per service for the first tenant.
5. The method according to any one of claims 1-4, wherein prior to obtaining the first SRv message, the method further comprises:
And determining the first bandwidth control strategy according to the association relation between the first indication information and the first bandwidth control strategy.
6. The method of claim 5, wherein the association comprises a correspondence of the first indication information and the first transport service type, and a correspondence of the first transport service type and the first bandwidth control policy.
7. The method according to claim 5 or 6, wherein the first PE device stores an association relationship between the first indication information and the first bandwidth control policy.
8. The method of claim 7, wherein the association is stored in an access control list, a local segment identification SID table, a routing information base table, or a forwarding information base table of the first PE device.
9. The method of any of claims 1-8, wherein the processing the first SRv message based on a first bandwidth control policy associated with the first indication information comprises:
inquiring the first bandwidth control strategy according to the first indication information.
10. The method according to any of claims 1-9, wherein the first bandwidth control policy comprises a committed access rate, CAR, comprising a committed rate and/or a peak rate.
11. The method of claim 10, wherein the first bandwidth control is based on a length of a payload of the first SRv message.
12. The method of any of claims 1-11, wherein the processing the first SRv message based on a first bandwidth control policy associated with the first indication information comprises:
determining a first transmission path corresponding to the first transmission service type according to the first indication information;
forwarding the first SRv message based on the first bandwidth control policy and the first transmission path, wherein an input node of the first transmission path is the first PE device, an output node of the first transmission path is the second PE device, and a destination node of the second first SRv message accesses an operator network through the second PE device.
13. The method of any of claims 1-12, wherein a value of a segment remainder of the first SRv message is greater than 1, the processing the first SRv message based on a first bandwidth control policy associated with the first indication information comprising:
discarding the first SRv message.
14. The method of any of claims 1-12, wherein a value of a segment remainder of the first SRv6 message is equal to 1, the processing the first SRv6 message based on the first bandwidth control policy comprising:
Forwarding the first SRv message.
15. The method according to any one of claims 1-14, further comprising:
acquiring a second SRv6 message, wherein the second SRv6 message comprises second indication information for indicating a second transmission service type of a second tenant;
the second SRv message is processed based on a second bandwidth control policy associated with the second indication information.
16. The method of claim 15, wherein the second tenant and the first tenant are the same tenant, the second transport service type and the first transport service type are different transport service types, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies.
17. The method of claim 15, wherein the second tenant and the first tenant are different tenants, the second transport service type and the first transport service type are the same transport service type, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies.
18. The method of any of claims 15-17, wherein the second indication information is a second SRv SID, the second SRv SID is a destination address of the second SRv6 message, and the second SRv SID is a SID allocated by the first PE device per tenant per service for the second tenant.
19. The method according to any one of claims 15-18, wherein prior to obtaining the second SRv message, the method further comprises:
and determining the second bandwidth control strategy according to the association relation between the second indication information and the second bandwidth control strategy.
20. The method of claim 19, wherein the first PE device stores an association of the second indication information and the second bandwidth control policy.
21. A data transmission apparatus, configured to be disposed in a first provider edge PE device, the apparatus comprising:
an obtaining module, configured to obtain a first segment routing SRv packet based on a sixth version of internet protocol, where the first SRv packet includes first indication information, where the first indication information indicates a first transmission service type of a first tenant to an operator network;
and a forwarding module, configured to process the first SRv packet based on a first bandwidth control policy associated with the first indication information.
22. The apparatus of claim 21, wherein a destination address of the first SRv message carries the first indication information.
23. The apparatus of claim 21, wherein the first indication information is set in an IPv6 extension header of the first SRv message.
24. The apparatus of claim 21, wherein the first indication information is a first SRv6 SID, the first SRv SID is a destination address of the first SRv6 message, and the first SRv SID is a SID assigned to the first tenant by the first PE device per tenant per service.
25. The apparatus of any one of claims 21-24, wherein the forwarding module, prior to obtaining the first SRv6 message, is further configured to:
and determining the first bandwidth control strategy according to the association relation between the first indication information and the first bandwidth control strategy.
26. The apparatus of claim 25, wherein the association comprises a correspondence of the first indication information and the first transport service type, and a correspondence of the first transport service type and the first bandwidth control policy.
27. The apparatus according to claim 25 or 26, wherein the first PE device stores an association between the first indication information and the first bandwidth control policy.
28. The apparatus of claim 27, wherein the association is stored in an access control list, a local segment identification SID table, a routing information base table, or a forwarding information base table of the first PE device.
29. The apparatus according to any one of claims 21-28, wherein the forwarding module is specifically configured to:
inquiring the first bandwidth control strategy according to the first indication information.
30. The apparatus according to any of claims 21-29, wherein the first bandwidth control policy comprises a committed access rate, CAR, comprising a committed rate and/or a peak rate.
31. The apparatus of claim 30, wherein the first bandwidth control is based on a length of a payload of the first SRv message.
32. The apparatus according to any one of claims 21-31, wherein the forwarding module is specifically configured to:
determining a first transmission path corresponding to the first transmission service type according to the first indication information;
forwarding the first SRv message based on the first bandwidth control policy and the first transmission path, wherein an input node of the first transmission path is the first PE device, an output node of the first transmission path is the second PE device, and a destination node of the second first SRv message accesses an operator network through the second PE device.
33. The apparatus according to any of claims 21-32, wherein the value of the segment residuals of the first SRv message is greater than 1, and the forwarding module is specifically configured to:
discarding the first SRv message.
34. The apparatus according to any of claims 21-32, wherein the value of the segment residuals of the first SRv message is equal to 1, and the forwarding module is specifically configured to:
forwarding the first SRv message.
35. The apparatus of any one of claims 21-34, wherein the acquisition module is further configured to: acquiring a second SRv6 message, wherein the second SRv6 message comprises second indication information for indicating a second transmission service type of a second tenant;
the forwarding module is further configured to: the second SRv message is processed based on a second bandwidth control policy associated with the second indication information.
36. The apparatus of claim 35, wherein the second tenant and the first tenant are the same tenant, the second transport service type and the first transport service type are different transport service types, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies.
37. The apparatus of claim 36, wherein the second tenant and the first tenant are different tenants, the second transport service type and the first transport service type are the same transport service type, and the second bandwidth control policy and the first bandwidth control policy are different bandwidth control policies.
38. The apparatus of any one of claims 35-37, wherein the second indication information is a second SRv SID, the second SRv SID is a destination address of the second SRv6 message, and the second SRv SID is a SID allocated by the first PE device per tenant per service for the second tenant.
39. The apparatus according to any one of claims 35-38, wherein the acquisition module is further specifically configured to: and determining the second bandwidth control strategy according to the association relation between the second indication information and the second bandwidth control strategy.
40. The apparatus of claim 39, wherein the first PE device stores an association of the second indication information and the second bandwidth control policy.
41. A network device comprising a memory and a processor, the memory configured to store instructions; the method of any of the preceding claims 1-20 when executed by the processor.
42. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a computer program or instructions which, when run on a processor, performs the method of any of claims 1-20.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210912439.6A CN117527668A (en) | 2022-07-30 | 2022-07-30 | Data transmission method, device, network equipment and storage medium |
| PCT/CN2023/102953 WO2024027378A1 (en) | 2022-07-30 | 2023-06-27 | Data transmission method and apparatus, and network device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210912439.6A CN117527668A (en) | 2022-07-30 | 2022-07-30 | Data transmission method, device, network equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117527668A true CN117527668A (en) | 2024-02-06 |
Family
ID=89744415
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210912439.6A Pending CN117527668A (en) | 2022-07-30 | 2022-07-30 | Data transmission method, device, network equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN117527668A (en) |
| WO (1) | WO2024027378A1 (en) |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105337894B (en) * | 2014-06-24 | 2018-11-30 | 华为技术有限公司 | It is a kind of to provide the devices, systems, and methods of service quality QoS for service message |
| EP3994848A1 (en) * | 2019-07-31 | 2022-05-11 | Huawei Technologies Co., Ltd. | Transporting mtnc-id over srv6-header for 5g transport |
| CN113949645A (en) * | 2020-07-15 | 2022-01-18 | 华为技术有限公司 | Service processing method, device, equipment and system |
-
2022
- 2022-07-30 CN CN202210912439.6A patent/CN117527668A/en active Pending
-
2023
- 2023-06-27 WO PCT/CN2023/102953 patent/WO2024027378A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024027378A1 (en) | 2024-02-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112262553B (en) | Apparatus and method for tracking packets in a packet processing pipeline of a software defined network switch | |
| EP3624408B1 (en) | Method for generating forwarding table entry, controller, and network device | |
| EP4102785A1 (en) | Message processing method and apparatus, and network device and storage medium | |
| US8867349B2 (en) | Regulation of network traffic in virtual private networks | |
| US7486674B2 (en) | Data mirroring in a service | |
| CN112311675B (en) | Guaranteed bandwidth for Segment Routing (SR) paths | |
| CN112311673B (en) | Use and processing per-slice segment identifiers in networks employing segment routing | |
| US10412008B2 (en) | Packet processing method, apparatus, and system | |
| KR20220052343A (en) | Data transmission control method and device | |
| CN113347091B (en) | Flexible algorithm aware border gateway protocol prefix segment route identifier | |
| CN112019433B (en) | Message forwarding method and device | |
| EP3905609A1 (en) | Service data forwarding method, network device, and network system | |
| US20140351812A1 (en) | Recording medium, management device, and network system | |
| EP4113919A1 (en) | Method for forwarding message in srv6 service function chain, sff and sf device | |
| CN113395735B (en) | Message transmission method, device and network equipment | |
| US20240098019A1 (en) | Packet Processing Method and Related Device | |
| US20230412508A1 (en) | Packet processing method and related apparatus | |
| WO2020114083A1 (en) | Method and apparatus for processing ioam information | |
| CN117527668A (en) | Data transmission method, device, network equipment and storage medium | |
| CN114258109A (en) | Routing information transmission method and device | |
| CN114422415A (en) | Egress node processing flows in segmented routing | |
| WO2023231438A1 (en) | Message sending method, network device and system | |
| US20220174009A1 (en) | Segment Routing-Based Data Transmission Method and Apparatus | |
| WO2024007762A1 (en) | Route publishing method, and communication method and apparatus | |
| CN114143142A (en) | Message transmission method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |