WO2019158116A1

WO2019158116A1 - Sx protocol extension to support node pdr

Info

Publication number: WO2019158116A1
Application number: PCT/CN2019/075136
Authority: WO
Inventors: Yumei SONG; Jiehong YANG; Carlos JIMENEZ CORDON; Miguel Angel Munoz De La Torre Alonso; Miguel Angel PUENTE PESTANA
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2018-02-15
Filing date: 2019-02-15
Publication date: 2019-08-22
Also published as: BR112020016497A8; JP7153077B2; JP2021520679A; EP3753149A1; BR112020016497A2; EP3753149A4; BR112020016497B1; EP3753149B1; US11540339B2; US20200396779A1

Abstract

The embodiments herein relate to Sx protocol extension to support node PDR. In one embodiment, there proposes a method (500) in a first network node (301) configured as control plane function (CPF). The first network node (301) is coupled to a second network node (302) configured as user plane function (UPF) via an Sx interface. The method (500) comprising transmitting (S501) a message associated with a Packet Detection Rule (PDR) to the second network node (302) via the Sx interface, wherein the PDR is applicable to more than one Sx session. With embodiments herein, the CPF-UPF signaling throughput can be minimized significantly, and the memory footprint per Sx session can be decreased.

Description

SX PROTOCOL EXTENSION TO SUPPORT NODE PDR

Technical Field

The embodiments herein relate generally to the field of communication, and more particularly, the embodiments herein relate to Sx protocol extension to support node PDR.

Background

The third Generation Partnership Project (3GPP) Technical Specification TS 23.214 v14.2.0, which is incorporated herein by reference, specifies the overall stage 2 level functionality for control and user plane separation of Evolved Packet Core (EPC) 's Serving Gateway (SGW) , Packet Data Network Gateway (PGW) , and Traffic Detection Function (TDF) . This enables a flexible placement of the separated control plane and user plane functions for supporting diverse deployment scenarios (e.g. central or distributed user plane function) without affecting the overall functionality provided by these EPC entities.

Figure 1 is a schematic block diagram showing the architecture reference model in the case of separation between control plane and user plane. This architecture reference model covers non-roaming as well as home routed and local breakout roaming scenarios.

Furthermore, the usage of a combined SGW/PGW remains possible in a deployment with separated control and user planes. This is enabled by supporting an Sx interface with a common parameter structure for non-combined and combined cases. Figure 2 is a schematic block diagram showing the architecture reference model for a combined SGW/PGW in the case of separation between control plane and user plane.

Besides, 3GPP TS 29.244 v14.1.0, which is incorporated herein by reference, specifies the Packet Forwarding Control Protocol (PFCP) used on the interface between the control plane and the user plane function in a split SGW, PGW and TDF architecture in EPC. Sx protocol (PFCP) detailed in 3GPP TS 29.244 v14.1.0 provides a standard interface where a Control Plane (CP) can instruct a User Plane (UP) with the applicable Packet Detection Rules (PDRs) , Forwarding Action Rule (FAR) -ID, Usage Reporting Rule (URR) -ID, Quality of Service Enforcement Rule (QER) -ID, … on per Sx session basis.

Summary

In 3GPP TS 29.244 v14.1.0, the PDR is instructed by CP to UP on per Sx session basis. Thus, when a user session is requested to be started, the Control Plane (CP) will forward to the User Plane (UP) all the PDRs applicable to the traffic, which this user will generate along the session. Packets for this user session will be matching the different PDRs for the Sx session and needed actions will be taken for the packets according to the rules (FAR, QER, URR, .. ) linked to the PDR matched.

This means that the UP will handle a big amount of Sx sessions, where each of these Sx sessions will handle a list of PDRs.

There are scenarios in which, on top of the ongoing and active Sx sessions, CP will need to instruct with a PDR that is applicable to all the Sx sessions or applicable to a group of Sx sessions. To achieve it, considering 3GPP TS 29.244 v14.1.0, it will imply:

· to trigger an Sx Session Modification procedure for each of the active Sx Session. Each of these Sx Session Modification procedures will include exactly the same and new PDR.

· to add this new PDR in every new Sx Session establishment procedure.

This is not optimal from CP-UP Sx signaling point of view, as an Sx Session Modification procedure with the same PDR has to be sent by the CP to the UP as many times as active Sx sessions, and it is not optimal from UP memory point of view as the same PDR (with the same information) will have to be stored in all active Sx sessions and new Sx sessions.

As an example, following scenarios will be subject to be handled with the procedure stated above, where the same PDR will have to be provisioning to all existing and new Sx sessions:

· any TCP signaling (either setup and/or teardown) to be charged with a special rate;

· any TCP retransmitted packets, to be free of charge;

· any tethering traffic, to be charge with a different rate;

· traffic matching a default catch-all filter which will be charged in the same rate, and so on.

In view of the above typical case, the embodiments herein propose to optimize the way a CP shall instruct a PDR that it is applicable to all active Sx sessions, a group of Sx sessions, or the new Sx session to be created.

In one embodiment, there proposes a method in a first network node configured as control plane function (CPF) , the first network node is coupled to a second network node configured as user plane function (UPF) via an Sx interface, the method comprising: transmitting a message associated with a PDR to the second network node via the Sx interface, wherein the PDR is applicable to more than one Sx session.

In another embodiment, there proposes a method in a second network node configured as UPF, the second network node is coupled to a first network node configured as CPF via an Sx interface, the method comprising: receiving a message associated with a PDR from the first network node via the Sx interface, wherein the PDR is applicable to more than one Sx session.

In yet another embodiment, there proposes a first network node configured as CPF, the first network node is coupled to a second network node configured as UPF via an Sx interface, the first network node comprising: at least one processor; and a non-transitory computer readable medium coupled to the at least one processor, the non-transitory computer readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to: transmit a message associated with a PDR to the second network node via the Sx interface, wherein the PDR is applicable to more than one Sx session.

In yet another embodiment, there proposes a second network node configured as UPF, the second network node is coupled to a first network node configured as CPF via an Sx interface, the second network node comprising: at least one processor; and a non-transitory computer readable medium coupled to the at least one processor, the non-transitory computer readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to: receive a message associated with a PDR from the first network node via the Sx interface, wherein the PDR is applicable to more than one Sx session.

In yet another embodiment, there proposes a computer readable medium comprising computer readable code, which when run on an apparatus, causes the apparatus to perform any of the above methods.

With embodiments herein, which support PDRs applicable to all active Sx sessions or a group of Sx sessions, the CPF-UPF signaling throughput can be minimized significantly, and the memory footprint per Sx session can be decreased.

Brief Description of the Drawings

The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments of the present disclosure and, together with the description, further serve to explain the principles of the disclosure and to enable a person skilled in the pertinent art to make and use the embodiments disclosed herein. In the drawings, like reference numbers indicate identical or functionally similar elements, and in which:

Figure 1 is a schematic block diagram showing the architecture reference model in the case of separation between control plane and user plane;

Figure 2 is a schematic block diagram showing the architecture reference model for a combined SGW/PGW in the case of separation between control plane and user plane;

Figure 3 is a schematic block diagram showing an example communication system, in which the embodiments herein may be implemented;

Figure 4 is a schematic flow chart showing an example packet processing flow in the second network node, according to the embodiments herein;

Figure 5 is a schematic flow chart showing an example method in the first network node, according to the embodiments herein;

Figure 6 is a schematic flow chart showing an example method in the second network node, according to the embodiments herein;

Figure 7 is a schematic block diagram showing an example first network node, according to the embodiments herein;

Figure 8 is a schematic block diagram showing an example second network node, according to the embodiments herein;

Figure 9 is a schematic block diagram showing an apparatus, according to the embodiments herein.

Detailed Description of Embodiments

Embodiments herein will be described in detail hereinafter with reference to the accompanying drawings, in which embodiments are shown. These embodiments herein may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. The elements of the drawings are not necessarily to scale relative to each other.

Reference to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase "in one embodiment" appearing in various places throughout the specification are not necessarily all referring to the same embodiment.

The term "A, B, or C" used herein means "A" or "B" or "C" ; the term "A, B, and C" used herein means "A" and "B" and "C" ; the term "A, B, and/or C" used herein means "A" , "B" , "C" , "A and B" , "A and C" , "B and C" or "A, B, and C" .

The embodiments herein propose a new Sx node related procedure that will be used by the CP to instruct the UP those PDRs that are applicable to all active Sx sessions or to a group of Sx Sessions. The PDRs instructed by the CP will be handled by UP in a separate way to the traditional PDRs instructed per Sx session.

Figure 3 is a schematic block diagram showing an example communication system 300, in which the embodiments herein may be implemented.

In one embodiment, the communication system 300 may include but not limit to a first network node 301 and a second network node 302. The first network node 301 may be configured as control plane function, which also may be referred as CPF, CP function, or CP. The second network node 302 may be configured as user plane function, which also may be referred as UPF, UP function, or UP. The first network node 301 and the second network node 302 may be coupled to each other via an interface, which may be referred as Sx interface or Sx reference point.

In one embodiment, the first network node 301 may be configured as SGW CPF (SGW-C) , the second network node 302 may be configured as SGW UPF (SGW-U) , and the Sx interface may be Sxa interface between SGW-C and SGW-U.

In another embodiment, the first network node 301 may be configured as PGW CPF (PGW-C) , the second network node 302 may be configured as PGW UPF (PGW-U) , and the Sx interface may be Sxb interface between PGW-C and PGW-U.

In yet another embodiment, the first network node 301 may be configured as TDF CPF (TDF-C) , the second network node 302 may be configured as TDF UPF (TDF-U) , and the Sx interface may be Sxc interface between TDF-C and TDF-U.

In still yet another embodiment, the first network node 301 may be configured as combined SGW/PGW CPF (SGW/PGW-C) , the second network node 302 may be configured as combined SGW/PGW UPF (SGW/PGW-U) , and the Sx interface may be combined Sxa/Sxb interface between SGW/PGW-C and SGW/PGW-U.

To solve the problem in the prior art, the following embodiments are proposed at Sx procedure level and at traffic level.

Sx procedures level

A new procedure, for example Sx Node PDR Management Request and Response procedure, is proposed to be used by CP and UP for those scenarios where a PDR is applicable to all active Sx sessions or a group of Sx sessions, i.e., applicable to more than one Sx session. Note that, the proposed PDR type may be referred as node PDR or Node PDR whilst the standardized PDR may be referred as Sx session PDR.

Within Sx Node PDR Management Request message, the following Information Elements (IEs) are needed to be instructed by CP (e.g., the first network node 301) :

· the node PDR information. This PDR will have most of the IEs than an Sx session PDR, but:

There is no CP F-SEID IE, UP F-SEID IE, . etc which are used to identify the Sx session, since the Node PDR is applicable to more than one Sx session;

Relevant rules (FAR, QER, URR) identity linked to any Node PDR can also be linked from an Sx session PDR, meaning that there will not be a kind of Node FAR, Node QER, ....

· New IE, NodePDRId, is used to uniquely identify the Node PDR among all the other Node PDRs;

· New IE, GroupedSessionIdentity, is used to specify to which Sx sessions the Node PDR is applicable. A specific value (e.g., 0) can be used to indicate that the Node PDR is applicable to all the Sx sessions.

Within Sx Node PDR Management Request message, CP function (e.g., the first network node 301) will provide any change (s) , such as:

· Add new Node PDR (s) ;

· Change any field on existing Node PDR (s) ;

· Remove existing Node PDR (s) .

Within Sx Node PDR Management Response message, UP function (e.g., the second network node 302) will response "successful" if related actions are completed finely, otherwise the response will be "unsuccessful" .

Moreover, it is also needed a change in existing Sx session procedures to handle properly already mentioned GroupedSessionIdentity IE. Therefore, CP function will provide the GroupedSessionIdentity IE in the following procedure:

· Sx Session Establishment Request procedure, to indicate if this Sx session is included in a GroupedSessionIdentity.

· Sx Session Modification Request procedure, to indicate any modification related with GroupedSessionIdentity IE for this Sx session.

GroupedSessionIdentity IE is applicable on per Sx session and UP function will store this IE together with the rest of information for this Sx session.

It shall be upto the CP to define what is behind each of the GroupedSessionIdentity. As an example, one GroupedSessionIdentity can group all subscribers related with electric metering devices, so that each time an Sx session is established for any of these subscriptions, the right GroupedSessionIdentity shall be sent in any of these Sx Session Establishment procedures.

Alternative Sx procedure level

Alternatively, the above Sx procedure level may be embodied in three separate procedures:

· Sx Node PDR Establishment Request and Response procedure

· Sx Node PDR Modification Request and Response procedure

· Sx Node PDR Deletion Request and Response procedure.

Within Sx Node PDR Establishment Request procedure, following IEs are needed to be instructed by CP:

· the Node PDR (s) information. This PDR will have most of the IEs of an Sx session PDR, but:

There is no IEs such as CP F-SEID IE, UP F-SEID IE, . etc which are used to identify the Sx session, since the Node PDR is applicable to more than one Sx session.

Precedence for a Node PDR will be applicable among the rest of the Node PDRs together with session PDRs.

· New IE, NodePDRApplicability, to specify is the Node PDR is applicable to all Sx Sessions or the Node PDR is only applicable to a group of Sx sessions.

· When the Node PDR is applicable to a group of Sx sessions, another new IE, GroupedSessionIdentity, has to be instructed from CP. This may be understood as an identifier that will allow UPF to know to which Sx Sessions this Node PDR will apply.

Within Sx Node PDR Modification Request procedure, CP function will provide any change on an already existing Node PDR (s) like:

· Change on any field under PDR IE

· Change on NodePDRApplicability IE

· Change on GroupedSessionIdentity IE.

Within Sx Node PDR Deletion Request procedure, CP function will provide the Node PDR (s) to be deleted.

For these new three procedures, UP function will response "successful" if related actions are completed finely, otherwise, response will be "unsuccessful" .

Traffic level

Figure 4 is a schematic flow chart showing an example packet processing flow in the second network node 302, according to the embodiments herein.

For the payload traffic, it must be considered that:

· All Node PDRs will have their own precedence and they shall be evaluated together with session level PDR (s) .

· Along all Node PDRs, there could be Node PDR (s) applicable to all Sx sessions and Node PDR (s) applicable to a group of Sx sessions.

Therefore, when a payload packet is received in the UP, the following actions will be executed in the order described below:

· Sx session lookup is performed, to identify an Sx session to which a received user plane packet corresponds.

· When Sx session is known, it will be checked ifany Node PDR (s) is applicable to this Sx session. In one embodiment, one or more node PDRs applicable to the Sx session are found.

· If any, Node PDRs will be evaluated in precedence order together with session level PDR (s) . In one embodiment, the one or more node PDRs together with a session level PDR are evaluated in decreasing order of precedence, and the first matched PDR is selected.

· Apply instruction sets in the selected PDR, i.e., the first matched PDR.

As described above, the embodiments herein provide a new level of PDR, i.e., Node PDR. This PDRs type are defined to be applied to all Sx sessions or a group of Sx sessions.

By the embodiments herein, the following technical effects may be achieved:

· minimizing significantly the CP-UP signaling throughput, as there is no need to provide repeatedly a plurality of identical PDRs for a plurality of applicable Sx sessions (i.e., one node PDR may be enough) ; and

· decreasing the memory footprint per Sx session, as there is no need to store repeatedly a plurality of identical PDRs for a plurality of applicable Sx sessions (i.e., one node PDR may be enough) .

Figure 5 is a schematic flow chart showing an example method 500 in the first network node, according to the embodiments herein. In one embodiment, the flow chart in Figure 5 can be implemented in the first network node 301 in Figure 3.

The method 500 may begin at step S501, in which the first network node 301 may transmit a message associated with a PDR to the second network node 302, wherein the PDR may be applicable to more than one Sx session. The PDR is a node PDR, which is distinguishable from the traditional Sx session level PDR (the traditional Sx session PDR needs IE to identify an Sx session) .

In one embodiment, the first network node 301 (CPF) initiates the Sx Node PDR Management procedure to create a new Node PDR or to modify /delete an existing Node PDR. The CPF shall provide all the new, updated or deleted Rules. The updated Rules shall contain only the information which is to be changed, added and/or deleted.

In one embodiment, the node PDR may include a NodePDRId IE to identify the node PDR among all the other PDRs. An example NodePDRId IE may be coded as the following form:

Octets 5 to 6 contain the Rule ID and shall be encoded as an integer.

Furthermore, the node PDR may also include a GroupedSessionIdentity IE to identify a session group to which the node PDR is applicable. For the node PDR applicable to all Sx sessions, the GroupedSessionIdentity IE may be set to a specific value, for example 0. An example GroupedSessionIdentity IE may be coded as the following form:

The Grouped Session Identity value shall be encoded as Octet string. Note that, the Grouped Session Identity value "0" represents all sessions on the Node.

In one embodiment, the node PDR may also include a precedence IE to indicate its precedence when being applied by the second network node 302. Furthermore, the node PDR may include an indication of action (or rule) to be performed by the second network node 302.

In one embodiment, the message may be an Sx Node PDR Management Request message. An example Sx Node PDR Management Request message may be the following form:

In the Sx Node PDR Management Request message, the first network node 301 may instruct the second network node 302 to: add a node PDR; change a field on a node PDR; and/or remove a node PDR.

An example Create Node PDR IE can be the following form:

An example PDI IE can be the following form:

An example Update Node PDR IE can be the following form:

In one embodiment, the first network node 301 instructs the GroupedSessionIdentity IE in the following procedure:

· Sx Node PDR Management Request procedure, to indicate to which Sx sessions the node PDR will apply;

· Sx Session Establishment Request procedure, to indicate if the Sx session is included in a GroupedSessionIdentity; and

· Sx Session Modification Request procedure, to indicate any modification related with GroupedSessionIdentity IE for the Sx session.

Then, the method 500 may proceed to step S502, in which the first network node 301 may receive an Sx Node PDR Management Response message from the second network node 302 to indicate whether the Sx Node PDR Management Request message is accepted or rejected.

In one embodiment, when the first network node 301 (CPF) receives an Sx Node PDR Management Response with the cause "success" , it shall continue with the procedure which has initiated the Sx Node PDR Management procedure.

The above steps are only examples, and the first network node 301 can perform any actions described in connection to Figures 3, to manage the node PDR, by for example Sx Node PDR Management Request and Response procedure.

Figure 6 is a schematic flow chart showing an example method 600 in the second network node, according to the embodiments herein. In one embodiment, the flow chart in Figure 6 can be implemented in the second network node 302 in Figure 3.

The method 600 may begin at step S601, in which the second network node 302 may receive a message associated with a PDR from the first network node 301, wherein the PDR is applicable to more than one Sx session. The PDR is a node PDR, which is distinguishable from the traditional Sx session level PDR (the traditional Sx session PDR needs IE to identify an Sx session) .

In one embodiment, the node PDR may include a NodePDRId IE to identify the node PDR among all the other PDRs. Furthermore, the node PDR may also include a GroupedSessionIdentity IE to identify a session group to which the node PDR is applicable. For the node PDR applicable to all Sx sessions, the GroupedSessionIdentity IE may be set to a specific value, for example 0. In one embodiment, the node PDR may also include aprecedence IE to indicate its precedence when being applied by the second network node 302. Furthermore, the node PDR may include an indication of action (or rule) to be performed by the second network node 302.

In one embodiment, the message may be an Sx Node PDR Management Request message. In the Sx Node PDR Management Request message, the first network node 301 may instruct the second network node 302 to: add a node PDR; change a field on a node PDR; and/or remove a node PDR.

Then, the method 600 may proceed to step S602, in which the second network node 302 may apply the node PDR to more than one Sx session. In one embodiment, when applying the node PDR, the second network node 302 may perform the following actions:

-performing Sx session lookup, to identify an Sx session to which an received user plane packet corresponds;

-finding one or more node PDR applicable to the Sx session;

-selecting the first PDR matching to the received user plane packet among the one or more node PDR together with a session level PDR in decreasing order ofprecedence; and

-triggering the action (s) related to the PDR selected.

A packet matches a PDR if all the match fields of the Packet Detection Information (PDI) of the PDR are matching the corresponding packet header fields. If a match field is not included in the PDI, it shall be considered as matching all possible values in the header field of the packet. If the match field is present and does not include a mask, the match field shall be considered as matching the corresponding header field of the packet if it has the same value. If the match field is present and includes a mask (e.g. IP address with a prefix mask) , the match field shall be considered as matching the corresponding header field of the packet if it has the same value for the bits which are set in the mask.

In one embodiment, the precedence of the one or more node PDR is higher than the precedence of the session level PDR, so that the node PDR is considered firstly. The second network node 302 (UPF) may drop packets unmatched with any PDR (s) .

Then, the method 600 may proceed to step S603, in which the second network node 302 may transmit an Sx Node PDR Management Response message to the first network node 302 to indicate whether the Sx Node PDR Management Request message is accepted or rejected. Note that, the above steps S602 and S603 can be performed in any sequence, performed at the same time, or performed separately.

In one embodiment, the second network node 302 may perform respective action (s) as instructed by the first network node 301, for example, the second network node 302 may add a node PDR; change a field on a node PDR; and/or remove a node PDR. If the second network node 302 completes the actions finely, it will send Sx Node PDR Management Response message to indicate that the Sx Node PDR Management Request message is accepted. Otherwise, the second network node 302 may send Sx Node PDR Management Response message to indicate that the Sx Node PDR Management Request message is rejected and the reason (s) why this message is rejected.

In one embodiment, when the second network node 302 (UPF) receives an Sx Node PDR Modification Request, it shall:

-update and apply the rules received in the request and send an Sx Node PDR Management Response with cause "success" , if all rules in the Sx Node PDR Management Request are accepted and applied;

-Otherwise, if at least one rule failed to be updated or applied, return an appropriate error cause value with the Rule ID of the Rule causing the first error, discard all the received rules.

An example Sx Node PDR Management Response message can be the following form:

The above steps are only examples, and the second network node 302 can perform any actions described in connection to Figures 3-4, to manage the node PDR, by for example Sx Node PDR Management Request and Response procedure, and to apply the node PDR to the received packet.

Figure 7 is a schematic block diagram showing an example first network node 301, according to the embodiments herein.

In one embodiment, the first network node 301 may include at least one processor 701; and a non-transitory computer readable medium 702 coupled to the at least one processor 701. The non-transitory computer readable medium 702 contains instructions executable by the at least one processor 701, whereby the at least one processor 701 is configured to perform the steps in the example method 500 as shown in the schematic flow chart of Figure 5; the details thereof is omitted here.

Note that, the first network node 301 can be performed as hardware, software, firmware and any combination thereof. For example, the first network node 301 may include a plurality of units, circuities, or modules, each of which can be used to perform a step of the example method 500 or any step shown in Figure 3-4 related to the first network node 301.

Figure 8 is a schematic block diagram showing an example second network node 302, according to the embodiments herein.

In one embodiment, the second network node 302 may include at least one processor 801; and a non-transitory computer readable medium 802 coupled to the at least one processor 801. The non-transitory computer readable medium 802 contains instructions executable by the at least one processor 801, whereby the at least one processor 801 is configured to perform the steps in the example method 600 as shown in the schematic flow chart of Figure 6; the details thereof is omitted here.

Note that, the second network node 302 can be performed as hardware, software, firmware and any combination thereof. For example, the second network node 302 may include a plurality of units, circuities, or modules, each of which can be used to perform a step of the example method 600 or any step shown in Figure 3-4 related to the second network node 302.

Figure 9 is a schematic block diagram showing an apparatus 900, according to the embodiments herein. In one embodiment, the apparatus 900 can be configured as the above mentioned apparatus, such as the first network node 301 or the second network node 302.

In one embodiment, the apparatus 900 may include but not limited to at least one processor such as Central Processing Unit (CPU) 901, a computer-readable medium 902, and a memory 903. The memory 903 may comprise a volatile (e.g. Random Access Memory, RAM) and/or non-volatile memory (e.g. a hard disk or flash memory) . In one embodiment, the computer-readable medium 902 may be configured to store a computer program and/or instructions, which, when executed by the processor 901, causes the processor 901 to carry out any of the above mentioned methods.

In one embodiment, the computer-readable medium 902 (such as non-transitory computer readable medium) may be stored in the memory 903. In another embodiment, the computer program can be stored in a remote location for example computer program product 904 (also can be embodied as computer-readable medium) , and accessible by the processor 901 via for example carrier 905.

The computer-readable medium 902 and/or the computer program product 904 can be distributed and/or stored on a removable computer-readable medium, e.g. diskette, CD (Compact Disk) , DVD (Digital Video Disk) , flash or similar removable memory media (e.g. compact flash, SD (secure digital) , memory stick, mini SD card, MMC multimedia card, smart media) , HD-DVD (High Definition DVD) , or Blu-ray DVD, USB (Universal Serial Bus) based removable memory media, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or distributed as a propagated signal via a network (e.g. Ethernet, ATM, ISDN, PSTN, X. 25, Internet, Local Area Network (LAN) , or similar networks capable of transporting data packets to the infrastructure node) .

The following further aspects are proposed herein:

Aspect 1: A method for installing/creating PDRs which affects all the Sx sessions or a subset of the Sx sessions in the UPF.

Aspect 2. The method of aspect 1, comprising:

a. Sx Node PDR Management Request and Response message. The request including:

i. Create new Node PDR (s) .

1) the Node PDR parameters along with the list of session IDs that the PDR applies to,

2) a PDR precedence,

3) and an optional indication of a group of sessions that the PDR applies to (group ID) .

ii. Update Node PDR (s) , to modify the corresponding Node PDR parameters.

iii. Delete Node PDR (s) , to delete a certain Node PDR (s) .

b. The response on above procedure indicating the creation success.

Aspect 3. Existing Sx Session Establishment procedure, including an indication if the session belongs to a group.

Aspect 4. Existing Sx Session Modification procedure, including any modification on the group the session belongs to.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or non-transitory computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block (s) .

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc. ) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry, ” “a module” or variants thereof.

It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the following examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Abbreviations

3GPP third Generation Partnership Project

CPF Control Plane Function

EPC Evolved Packet Core

FAR Forwarding Action Rule

PCRF Policy and Charging Rule Function

PDI Packet Detection Information

PDR Packet Detection Rule

PFCP Packet Forwarding Control Protocol

PGW Packet Data Network Gateway

PGW-C PDN Gateway Control Plane Function

PGW-U PDN Gateway User Plane Function

QER QoS Enforcement Rule

SGW Servicing Network Gateway

SGW-C Serving Gateway Control Plane Function

SGW-U Serving Gateway User Plane Function

TDF Traffic Detection Function

TDF-C Traffic Detection Function Control Plane Function

TDF-U Traffic Detection Function User Plane Function

UPF User Plane Function

URR Usage Reporting Rule.

Claims

A method (500) in a first network node (301) configured as control plane function (CPF) , the first network node (301) is coupled to a second network node (302) configured as user plane function (UPF) via an Sx interface, the method (500) comprising:

- transmitting (S501) a message associated with a Packet Detection Rule (PDR) to the second network node (302) via the Sx interface, wherein the PDR is applicable to more than one Sx session.
the method (500) according to claim 1, wherein the PDR is a node PDR, and the message is an Sx Node PDR Management Request message.
the method (500) according to claim 2, wherein the Sx Node PDR Management Request message indicates at least one of:

· a node PDR is to be added;

· an Information Element (IE) of a node PDR is to be modified;

· a node PDR is to be removed.
the method (500) according to claim 2 or 3, wherein the node PDR includes:

a NodePDRId IE to identify the node PDR;

a GroupedSessionIdentity IE to identify a session group to which the node PDR is applicable.
the method (500) according to any one of claims 2 to 4, wherein the node PDR includes:

a precedence IE to identify a precedence of the node PDR.
the method (500) according to claim 4, wherein the node PDR is applicable to all Sx sessions, and the value of the GroupedSessionIdentity IE is 0.
the method (500) according to claim 4 or 6, wherein the first network node (301) transmits the Sx Node PDR Management Request message associated with the GroupedSessionIdentity IE of the node PDR in the following procedure:

· Sx Node PDR Management Request procedure, to indicate to which Sx sessions the node PDR are applicable;

· Sx Session Establishment Request procedure, to indicate if the Sx session to be established is included in the session group identified by the GroupedSessionIdentity; and

· Sx Session Modification Request procedure, to indicate a modification of the GroupedSessionIdentity IE of the node PDR applicable to the Sx session to be modified.
A method (600) in a second network node (302) configured as user plane function (UPF) , the second network node (302) is coupled to a first network node (301) configured as control plane function (CPF) via an Sx interface, the method (600) comprising:

- receiving (S601) a message associated with a Packet Detection Rule (PDR) from the first network node (301) via the Sx interface, wherein the PDR is applicable to more than one Sx session.
the method (600) according to claim 8, wherein the PDR is a node PDR, and the message is an Sx Node PDR Management Request message.
the method (600) according to claim 9, wherein the method (600) further comprising:

- according to the Sx Node PDR Management Request message, performing at least one of:

· adding a node PDR;

· modifying an Information Element (IE) of a node PDR;

· removing a node PDR.
the method (600) according to claim 9 or 10, wherein the node PDR includes:

a NodePDRId IE to identify the node PDR;

a GroupedSessionIdentity IE to identify a session group to which the node PDR is applicable.
the method (600) according to any one of claims 9 to 11, wherein the node PDR includes:

a precedence IE to identify a precedence of the node PDR.
the method (600) according to claim 11, wherein the node PDR is applicable to all Sx sessions, and the value of the GroupedSessionIdentity IE is 0.
the method (600) according to any one of claims 9 to 13, wherein the method (600) further comprising:

- applying (S602) the node PDR to more than one Sx session, including:

- performing Sx session lookup, to identify an Sx session to which an received user plane packet corresponds;

- finding one or more node PDR applicable to the Sx session;

- selecting the first PDR matching to the received user plane packet among the one or more node PDR together with a session level PDR in decreasing order of precedence, wherein the session level PDR includes IE to identify an Sx session; and

- applying the selected PDR.
the method (600) according to claim 14, wherein the precedence of each of the one or more node PDRs is higher than the precedence of the session level PDR.
the method (600) according to any one of claims 8 to 15, the method (600) further comprising:

- transmitting (S603) an Sx Node PDR Management Response message to the first network node (301) to indicate whether the Sx Node PDR Management Request message is accepted or rejected.
A first network node (301) configured as control plane function (CPF) , the first network node (301) is coupled to a second network node (302) configured as user plane function (UPF) via an Sx interface, the first network node (301) comprising:

at least one processor (701) ; and

a non-transitory computer readable medium (702) coupled to the at least one processor (701) , the non-transitory computer readable medium (702) contains instructions executable by the at least one processor (701) , whereby the at least one processor (702) is configured to perform the methods of any one of claims 1 to 7.
A second network node (302) configured as user plane function (UPF) , the second network node (302) is coupled to a first network node (301) configured as control plane function (CPF) via an Sx interface, the second network node (302) comprising:

at least one processor (801) ; and

a non-transitory computer readable medium (802) coupled to the at least one processor (801) , the non-transitory computer readable medium (802) contains instructions executable by the at least one processor (801) , whereby the at least one processor (801) is configured to perform the methods of any one of claims 8 to 16.
A computer readable medium (702, 902, 904) comprising computer readable code, which when run on an apparatus (900) , causes the apparatus (900) to perform the method (500) according to any one of claims 1 to 7.
A computer readable medium (802, 902, 904) comprising computer readable code, which when run on an apparatus (900) , causes the apparatus (900) to perform the method (600) according to any one of claims 8 to 16.