WO2022262951A1 - Coordination de chaînes de services segmentées - Google Patents

Coordination de chaînes de services segmentées Download PDF

Info

Publication number
WO2022262951A1
WO2022262951A1 PCT/EP2021/066084 EP2021066084W WO2022262951A1 WO 2022262951 A1 WO2022262951 A1 WO 2022262951A1 EP 2021066084 W EP2021066084 W EP 2021066084W WO 2022262951 A1 WO2022262951 A1 WO 2022262951A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule information
application services
based application
segment
function entity
Prior art date
Application number
PCT/EP2021/066084
Other languages
English (en)
Inventor
Hannu Flinck
Laurent Thiebaut
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2021/066084 priority Critical patent/WO2022262951A1/fr
Publication of WO2022262951A1 publication Critical patent/WO2022262951A1/fr

Links

Classifications

    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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/0894—Policy-based network configuration management
    • 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/34—Signalling channels for network management communication

Definitions

  • Various example embodiments relate to coordination of segmented service chains. More specifically, various example embodiments exemplarily relate to measures (including methods, apparatuses and computer program products) for realizing coordination of segmented service chains.
  • the present specification generally relates to service function chain where multiple composite micro service functions are traversed in a specific order to implement the complete service.
  • micro services are typically decomposed into sub-services.
  • end-to-end services/applications are made up of a collection of loosely coupled services, called micro services.
  • micro services can be connected by a service function chain where multiple composite micro service functions are traversed in a specific order to implement the complete service.
  • micro services or component services
  • encoding/decoding of an encrypted stream caching frequently used content or request-responses, WAN acceleration, server load balancing, hierarchical content caching, augmented reality (AR)/ virtual reality (VR) where local information is overlaid on top base image from the centralized server, etc.
  • AR augmented reality
  • VR virtual reality
  • An architecture for service chaining is provided in Internet Engineering Task Force (IETF) RFC 7665 "Architecture for Service Function Chains” (SFC). Protocol mechanisms for service function chaining is provided in IETF RFC 8300 "Network Service Header” (NSH).
  • IETF Internet Engineering Task Force
  • SFC Architecture for Service Function Chains
  • NSH Network Service Header
  • the current service chain model applied in 3GPP networks including 5G core network (5GC) is based on the FMSS concept (thus based on evolved packet core (EPC) architecture), and considers N6-LAN as being outside of the 3GPP scope.
  • 5GC has introduced some new powerful features to support traffic routing to edge clouds whose interaction with service flow chaining (SFC)/mobile service steering has not been studied.
  • SFC service flow chaining
  • Examples of such features to support traffic routing to edge clouds are uplink classifier (UL CL), branching point (BP), powerful forwarding and detection rules to support multiple N 6- interfaces, and local break out, etc.
  • Introduction of core and edge services may facilitate the execution of services in stages where one part of the services is in the edge and other part is in the core network. Time critical or location context relevant parts of a service might be executed in the edge, while parts that require network wide or global context might be executed in the core.
  • 3GPP TS 23.503 (R-16) defines policy and charging control (PCC) rule information in 5GC, which according to the following table (Table 6.3.1) contains: According to NOTE 18, only one of the two shall be present in a PCC rule.
  • a traffic steering policy identifier and/or N6 traffic routing information can be provided. If the pre-configured traffic steering policy (that is referenced by the traffic steering policy identifier) contains information that is overlapping with the N6 traffic routing information, the N6 traffic routing information shall take precedence.
  • end-to-end services are executed as a chain of smaller services or component services that are progressed in stages.
  • N6 is the name of the interface or reference point between a user plane function (UPF) and a data network.
  • UPF user plane function
  • Multiple N6-interfaces and routes to the data network(s) are e.g. defined in TS23.501, section 5.6.4.
  • Some of N6 interfaces may be located at the edge close to the UE, while some of N6 interfaces may be centrally located at the core network.
  • a packet data unit (PDU) session is between a terminal such as a user equipment (UE) and the local break out N6 (edge service accessed by the local N6-LAN), and/or between the UE and the central N6 (central application service).
  • UE user equipment
  • N6 edge service accessed by the local N6-LAN
  • central N6 central application service
  • a method comprising transmitting policy charging control rule information towards a session management function entity, wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • a method comprising receiving policy charging control rule information from a policy control function entity, wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • a method of a user plane function entity interfacing with application services of a segment of a segmented service function chain comprising receiving, from a session management function entity, mappings between uplink/downlink packet detection rule information and a forwarding rule information containing a service function chain identifier.
  • a method of a user plane function entity comprising receiving, from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • a method of a user plane function entity comprising receiving, from said session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • an apparatus comprising transmitting circuitry configured to transmit policy charging control rule information towards a session management function entity, wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • an apparatus comprising receiving circuitry configured to receive policy charging control rule information from a policy control function entity, wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • an apparatus of a user plane function entity interfacing with application services of a segment of a segmented service function chain comprising receiving circuitry configured to receive, from a session management function entity, mappings between uplink/downlink packet detection rule information and a forwarding rule information containing a service function chain identifier.
  • an apparatus of a user plane function entity comprising receiving circuitry configured to receive, from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • an apparatus of a user plane function entity comprising receiving circuitry configured to receive, from a session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform transmitting policy charging control rule information towards a session management function entity, wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving policy charging control rule information from a policy control function entity, wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • an apparatus of a user plane function entity interfacing with application services of a segment of a segmented service function chain comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving, from a session management function entity, mappings between uplink/downlink packet detection rule information and a forwarding rule information containing a service function chain identifier.
  • an apparatus of a user plane function entity comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving, from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • an apparatus of a user plane function entity comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving, from a session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present disclosure), is configured to cause the computer to carry out the method according to any one of the aforementioned method- related exemplary aspects of the present disclosure.
  • Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computer- executable computer program code is stored, and/or the program may be directly loadable into an internal memory of the computer or a processor thereof.
  • Any one of the above aspects enables an efficient control and management of separated service chains, thereby enabling an improvement of service quality by exploiting respective advantages of respective service segment locations, to thereby solve at least part of the problems and drawbacks identified in relation to the prior art.
  • coordination of segmented service chains More specifically, by way of example embodiments, there are provided measures and mechanisms for realizing coordination of segmented service chains.
  • Figure 1 is a block diagram illustrating an apparatus according to example embodiments
  • Figure 2 is a block diagram illustrating an apparatus according to example embodiments
  • Figure 3 is a block diagram illustrating an apparatus according to example embodiments
  • Figure 4 is a block diagram illustrating an apparatus according to example embodiments
  • Figure 5 is a block diagram illustrating an apparatus according to example embodiments
  • Figure 6 is a block diagram illustrating an apparatus according to example embodiments
  • Figure 7 is a schematic diagram of a procedure according to example embodiments
  • Figure 8 is a schematic diagram of a procedure according to example embodiments
  • Figure 9 is a schematic diagram of a procedure according to example embodiments.
  • Figure 10 shows a schematic diagram of an example of a system environment with signaling variants according to example embodiments
  • Figure 11 shows a schematic diagram of an example of a system environment with interfaces between network entities according to example embodiments
  • Figure 12 shows a schematic diagram of signaling sequences according to example embodiments.
  • Figure 13 is a block diagram alternatively illustrating apparatuses according to example embodiments.
  • mechanisms and related traffic forwarding rules for 5G UPFs to forward packets of a data flow selectively back to UE or to further processing at the service chain segment either in the core or in the edge depending on where the service chaining continues are defined.
  • Figure 10 shows a schematic diagram of an example of a system environment with signaling variants according to example embodiments.
  • Figure 10 illustrates concatenating a service flow processing in the edge and in the core according to example embodiments compared to service flow processing only in the edge or only in the core.
  • the system environment illustrates a radio access network (RAN) (to which a terminal, e.g. a UE, is connected), a UPF associated with Edge Application Services (linked via a local N6 interface) and linked with the RAN via an N3 interface, a UPF associated with Central Application Services (linked via a central N6 interface) and linked with the former UPF via an N9 interface.
  • RAN radio access network
  • the RAN could be replaced by any 5G Access Network (such as a W-AGF for Wireline access, N3IWF for untrusted Non 3GPP access, etc.).
  • example embodiments cover also cases where multiple UPF(s) are used, while Figure 10 only shows a single UPF.
  • new PCC rules for a session management function (SMF) and a UPF to steer traffic between the edge cloud resident SFC-segment and the central cloud resident SFC- segment are defined so that a correct GTP-U tunnel can be identified with an embedded terminal identifier (e.g. UE IP address).
  • an embedded terminal identifier e.g. UE IP address.
  • importance is attached to traffic steering between the concatenated SFC-segments (e.g. SFC part A and SFC B in Figure 10).
  • the UPF decides if the packet of a flow needs to be forwarded to the next SFC-segment (e.g. SFC- segment part B in Figure 10) or sent back to the UE.
  • the next SFC-segment e.g. SFC- segment part B in Figure 10.
  • the UPF learns via PDR (and FAR) whether the UL traffic from the local SFC environment needs to be forwarded to the next SFC-segment (e.g. SFC-segment part B in Figure 10) or sent back to the UE.
  • PDR and FAR
  • a novel PDR rule is defined for the egress UPF (acting as an auxiliary service function forwarder SFF) to look for the UE IP address, or in general, for the UE ID (as an example for the terminal identifier) inside the encapsulated data packet, i.e., for the source address of an inner IP packet, or to look for the UE ID from a NSH header metadata or from being embedded into an SFC ID. Then an already defined FAR can forward the traffic to the next SFC-segment.
  • SFF auxiliary service function forwarder
  • related policy rules in a policy control function (PCF) and the associated packet detection rules (PDR) and forwarding rules (FAR) that are communicated by the SMF to the UPF are extended to steer the flow of packets accordingly between the segments of the SFC.
  • PCF policy control function
  • PDR packet detection rules
  • FAR forwarding rules
  • Figure 1 is a block diagram illustrating an apparatus according to example embodiments.
  • the apparatus may be a network entity 10 such as a policy control function entity comprising a transmitting circuitry 11.
  • the transmitting circuitry 11 transmits policy charging control rule information towards a session management function entity.
  • the policy charging control rule information is indicative of a segmented service function chain. Further, the segmented service function chain is segmented into a first segment and a second segment.
  • Figure 7 is a schematic diagram of a procedure according to example embodiments.
  • the apparatus according to Figure 1 may perform the method of Figure 7 but is not limited to this method.
  • the method of Figure 7 may be performed by the apparatus of Figure 1 but is not limited to being performed by this apparatus.
  • a procedure comprises an operation of transmitting (S71) policy charging control rule information towards a session management function entity.
  • the policy charging control rule information is indicative of a segmented service function chain. Further, the segmented service function chain is segmented into a first segment and a second segment.
  • Figure 2 is a block diagram illustrating an apparatus according to example embodiments.
  • Figure 2 illustrates a variation of the apparatus shown in Figure 1.
  • the apparatus according to Figure 2 may thus further comprise a grouping circuitry 21.
  • At least some of the functionalities of the apparatus shown in Figure 1 may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
  • said first segment is any one of a service function chain segment of core network based application services and a service function chain segment of network edge based application services.
  • said second segment is the other one of said service function chain segment of core network based application services and said service function chain segment of network edge based application services.
  • said policy charging control rule information is indicative of a segmented service function chain.
  • said policy charging control rule information includes a traffic steering policy identifier referencing a pre configured traffic steering policy at an interface towards said network edge based application services.
  • said policy charging control rule information includes traffic routing information related to traffic routing at said interface towards said network edge based application services.
  • said policy charging control rule information contains said indication of a segmented service function chain associated with a traffic offload indication.
  • said indication of a segmented service function chain is associated with a traffic offload indication.
  • the policy charging control rule information contains a rule referencing to traffic steering policies to apply when no traffic offload takes place and a rule referencing to other traffic steering policies to apply when traffic offload takes place.
  • said interface towards said core network based application services is a central N6 interface.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method according to example embodiments may comprise an operation of identifying and grouping service function segments into edge segments and core segments to be shared across different end to end services chains and their user as indicated by said policy charging control rule information.
  • Figure 3 is a block diagram illustrating an apparatus according to example embodiments.
  • the apparatus may be a network entity 30 such as a session management function entity comprising a receiving circuitry 31.
  • the receiving circuitry 31 receives policy charging control rule information from a policy control function entity.
  • the policy charging control rule information is indicative of a segmented service function chain. Further, the segmented service function chain is segmented into a first segment and a second segment.
  • Figure 8 is a schematic diagram of a procedure according to example embodiments.
  • the apparatus according to Figure 3 may perform the method of Figure 8 but is not limited to this method.
  • the method of Figure 8 may be performed by the apparatus of Figure 3 but is not limited to being performed by this apparatus.
  • a procedure comprises an operation of receiving (S81) policy charging control rule information from a policy control function entity.
  • the policy charging control rule information is indicative of a segmented service function chain. Further, the segmented service function chain is segmented into a first segment and a second segment.
  • Figure 4 is a block diagram illustrating an apparatus according to example embodiments.
  • Figure 4 illustrates a variation of the apparatus shown in Figure 3.
  • the apparatus according to Figure 4 may thus further comprise a grouping circuitry 41, a selecting circuitry 42, and/or a transmitting circuitry 43.
  • At least some of the functionalities of the apparatus shown in Figure 3 may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
  • said first segment is any one of a service function chain segment of core network based application services and a service function chain segment of network edge based application services.
  • said second segment is the other one of said service function chain segment of core network based application services and said service function chain segment of network edge based application services.
  • said policy charging control rule information includes a traffic steering policy identifier referencing a pre configured traffic steering policy at an interface towards said network edge based application services.
  • said policy charging control rule information includes traffic routing information related to traffic routing at said interface towards said network edge based application services.
  • said indication of a segmented service function chain is associated with a traffic offload indication.
  • the policy charging control rule information contains a rule referencing to traffic steering policies to apply when no traffic offload takes place and a rule referencing to other traffic steering policies to apply when traffic offload takes place.
  • said interface towards said core network based application services is a central N6 interface.
  • an exemplary method may comprise an operation of identifying and grouping service function segments into edge segments and core segments to be shared across different end to end services chains and their user as indicated by said policy charging control rule information.
  • an exemplary method may comprise an operation of selecting at least one first user plane function entity for application services of said first segment based on said policy charging control rule information, and an operation of selecting at least one second user plane function entity for application services of said second segment based on said policy charging control rule information.
  • an exemplary method may comprise an operation of transmitting, towards any of said at least one first user plane function entity and said at least one second user plane function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • an exemplary method may comprise an operation of transmitting, towards any of said at least one first user plane function entity and said at least one second user plane function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • said forwarding rule information is indicative of a tunnel towards said one first user plane function entity (i.e., towards one of said at least one first user plane function entity) or a tunnel towards said one second user plane function entity (i.e., towards one of said at least one second user plane function entity), wherein said tunnel towards said one first user plane function entity and said tunnel towards said one second user plane function entity are associated with a data session of a user equipment.
  • an exemplary method may comprise an operation of transmitting, towards any of said at least one first user plane function entity and said at least one second user plane function entity, forwarding rule information containing an explicit service function chain identifier.
  • FIG. 5 is a block diagram illustrating an apparatus according to example embodiments.
  • the apparatus may be a network entity 50 such as a user plane function entity (interfacing with application services of a segment of a segmented service function chain) comprising a receiving circuitry 51.
  • the receiving circuitry 51 receives, from a session management function entity, mappings between uplink/downlink packet detection rule information and a forwarding rule information containing a service function chain identifier.
  • the receiving circuitry 51 receives, from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • the receiving circuitry 51 receives, from a session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • Figure 9 is a schematic diagram of a procedure according to example embodiments.
  • the apparatus according to Figure 5 may perform the method of Figure 9 but is not limited to this method.
  • the method of Figure 9 may be performed by the apparatus of Figure 5 but is not limited to being performed by this apparatus.
  • a procedure according to example embodiments comprises an operation of receiving (S91), from a session management function entity, mappings between uplink/downlink packet detection rule information and a forwarding rule information containing a service function chain identifier.
  • a procedure according to example embodiments comprises an operation of receiving (S91), from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • a procedure according to example embodiments comprises an operation of receiving (S91), from a session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • Figure 6 is a block diagram illustrating an apparatus according to example embodiments.
  • Figure 6 illustrates a variation of the apparatus shown in Figure 5.
  • the apparatus according to Figure 6 may thus further comprise a matching circuitry 61, an adding circuitry 62, and/or an acting circuitry 63.
  • At least some of the functionalities of the apparatus shown in Figure 5 may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
  • an exemplary method may comprise an operation of receiving, from said session management function entity, mappings between said uplink/downlink packet detection rule information and a service function chain identifier.
  • an exemplary method may comprise an operation of receiving, from said session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services.
  • said method is a method of a first user plane function entity, and said forwarding rule information is indicative of a tunnel towards a second user plane function entity, wherein said tunnel is associated with a data session of a user equipment.
  • an exemplary method may comprise an operation of receiving a packet of a service data flow, and an operation of matching said packet with said uplink/downlink packet detection rule information. If said packet matches with said uplink/downlink packet detection rule information, such exemplary method according to example embodiments may comprise an operation of adding a service identifier to said packet, and an operation of adding a transport encapsulation to said packet.
  • said uplink/downlink packet detection rule information is indicative of looking up a user equipment identifier or a user equipment address from an inner packet of a transport encapsulated packet.
  • said uplink/downlink packet detection rule information is indicative of looking up said user equipment identifier or said user equipment address from metadata of a service header.
  • an exemplary method may comprise an operation of receiving a packet of a service data flow from an interface towards core network based application services or an interface towards network edge based application services, and an operation of matching said packet with said uplink/downlink packet detection rule information. If said packet matches with said uplink/downlink packet detection rule information, such exemplary method according to example embodiments may comprise an operation of matching said packet with forwarding rule information.
  • an exemplary method according to example embodiments may comprise an operation of, if said packet matches said forwarding rule information, acting according to said forwarding rule information.
  • said service identifier is a network service header.
  • the PCF when the PCF desires to control the service function chain related behavior of the 5GC and supports SFC split up between edge and core service function entities, the PCC rules (rules sent from PCF to SMF) and the N4 rules (rules sent from SMF to UPF) are modified as described below.
  • N4 is the name of the interface between a session management function (SMF) and a user plane function (UPF) and is defined in TS 29.244.
  • SMF session management function
  • UPF user plane function
  • new PCC rule information from PCF instructs the SMF to deal with a service chaining that is segmented between the core and edge clouds.
  • the SMF selects a proper set of UPF(s) for the edge services and an anchor UPF for the central services based on these PCC rules.
  • edge services may correspond to traffic offload in one edge data center and that there may be multiple such edge data centers that simultaneously apply to the PDU Session.
  • an indication of a segmented service function chain may be provided per data network access identifier (DNAI).
  • DNAI data network access identifier
  • the PCF may provide different PCC rules to the SMF, where for one rule the AF influenced Traffic Steering Enforcement Control contains at least a DNAI and an indication of a segmented service function chain because there is a segmented service function chain for traffic offloaded to this DNAI, and for one other rule the AF influenced Traffic Steering Enforcement Control contains a DNAI and no indication of a segmented service function chain because there is no segmented service function chain for traffic offloaded to this DNAI.
  • the PCF may provide different PCC rules to the SMF, where for one rule there is no AF influenced Traffic Steering Enforcement Control but a N6-1-AN Traffic Steering Enforcement Control information with no indication of a segmented service function chain because there is no segmented service function chain for traffic not being offloaded, and for another rule the AF influenced Traffic Steering Enforcement Control contains a DNAI and an indication of a segmented service function chain because there is segmented service function chain for traffic offloaded to this DNAI.
  • these policy control rules can be changed dynamically by the AF through Nnef_TrafficInfluence API of TS 29.522, if, for example, the UE wants to have better QoS by using edge services.
  • applications/services can be grouped into edge segments and core segments to be shared across different end to end services chains and their user as indicated by said policy charging control rule information; then based on the indication of a segmented service function chain the SMF is to create N4 rules (PDR/FAR) enforcing that once UL traffic has been handled by and received from the edge based group of applications it can be properly directed to the core network based group of applications via the inter UPF (GTP-u) tunnel associated with the corresponding UE.
  • PDR/FAR N4 rules
  • the SMF provides UL/DL packet detection rules (PDR) to forward packets between edge and core associated N 9/6- interfaces.
  • PDR packet detection rules
  • the rules are provided over interface N4.
  • Figure 11 shows a schematic diagram of an example of a system environment with interfaces between network entities according to example embodiments.
  • Figure 11 illustrates 3GPP interfaces relevant for decomposed service chains between edge and core.
  • the UPF may implement a RFC 7665 service chain classifier function (SCF) that adds a network service header (NSH) or similar identifier and transport encapsulation to a matching service data flow.
  • SCF service chain classifier function
  • PCF may be controlled by the PCF sending evolved "Per DNAI: N6 traffic routing information" within a PCC rule (as defined in 3GPP TS 23.503 Table 6.3.1: "The PCC rule information in 5GC") where the PCF may explicitly refer to NSH values or service path ID (and not implicitly as per R16 TS29.244) to be used when forwarding traffic to a service function chain over N6.
  • This information received in evolved "Per DNAI: N6 traffic routing information" within a PCC rule may be propagated by the SMF (via FAR rule sent) to the UPF interfacing a Service Function Chain which can be any Service Function Chain of the Figure 10.
  • the FAR rules (sent from SMF over the N4 interface) can explicitly refer to NSH values or service path ID (and not implicitly as per R16 TS29.244) to be used by UPF when forwarding traffic over N6.
  • New information carried within N6 traffic routing information can be used for the SMF to indicate the NSH values or service path ID to be added by the SF classifier functionality of 5GC (in UPF). According to example embodiments, this may apply regardless of whether the service function chain handling applies at central N6, at edge/local N6 or is split up between these two N6 interfaces.
  • the last service function (SF) (SF-n in Figure 11) of the first service chain segment (SF-1 to SF-n, in the Figure 11) may complete the service processing by removing the service flow (e.g. NSH) encapsulation and sends the packet either back to the UE, or to the destination of the packet (broken curve in Figure 10). If the last SF of the first service chain segment (SF-n in Figure 11) is not the last SF of the whole end-to-end service chain (i.e.
  • the packet is to be processed by the core SF chain as well), according to example embodiments, the last SF of the first service chain segment sends the packet to the local break-out UPF (that appears as an auxiliary of a service function forwarder (SFF)).
  • SFF service function forwarder
  • the local break-out UPF needs to forward the packet over N9 interface to the central service chain for further processing based using the UE specific GTP-U tunnel.
  • this UPF is configured with
  • This PDR is defined as explained below.
  • FAR that refers to GTP-U encapsulation and may be defined according to R-16 specifications.
  • the above-mentioned PDR is defined to relate on
  • a specific packet detection information (PDI)/traffic filter that instructs the UPF to look up the UE (User Equipment) address (e.g. UE IP as an example of a terminal identifier) from the inner IP packet of the service flow, e.g. an NSH encapsulated packet, and thus to skip the NSH header for the sake of PDR related filtering, or
  • Figure 12 shows a schematic diagram of signaling sequences according to example embodiments.
  • Figure 12 illustrates a flowchart of user plane packet processing according to example embodiments.
  • exemplary user plane events as packets flow from the UE to the first service chain segment in the edge and from there to the core service chain segment are described. Presumption is that the SMF has set service data flow detection filters in the LBO-UPF.
  • these filters can be based on IP 5-Tuple, application ID or other operator policies as defined e.g. in TS 23.503.
  • a forwarding rule (FAR) set by the SMF is applied to redirect the packets of the service flow to the LBO-N6 and to the service classification function (SCF) of the edge service chain (SCF can be co-located with the LBO-UPF).
  • FAR forwarding rule
  • PDR Packet Detection Rule
  • FAR send to local N6 and to SFC
  • the SFC encapsulates the packet with a relevant transport header and NSH as needed and sends the packet to be processed by the first service function (SF-1) of the first segment of the service chain.
  • SF-1 first service function
  • the packet is then processed within the first SFC segment by the service functions from SF-1 to SF-n.
  • the service Forwarder of the edge network service function chain segment may, after last SF (SF-n) of the edge service chain has processed a packet, decide whether the packet needs to be further processed by the core network service function chain segment.
  • the SF chain header (e.g. NSH) has been removed and the packet is forwarded to the destination of the original packet or to the UE as per R16 specifications (for the case where the packet is to be sent back to the UE).
  • the packet is to be processed by the core SFC (as according to the present concept), e.g. if the last SF of the service chain segment (SF-n in Figure 11) or the Service Function Forwarder decides that the packet needs further processing by the core SFC segment, then if NSH is used, according to example embodiments, the NSH is not removed.
  • the packet is sent to LBO-UPF that is also acting as an auxiliary of SFF (Service Function Forwarding). In this case the packet still carries SF (Service Flow) chain related header.
  • the UPF applies a FAR (received from SMF) that requests it to encapsulate the packet and sends it to the N9 GTP-U tunnel to the central UPF corresponding to the PDU session from the UE (solid curve/service path of Figure 10).
  • FAR received from SMF
  • N9 GTP-U tunnel to the central UPF corresponding to the PDU session from the UE (solid curve/service path of Figure 10).
  • transport header is used instead of NSH is described in more detail in the following.
  • the UE ID can be carried in the metadata of the NSH (i.e.
  • the UPF acting as SFF auxiliary can find out the UE ID based on the PDR rule containing indication where UE IP address can be found in the encapsulated packet and then based on the associated FAR received from SMF select the right N9-tunnel matching the PDU Session of the UE.
  • the SFF (or LBO-UFP if they are co-located) may find the UE IP address from the source address of the inner encapsulated IP packet.
  • the packet is processed in the central SFC in normal manner.
  • Service Flow Forwarding of the core network SFC segment may decide that the packet needs to be sent to the edge SFC segment for further processing.
  • the UE ID information (UE IP address) is provided using either of the above-presented mechanisms, namely, embedding the UE ID into NSH context metadata or in the UE IP address in the encapsulated inner packet.
  • the SF chain header (e.g. NSH) has been removed and the packet is forwarded to the UE as per R16 specifications.
  • the packet is to be processed by the edge SFC (as according to the present concept), i.e. if after the last SF of the core service chain segment has processed the packet it is decided that the packet needs further processing by the edge SFC segment, then if NSH is used, according to example embodiments, the NSH is not removed and the destination of the outer IP packet is set to the edge SFC.
  • the packet is sent to central PF that is also acting as an auxiliary of SFF (Service Function Forwarding). In this case the packet still carries SF (Service Flow) chain related header.
  • SFF Service Function Forwarding
  • the UPF applies a FAR (received from SMF) that requests it to encapsulate the packet and sends it to the N9 GTP-U tunnel to the edge UPF corresponding to the PDU session from the UE (solid curve/service path of Figure 10).
  • FAR received from SMF
  • the network entity may comprise further units that are necessary for its respective operation. However, a description of these units is omitted in this specification.
  • the arrangement of the functional blocks of the devices is not construed to limit the disclosure, and the functions may be performed by one block or further split into sub-blocks.
  • the apparatus i.e. network entity (or some other means) is configured to perform some function
  • this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • a (i.e. at least one) processor or corresponding circuitry potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to” is construed to be equivalent to an expression such as "means for").
  • the apparatus (network entity) 10' (corresponding to the network entity 10) comprises a processor 1311, a memory 1312 and an interface 1313, which are connected by a bus 1314 or the like.
  • the apparatus (network entity) 30' (corresponding to the network entity 30) comprises a processor 1331, a memory 1332 and an interface 1333, which are connected by a bus 1334 or the like.
  • the apparatus (network entity) 50' (corresponding to the network entity 50) comprises a processor 1351, a memory 1352 and an interface 1353, which are connected by a bus 1354 or the like.
  • the apparatuses may be connected via links 130a, 130b, respectively.
  • the processor 1311/1331/1351 and/or the interface 1313/1333/1353 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively.
  • the interface 1313/1333/1353 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively.
  • the interface 1313/1333/1353 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.
  • the memory 1312/1332/1352 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the example embodiments.
  • the respective devices/apparatuses may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.
  • processor or some other means
  • the processor is configured to perform some function
  • this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression "processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as "means for xxx-ing").
  • an apparatus representing the network entity 10 comprises at least one processor 1311, at least one memory 1312 including computer program code, and at least one interface 1313 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 1311, with the at least one memory 1312 and the computer program code
  • the processor is configured to perform transmitting policy charging control rule information towards a session management function entity (thus the apparatus comprising corresponding means for transmitting), wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • an apparatus representing the network entity 30 comprises at least one processor 1331, at least one memory 1332 including computer program code, and at least one interface 1333 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 1331, with the at least one memory 1332 and the computer program code
  • the processor is configured to perform receiving policy charging control rule information from a policy control function entity (thus the apparatus comprising corresponding means for receiving), wherein said policy charging control rule information is indicative of a segmented service function chain, and said segmented service function chain is segmented into a first segment and a second segment.
  • an apparatus representing the network entity 50 comprises at least one processor 1351, at least one memory 1352 including computer program code, and at least one interface 1353 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 1351, with the at least one memory 1352 and the computer program code
  • the processor is configured to perform (at a user plane function entity interfacing with application services of a segment of a segmented service function chain) receiving, from a session management function entity, mappings between uplink/downlink packet detection rule information and a forwarding rule information containing a service function chain identifier, or to perform receiving, from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services (thus the apparatus comprising corresponding means for receiving), or to perform receiving, from a session management function entity, forwarding rule information to be used for forwarding between an interface towards core network based application services and an interface towards network edge based application services (thus the apparatus
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field-programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means e.g. the above-defined network entity or network register, or any one of their respective units/means
  • an apparatus like the user equipment and the network entity /network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • the present disclosure also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.
  • Such measures exemplarily comprise, at a user plane function entity interfacing with application services of a segment of a segmented service function chain, receiving, from a session management function entity, uplink/downlink packet detection rule information indicative of forwarding between an interface towards core network based application services and an interface towards network edge based application services.

Landscapes

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

Abstract

L'invention concerne des mesures correspondant à la coordination de chaînes de services segmentées. De telles mesures consistent, à titre d'exemple, au niveau d'une entité de fonction de plan utilisateur en interface avec des services d'application d'un segment d'une chaîne à fonction de services segmentée, à recevoir, en provenance d'une entité de fonction de gestion de session, des informations de règle de détection de paquet de liaison montante/liaison descendante indiquant un transfert entre une interface vers des services d'application basés sur un réseau central et une interface vers des services d'application basés sur une périphérie de réseau.
PCT/EP2021/066084 2021-06-15 2021-06-15 Coordination de chaînes de services segmentées WO2022262951A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/066084 WO2022262951A1 (fr) 2021-06-15 2021-06-15 Coordination de chaînes de services segmentées

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/066084 WO2022262951A1 (fr) 2021-06-15 2021-06-15 Coordination de chaînes de services segmentées

Publications (1)

Publication Number Publication Date
WO2022262951A1 true WO2022262951A1 (fr) 2022-12-22

Family

ID=76641644

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/066084 WO2022262951A1 (fr) 2021-06-15 2021-06-15 Coordination de chaînes de services segmentées

Country Status (1)

Country Link
WO (1) WO2022262951A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018224126A1 (fr) * 2017-06-06 2018-12-13 Telefonaktiebolaget Lm Ericsson (Publ) Technique d'attribution de fonction de plan utilisateur
WO2021001051A1 (fr) * 2019-07-03 2021-01-07 Telefonaktiebolaget Lm Ericsson (Publ) Établissement d'une session de protocole de commande de transfert de paquets
WO2021017381A1 (fr) * 2019-07-31 2021-02-04 Huawei Technologies Co., Ltd. Systèmes et procédés de prise en charge de direction de trafic par l'intermédiaire d'une chaîne de fonctions de service

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018224126A1 (fr) * 2017-06-06 2018-12-13 Telefonaktiebolaget Lm Ericsson (Publ) Technique d'attribution de fonction de plan utilisateur
WO2021001051A1 (fr) * 2019-07-03 2021-01-07 Telefonaktiebolaget Lm Ericsson (Publ) Établissement d'une session de protocole de commande de transfert de paquets
WO2021017381A1 (fr) * 2019-07-31 2021-02-04 Huawei Technologies Co., Ltd. Systèmes et procédés de prise en charge de direction de trafic par l'intermédiaire d'une chaîne de fonctions de service

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Architecture for Service Function Chains", INTERNET ENGINEERING TASK FORCE (IETF) RFC 7665
"Network Service Header", IETF RFC 8300

Similar Documents

Publication Publication Date Title
US11743767B2 (en) Compression of ethernet packet header
US11509591B2 (en) System and method for hosting mobile packet core and value-added services using a software defined network and service chains
US10110433B2 (en) System and method for exchanging information in a mobile wireless network environment
US20190109721A1 (en) Ethernet type packet data unit session communications
US9497661B2 (en) Implementing EPC in a cloud computer with openflow data plane
US10165487B2 (en) Apparatus, systems, and methods for providing offloading to an alternate network
EP2831733B1 (fr) Mise en oeuvre d'epc dans un ordinateur en nuage à plan de données openflow
CA2847103C (fr) Mise en oeuvre d'un cour de paquet 3g dans un ordinateur en nuage au moeyen de plans de commandes et de donnees openflow
US7779245B2 (en) Providing access bearer related information in a packet data network
WO2018191031A1 (fr) Système et procédé pour faciliter une gestion de tranche dans un environnement de réseau
CN110383792B (zh) 通信系统中的计算系统和方法
CN114651477A (zh) 用于用户面处理的系统和方法
US10887229B2 (en) Systems and methods for tunnel free connectionless packet routing to a service edge
JP7382429B2 (ja) インテリジェントエッジルーティングのシステム及び方法
WO2022262951A1 (fr) Coordination de chaînes de services segmentées
EP3167687B1 (fr) Noeud de réseau et procédé destinés à des fonctions epdg et pgw co-implantées
US20120304246A1 (en) System and Method for Selective Security of Wireless Bearers

Legal Events

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

Ref document number: 21735187

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21735187

Country of ref document: EP

Kind code of ref document: A1