CN112995030A

CN112995030A - Business processing method and device, storage medium and electronic device

Info

Publication number: CN112995030A
Application number: CN202110169525.8A
Authority: CN
Inventors: 刘尧
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2021-02-07
Filing date: 2021-02-07
Publication date: 2021-06-18
Also published as: WO2022166691A1

Abstract

The embodiment of the invention provides a service processing method, a service processing device, a storage medium and an electronic device, wherein the method comprises the following steps: acquiring a target slice identifier corresponding to the target service according to the corresponding relation between the service and the slice identifier; determining a target SR path corresponding to the target slice identifier according to the corresponding relation between the slice identifier and the segment routing SR path; the target service is forwarded according to the target SR path, the problems that SR Po i cy with the same head end, color and end point cannot be distinguished and identified and requirements of services of different slices related to different SR paths cannot be well met in network slices realized based on SR in the related technology can be solved, the services determine the SR paths through the slice identifiers and are forwarded, and the slice identifiers are carried in the SR paths, so that the head nodes can be helped to select the SR paths in specific slices.

Description

Business processing method and device, storage medium and electronic device

Technical Field

The embodiment of the invention relates to the field of communication, in particular to a service processing method, a service processing device, a storage medium and an electronic device.

Background

Segment Routing (SR) is a Routing method based on a source address, and a Segment Routing Header (SRheader) is carried in a packet Header of an existing Multi-Protocol Label Switching (MPLS) network or an internet Protocol Version 6 (IPv 6) packet Header, and a series of indication operations (also called Segment operations) are carried in an SRH for Routing and transmitting data in the network.

The basis of SR traffic engineering is defined in draft: SR Policy. SR Policy introduces a new model to implement traffic engineering through segment list.

SR Policy is identified by the following triplets:

head end (Headend): where SR Policy is generated/implemented;

color (Color): is an arbitrary 32-bit value, an important property of SR Policy, which generally represents intent, indicates a particular way to reach an endpoint (e.g., low latency, etc.);

endpoint (Endpoint): the end point of SR Policy is an IPv4/IPv6 address.

At a given head-end node, SR Policy is identified by a (color, end-point) tuple.

The Candidate Path for SR Policy (Candidate Path) represents a particular way to transport traffic from the corresponding SR Policy head-end to the end-points. Each candidate path has a Preference value (Preference). The higher the preference value of the path, the more preferred. SR Policy has at least one candidate path, where the active candidate path with the highest preference value is the active candidate path.

Each candidate path may have one or more Segment lists (Segment lists), each Segment List having an associated load balancing Weight (Weight) for load balancing.

The 5G Network architecture proposes a breakthrough concept of Network Slicing (Network Slicing). Through network slicing, an operator can construct a plurality of special, virtualized and mutually isolated logic networks on a general physical platform to meet different requirements of different customers on network capacity. Network slices are virtual network structures that are logically independent through the combination of network functions. The Identity (ID) of a network slice may be referred to simply as a slice Identity or slice ID.

SR is one of the options to implement network slicing. In the SR network, different segment identifiers (abbreviated as SIDs) may be allocated to resources (nodes, links, etc.) belonging to different slices, and then paths are calculated within the slices and the SIDs are selected, so that SR paths for different slices can be obtained.

In a network slice realized based on the SR, the prior art cannot distinguish and identify SR policies with the same head end, color, and end point, and cannot well meet the requirement that services of different slices are associated to different SR paths.

For the problem that SR policies with the same head end, color and end point cannot be distinguished and identified in the network slice realized based on SR in the related art, and the requirement that the services of different slices are associated to different SR paths cannot be well met, no solution has been proposed.

Disclosure of Invention

Embodiments of the present invention provide a service processing method, an apparatus, a storage medium, and an electronic apparatus, so as to at least solve the problem that SR policies with the same head end, color, and end point cannot be distinguished and identified in a network slice implemented based on SR in the related art, and the requirement that services of different slices are associated with different SR paths cannot be well satisfied.

According to an embodiment of the present invention, there is provided a service processing method, including:

acquiring a target slice identifier corresponding to the target service according to the corresponding relation between the service and the slice identifier;

determining a target SR path corresponding to the target slice identifier according to the corresponding relation between the slice identifier and the segment routing SR path;

and forwarding the target service according to the target SR path.

According to another embodiment of the present invention, there is also provided a service processing apparatus, including:

the first acquisition module is used for acquiring a target slice identifier corresponding to a target service according to the corresponding relation between the service and the slice identifier;

the determining module is used for determining a target SR path corresponding to the target slice identifier according to the corresponding relation between the slice identifier and the segment routing SR path;

and the forwarding module is used for forwarding the target service according to the target SR path.

According to a further embodiment of the present invention, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to perform the steps of any of the above-described method embodiments when executed.

According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.

According to the embodiment of the invention, the target slice identifier corresponding to the target service is obtained through the corresponding relation between the service and the slice identifier; determining a target SR path corresponding to the target slice identifier according to the corresponding relation between the slice identifier and the segment routing SR path; the target service is forwarded according to the target SR path, so that the problems that in a network slice realized based on SR in the related technology, SR policies with the same head end, color and end point cannot be distinguished and identified, and the requirements of the services of different slices associated with different SR paths cannot be well met can be solved.

Drawings

Fig. 1 is a block diagram of a hardware structure of a mobile terminal of a service processing method according to an embodiment of the present invention;

FIG. 2 is a flow chart of a method of business processing according to an embodiment of the invention;

fig. 3 is a flowchart of a method of determining a traffic forwarding path according to the present embodiment;

fig. 4 is a schematic diagram of a BGP-issued SR path carrying a slice identifier according to this embodiment;

fig. 5 is a schematic diagram of a BGP-issued SR path carrying a slice identifier according to this embodiment;

fig. 6 is a schematic diagram of issuing a slice identifier corresponding to a candidate path through PCEP according to this embodiment;

FIG. 7 is a schematic diagram of a slice topology according to the present embodiment;

FIG. 8 is a schematic diagram of an extension through BGP-LS according to the present embodiment;

FIG. 9 is a flow diagram of message interaction between a PCE and a PCC according to the present embodiment;

fig. 10 is a flowchart of slice path end-to-end protection according to the present embodiment;

FIG. 11 is a schematic diagram of multiple SR policies providing protection according to the present embodiment;

FIG. 12 is a diagram of the same SR Policy providing protection according to this embodiment;

fig. 13 is a block diagram of a traffic processing apparatus according to the present embodiment.

Detailed Description

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings in conjunction with the embodiments.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

The method embodiments provided in the embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking a mobile terminal as an example, fig. 1 is a hardware structure block diagram of a mobile terminal of a service processing method according to an embodiment of the present invention, and as shown in fig. 1, the mobile terminal may include one or more processors 102 (only one is shown in fig. 1) (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 104 for storing data, where the mobile terminal may further include a transmission device 106 for a communication function and an input/output device 108. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration, and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The memory 104 can be used for storing computer programs, for example, software programs and modules of application software, such as computer programs corresponding to the service processing method in the embodiment of the present invention, and the processor 102 executes various functional applications and service chain address pool slicing processing by running the computer programs stored in the memory 104, that is, implementing the above-mentioned method. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the mobile terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a Network adapter (NIC), which can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

In this embodiment, a service processing method operating in the mobile terminal or the network architecture is provided, and fig. 2 is a flowchart of the service processing method according to the embodiment of the present invention, as shown in fig. 2, the flow includes the following steps:

step S202, obtaining a target slice identifier corresponding to a target service through the corresponding relation between the service and the slice identifier;

step S204, determining a target SR path corresponding to the target slice identifier according to the corresponding relation between the slice identifier and the segment routing SR path;

step S206, forwarding the target service according to the target SR path.

Through the steps S202 to S206, a target slice identifier corresponding to the target service is obtained through the correspondence between the service and the slice identifier; determining a target SR path corresponding to the target slice identifier according to the corresponding relation between the slice identifier and the segment routing SR path; the target service is forwarded according to the target SR path, so that the problems that in a network slice realized based on SR in the related technology, SR policies with the same head end, color and end point cannot be distinguished and identified, and the requirements of the services of different slices associated with different SR paths cannot be well met can be solved.

In an exemplary embodiment, the step S204 may specifically include:

if the target slice identifier comprises a plurality of slice identifiers, determining a plurality of SR paths corresponding to the plurality of slice identifiers according to the corresponding relation between the slice identifiers and the segment routing SR paths, wherein the target SR paths comprise a plurality of SR paths;

selecting an SR path with the highest priority according to the priorities of the slices corresponding to the slice identifications;

and determining the SR path with the highest priority as a main path, and determining other SR paths except the SR path with the highest priority in the plurality of SR paths as standby paths.

Correspondingly, the step S206 may specifically include:

forwarding the target service according to the main path under the condition that the main path is valid, specifically, selecting one target path from a plurality of candidate paths corresponding to the main path, and forwarding the target service according to a segment list contained in the target path;

and forwarding the target service according to the standby path when the main path fails, specifically, selecting one target path from a plurality of candidate paths corresponding to the standby path, and forwarding the target service according to a segment list contained in the target path.

In an optional embodiment, the corresponding relationship between the slice identifier and an SR path is obtained, further, the corresponding relationship between the locally configured slice identifier and the SR path is obtained, the corresponding relationship between the slice identifier and the SR path remotely configured by a configuration node is obtained, and optionally, the corresponding relationship between the slice identifier and the SR path is sent to the controller, where the SR path includes a candidate path corresponding to the SR policy and the SR policy, and the SR path carrying the slice identifier is sent to the controller specifically through NETCONF, YANG, BGP-LS (BGP Link State, BGP Link State protocol) or PCEP;

the method includes the steps of obtaining the SR path which is issued by a controller and carries the slice identifier, obtaining the corresponding relation between the slice identifier and the SR path, and further obtaining the SR strategy which is issued by the controller and carries the slice identifier or a candidate path corresponding to the SR strategy, wherein the SR path comprises the SR strategy and the candidate path corresponding to the SR strategy.

In this embodiment, the SR policy carrying the Slice identifier or the candidate path corresponding to the SR policy issued by the BGP may be issued through BGP, PCEP, and NETCONF/YANG, and specifically, the BGP is configured to carry the Slice identifier corresponding to the SR policy through an extended BGP NLRI (Network Layer accessibility Information), or carry the Slice identifier corresponding to the candidate path corresponding to the SR policy through an extended Slice Sub-TLV (Type, Length, Value, Type, Length, Value);

acquiring the SR strategy which is issued by the PCEP and carries the Slice identifier or a candidate path corresponding to the SR strategy, wherein the PCEP is used for carrying the Slice identifier corresponding to the candidate path corresponding to the SR strategy through a newly added Slice ID TLV;

and acquiring the SR strategy which is issued by NETCONF or YANG and carries the slice identifier or a candidate path corresponding to the SR strategy, wherein NETCONF is a network management protocol, and YANG is a data modeling language of NETCONF.

In the SDN scenario, the controller may send SR Policy to a head node (head node) of an SR path actively or on demand, and currently, the sending modes include bgp (border Gateway protocol), pcep (path Computation Element protocol), netconf (network configuration protocol), and yang (yet antenna Next Generation data modulation).

Fig. 3 is a flowchart of a method for determining a service forwarding path according to the present embodiment, and as shown in fig. 3, the method includes the following steps:

the slice identifier is used to identify a network slice, and according to a technical means for specifically implementing the network slice, the slice identifier may have different meanings and forms, and one identifier may be regarded as a slice identifier as long as it can uniquely distinguish the slice within a limited range, such as within an Interior Gateway Protocol (IGP), within a full network range, and the like. For example, in draft-dong-6man-enhanced-vpn-vtn-ID, the partition of the slice virtual topology is performed according to IGP Multi-topology (Multi-topology), and the slice identifier may be a Multi-topology ID; if the slicing is divided according to the IGP multiprocess, the slice identifier may be an IGP process number; if the slice is globally identified according to a global identification AII (advanced instant identifier) in the draft-pen-lsr-network-sliding, the AII serves as the slice identifier.

S302, the node acquires the corresponding relation between the slice identifier and the SR path.

The relationship between the node acquiring the SR path and the slice identifier includes, but is not limited to, the following ways:

through configuring nodes, the SR path and the slice identifier are associated, and the configuration mode comprises node local configuration and remote configuration;

when the controller issues the SR path to the node, the controller directly carries the slice identifier, and the issuing mode comprises Netconf/YANG, BGP, PCEP and the like. The SR path may be at SR Policy level or at candidate path level.

The slice identifier and SR Policy may be in a 1-to-1 or multiple-to-1 relationship, and the association method includes but is not limited to:

SR Policy is directly associated with the slice identifier, for example, the slice identifier is used as a new identifier attribute of SR Policy outside the header/endpoint/color. After the association is carried out in the mode, the slice attribute of the candidate path under the SR Policy inherits the SR Policy;

and associating the slice with the candidate path, and indirectly associating the slice with the SR Policy to which the candidate path belongs. If the candidate paths under the same SR Policy have different slice identities, the slice identity of SR Policy contains the slice identities of all its candidate paths.

S304, configuring the corresponding relation between the service on the corresponding node and the slice.

The corresponding relationship between the corresponding feature and the slice identifier may be configured by combining features of a single or multiple packets, such as a specific field (e.g., a source IP address, a destination IP address, a source MAC address, a destination MAC address, a flow label in an IPv6 packet header, etc.) of the port/Vlan/packet header, for example, the Vlan sub-interface 10 of the physical port a corresponds to the slice identifier 100. Other possible configuration modes further include configuring the correspondence between the service and the slice identifier with VPN granularity or routing process number granularity, configuring the slice identifier 100 corresponding to the VPN, or configuring the slice identifier 100 corresponding to the OSPF routing process 1.

S306, the node associates the service with the segment routing strategy through the slice identifier, and determines a forwarding path corresponding to the service.

One mode is that the SR Policy containing the same identification is determined through the slice identification, and then the matching is continued according to the conventional SR Policy drainage means, such as color, endpoint and the like, and the corresponding forwarding path is selected; for the situation that the slice identifier carried by each candidate path is different when the same SR Policy contains multiple candidate paths, the corresponding candidate path is further selected according to the slice identifier after the SR Policy is matched.

In the second way, SR Policy meeting the matching condition except for the slice identifier can be found according to the conventional drainage method, and then further path matching and selection can be performed according to the slice identifier.

Fig. 4 is a schematic diagram of the SR path delivered by BGP according to this embodiment carrying the Slice identifier, and as shown in fig. 4, compared with an NLRI in an existing SR Policy SAFI in a draft-ietf-idr-segment-routing-te-Policy, the extended manner of carrying the Slice identifier by the SR path delivered by BGP carries one more Slice ID information, which represents the Slice identifier corresponding to the SR Policy. The candidate paths in the NLRI have the same slice attribute as SR Policy.

Fig. 5 is a schematic diagram of a Slice identifier carried by an SR path issued by BGP according to this embodiment, and as shown in fig. 5, a Slice Sub-TLV is newly extended under BGP Tunnel Encapsulation Attribute by a second extension manner in which the SR path issued by BGP carries the Slice identifier, and represents a corresponding Slice identifier of an SR candidate path issued.

Fig. 6 is a schematic diagram of issuing a Slice identifier corresponding to a candidate Path through PCEP according to this embodiment, and as shown in fig. 6, a Slice ID TLV is newly added in an SR Policy Association Group object through an extension manner of issuing a Slice identifier corresponding to a candidate Path through PCEP, and an existing Path Computation Element (PCE for short) is extended to issue a scenario of a candidate Path to a Path Computation Client (PCC for short). The PCE sends a PCInitiate message of PCC to inform the PCC of instantiating a corresponding SR candidate path by the information provided by the PCE (if the SR Policy of the candidate path does not exist, a new SR Policy is also created), after a Slice ID TLV is added, the original instantiation process is not changed, but the SR Policy is changed from (color, end) identification to (color, end, Slice ID) identification.

Another possible way of issuing the Slice identifier corresponding to the SR path through the PCEP is to add an SR Policy precise path child Object (ERO) subobject, which includes color, end, and Slice ID attributes of the SR Policy and is carried when the SR path is issued, and directly describe the Slice identifier corresponding to the SR Policy.

If the controller issues the SR path by adopting a NETCONF protocol, corresponding slice identifiers need to be added in a modeling data YANG model of the NETCONF. In the SR Policy YANG model defined in draft-ietf-spring-SR-Policy-YANG, the slice identification field can be added to the SR Policy level in addition to the existing color and endpoint. The slice identifier field may be added to the candidate path level, in addition to the existing protocol-origin, or discriminator.

FIG. 7 is a schematic diagram of a slice topology according to the embodiment, as shown in FIG. 7, in the slice1 topology, from header H to end E, a controller calculates three SR policies, P1-red, P1-green and P1-blue respectively for color red (low latency), color green (high bandwidth) and color blue (low cost) requirements; similarly, within the slice 2 topology, the controller computes three SR policies, P2-red, P2-green, and P2-blue, for the same head-to-tail nodes and color.

On E, a route is advertised to H through BGP, and the content is (destination CE2, route color attribute red, next hop is end address). H, configuration, and the traffic coming in from the connection CE1 port belongs to slice 1.

CE1 sends traffic with the destination address CE 2. After receiving the flow, the H hits a BGP routing table according to the destination address, and the next hop of the flow is end, color red; judging a flow attribution slice1 according to a source port; therefore H is matched to P1-red according to endpoint and color within slice 1.

In some networking scenarios, there is a need for a node to report an SR path state on the node to a controller, for example, reporting through BGP-LS defined in draft-ietf-idr-te-lsp-distribution, or reporting through a NETCONF channel. After the controller issues the path carrying the slice identifier to the node, the following process may be further included:

and when the node reports the SR path state, the node carries the slice identifier corresponding to the SR path. Therefore, the controller can distinguish that two other reported attributes are the same (for SR Policy on the same node, endpoint and color), but belong to SR paths of different slices.

Fig. 8 is a schematic diagram of an extension by BGP-LS according to this embodiment, and as shown in fig. 8, one possible extension manner in BGP-LS is based on draft-ietf-idr-te-lsp-distribution, extended SR Policy conditional Path Descriptor TLV, in which a SLICE-ID field is newly added.

If the node reports the SR path by using a NETCONF protocol, a corresponding slice identifier needs to be added in a modeling data YANG model of the NETCONF. In the SR Policy YANG model defined in draft-ietf-spring-SR-Policy-YANG, the slice identification field can be added to the SR Policy level in addition to the existing color and endpoint. The slice identifier field may be added to the candidate path level, in addition to the existing protocol-origin, or discriminator.

In some networking scenarios, the controller may only be responsible for calculating a specific path, and does not sense the correspondence between the path and the slice. In a scenario where the controller does not perceive the slice and SR path correspondence, the following process may also be included:

s202, the node reports the corresponding relation between the controller slice and the SR path, and the reporting mode includes but is not limited to NETCONF, BGP-LS, PCEP and the like.

After the controller obtains the corresponding relationship, the controller can be used for the purposes of optimizing local route calculation logic and the like, such as preferentially processing route calculation requests belonging to important slices.

Similar to the above scheme, the SR path may be an SR Policy or a candidate path.

This example will be described with reference to PCEP as an example.

RFC8664 describes how PCC requests and how PCE issues SR Policy candidate paths, wherein the SR Policy candidate paths issued by the PCE only carry segment list information. In order to enable the PCC to report the candidate path and the attribute information of the SR Policy to which the PCC belongs to the PCE, an SR Policy Association Group object introduced in the draft-ietf-PCE-segment-routing-Policy-cp carries the attribute information.

As shown in fig. 6, a slice identifier TLV is added to the SR Policy Association Group object in an extended manner of carrying a slice identifier when candidate path in PCEP.

Fig. 9 is a flowchart of message interaction between PCEs and PCCs according to the present embodiment, as shown in fig. 9, including:

ST1, PCC requests path from PCE, carries constraint conditions such as time delay, bandwidth, etc.;

ST2, PCE calculates an SR path and sends it to PCC according to the constraint condition;

ST3, PCC sends information to PCE according to the acquired corresponding relation between slice identification and SR path, and carries SR candidate path information and slice identification information, and PCE acquires the corresponding relation after receiving the information.

Slice identification may be used to provide slice-based end-to-end path protection, and fig. 10 is a flowchart of slice path end-to-end protection according to this embodiment, as shown in fig. 10, including:

s1002, configuring nodes, associating a plurality of slice identifiers with one service, and explaining the priority of each slice;

s1004, according to the slice identifier, the service is associated to a plurality of SR paths, and according to the slice priority, the effective SR path with the highest priority is selected as a main path, and SR paths of other slices are backup paths;

and S1006, after the main path fails, the node is switched to a backup path under another slice.

The SR path may be SR Policy or a candidate path in SR Policy, that is, protection may be provided based on SR Policy, or slice protection may be provided based on candidate path, which is described below by way of example.

Fig. 11 is a schematic diagram of protection provided by multiple SR policies according to this embodiment, and as shown in fig. 11, for the same header, endpoint, and color (e.g., low latency), the controller calculates two SR policies, P1, and P2, which correspond to Slice identifiers Slice1 and Slice 2, respectively, and sends the Slice identifiers Slice1 and Slice 2 to the node H. Slice1 is a Slice corresponding to normal service, and Slice 2 is a special protection Slice. The SR Policy P1 issued contains two candidate paths CP1 and CP 2.

H is the head node of the path, and configuration is performed on H to associate the traffic S to two slices, Slice1, Slice 2, and configure Slice1 with the highest priority.

When the path of the service S is selected, P1 and P2 are selected according to the slice ID, and under the condition that other conditions are equal, P1 with higher slice priority is the main SR Policy, and according to the prior art, selection is performed in CP1 and CP2, for example, CP1 is selected as an effective path, forwarding is performed according to segment list contained in CP1, and CP2 is used as a backup.

After all segment lists in the CP1 in P1 fail, the path is switched to the CP2 to provide protection in the same slice, and when the CP2 fails, the SR Policy P1 fails, namely the forwarding path in the slice1 fails. Then H switches the transfer path of S into slice 2, and selects a path as P2 for transfer.

Fig. 12 is a schematic diagram of protection provided by the same SR Policy according to this embodiment, and as shown in fig. 12, for the same header, endpoint, and color (e.g., low latency), the controller calculates two SR candidate paths, CP1 and CP2, which respectively correspond to Slice identifiers Slice1 and Slice 2 and belong to the same SR Policy P.

H, when the path of the service S is selected, the SR Policy P is selected according to the slice ID, and further, a CP1 with higher slice priority is selected according to the slice identification carried by the candidate path in the SR Policy under the condition that other conditions are equal, and the CP1 carries out forwarding according to the segment list contained in the CP1, and the CP2 serves as a backup. After all segment lists in the CP1 fail, H considers that the path corresponding to the slice1 fails, switches to the CP2 corresponding to the backup slice 2, and switches to the slice 2 for forwarding.

According to another embodiment of the present invention, there is also provided a service processing apparatus, and fig. 13 is a block diagram of the service processing apparatus according to the present embodiment, as shown in fig. 13, the apparatus includes:

a first obtaining module 132, configured to obtain a target slice identifier corresponding to a target service according to a correspondence between the service and the slice identifier;

a determining module 134, configured to determine, according to a correspondence between a slice identifier and a segment routing SR path, a target SR path corresponding to the target slice identifier;

a forwarding module 136, configured to forward the target service according to the target SR path.

In an exemplary embodiment, the determination module 134 includes:

a first determining sub-module, configured to determine, if the target slice identifier includes multiple slice identifiers, multiple SR paths corresponding to the multiple slice identifiers according to a correspondence between the slice identifiers and segment routing SR paths, where the target SR path includes the multiple SR paths;

the selection submodule is used for selecting an SR path with the highest priority according to the priorities of the slices corresponding to the slice identifications;

and a second determining sub-module, configured to determine the SR path with the highest priority as a primary path, and determine other SR paths except the SR path with the highest priority in the plurality of SR paths as backup paths.

In an exemplary embodiment, the forwarding module 136 includes:

the first forwarding sub-module is used for forwarding the target service according to the main path under the condition that the main path is effective;

and the second forwarding sub-module is used for forwarding the target service according to the standby path under the condition that the main path fails.

In an exemplary embodiment, the first forwarding sub-module is further configured to select a target path from a plurality of candidate paths corresponding to the main path, and forward the target service according to a segment list included in the target path;

the second forwarding sub-module is further configured to select a target path from the multiple candidate paths corresponding to the standby path, and forward the target service according to a segment list included in the target path.

In an exemplary embodiment, the apparatus further comprises:

and the second acquisition module is used for acquiring the corresponding relation between the slice identifier and the SR path.

In an exemplary embodiment, the second obtaining module includes:

the first obtaining submodule is used for obtaining the corresponding relation between the locally configured slice identifier and the SR path;

the second obtaining submodule is used for obtaining the corresponding relation between the slice identifier remotely configured through the configuration node and the SR path;

and the third obtaining sub-module is used for obtaining the SR path which is issued by the controller and carries the slice identifier, and obtaining the corresponding relation between the slice identifier and the SR path.

In an exemplary embodiment, the third control sub-module is further configured to

And acquiring an SR strategy which is issued by a controller and carries the slice identifier or a candidate path corresponding to the SR strategy, wherein the SR path comprises the SR strategy and the candidate path corresponding to the SR strategy.

In an exemplary embodiment, the third control sub-module comprises:

a first obtaining unit, configured to obtain an SR policy that carries the Slice identifier and is issued by BGP or a candidate path corresponding to the SR policy, where the BGP is configured to carry the Slice identifier corresponding to the SR policy through an extended BGP NLRI, or carry the Slice identifier corresponding to the candidate path corresponding to the SR policy through an extended Slice Sub-TLV;

a second obtaining unit, configured to obtain the SR policy that carries the Slice identifier and is issued by a PCEP or a candidate path corresponding to the SR policy, where the PCEP is configured to carry the Slice identifier corresponding to the candidate path corresponding to the SR policy through a newly added Slice ID TLV;

and the third obtaining unit is used for obtaining the SR strategy which is issued by NETCONF or YANG and carries the slice identifier or the candidate path corresponding to the SR strategy.

In an exemplary embodiment, the apparatus further comprises:

and the sending submodule is used for sending the corresponding relation between the slice identifier and the SR path to the controller, wherein the SR path comprises the SR strategy and a candidate path corresponding to the SR strategy.

In an exemplary embodiment, the sending submodule is further configured to

And sending the SR path carrying the slice identifier to the controller through NETCONF, YANG, BGP-LS or PCEP.

Embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above-mentioned method embodiments when executed.

In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.

In an exemplary embodiment, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.

For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary embodiments, and details of this embodiment are not repeated herein.

It will be apparent to those skilled in the art that the various modules or steps of the invention described above may be implemented using a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and they may be implemented using program code executable by the computing devices, such that they may be stored in a memory device and executed by the computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into various integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for processing a service, the method comprising:

and forwarding the target service according to the target SR path.

2. The method of claim 1, wherein determining the target SR path corresponding to the target slice identifier according to the correspondence between the slice identifier and the Segment Routing (SR) path comprises:

3. The method of claim 2, wherein forwarding the target traffic according to the target SR path comprises:

forwarding the target service according to the main path under the condition that the main path is effective;

and forwarding the target service according to the standby path under the condition that the main path fails.

4. The method of claim 3,

forwarding the target traffic according to the primary path includes:

selecting a target path from a plurality of candidate paths corresponding to the main path, and forwarding the target service according to a segment list contained in the target path;

forwarding the target service according to the standby path comprises:

and selecting a target path from a plurality of candidate paths corresponding to the standby path, and forwarding the target service according to segment list contained in the target path.

5. The method according to any one of claims 1 to 4, further comprising:

and acquiring the corresponding relation between the slice identifier and the SR path.

6. The method of claim 5, wherein obtaining the slice identity to SR path correspondence comprises:

acquiring the corresponding relation between the locally configured slice identifier and the SR path;

acquiring a corresponding relation between the slice identifier remotely configured through a configuration node and the SR path;

and acquiring the SR path which is issued by the controller and carries the slice identifier, and acquiring the corresponding relation between the slice identifier and the SR path.

7. The method of claim 6, wherein obtaining the SR path carrying the slice identifier sent by a controller comprises:

8. The method of claim 7, wherein obtaining the SR policy carrying the slice identifier or the candidate path corresponding to the SR policy issued by the controller comprises:

acquiring an SR strategy which is issued by a Border Gateway Protocol (BGP) and carries the Slice identifier or a candidate path corresponding to the SR strategy, wherein the BGP is used for carrying the Slice identifier corresponding to the SR strategy through an extended BGP NLRI, or carrying the Slice identifier corresponding to the candidate path corresponding to the SR strategy through an extended Slice Sub-TLV;

acquiring the SR strategy which is issued by a path computation element protocol PCEP and carries the Slice identifier or a candidate path corresponding to the SR strategy, wherein the PCEP is used for carrying the Slice identifier corresponding to the candidate path corresponding to the SR strategy through a newly added Slice ID TLV;

and acquiring the SR strategy carrying the slice identifier issued by a network configuration protocol NETCONF or a next generation data model language YANG or a candidate path corresponding to the SR strategy.

9. The method of claim 6, further comprising:

and sending the corresponding relation between the slice identifier and the SR path to the controller, wherein the SR path comprises the SR strategy and a candidate path corresponding to the SR strategy.

10. The method of claim 9, wherein sending the correspondence of the slice identification to the SR path to the controller comprises:

and sending the SR path carrying the slice identifier to the controller through a network configuration protocol NETCONF, a next generation data model language YANG, a border gateway protocol link state protocol BGP-LS or a path computation element protocol PCEP.

11. A traffic processing apparatus, characterized in that the apparatus comprises:

12. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to carry out the method of any one of claims 1 to 10 when executed.

13. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 10.