Patent ID: 12224944

The drawings are not necessarily to scale and the dimensions of certain features may have been exaggerated for the sake of clarity. Emphasis is instead placed upon illustrating a principle.

DETAILED DESCRIPTION

FIG.2depicts a communications system100. The communications system100may apply to one or more radio access technologies such as for example 2G, 3G, 4G, 5G or any other previous, current or future Third Generation Partnership Project (3GPP) radio access technology, or other radio access technologies such as e.g. Wireless Local Area Network (WLAN). The communications system100may be referred to as a communication network, a network, a system, a wireless communications system, a wireless communication network etc.

The communications system100comprises a PCF101and a SMF103adapted to communicate with each other. The SMF103is adapted to be connected to multiple UPFs105.FIG.2shows two UPFs105, i.e. a first UPF node105aand a next UPF node105b, but the communications system100may comprise any n number of UPF105, where n is a positive integer. The reference number105is used herein when referring to any of the UPF nodes105comprised in the communications system100. The next UPF node105bmay be a second UPF node, a third UPF node, or any other m UPF node, where m is a positive integer larger than one.

As mentioned earlier, the PCF101supports different functionality, e.g. unified policy framework to govern network behavior, provides policy rules to Control Plane function(s) to enforce them, and accesses subscription information relevant for policy decisions in the UDR108. The SMF103supports different functionality, e.g. Session Establishment, modify and release, and policy related functionalities like termination of interfaces towards Policy control functions, Charging data collection, support of charging interfaces and control and coordination of charging data collection at an UPF105. The UPF105supports handling of user plane traffic, including packet inspection, e.g. analysis and Classification, packet routing and forwarding, including traffic steering, traffic usage reporting and Quality of Service (QoS) handling. The PCF101, the SMF103and the UPFs105may be seen as being comprised in a core network in the communications system100, e.g. they may be CN nodes.

The communication system100may comprise a UE (not shown inFIG.2) The UE may be served by a network node (not shown inFIG.2), and is in this case capable of communicating with the network node over a communications link. The UE may be adapted to communicate with the core network, e.g. via a core network node and/or via a network node.

The UE may be a device by which a subscriber may access services offered by an operator's network and services outside operator's network to which the operator's radio access network and core network provide access, e.g. access to the Internet. The UE may be any device, mobile or stationary, enabled to communicate in the communications network, for instance but not limited to e.g. user equipment, mobile phone, smart phone, sensors, meters, vehicles, household appliances, medical appliances, media players, cameras, Machine to Machine (M2M) device, Device to Device (D2D) device, Internet of Things (IoT) device, terminal device, communication device or any type of consumer electronic, for instance but not limited to television, radio, lighting arrangements, tablet computer, laptop or Personal Computer (PC). The UE may be portable, pocket storable, hand held, computer comprised, or vehicle mounted devices, enabled to communicate voice and/or data, via the radio access network, with another entity, such as another UE or a server.

It should be noted that the communication links in the communications system100may be of any suitable kind including either a wired or wireless link. The link may use any suitable protocol depending on type and level of layer, e.g. as indicated by the Open Systems Interconnection (OSI) model, as understood by the person skilled in the art.

The user plane traffic classification in a scenario of multiple UPFs105in the context of a communications system100such as e.g. a 5G network supporting CUPS is optimized. To achieve this, the 3GPP PFCP protocol may be extended. The following PFCP protocol extensions may be applicable:A COMU capability, e.g. in the PFCP Association procedure.A class identifier, e.g. a Class-ID Enrichment IE in the Forwarding Parameters IE in FAR at PFCP Session Establishment/Modification Request, for the SMF node103to indicate to the first UPF node105ato convey a class indicator, e.g. Class-ID, to the next UPF node105b.A class indicator, e.g. a PDI type, Class-ID, in the Create PDR IE within a PFCP Session Establishment/Modification Request, for the SMF node103to indicate to the first UPF105ato match incoming application traffic based on the class indicator, e.g. Class-ID.

FIG.3illustrates a method which optimizes classification in a scenario with multiple UPF nodes105. A SMF node103is shown inFIG.3which is adapted to communicate with the first UPF node105aand the next UPF node105b.

In step301, the SMF node103provides a first detection rule and a class identifier to the first UPF node105a. The first detection rule may be in the form of a first PDR. The class identifier may be referred to as Class ID Enrichment or Class ID Enrichment ID. The class identifier may be comprised in first instruction rule, e.g. a Forwarding Action Rule (FAR). A FAR may comprise the class ID. The first instruction rule may be referred to as a first enforcement action or first enforcement rule.

In step303, the SMF node103provides a next detection rule to the next UPF node105b. The next detection rule may be in the form of a next PDR. The next detection rule may comprise a class indicator, and the class indicator may be referred to as class ID. The class indicator may be a PDI. The class indicator may be a separate indicator, i.e. not comprised in the next detection rule. In step303, the SMF node103provides a next instructions rule, e.g. in the form of next FAR. The next instructions rule may be referred to as a next enforcement rule.

In step305, the first UPF node105areceives a packet, and the packet301may be data traffic, application traffic or comprised in application traffic, or it may be user plane traffic.

The first UPF node105aperforms PDR matching in step308, i.e. it matches the packet from step305with the PDR from step301. Matching may also be referred to as classification.

In step310, the first UPF node105aperforms or executes a first instruction rule. The first instruction rule may be an enforcement action or enforcement rule. The first instruction rule may be e.g. one or more of the FAR from step301, QoS Enforcement Rule (QER), Usage Reporting Rule (URR) etc.

In step313, the first UPF node105aforwards the packet to the next UPF node105btogether with the class identifier from step301.

The next UPF node105bperforms PDR matching in step315and class ID matching in step318. The next UPF node105bperforms or executes a next instruction rule in step320. The next instruction rule may be a next enforcement action or next enforcement rule. The next instruction rule may be one or more of the FAR from step303, QER, URR etc.

In step323, the next UPF node105bforwards the packet in accordance with the next instruction rule, e.g. instructions in the FAR. The forwarded packet may be the same as the packet in step305.

Summarized,FIG.3shows that the next UPF node105bleverages the classification (e.g. PDR matching) done by the first UPF node105a, by means of running a lighter class ID matching instead of the regular PDR matching. The class ID matching is lighter in terms of processing. The class ID matching may comprise to look for a string in the packet, i.e. the Class ID value and match it against the Class ID values in the configuration. Regular PDR matching usually requires complex processing, e.g. L3/L4/L7 analysis and classification or even calculating complex metrics like packet arrival times.

FIG.4aandFIG.4bare signalling diagrams illustrating a method.FIG.4acomprises steps401-412andFIG.4bcomprises steps413-419.FIG.4bmay be described as a continuation ofFIG.4a. In addition to the PCF node101, the SMF node103, the first UPF node105aand the next UPF node105b,FIGS.4aand4bshows the UDR108, the UE114, the AMF node115and the AS125. The signalling diagrams inFIGS.4aand4billustrate a PDU session with two UPFs105. The method inFIGS.4aand4bcomprises at least one of the following steps, which steps may be performed in any suitable order than described below:

Steps401-404described below may be seen as being comprised in a Packet Flow Control Protocol (PFCP) association procedure. The PFCP association procedure is associated with UPF capabilities.

Step401

This step is seen inFIG.4a. The first UPF node105atransmits a PFCP association request message to the SMF node103. The PCFP association request message is a request notifying of UPF capabilities. The PFCP association request comprises a COMU capability of the first UPF node105a. The COMU capability indicates that the first UPF node105ahas a COMU capability, e.g. that it supports COMU. The SMF node103receives the PFCP association request from the first UPF node105a.

Step402

This step is seen inFIG.4a. The SMF node103transmits a PFCP association response message to the first UPF node105a. The first UPF node105areceives the PFCP association response message from the SMF node103. The PFCP association response message is a response to the PFCP association request message in step401. With this, the SMF node103knows that the first UPF node105ahas a COMU capability.

Step403

This step is seen inFIG.4a. The next UPF node105btransmits a PFCP association request message to the SMF node103. The PCFP association request message is a request notifying of UPF capabilities. The PFCP association request comprises a COMU capability. The COMU capability indicates that the next UPF node105bhas a COMU capability, e.g. that it supports COMU. The SMF node103receives the PFCP association request from the next UPF node105b. With this, the SMF node103knows that the next UPF node105bhas a COMU capability.

Step404

This step is seen inFIG.4a. The SMF node103transmits a PFCP association response message to the next UPF node105b. The next UPF node105breceives the PFCP association response message from the SMF node103. The PFCP association response message is a response to the PFCP association request message in step403.

In steps401-404described above, at the PCFP association procedure between the UPF nodes105and the SMF node103, the first UPF node105aand the next UPF node105bwill report their support for COMU or capability of COMU. Based on this, the SMF node103will select a UPF105having a COMU capability. Additionally, the COMU functionality shall be activated or enabled in the UPF105having the COMU functionality. If the COMU functionality is not activated, the UPF105may not perform any action in relation with this functionality. UPF capabilities of UPF nodes105may be reported using a COMU capability parameter or Information Element (IE). This may allow the SMF node103to know which UPFs105support this capability and thus can influence the SMF node's selection of UPF node105. Alternatively, this COMU capability may be split into two different capabilities, e.g. a class identifier and a class indicator. Table 1 below shows UP function features where the COMU capability is seen in the last row.

TABLE 1UP Function FeaturesFeatureOctet/BitFeatureInterfaceDescription5/1BUCPSxa, N4Downlink Data Buffering in CP functionis supported by the UP function.5/2DDNDSxa, N4The buffering parameter ‘Downlink DataNotification Delay’ is supported by theUP function.5/3DLBDSxa, N4The buffering parameter ‘DL BufferingDuration’ is supported by the UP function.5/4TRSTSxb, Sxc,Traffic Steering is supported by the UPN4function.5/5FTUPSxa, Sxb,F-TEID allocation/release in the UPN4function is supported by the UP function.5/6PFDMSxb, Sxc,The PFD Management procedure isN4supported by the UP function.5/7HEEUSxb, Sxc,Header Enrichment of Uplink traffic isN4supported by the UP function.5/8TREUSxb, Sxc,Traffic Redirection Enforcement in the UPN4function is supported by the UP function.6/1EMPUSxa, Sxb,Sending of End Marker packets supportedN4by the UP function.6/2PDIUSxa, Sxb,Support of PDI optimised signalling in UPSxc, N4function (see clause 5.2.1A.2).6/3UDBCSxb, Sxc,Support of UL/DL Buffering ControlN46/4QUOACSxb, Sxc,The UP function supports beingN4provisioned with the Quota Action toapply when reaching quotas.6/5TRACESxa, Sxb,The UP function supports Trace (seeSxc, N4clause 5.x).6/6FRRTSxb, N4The UP function supports FramedRouting (see IETF RFC 2865 [37] andIETF RFC 3162 [38]).6/7PFDESxb, N4The UP function supports a PFD Contentsincluding a property with multiple values.6/8EPFARSxa, Sxb,The UP function supports the EnhancedSxc, N4PFCP Association Release feature (seeclause 5.18).7/1DPDRASxb, Sxc,The UP function supports Deferred PDRN4Activation or Deactivation.7/2ADPDPSxa, Sxb,The UP function supports the ActivationSxc, N4and Deactivation of Pre-defined PDRs(see clause 5.19).7/3UEIPN4The UPF supports allocating UE IPaddresses or prefixes (see clause 5.21).7/4SSETN4UPF support of PFCP sessionssuccessively controlled by different SMFsof a same SMF Set (see clause 5.22).7/5COMUSxb, SxcClassification Optimization for MultipleUPFs capability is supported by the UPfunction.

Steps405-414which will now be described may be seen as being comprised in a PDU session establishment procedure.

Step405

This step is seen inFIG.4a. The UE114transmits a PDU session establishment request message to the AMF node115. The AMF node115receives the PDU session establishment request message from the UE114.

Step406

This step is seen inFIG.4a. The AMF node115transmits a Namf PDU session create message to the SMF node103. The SMF node103receives the Namf PDU session create message from the AMF node115.

Step407

This step is seen inFIG.4a. The SMF node103transmits an Npcf policy request message to the PCF node101. The PCF node101receives the Npcf policy request message from the SMF node103.

Step408

This step is seen inFIG.4a. The PCF node101transmits a UDR policy profile request message to the UDR108. The UDR policy profile request message comprises a Subscription Permanent Identifier (SUPI).

In steps405-409described above, the UE114triggers a PDU session establishment procedure. As part of this procedure, at step409, the PCF node101retrieves the subscriber profile from the UDR108, which in this case indicates that the COMU functionality is required for this subscriber, indicated with COMU required=YES inFIG.4a. The subscriber profile is a profile for the subscriber associated with the UE114.

Step409

This step is seen inFIG.4a. The UDR108transmits a UDR policy profile response message to the PCF node101. The PCF node101receives the UDR policy profile response message from the UDR108. The UDR policy profile response message comprises information indicating that COMU is required.

Step410

This step is seen inFIG.4a. The PCF node101transmits the Npcf policy response message to the SMF node103. The Npcf policy response message may comprise at least one of PCC rules, an indicator indicating COMU etc. The SMF node103receives the Npcf policy response message from the PCF node101.

In this step, the PCF node101installs, in the SMF node103, the policy rules, e.g. PCC rules, for the different applications, e.g. YouTube, Netflix, Facebook, etc. On a per PDU session basis, an indicator indicating COMU is transmitted to the SMF node103. The indicator indicating COMU may be described as a parameter indicating if COMU is to be enabled in the SMF node103. Note that the SMF node103may act as an intermediate network function (NF). The COMU is actually enabled in the UPF105by the SMF node103in step411described below.

Step411

This step is seen inFIG.4a. The SMF node103transmits a PFCP session establishment request message to the first UPF node105a. The first UPF node105areceives the PFCP session establishment request message from the SMF node103. The PFCP session establishment request message may comprise one or more of: PDRs, FARs, QERs, URRs etc. The PDR may comprise a class identifier. The class identifier may be a class ID PDI type. This step may be described as the SMF node103enabling the COMU functionality in the first UPF node105a.

Step412

This step is seen inFIG.4a. The first UPF node105atransmits a PFCP session establishment response message to the SMF node103. The SMF node103receives the PFCP session establishment message from the first UPF node105a.

Steps411-412described above, the SMF node101triggers the PFCP Session Establishment procedure towards the first UPF node105ato indicate the PDRs and the corresponding enforcement actions, e.g. FARs, QERs, URRs, etc. for the PDU session. As the COMU functionality is enabled, the SMF node103will indicate to the first UPF node105ato carry the results of the classification, e.g. matched PDR as class indicator towards the next UPF node105b, by means of extending a PFCP protocol with a class identifier. The class identifier may be referred to as a class ID enrichment IE and may be comprised in a Forwarding Parameters IE in FAR at PFCP Session Establishment Request, as shown in the last row in Table 2:

TABLE 2Forwarding Parameters IE in FAROctet 1 and 2 Forwarding Parameters IE Type = 4 (decimal)Octets 3 and 4 Length = nInformationAppl.elementsPCondition/CommentSxaSxbSxCN4IE TypeDestinationMThis IE shall identify the destinationXXXXDestinationInterfaceinterface of the outgoing packet.InterfaceNetworkOWhen present, this IE shall identify theXXXXNetworkInstanceNetwork instance towards which to sendInstancethe outgoing packet. See NOTE 1.RedirectCThis IE shall be present if the UP function—XXXRedirectInformationis required to enforce traffic redirectionInformationtowards a redirect destination provided bythe CP function.Outer HeaderCThis IE shall be present if the UP functionXX—XOuterCreationis required to add one or more outerHeaderheader(s) to the outgoing packet. IfCreationpresent, it shall contain the F-TEID of theremote GTP-U peer when adding a GTP-U/UDP/IP header, or the Destination IPaddress and/or Port Number when addinga UDP/IP header or an IP header or theC-TAG/S-TAG (for 5GC). See NOTE 2.Transport LevelCThis IE shall be present if the UP functionXX—XTransportMarkingis required to mark the IP header with theLevelDSCP marking as defined byMarkingIETF RFC 2474 [22]. When present forEPC, it shall contain the value of the DSCPin the TOS/Traffic Class field set based onthe QCI, and optionally the ARP prioritylevel, of the associated EPS bearer, asdescribed in clause 5.10 of3GPP TS 23.214 [2]. When present for5GC, it shall contain the value of the DSCPin the TOS/Traffic Class field set based onthe 5QI, the Priority Level (if explicitlysignalled), and optionally the ARP prioritylevel, of the associated QoS flow, asdescribed in clause 5.8.2.7 of3GPP TS 23.501 [28],ForwardingCThis IE shall be present if a specific—XXXForwardingPolicyforwarding policy is required to be appliedPolicyto the packets. It shall be present if theDestination Interface IE is set to SGi-LAN/N6-LAN. It may be present if theDestination Interface is set to Core,Access, or CP-Function. See NOTE 2.When present, it shall contain an Identifierof the Forwarding Policy locally configuredin the UP function.HeaderOThis IE may be present if the UP function—XXXHeaderEnrichmentindicated support of Header Enrichment ofEnrichmentUL traffic. When present, it shall containinformation for header enrichment.Linked TrafficCThis IE may be present, if it is availableXX—XTrafficEndpoint IDand the UP function indicated support ofEndpoint IDthe PDI optimisation feature, (see clause8.2.25). When present, it shall identify theTraffic Endpoint ID allocated for this PFCPsession to receive the traffic in the reversedirection (see clause 5.2.3.1).ProxyingCThis IE shall be present if proxying is to be———XProxyingperformed by the UP function.When present, this IE shall contain theinformation that the UPF shall respond toAddress Resolution Protocol and/or IPv6Neighbour Solicitation based on the localcache information for the Ethernet PDUs.DestinationOThis IE may be present to indicate theXX—X3GPPInterface Type3GPP interface type of the destinationInterfaceinterface, if required by functionalities inTypethe UP Function, e.g. for performancemeasurements.Class-IDOThis IE may be present if the UP function—XXXClass-IDEnrichmentindicated support of OptimizedEnrichmentClassification in Multiple UPF scenarios.When present, it shall compriseinformation for Class-ID enrichment.
Step413

This step is seen inFIG.4b. The SMF node103transmits a PFCP session establishment request message to the next UPF node105b. The next UPF node105breceives the PFCP session establishment request message from the SMF node103. The PFCP session establishment request message comprises one or more of: PDRs, FARs, QERs, URRs etc. The PDR may comprise the class identifier. The class identifier may be a class ID PDI type.

Step414

This step is seen inFIG.4b. The next UPF node105btransmits a PFCP session establishment response message to the SMF node103. The SMF node103receives the PFCP session establishment response message from the next UPF node105b.

In steps413-414, the SMF node103triggers a PFCP session establishment procedure towards the next UPF node105bto indicate the PDRs and the corresponding enforcement actions for the PDU session. The corresponding enforcement actions may be e.g. FARs, QERs, URRs, etc. As the COMU functionality is enabled in the SMF node103, the SMF node103will indicate the next UPF105bto classify application traffic based on the class identifier, e.g.in the GTP-U header, by means of a class indicator. The application traffic may be referred to as user plane traffic. The PFCP protocol may comprise the class indicator. The class indicator, e.g. Class ID, may be a PDI type in the create PDR IE within PFCP Session Establishment Request, as shown in the last row in Table 3 below:

TABLE 3PDI IE within PFCP Session Establishment RequestOctet 1 and 2 PDI IE Type = 2 (decimal)Octets 3 and 4 Length = nInformationAppl.elementsPCondition/CommentSxaSxbSxcN4IE TypeSourceMThis IE shall identify the source interface ofXXXXSourceInterfacethe incoming packet.InterfaceLocal F-TEIDOThis IE shall not be present if TrafficXX—XF-TEIDEndpoint ID is present.If present, this IE shall identify the localF-TEID to match for an incoming packet.The CP function shall set the CHOOSE(CH) bit to 1 if the UP function supports theallocation of F-TEID and the CP functionrequests the UP function to assign a localF-TEID to the PDR.NetworkOThis IE shall not be present if TrafficXXXXNetworkInstanceEndpoint ID is present. It shall be present ifInstancethe CP function requests the UP function toallocate a UE IP address/prefix and theTraffic Endpoint ID is not present.If present, this IE shall identify the Networkinstance to match for the incoming packet.See NOTE 1, NOTE2.UE IP addressOThis IE shall not be present if Traffic—XXXUE IPEndpoint ID is present.addressIf present, this IE shall identify the sourceor destination IP address to match for theincoming packet. (NOTE 5)The CP function shall set the CHOOSE(CH) bit to 1 if the UP function supports theallocation of UE IP address/ prefix and theCP function requests the UP function toassign a UE IP address/prefix to the PDR.TrafficCThis IE may be present if the UP functionXXXXTrafficEndpoint IDhas indicated the support of PDIEndpointoptimization.IDIf present, this IE shall uniquely identify theTraffic Endpoint for that PFCP session.SDF FilterOIf present, this IE shall identify the SDF—XXXSDF Filterfilter to match for the incoming packet.Several IEs with the same IE type may bepresent to provision a list of SDF Filters.The full set of applicable SDF filters, if any,shall be provided during the creation or themodification of the PDI.See NOTE 3.Application IDOIf present, this IE shall identify the—XXXApplicationApplication ID to match for the incomingIDpacket.Ethernet PDUOThis IE may be present to identify all the———XEthernetSession(DL) Ethernet packets matching anPDUInformationEthernet PDU session (see clause 5.13.1).SessionInformationEthernetOIf present, this IE shall identify the Ethernet———XEthernetPacket FilterPDU to match for the incoming packet.PacketSeveral IEs with the same IE type may beFilterpresent to represent a list of EthernetPacket Filters.The full set of applicable Ethernet Packetfilters, if any, shall be provided during thecreation or the modification of the PDI.QFIOIf present, this IE shall identify the QoS———XQFIFlow Identifier to match for the incomingpacket.Several IEs with the same IE type may bepresent to provision a list of QFIs. Whenpresent, the full set of applicable QFIs shallbe provided during the creation or themodification of the PDI.Framed-RouteOThis IE may be present for a DL PDR if the—X—XFramed-UPF indicated support of Framed RoutingRoute(see clause 8.2.25). If present, this IE shalldescribe a framed route.Several IEs with the same IE type may bepresent to provision a list of framed routes.(NOTE 5)Framed-OThis IE may be present for a DL PDR if the—X—XFramed-RoutingUPF indicated support of Framed RoutingRouting(see clause 8.2.25). If present, this IE shalldescribe a framed route.Framed-IPv6-OThis IE may be present for a DL PDR if the—X—XFramed-RouteUPF indicated support of Framed RoutingIPv6-Route(see clause 8.2.25). If present, this IE shalldescribe a framed IPv6 route.Several IEs with the same IE type may bepresent to provision a list of framed IPv6routes. (NOTE 5)SourceOThis IE may be present to indicate theXX—X3GPPInterface Type3GPP interface type of the sourceInterfaceinterface, if required by functionalities in theTypeUP Function, e.g. for performancemeasurements.Class-IDOIf present, this IE shall identify the—XXXClass-IDClass-ID to match for the incomingpacket.

Alternatively, instead of creating a PDI type, e.g. Class-ID, in the PDR, it is also possible to define the Class-ID outside the PDR, as part of a new class detection rule, as opposed to the PDR.

After step414, the PDU session establishment continues.

Steps415-419describe application traffic. The application traffic may be described as data traffic, traffic, packets, user plane traffic. The application traffic may be e.g. YouTube data.

Step415

This step is seen inFIG.4b. The UE114transmits application traffic to the first UPF node105a. The first UPF node105areceives application traffic from the UE114.

Step416

This step is seen inFIG.4b. The first UPF node105adetects the application traffic, performs classification and includes the classification result as a class identifier. The class identifier may be indicated in the FAR.

Step417

This step is seen inFIG.4b. The first UPF node105aforwards the application traffic to the next UPF105b, together with the class identifier. The next UPF105breceives the application traffic together with the class identifier from the first UPF node105a.

In steps415to417, the UE114starts application traffic, e.g. YouTube. The first UPF node105awill detect this application traffic, that will match the corresponding PDR, e.g. PDR with appld=YouTube. After the PDR matching, the corresponding enforcement actions, e.g. QER, URR, FAR, etc., will be performed. The PDR matching may also be referred to as classification. As the COMU functionality is enabled at the first UPF node105afor this PDU session, the following extra step is performed by the first UPF node105a:

The first UPF node105awill include the classification result, e.g. the matched PDR or the corresponding application Id (appld), in the class indicator parameter, as indicated by the

SMF node103in the class identifier IE at step411above. The GTP-U header in N9 interface between UPFs may be extended to convey the class indicator parameter value, so the IP packet encapsulated within the GTP-U header may be carried towards the next UPF nod105b.

Step418

This step is seen inFIG.4b. The next UPF node105bclassifies the incoming application traffic based on the class identifier, e.g. the class ID. The application traffic may be user plane traffic.

Step419

This step is seen inFIG.4b. The next UPF105bforwards the application traffic to the AS125. The AS125receives the application traffic from the next UPF125b.

In steps418and419, the next UPF node105bwill receive the IP packet encapsulated in the GTP-U header. As the COMU functionality is enabled at the second UPF node105bfor this PDU session, the following extra actions will be performed by the second UPF node105b:

The second UPF node105bwill run the PDR matching based on the class identifier, e.g. a class-ID PDI type, as indicated by the SMF node103at step413above. The next UPF node105bwill retrieve the class indicator, e.g. Class-ID retrieved from the GTP-U header, and will match it against the set of PDRs in this PFCP session, which will include the class identifier, e.g. the Class-ID PDI type). This matching procedure results in much less processing than a procedure with extraction of the IP packet and matching it against the existing PDRs of Application ID or Service Data Flow (SDF) filter types.

The method described above will now be described seen from the perspective of the PCF node101.FIG.5is a flowchart describing the method performed by the PCF node101for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105. The method comprises at least one of the following steps to be performed by the PCF node101, which steps may be performed in any suitable order than described below:

Step501

This step corresponds to step407inFIG.4a. The PCF node101receives, from a SMF node103, a policy request fora UE114.

Step502

This step corresponds to steps408and409inFIG.4a. The PCF node101obtains, from a UDR108, an indicator indicating COMU for the UE114.

A profile for the UE114may be obtained together with the indicator indicating COMU. The profile may comprise information associated with e.g. a subscriber associated with the UE114.

Step503

This step corresponds to step410inFIG.4a. The PCF node101transmits, to the SMF node103, a policy response comprising the indicator indicating COMU.

The method described above will now be described seen from the perspective of the SMF node103.FIG.6is a flowchart describing the method performed by the SMF node103for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105. The method comprises at least one of the following steps to be performed by the SMF node103, which steps may be performed in any suitable order than described below:

Step601

This step corresponds to steps401and403inFIG.4a. The SMF node103may receive a COMU capability from at least one of the first UPF node105aand the next UPF node (105b. The COMU capability indicates that the UPF node105, which sends it, is capable of or supports COMU.

The COMU capability may comprise at least one of the class identifier and the class indicator.

Step602

The SMF node103may select the at least one of the first UPF node105aand the next UPF node105bbased on the received COMU capability. The SMF node103may select the UPF node105from which the SMF node103has received a COMU capability. If the first UPF node105asends the COMU capability, then the SMF node103may select the first UPF node105a. If the next UPF node105bsends the COMU capability, then the SMF node103may select the next UPF node105b. If both the first UPF node105aand the next UPF node105bsend a COMU capability, then the SMF node selects both first UPF node105aand next UPF node105b, since they have previously reported that they have COMU capability.

Step603

This step corresponds to step407inFIG.4a. The SMF node103transmits, to a PCF node101, a policy request for a UE114.

Step604

This step corresponds to step410inFIG.4a. The SMF node103receives, from the PCF node101, a policy response comprising an indicator indicating COMU for the UE114. The indicator indicating COMU indicates that a COMU functionality in the SMF node103should be enabled. The indicator indicating COMU is the same as in step409inFIG.4a. The policy response may further comprise control rules for applications.

Step605

This step corresponds to step411inFIG.4a. The SMF node103transmits the following to a first UPF node105:A first detection rule to classify application traffic,First instructions rules to be applied to the classified application traffic, andBased at least on the indicator indicating COMU, a class identifier to identify the classified application traffic towards a next UPF node105b.

The class identifier, apart from being based on the indicator indicating COMU, may also be based on the COMU capability received in step601.

The indicator indicating COMU is the same as in step409inFIG.4a.

The indicator indicating COMU may be described as a UPF class identifier capability, and it is not associated with the UDR108.

The class identifier may be referred to as a Class-ID Enrichment parameter or a Class-ID Enrichment IE.

The application traffic may be user plane traffic.

Step606

This step corresponds to step413inFIG.4b. The SMF node103transmits the following to a next UPF node105b:

Next detection rules to classify application traffic.

Next instructions rules for each next detection rule and to be applied to the classified application traffic, and,

Based at least on the indicator indicating COMU, a class indicator indicating to classify the application traffic received from the first UPF node105ain accordance with the class identifier.

The class indicator, apart from being based on the indicator indicating COMU, may also be based on the COMU capability received in step601.

The indicator indicating COMU may be described as a UPF class identifier capability, and it is not associated with the UDR108.

The class indicator may be referred to as a Class-ID. The class indicator may be a PDI IE comprised in a Create PDR IE, or the class indicator may be a part of a Class Detection Rule.

The class identifier may be referred to as a Class-ID Enrichment parameter or Class-ID Enrichment IE. The class identifier may be a Class-ID Enrichment Information IE comprised in a Forwarding Parameters IE in a FAR.

The application traffic may be user plane traffic.

The method described above will now be described seen from the perspective of the first UPF node105a.FIG.7is a flowchart describing the method performed by the first UPF node105afor enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105. The method comprises at least one of the following steps to be performed by the first UPF node105a, which steps may be performed in any suitable order than described below:

Step700

This step corresponds to step401inFIG.4a. The first UPF node105amay transmit a COMU capability to the SMF node103. The COMU capability indicates that the first UPF node105is capable of or supports COMU.

The COMU capability may comprise at least one of the class identifier and a class indicator.

Step701

This step corresponds to step411inFIG.4a. The first UPF node105areceives, from a SMF node103, a first detection rule to classify application traffic, first instructions rules to be applied to the classified application traffic and a class identifier to identify the classified application traffic towards a next UPF node105b. The application traffic may be user plane traffic.

Step702

This step corresponds to step416inFIG.4b. The first UPF node105adetects the application traffic with the first detection rule.

Step703

This step corresponds to step416inFIG.4b. The first UPF node105aclassifies the application traffic in accordance with the first detection rule. The classification results in a classification result. The classification result may be a PDR ID, e.g. the PDR ID of the matched PDR.

Step704

This step corresponds to step416inFIG.4b. The first UPF node105aapplies the first instruction rules to the classified application traffic.

Step705

This step corresponds to step417inFIG.4b. The first UPF node105aforwards the application traffic toward the next UPF node105balong with the class identifier identifying a classification result.

The application traffic along with the class identifier identifying a classification result may be comprised in an IP packet encapsulated in a GTP-U header.

The method described above will now be described seen from the perspective of the next UPF node105b.FIG.8is a flowchart describing the method performed by the next UPF node105bfor enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105. The method comprises at least one of the following steps to be performed by the next UPF node105b, which steps may be performed in any suitable order than described below:

Step800

This step corresponds to step403inFIG.4a. The next UPF node105bmay transmit a COMU capability to the SMF node103. The COMU capability may indicate that the next UPF node105bis capable of or supports COMU. The COMU capability may be referred to as a COMU capability parameter or COMU capability information.

The COMU capability may comprise at least one of a class identifier and the class indicator.

Step801

This step corresponds to step413inFIG.4b. The next UPF node105breceives the following from a SMF node103:Next detection rules to classify application trafficNext instructions rules for each next detection rule and to be applied to the classified application traffic, andA class indicator indicating to classify application traffic received from a first UPF node105ain accordance with a class identifier identifying a classification result.

The class indicator may be referred to as a Class-ID. The class indicator may be a PDI IE comprised in a Create PDR IE, or the class indicator may be a part of a Class Detection Rule.

The class identifier may be referred to as a Class-ID Enrichment parameter or Class-ID Enrichment IE. The class identifier may be a Class-ID Enrichment Information IE comprised in a Forwarding Parameters IE in a FAR.

The application traffic may be user plane traffic.

Step802

This step corresponds to step417inFIG.4b. The next UPF node105breceives the application traffic from the first UPF node105aalong with the class identifier identifying the classification result.

Step803

This step corresponds to step418inFIG.4b. Based on the class indicator, the next UPF node105bdetermines a second detection rule amongst the next detection rules. The second detection rule matches the classification result identified in the class identifier.

Step804

This step corresponds to step418inFIG.4b. The next UPF node105bclassifies the received application traffic in accordance with the second detection rule and applies instruction rules for the second detection rule to the received application traffic.

Step805

This step corresponds to step419inFIG.4b. The next UPF node150bmay forward the application traffic to an AS125. The AS125may process the received application traffic.

To perform the method steps shown inFIGS.3,4a,4band5for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105, the PCF node101may comprise an arrangement as shown inFIG.100aorFIG.100b, or both.

The PCF node101for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105is adapted to, e.g. by means of a receiving unit1001, receive, from a SMF node103, a policy request for a UE114.

The PCF node101is adapted to, e.g. by means of an obtaining unit1003, obtain, from a UDR108, an indicator indicating COMU for the UE114. A profile for the UE114may be obtained together with the indicator indicating COMU.

The PCF node101is adapted to, e.g. by means of a transmitting unit1005, transmit, to the SMF node103, a policy response comprising the indicator indicating COMU.

The present mechanism performed by the PCF node101may be implemented through one or more processors, such as a processor1010in the PCF node101depicted inFIG.100a, together with computer program code for performing the functions and actions of. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the methods described herein when being loaded into the PCF node101. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the PCF node101.

The PCF node101may comprise a memory1013comprising one or more memory units. The memory1013is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the PCF node101.

The PCF node101may receive information from, e.g. the SMF node103, the first UPF node105a, the next UPF node105b, through a receiving port1015. The receiving port1015may be connected to one or more antennas in PCF node101. The PCF node101may receive information from another structure in the communications system100through the receiving port1015. Since the receiving port1015may be in communication with the processor1010, the receiving port1015may then send the received information to the processor1010. The receiving port1015may also be configured to receive other information.

The processor1010in the PCF node101may be further configured to transmit or send information to e.g. the SMF node103, the first UPF node105a, the next UPF node105b, or another structure in the communications system100, through a sending port1018, which may be in communication with the processor1010, and the memory1013.

The PCF node101may comprise the receiving unit1001, the obtaining unit1003, the transmitting unit1005, other units1008etc., as described above.

The receiving unit1001, the obtaining unit1003, the transmitting unit1005, other units1008described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor1010, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

The different units1001-1008described above may be implemented as one or more applications running on one or more processors such as the processor1010.

The methods described herein for the PCF node101may be respectively implemented by means of a computer program1020product, comprising instructions, i.e., software code portions, which, when executed on at least one processor010, cause the at least one processor1010to carry out the actions described herein, as performed by the PCF node101. The computer program1020product may be stored on a computer-readable storage medium1023. The computer-readable storage medium1023, having stored thereon the computer program1010, may comprise instructions which, when executed on at least one processor1010, cause the at least one processor1010to carry out the actions described herein, as performed by the PCF node101. The computer-readable storage medium1023may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. The computer program1020product may be stored on a carrier comprising the computer program1020just described. The carrier is one of an electronic signal, optical signal, radio signal, or the first computer-readable storage medium1023, as described above.

The PCF node101may comprise a communication interface configured to facilitate communications between the PCF node101and other nodes or devices, e.g., the SMF node103, the first UPF node105a, the next UPF node105b, or another structure. The interface may comprise a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The PCF node101may comprise the arrangement depicted inFIG.100b. The PCF node101may comprise a processing circuitry1025, e.g., one or more processors such as the processor1010, in the PCF node101and the memory1013. The PCF node101may also comprise a radio circuitry1028, which may comprise e.g., the receiving port1015and the sending port1018. The processing circuitry1025may be configured to, or operable to, perform the method actions according toFIGS.3,4a,4band5in a similar manner as that described in relation toFIG.100a. The radio circuitry1028may be configured to set up and maintain at least a wireless connection with the PCF node101. Circuitry may be understood herein as a hardware component.

The PCF node101is operative to operate in the communications system100. The PCF node101may comprise the processing circuitry1025and the memory1013. The memory1013comprises instructions executable by the processing circuitry1025. The PCF node101is operative to perform the actions described herein in relation to the PCF node101, e.g., inFIGS.3,4a,4band5.

To perform the method steps shown inFIGS.3,4a,4band6for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105, the SMF node103may comprise an arrangement as shown inFIG.200aorFIG.200b, or both.

The SMF node103is adapted to, e.g. by means of a transmitting unit2001, transmit, to a PCF node101, a policy request fora UE114.

The SMF node103is adapted to, e.g. by means of a receiving unit2003, receive, from the PCF node101, a policy response comprising an indicator indicating COMU for the UE114. The policy response may comprise control rules for applications.

The SMF node103is adapted to, e.g. by means of the transmitting unit2001, transmit, to a first UPF node105a, a first detection rule to classify application traffic, first instructions rules to be applied to the classified application traffic and, based at least on the indicator indicating COMU, a class identifier to identify the classified application traffic towards a next UPF node105b. The class identifier may be a Class-ID Enrichment IE comprised in a Forwarding Parameters IE in a FAR. The application traffic may be user plane traffic.

The SMF node103is adapted to, e.g. by means of the transmitting unit2001, transmit, to a next UPF node105b, next detection rules to classify application traffic, next instructions rules for each next detection rule and to be applied to the classified application traffic and, based at least on the indicator indicating COMU, a class indicator indicating to classify an application traffic received from the first UPF node105ain accordance with the class identifier. The class indicator may be a PDI comprised in a Create PDR IE, or the class indicator may be a part of a Class Detection Rule.

The SMF node103may be adapted to, e.g. by means of the receiving unit2003, receive a COMU capability from at least one of the first UPF node105aand the next UPF node105b. The COMU capability may comprise at least one of the class identifier and the class indicator.

The SMF node103may be adapted to, e.g. by means of a selecting unit2005, select the at least one of the first UPF node105aand the next UPF node105bbased on the received COMU capability.

The present mechanism performed by the SMF node103may be implemented through one or more processors, such as a processor2010in the SMF node103depicted inFIG.200a, together with computer program code for performing the functions and actions described herein. A processor may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the methods described herein when being loaded into the SMF node103. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the SMF node103.

The SMF node103may comprise a memory2013comprising one or more memory units. The memory2013is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the SMF node103.

The SMF node103may receive information from, e.g. the PCF node101, the first UPF node105a, the next UPF node105b, through a receiving port2015. The receiving port2015may be connected to one or more antennas in SMF node103. The SMF node103may receive information from another structure in the communications system100through the receiving port2015. Since the receiving port2015may be in communication with the processor2010, the receiving port2015may then send the received information to the processor2010. The receiving port2015may also be configured to receive other information.

The processor2010in the SMF node103may be further configured to transmit or send information to e.g. the PCF node101, the first UPF node105a, the next UPF node105b, or another structure in the communications system100, through a sending port2018, which may be in communication with the processor2010, and the memory2013.

The SMF node103may comprise the transmitting unit2001, the receiving unit2003, the selecting unit2005, other units2008etc., as described above. The transmitting unit2001, the receiving unit2003, the selecting unit2005, other units2008described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor2010, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

The different units2001-2008described above may be implemented as one or more applications running on one or more processors such as the processor2010.

The methods described herein for the SMF node103may be respectively implemented by means of a computer program2020product, comprising instructions, i.e., software code portions, which, when executed on at least one processor2010, cause the at least one processor2010to carry out the actions described herein, as performed by the SMF node103. The computer program2020product may be stored on a computer-readable storage medium2023. The computer-readable storage medium2023, having stored thereon the computer program2020, may comprise instructions which, when executed on at least one processor2010, cause the at least one processor2010to carry out the actions described herein, as performed by the SMF node103. The computer-readable storage medium2023may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. The computer program2020product may be stored on a carrier comprising the computer program2020just described. The carrier is one of an electronic signal, optical signal, radio signal, or the first computer-readable storage medium2023, as described above.

The SMF node103may comprise a communication interface configured to facilitate communications between the SMF node103and other nodes or devices, e.g., the PCF node101, the first UPF node105a, the next UPF node105b, or another structure. The interface may comprise a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The SMF node103may comprise the arrangement depicted inFIG.200b. The SMF node103may comprise a processing circuitry2025, e.g., one or more processors such as the processor2010, in the SMF node103and the memory2013. The SMF node103may also comprise a radio circuitry2028, which may comprise e.g., the receiving port2015and the sending port2018. The processing circuitry2025may be configured to, or operable to, perform the method actions according toFIGS.3,4a,4band6in a similar manner as that described in relation toFIG.200a. The radio circuitry2028may be configured to set up and maintain at least a wireless connection with the SMF node103. Circuitry may be understood herein as a hardware component.

The SMF node103is operative to operate in the communications system100. The SMF node103may comprise the processing circuitry2025and the memory2013. The memory2013comprises instructions executable by the processing circuitry2025. The SMF node103is operative to perform the actions described herein in relation to the SMF node103, e.g., inFIGS.3,4a,4band6.

To perform the method steps shown inFIGS.3,4a,4band7for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105, the first UPF node105amay comprise an arrangement as shown inFIG.300aorFIG.300b, or both.

The first UPF node105ais adapted to, e.g. by means of a receiving unit3001, receive, from a SMF node103, a first detection rule to classify application traffic, first instructions rules to be applied to the classified application traffic and a class identifier to identify the classified application traffic towards a next UPF node105b. The application traffic may be user plane traffic.

The first UPF node105ais adapted to, e.g. by means of a detecting unit3003, detect the application traffic with the first detection rule.

The first UPF node105ais adapted to, e.g. by means of a classifying unit3005, classify the application traffic in accordance with the first detection rule.

The first UPF node105ais adapted to, e.g. by means of an applying unit3008, apply the first instruction rules to the classified application traffic.

The first UPF node105ais adapted to, e.g. by means of a forwarding unit3010, forward the application traffic toward the next UPF node105balong with the class identifier identifying a classification result.

The first UPF node105amay be adapted to, e.g. by means of a transmitting unit3013, transmit a COMU capability to the SMF node103. The COMU capability may comprise at least one of the class identifier and a class indicator.

The present mechanism performed by the first UPF node105amay be implemented through one or more processors, such as a processor3020in the first UPF node105adepicted inFIG.300a, together with computer program code for performing the functions and actions described herein. A processor may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the methods described herein when being loaded into the first UPF node105a. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first UPF node105a.

The first UPF node105amay comprise a memory3023comprising one or more memory units. The memory3023is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first UPF node105a.

The first UPF node105amay receive information from, e.g. the PCF node101, the SMF node103, the next UPF node105b, through a receiving port3025. The receiving port3025may be connected to one or more antennas in first UPF node105a. The first UPF node105amay receive information from another structure in the communications system100through the receiving port3025. Since the receiving port3025may be in communication with the processor3020, the receiving port3025may then send the received information to the processor3020. The receiving port3025may also be configured to receive other information.

The processor3020in the first UPF node105amay be further configured to transmit or send information to e.g. the PCF node101, the SMF node103, the next UPF node105b, or another structure in the communications system100, through a sending port3028, which may be in communication with the processor3020, and the memory3023.

The first UPF node105amay comprise the receiving unit3001, the detecting unit3003, the classifying unit3005, the applying unit3008, the forwarding unit3010, the transmitting unit3013, other units3015etc., as described above.

The receiving unit3001, the detecting unit3003, the classifying unit3005, the applying unit3008, the forwarding unit3010, the transmitting unit3013, other units3015described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor3020, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

The different units3001-3015described above may be implemented as one or more applications running on one or more processors such as the processor3020.

The methods described herein for the first UPF node105amay be respectively implemented by means of a computer program3030product, comprising instructions, i.e., software code portions, which, when executed on at least one processor3020, cause the at least one processor3020to carry out the actions described herein, as performed by the first UPF node105a. The computer program3030product may be stored on a computer-readable storage medium3033. The computer-readable storage medium3033, having stored thereon the computer program3030, may comprise instructions which, when executed on at least one processor3020, cause the at least one processor3020to carry out the actions described herein, as performed by the first UPF node105a.

The computer-readable storage medium3033may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. The computer program3030product may be stored on a carrier comprising the computer program3030just described. The carrier is one of an electronic signal, optical signal, radio signal, or the first computer-readable storage medium3033, as described above.

The first UPF node105amay comprise a communication interface configured to facilitate communications between the first UPF node105aand other nodes or devices, e.g., the PCF node101, the SMF node103, the next UPF node105b, or another structure. The interface may comprise a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The first UPF node105amay comprise the arrangement depicted inFIG.300b. The first UPF node105amay comprise a processing circuitry3035, e.g., one or more processors such as the processor3020, in the first UPF node105aand the memory3023. The first UPF node105amay also comprise a radio circuitry3038, which may comprise e.g., the receiving port3025and the sending port3028. The processing circuitry3035may be configured to, or operable to, perform the method actions according toFIGS.3,4a,4band7in a similar manner as that described in relation toFIG.300a. The radio circuitry3038may be configured to set up and maintain at least a wireless connection with the SMF node103, the PCF node101and the next UPF node105b. Circuitry may be understood herein as a hardware component.

The first UPF node105ais operative to operate in the communications system100. The first UPF node105amay comprise the processing circuitry3035and the memory3023.

The memory3023comprises instructions executable by the processing circuitry3035. The first UPF node105ais operative to perform the actions described herein in relation to the first UPF node105a, e.g., inFIGS.3,4a,4band7.

To perform the method steps shown inFIGS.3,4a,4band8for enabling user plane traffic classification in a communications system100supporting CUPS with multiple UPF nodes105, the next UPF node105bmay comprise an arrangement as shown inFIG.400aorFIG.400b, or both.

The next UPF node105bis adapted to, e.g. by means of a receiving unit4001, receive, from a SMF node103, next detection rules to classify application traffic, next instructions rules for each next detection rule and to be applied to the classified application traffic, and a class indicator indicating to classify an application traffic received from a first UPF node105ain accordance with a class identifier identifying a classification result. The application traffic may be user plane traffic.

The next UPF node105bis adapted to, e.g. by means of the receiving unit4001, receive the application traffic from the first UPF node105aalong with the class identifier identifying the classification result. The application traffic along with the class identifier identifying the classification result may be comprised in an IP packet encapsulated in a GTP-U header.

The next UPF node105bis adapted to, e.g. by means of a determining unit4003, based on the class indicator, determine a second detection rule amongst the next detection rules. The second detection rule matches the classification result identified in the class identifier.

The next UPF node105bis adapted to, e.g. by means of a classifying unit4005, classify the received application traffic in accordance with the second detection rule and applying instruction rules for the second detection rule to the received application traffic.

The next UPF node105bmay be adapted to, e.g. by means of a transmitting unit4008, transmit a COMU capability to the SMF node103. The COMU capability may comprise at least one of a class identifier and the class indicator.

The next UPF node105bmay be adapted to, e.g. by means of a forwarding unit4010. forward the application traffic to an AS125.

The present mechanism performed by the next UPF node105bmay be implemented through one or more processors, such as a processor4020in the next UPF node105bdepicted inFIG.400a, together with computer program code for performing the functions and actions described herein. A processor may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the methods described herein when being loaded into the next UPF node105b. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the next UPF node105b.

The next UPF node105bmay comprise a memory4023comprising one or more memory units. The memory4023is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the next UPF node105b.

The next UPF node105bmay receive information from, e.g. the PCF node101, the SMF node103, the first UPF node105a, through a receiving port4025. The receiving port4025may be connected to one or more antennas in next UPF node105b. The next UPF node105bmay receive information from another structure in the communications system100through the receiving port4025. Since the receiving port4025may be in communication with the processor4020, the receiving port4025may then send the received information to the processor4020. The receiving port4025may also be configured to receive other information.

The processor4020in the next UPF node105bmay be further configured to transmit or send information to e.g. the PCF node101, the SMF node103, the first UPF node105a, or another structure in the communications system100, through a sending port4028, which may be in communication with the processor4020, and the memory4023.

The next UPF node105bmay comprise the receiving unit4001, the determining unit4003, the classifying unit4005, the transmitting unit4008, the forwarding unit4010, other units4013etc., as described above.

The receiving unit4001, the determining unit4003, the classifying unit4005, the transmitting unit4008, the forwarding unit4010, other units4013described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor4020, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

The different units4001-413described above may be implemented as one or more applications running on one or more processors such as the processor4020.

The methods described herein for the next UPF node105bmay be respectively implemented by means of a computer program4030product, comprising instructions, i.e., software code portions, which, when executed on at least one processor4020, cause the at least one processor4020to carry out the actions described herein, as performed by the next UPF node105b. The computer program4030product may be stored on a computer-readable storage medium4033. The computer-readable storage medium4033, having stored thereon the computer program4030, may comprise instructions which, when executed on at least one processor4020, cause the at least one processor4020to carry out the actions described herein, as performed by the next UPF node105b. The computer-readable storage medium4033may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. The computer program4030product may be stored on a carrier comprising the computer program4030just described. The carrier is one of an electronic signal, optical signal, radio signal, or the first computer-readable storage medium4033, as described above.

The next UPF node105bmay comprise a communication interface configured to facilitate communications between the next UPF node105band other nodes or devices, e.g., the PCF node101, the SMF node103, the first UPF node105a, or another structure. The interface may comprise a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The next UPF node105bmay comprise the arrangement depicted inFIG.400b. The next UPF node105bmay comprise a processing circuitry4035, e.g., one or more processors such as the processor4020, in the next UPF node105band the memory4023. The next UPF node105bmay also comprise a radio circuitry4038, which may comprise e.g., the receiving port4025and the sending port4028. The processing circuitry4035may be configured to, or operable to, perform the method actions according toFIGS.3,4a,4band8in a similar manner as that described in relation toFIG.400a. The radio circuitry4038may be configured to set up and maintain at least a wireless connection with the SMF node103, the PCF node101and the first UPF node105a. Circuitry may be understood herein as a hardware component.

The next UPF node105bis operative to operate in the communications system100. The next UPF node105bmay comprise the processing circuitry4035and the memory4023. The memory4023comprises instructions executable by the processing circuitry4035. The next UPF node105bis operative to perform the actions described herein in relation to the next UPF node105b, e.g., inFIGS.3,4a,4band8.

In summary, the PFCP protocol for the SMF node103is extended to indicate to the first UPF node105aand the next UPF node105bto apply COMU in a scenario of multiple UPFs105, in the context of 5G networks supporting CUPS.

This disclosure relates to packet core in 5G. The disclosure also relates to policy, e.g. application traffic analysis and/or application traffic classification, in the context of 3GPP CUPS.

The user plane traffic classification in a scenario of multiple UPFs105is optimized by extending the 3GPP PFCP protocol with at least one of the following:A COMU capability in the PFCP Association procedure.A class identifier, e.g. a Class-ID Enrichment IE in the Forwarding Parameters IE in FAR at PFCP Session Establishment/Modification Request, for the SMF node103to indicate to the first UPF105ato convey the class indicator, e.g. Class-ID, to the next UPF node105b.A class indicator, e.g. a PDI type, Class-ID in the Create PDR IE within PFCP Session Establishment/Modification Request, for the SMF node103to indicate to the first UPF105ato match incoming application traffic based on the class indicator, e.g. Class-ID.

The present disclosure is not limited to the above description. Various alternatives, modifications and equivalents may be used. Therefore, the above disclosure should not be taken as limiting the scope, which is defined by the appended claims. A feature may be combined with one or more other features disclosed herein.

The term “at least one of A and B” should be understood to mean “only A, only B, or both A and B.”, where A and B are any parameter, number, indication used herein etc.

It should be emphasized that the term “comprises/comprising” when used in this specification is taken to specify the presence of stated features, integers, steps or components, but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. It should also be noted that the words “a” or “an” preceding an element do not exclude the presence of a plurality of such elements.

The term “configured to” used herein may also be referred to as “arranged to”, “adapted to”, “capable of” or “operative to”.

It should also be emphasised that the steps of the methods defined in the appended claims may be performed in another order than the order in which they appear in the claims.