WO2023179888A1

WO2023179888A1 - Enforcing route selection policy rules in a wireless communication network

Info

Publication number: WO2023179888A1
Application number: PCT/EP2022/063053
Authority: WO
Inventors: Dimitrios Karampatsis; Genadi Velev; Apostolis Salkintzis
Original assignee: Lenovo (Singapore) Pte. Ltd
Priority date: 2022-03-24
Filing date: 2022-05-13
Publication date: 2023-09-28

Abstract

A method in an apparatus in a wireless communication network. The method comprises receiving a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The method further comprises identifying a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session. The method further comprises sending to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The method further still comprises receiving from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

Description

ENFORCING ROUTE SELECTION POLICY RULES IN

A WIRELESS COMMUNICATION NETWORK

Field

[0001] The subject matter disclosed herein relates generally to the field of enforcing route selection policy rules in a wireless communication network. This document defines an apparatus in a wireless communication network, a method in an apparatus in a wireless communication network, a first network function in a wireless communication network, and a method in a first network function of a wireless communication network.

Background

[0002] User Equipment (UE) Route Selection Policy (URSP) rules and the procedures for a UE to apply URSP rules are described in 3GPP TS 23.502 vl7.2.1 and 3GPP TS 23.503 vl7.2.0. The URSP rules contain a Traffic Descriptor that allows the UE to determine if a URSP rule matches application traffic. Traffic Descriptors include Application Descriptors which may define the operating system identity (OSID) and the application identity (OSAppID). Traffic Descriptors also include IP flow descriptors such as the target address of application traffic, a requested Data Network Name by the application, and/ or a connection capability requested by an application (e.g. an IMS connection).

[0003] S2-2200860 is a 3GPP discussion document titled “Solution for WT#4” submitted by Huawei and HiSilicon at SA2 Meeting #149E, an e-meeting on 14 February 2022. S2-2200860 states that the UE should include a rule identifier in the PDU session establishment request of the matched URSP rule that triggered the UE to request a PDU session. The PCF may then check that the S-NSSAI/DNN requested by the UE matches the Route Selection Descriptors of the URSP rule associated with the rule identifier.

Summary

[0004] Route section policy rules such as URSP rules allow a wireless communication network to appropriately route traffic from wireless communication devices such as UEs according to wireless communication network policies. However, a wireless communication device may fail to implement a route selection policy rule where it should. Such failure may be due to malicious activity at the wireless communication device. Such a failure may be due to a route selection policy rule failing to capture traffic that it was intended to be applied to.

[0005] Disclosed herein are procedures for enforcing route selection policy rules in a wireless communication network. Said procedures may be implemented by an apparatus in a wireless communication network, a method in an apparatus in a wireless communication network, a first network function in a wireless communication network, and a method in a first network function of a wireless communication network.

[0006] Accordingly, there is provided an apparatus in a wireless communication network, the apparatus comprising a receiver, a processor and a transmitter. The receiver is arranged to receive a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The processor is arranged to identify a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session. The transmitter is arranged to send to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The receiver is further arranged to receive from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

[0007] There is further provided a method in an apparatus in a wireless communication network. The method comprises receiving a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The method further comprises identifying a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session. The method further comprises sending to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The method further still comprises receiving from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows. [0008] There is further provided a first network function in a wireless communication network, the first network function comprising a transmitter and a receiver. The transmitter is arranged to send a first request to a second network function, wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The receiver is arranged to receive from the second network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The transmitter is further arranged to send an indication to the second network function of a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

[0009] There is further provided a method in a first network function of a wireless communication network. The method comprises sending a first request to a second network function, wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The method further comprises receiving from the second network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The method further comprises sending an indication to the second network of a report indicating that traffic is detected in the data connection that is not included in the list of service data flows. [0010] There is further provided a wireless communication device comprising: a processor arranged to determine that a data session is required, wherein a route selection policy rule is associated with the data session; a transmitter arranged to send a data session establishment request, wherein the data session establishment request includes an indication of the route selection policy rule that is associated with the data session.

There is further provided a method in a wireless communication device, the method comprising: determining that a data session is required, wherein a route selection policy rule is associated with the data session; sending a data session establishment request, wherein the data session establishment request includes an indication of the route selection policy rule that is associated with the data session. Brief description of the drawings

[0011] In order to describe the manner in which advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to certain apparatus and methods which are illustrated in the appended drawings. Each of these drawings depict only certain aspects of the disclosure and are not therefore to be considered to be limiting of its scope. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0012] Methods and apparatus for enforcing route selection policy rules in a wireless communication network will now be described, by way of example only, with reference to the accompanying drawings, in which:

Figure 1 illustrates a known arrangement whereby a UE routes application traffic via a EDU session that matches Route Selection Descriptor components according to URSP rules;

Figure 2 depicts a user equipment apparatus that may be used for implementing the methods described herein;

Figure 3 depicts further details of the network node that may be used for implementing the methods described herein;

Figure 4 illustrates a method in an apparatus in a wireless communication network;

Figure 5 illustrates a method in a first network function of a wireless communication network;

Figure 6 illustrates a method in a wireless communication device, and

Figure 7 is a messaging diagram illustrating an arrangement as described herein.

Detailed description

[0013] As will be appreciated by one skilled in the art, aspects of this disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, arrangements described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, micro-code, etc.) or a form combining software and hardware aspects.

[0014] For example, the disclosed methods and apparatus may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0015] Furthermore, methods and apparatus may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/ or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/ or non-transmission. The storage devices may not embody signals. In certain arrangements, the storage devices only employ signals for accessing code.

[0016] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0017] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.

[0018] Reference throughout this specification to an example of a particular method or apparatus, or similar language, means that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the method and apparatus described herein. Thus, reference to features of an example of a particular method or apparatus, or similar language, may, but do not necessarily, all refer to the same example, but mean “one or more but not all examples” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0019] As used herein, a list with a conjunction of “and/ or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/ or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of’ includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.

[0020] Furthermore, the described features, structures, or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed methods and apparatus may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well- known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

[0021] Aspects of the disclosed method and apparatus are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowchart diagrams and/ or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions /acts specified in the schematic flowchart diagrams and/or schematic block diagrams.

[0022] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/ act specified in the schematic flowchart diagrams and/or schematic block diagrams.

[0023] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions /acts specified in the schematic flowchart diagrams and/ or schematic block diagram.

[0024] The schematic flowchart diagrams and/ or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0025] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. 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 involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0026] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures.

[0027] Since Release 15 onwards URSP rules have been defined to allow a wireless communication device such as a UE to determine how to route application traffic via a wireless communication network. The wireless communication network may comprise a 3GPP access or non-3GPP access via an untrusted or trusted WLAN access. Alternatively, the UE may route application traffic non-seamlessly bypassing the wireless communication network via a WLAN connection. The URSP rules and the procedures for the UE to apply URSP rules are described in 3GPP TS 23.502 vl 7.3.0 and 3GPP TS 23.503 vl7.3.0 (URSP rules definitions and procedures are included from version 15.0.0 onwards of 23.502 and 23.503).

[0028] The URSP rules contain a Traffic Descriptor that allows the UE to determine if a URSP rule matches application traffic. Traffic Descriptors include: Application Descriptors (OSID/OSAppID), IP flow descriptors (e.g. target address of application traffic, a requested DNN by the application or a connection capability requested by an application (e.g. an IMS connection).

[0029] Each URSP rule contains a Route Selection Descriptor (RSD) that describes to the UE how the UE is to route a PDU session that is established for application traffic matching the Traffic Descriptors for that URSP rule. The RSD includes one or more of the following: SSC Mode Selection, Network Slice Selection, DNN Selection, PDU Session Type Selection, Non-Seamless Offload indication, Access Type preference.

[0030] The UE routes the application traffic via the PDU session that matches the RSD components according to the relevant URSP rule and via 3GPP or non-3GPP access.

[0031] Figure 1 illustrates a known arrangement whereby a UE routes application traffic via a PDU session that matches Route Selection Descriptor components according to URSP rules. Figure 1 illustrates a UE application 110, an operating system 120, and a connection layer 130 of a UE 100. The UE 100 may be a user equipment apparatus 200 or a UE 710 as described herein. The apparatus communicates with a wireless communications network. In operation, the Connection layer 130 accesses URSP rules 135.

[0032] The operation of the arrangement of figure 1 will now be described. At 141, the UE application 110 requests a network connection from the operating system 120 of the apparatus. At 142, the operating system 120 sends a Traffic Descriptor, such as the application identity, to the Connection layer 130. In response thereto, at 143, the Connection layer 130 identifies a URSP rule from a set of available URSP rules 135 stored in the UE and that matches the received Traffic Descriptor. From the identified URSP rule the connection layer 130 determines a Route Selection Descriptor.

Subsequently, at 144, the connection layer 130 sends, to the operating system 120, the determined Route Selection Descriptor. At 145, the operating system 120 initiates the establishing of a PDU session according to the Route Selection Descriptor. At 146, when the PDU session is established, the operating system 120 reports, to the UE application 110, that the connection is established.

[0033] Figure 1 merely shows an example implementation within a UE. In practice the exact mechanism for applying routing rules to application traffic is an implementation detail. For example, routing rules can be pre-assigned by the apparatus to every installed application, ready to be recalled and implemented when an application requests a connection. Alternatively, the apparatus may only assign a routing rule to an application when that application requests a connection. The routing rules are stored in the UE and can be updated by the network.

[0034] This document presents a mechanism by which the 5G Core (5GC) can identify whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on a URSP rule provisioned by 5GC. Further, this document defines actions that the 5G System (5GS) can take after the 5GC identifies that a UE has not applied a a URSP rule for specific application traffic when it should have done.

[0035] The solutions presented herein tend to address how a consumer, such as a PCF can determine which UEs do not correctly apply the URSP rules provisioned thereon. Some of the solutions presented herein comprise a PCF requesting the UPF directly or indirectly to monitor the UE traffic when the UE establishes a PDU session to a specific S-NSSAI/DNN.

[0036] Figure 2 depicts a user equipment apparatus 200 that may be used for implementing the methods described herein. The user equipment apparatus 200 may be a UE 100 or a UE 710. The user equipment apparatus 200 is used to implement one or more of the solutions described herein. The user equipment apparatus 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0037] The input device 215 and the output device 220 may be combined into a single device, such as a touchscreen. In some implementations, the user equipment apparatus 200 does not include any input device 215 and/ or output device 220. The user equipment apparatus 200 may include one or more of: the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and/ or the output device 220.

[0038] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 may communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 may be operable on unlicensed spectrum. Moreover, the transceiver 225 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 225 may support at least one network interface 240 and/ or application interface 245. The application interface(s) 245 may support one or more APIs. The network interface(s) 240 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 240 may be supported, as understood by one of ordinary skill in the art.

[0039] The processor 205 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations. For example, the processor 205 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. The processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225. [0040] The processor 205 may control the user equipment apparatus 200 to implement the above-described UE behaviors. The processor 205 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0041] The memory 210 may be a computer readable storage medium. The memory 210 may include volatile computer storage media. For example, the memory 210 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”). The memory 210 may include non-volatile computer storage media. For example, the memory 210 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 210 may include both volatile and non-volatile computer storage media.

[0042] The memory 210 may store data related to implement a traffic category field as describe above. The memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on the apparatus 200.

[0043] The input device 215 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. The input device 215 may be integrated with the output device 220, for example, as a touchscreen or similar touch-sensitive display. The input device 215 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen. The input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0044] The output device 220 may be designed to output visual, audible, and/ or haptic signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 220 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light- Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 220 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 200, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0045] The output device 220 may include one or more speakers for producing sound. For example, the output device 220 may produce an audible alert or notification (e.g., a beep or chime). The output device 220 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 220 may be integrated with the input device 215. For example, the input device 215 and output device 220 may form a touchscreen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0046] The transceiver 225 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times in order to send and receive messages.

[0047] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The one or more transmitters 230 may be used to provide UL communication signals to a base unit of a wireless communications network. Similarly, the one or more receivers 235 may be used to receive DL communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are illustrated, the user equipment apparatus 200 may have any suitable number of transmitters 230 and receivers 235. Further, the trans mi tter(s) 230 and the receiver(s) 235 may be any suitable type of transmiters and receivers. The transceiver 225 may include a first transmiter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmiter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

[0048] The first transmitter/ receiver pair may be used to communicate with a mobile communication network over licensed radio spectrum and the second transmiter/ receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. The first transmitter/receiver pair and the second transmiter/receiver pair may share one or more hardware components. For example, certain transceivers 225, transmiters 230, and receivers 235 may be implemented as physically separate components that access a shared hardware resource and/ or software resource, such as for example, the network interface 240.

[0049] One or more transmiters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a single hardware component, such as a multitransceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component. One or more transmiters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a multi-chip module. Other components such as the network interface 240 or other hardware components/ circuits may be integrated with any number of transmiters 230 and/ or receivers 235 into a single chip. The transmitters 230 and receivers 235 may be logically configured as a transceiver 225 that uses one more common control signals or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or in a multi-chip module.

[0050] Figure 3 depicts further details of the network node 300 that may be used for implementing the methods described herein. The network node 300 may be one implementation of an entity in the wireless communications network. The network node 300 may be an apparatus or a first network function as described herein. The network node 300 may be PCF 720, a UDR 730, an SMF 740, an AM PCF 750 or a UPF 760.

The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0051] The input device 315 and the output device 320 may be combined into a single device, such as a touchscreen. In some implementations, the network node 300 does not include any input device 315 and/ or output device 320. The network node 300 may include one or more of: the processor 305, the memory 310, and the transceiver 325, and may not include the input device 315 and/ or the output device 320.

[0052] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 may support at least one network interface 340 and/ or application interface 345. The application interface(s) 345 may support one or more APIs. The network interface(s) 340 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 340 may be supported, as understood by one of ordinary skill in the art.

[0053] The processor 305 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0054] The memory 310 may be a computer readable storage medium. The memory 310 may include volatile computer storage media. For example, the memory 310 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”). The memory 310 may include non-volatile computer storage media. For example, the memory 310 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 310 may include both volatile and non-volatile computer storage media.

[0055] The memory 310 may store data related to establishing a multipath unicast link and/ or mobile operation. For example, the memory 310 may store parameters, configurations, resource assignments, policies, and the like, as described above. The memory 310 may also stores program code and related data, such as an operating system or other controller algorithms operating on the network node 300.

[0056] The input device 315 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. The input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display. The input device 315 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen. The input device 315 may include two or more different devices, such as a keyboard and a touch panel.

[0057] The output device 320 may be designed to output visual, audible, and/ or haptic signals. The output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 320 may include a wearable display separate from, but communicatively coupled to, the rest of the network node 300, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 320 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0058] The output device 320 may include one or more speakers for producing sound. For example, the output device 320 may produce an audible alert or notification (e.g., a beep or chime). The output device 320 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 320 may be integrated with the input device 315. For example, the input device 315 and output device 320 may form a touchscreen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0059] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The one or more transmitters 330 may be used to communicate with the UE, as described herein. Similarly, the one or more receivers 335 may be used to communicate with network functions in the PLMN and/ or RAN, as described herein. Although only one transmitter 330 and one receiver 335 are illustrated, the network node 300 may have any suitable number of transmitters 330 and receivers 335. Further, the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitters and receivers.

[0060] There is provided an apparatus in a wireless communication network, the apparatus comprising a receiver, a processor and a transmitter. The receiver is arranged to receive a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The processor is arranged to identify a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session. The transmitter is arranged to send to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The receiver is further arranged to receive from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

[0061] The apparatus may be a policy control function (PCF). The first network function may be a session management function (SMF). The wireless communication device may be a user equipment (UE). The route selection policy rule may be a UE route selection policy (URSP) rule.

[0062] The apparatus described herein may determine that the wireless communication device requests establishment of a data session using network resource typically reserved only for a route selection policy rule, then the apparatus indicates to the second network function to report if the wireless communication device routes traffic via the data session that is not intended for that data session.

[0063] The processor may be further arranged to determine whether the wireless communication device routes service data flows in accordance with the route selection policy rule.

[0064] The traffic reporting rules may request that traffic sent via the data session that is not intended for the data session is reported to the apparatus.

[0065] The route selection policy rule may include at least one traffic descriptor. The traffic reporting rules may comprise the at least one traffic descriptor of the route selection policy rule.

[0066] The processor may be further arranged to identify the route selection policy rule that is associated with the data session based upon a route selection policy rule indication received in the first request.

[0067] The processor may be arranged to identify the route selection policy rule that is associated with the data session based upon a network slice identifier or a data network name (DNN). The network slice identifier may comprise a single Network Slice Selection Assistance Information (S-NSSAI).

[0068] The processor may be arranged to determine if the wireless communication device routes traffic according to a provisioned route selection policy rule based upon configuration information received in a Unified Data Repository (UDR). The configuration information may comprise a local configuration. [0069] The first list of service data flows that are allowed to be routed via the data session may be determined by retrieving the identified route selection policy rule associated with a network slice identifier or a data network name (DNN) of the data session.

[0070] The identified route selection policy rule that is associated with the data session may be retrieved from the UDR. The identified route selection policy rule that is associated with the data session may be retrieved from an access and mobility management (AM) PCF.

[0071] The transmitter may be further arranged to send a request to a UDR to retrieve the route selection policy rule, the request including a route selection policy rule identifier received in the first request.

[0072] Figure 4 illustrates a method 400 in an apparatus in a wireless communication network. The method 400 comprises receiving 410 a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The method 400 further comprises identifying 420 a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session. The method 400 further comprises sending 430 to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The method 400 further still comprises receiving 440 from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

[0073] The method described herein may cause the apparatus to determine that the wireless communication device requests establishment of a data session using network resource typically reserved only for a route selection policy rule, and as a result thereof the method may cause the apparatus to indicate to the second network function a report if the wireless communication device routes traffic via the data session that is not intended for that data session.

[0074] There is further provided a first network function in a wireless communication network, the first network function comprising a transmitter and a receiver. The transmitter is arranged to send a first request to a second network function, wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The receiver is arranged to receive from the second network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The transmitter is further arranged to send an indication to the second network function of a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

[0075] The second network function may be a PCF. The first network function may be an SMF. The route selection policy rule may be a URSP.

[0076] The first network function may thus be arranged to coordinate a verification that a wireless communication device routes traffic via a data session that is intended for that data session, and where the wireless communication device fails in this regard, to report this to the second network function.

[0077] The traffic reporting rules may comprise an indication to report any traffic except for the traffic intended to be routed to the data session.

[0078] The identified route selection policy rule that is associated with the data session may be retrieved from the UDR. The identified route selection policy rule that is associated with the data session may be retrieved from an AM PCF.

[0079] The transmitter may be further arranged to send node-level rules to a user plane function (UPF), the node-level rules defining traffic that is allowed over the data session. [0080] The node-level rules may be N4 rules sent over the N4 interface between the SMF and the UPF.

[0081] The receiver may be further arranged to receive a report of non-allowed traffic from the UPF.

[0082] Figure 5 illustrates a method 500 in a first network function of a wireless communication network. The method 500 comprises sending 510 a first request to a second network function, wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session. The method 500 further comprises receiving 520 from the second network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data. The method 500 further comprises sending 530 an indication to the second network of a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

[0083] The method may cause a first network function to coordinate a verification that a wireless communication device routes traffic via a data session that is intended for that data session, and where the wireless communication device fails in this regard, to report this to the second network function.

[0084] There is further provided a wireless communication device comprising: a processor arranged to determine that a data session is required, wherein a route selection policy rule is associated with the data session; a transmitter arranged to send a data session establishment request, wherein the data session establishment request includes an indication of the route selection policy rule that is associated with the data session.

[0085] The wireless communication device may thus facilitate another node determining whether the wireless communication device has routed traffic via the data session that is not intended for that data session.

[0086] Figure 6 illustrates a method 600 in a wireless communication device, the method 600 comprising: determining 610 that a data session is required, wherein a route selection policy rule is associated with the data session; sending 620 a data session establishment request, wherein the data session establishment request includes an indication of the route selection policy rule that is associated with the data session.

The method may cause a wireless communication device to facilitate another node in determining whether the wireless communication device has routed traffic via the data session that is not intended for that data session.

[0087] According to a solution presented herein, the PCF identifies if a UE route traffic correctly when the UE establishes a PDU session for an S-NSSAI/DNN/RAT type that matches a Route Selection Descriptor of a URSP rule that was provisioned to the UE.

[0088] The PCF may make a determination that it will identify if the UE routes traffic correctly based on at least one of: a configuration at the PCF; URSP rule information; according to a specific identity of a network slice selected by the UE; and/ or upon indication received from the UE.

[0089] For example, the PCF may be configured (either locally or from the UDR) such that when a UE requests a PDU session to a specific S-NSSAI/DNN/RAT type or combination of, the PCF is to identify if the UE routes application traffic according to a URSP rule via this PDU session. In addition, the PCF may be configured with the traffic allowed to be routed via the S-NSSAI/DNN. [0090] By way of further example, the PCF may be provided with URSP rule information, the USRP rule information comprising information about URSP rules provisioned to the UE. Thus, the PCF is aware of a potential URSP rule that caused the UE to establish a PDU session to a specific S-NSSAI/DNN/RAT. In other words, the PCF maps a PDU session established by a UE to a particular route selection policy rule provisioned to the UE based upon the route selected for the PDU session by the UE. The PCF can receive route selection policy rule information by interfacing with the UDR and obtaining the latest list of UE policy sections identified by PSI identifiers, that contain URSP rules from the UDR. Such an interface may use the Nudr_DM_Query service operation. The Nudr_DM_Query service operation may comprise SUPI, Policy Data, UE context policy control data, and Policy Set Entry.

[0091] A URSP rule includes a Traffic Descriptor that contains information to allow the UE to determine if application traffic matches a URSP rule. The URSP rule also includes Route Selection Descriptors (S-NSSAI, DNN, SSC mode, RAT type) that allow the UE to determine which PDU session is required to route application traffic to mobile core network. The established PDU session may be further defines according to components such as S-NSSAI, DNN. Based on the S-NSSAI, DNN and/ or RAT type requested by the UE in the PDU session establishment the PCF may determine the URSP rule and Traffic Descriptor that triggered the UE to request a PDU session.

[0092] The PCF may be configured to identify how the UE routes traffic if the UE triggers PDU session establishment to an S-NSSAI/DNN based on a URSP rule indication.

[0093] By way of further example, the UE may indicate to the PCF, with a request to establish a data session, the identity of the route selection policy rule that applies to the data session. The UE may include an indication in the PDU Session establishment request that the request is due to a URSP rule. The UE may include a URSP rule identifier of the URSP rule that triggered the UE to request establishment of a PDU session or may include the Policy Section Identifier of the policy section that contained the URSP rule that triggered the PDU session establishment.

[0094] When the PCF is triggered to identify if the UE routes traffic to an S- NSSAI/DNN according to the configured URSP rule, then the PCF subscribes to the UPF (either via the SMF or NWDAF) to report if the UE routes traffic not intended via the specific PDU session. The PCF requests that the UPF reports any traffic that does not match the traffic according to the Traffic Descriptor of the URSP rule. [0095] Figure 7 is a messaging diagram illustrating an arrangement as described herein. Figure 7 illustrates a system 700 comprising a UE 710, a PCF 720, a UDR 730, an SMF 740, an AM PCF 750, and a UPF 760. The UE 710 may be a UE 100 or a user equipment apparatus 200.

[0096] At 770, an application in the UE 710 sends traffic or a request for a data connection.

[0097] At 771, the UE 710 detects new application traffic and determines that application traffic needs to be routed via a PDU session of a specific DNN, S-NSSAI, RAT type. The determination may be based due to a configured URSP rule, local configuration or application request.

[0098] At 772, the UE 710 requests establishment of a PDU session using specific S- NSSAI, DNN, SSC mode. Optionally, if the determination in step 771 was made due to a URSP rule the UE may include a URSP indication in the PDU session establishment request. The indication may include an identifier of the URSP rule that triggered the UE to request establishment of a PDU session or may include the Policy Section Identifier of the policy section that contained the URSP rule that triggered the PDU session establishment.

[0099] At 773, the SMF 740 selects a PCF 720 and requests policies by establishing an SM Policy Association. The SMF 740 sends an Npcf_SM_PolicyControl_Create including the SUPI, PDU session ID, DNN, S-NSSAI requested and RAT type of the access that the UE 710 requested establishment of a PDU session. If the UE 710 included a URSP indication in step 772 the SMF 740 forwards the indication to the PCF 720.

[0100] At 774, the PCF 720 determines to check for the UE 710 requested PDU session if the UE 710 routes traffic according to a configured URSP rule as described above. If the PCF 720 is configured from the UDR 730, the UDR 730 may include Traffic Monitoring related information by including a Traffic Monitoring Identifier that indicates to the PCF 720 which Policy and Charging Control (PCC) rules or PDU session related information rule must report usage information. Alternatively, the UDR 730 may include an indication, or the PCF 720 may be locally configured, to identify if a URSP rule is enforced correctly when a UE requests a PDU session to a specific S-NSSAI/DNN or when the UE 710 includes a URSP indication when the UE 710 requests a PDU session to a specific S-NSSAI/DNN. [0101] At 775, the PCF 720 determines the potential URSP rule and the corresponding Traffic Descriptor of the URSP rule that triggered the UE 710 to request establishment of a PDU session to a specific S-NSSAI/DNN.

[0102] It should be noted that steps 775a to 775d are optional and dependent on implementation. One example comprises steps 775a and 775b, another example comprises steps 775c and 775d. In yet a further example, where the PCF 720 is an PCF 720 that provisions URSP rules (that is, a PCF 720 responsible for AM policies) then none of steps 775a to 775dare required.

[0103] At 775a, the PCF 720 obtains the URSP rule by interfacing with the UDR 730 to obtain the policy sections of URSP rules provisioned to the UE 710. The PCF 720 may include the PSI identifier or URSP rule id if included by the UE in step 772.

[0104] At 775b, the UDR 730 provides policy sections of the URSP rule.

[0105] At 775c, the PCF 720 finds the PCF, which may be an AM PCF 750 that provisioned the URSP rules to the UE 710 and request the AM PCF 750 provides the URSP rule for the S-NSSAI/DNN requested by the UE 710. Alternatively the AM PCF 750 may include a rule ID or a PSI id if provided by the UE 710 in step 772. The AM PCF 750 may be the PCF that manages AM policies for the UE 710.

[0106] At 775d, the AM PCF 750 provides the potential URSP rule to the PCF 720. It should further be noted that in certain arrangements the AM PCF 750 may carry out steps 775a and 775b to obtain the URSP rule.

[0107] At 776, the PCF 720 makes policy decisions according to a subscription of the UE 710.

[0108] At 777, the PCF 720 provides PDU session related information rules and PCC rules in an Npcf_SMPolicyCreate_Response. The PCF 720 also includes rules to the SMF 740 to report non-matching traffic (i.e. traffic different to the allowed traffic) via the S-NSSAI, DNN or RAT type. The PCF 720 includes the Allowed Traffic that can be routed via the PDU session (S-NSSAI/DNN/RAT-type). In one embodiment the PCF 720 includes the Traffic Descriptor of the determined URSP rule denoting the allowed traffic. In an alternative embodiment the PCF 720 determines the allowed traffic, i.e. service data flows, according to the traffic descriptor of the URSP rule and provides the service data flows indicating allowed traffic to the SMF 740.

[0109] The PCF 720 may provide the URSP rule at a later stage by invoking an Npcf_SMPolicyModication request. [0110] At 778, the SMF 740 installs N4 rules at the UPF 760, based on the received PCC rules. The SMF 740 includes rules to the UPF 760 to report non-matching traffic via the S-NSSAI, DNN and includes also the allowed traffic. In an alternative embodiment if the PCF 720 provided the Traffic Descriptor of the URSP rule the SMF 740 determines the allowed traffic, i.e. service data flows, according to the traffic descriptor of the URSP rule and provides the service data flows indicating allowed traffic to the UPF 760.

[0111] At 779, if the SMF 740 included the traffic descriptor of the URSP rule in step 778 the UPF 760 determines the allowed traffic according to the traffic descriptor. When the UPF 760 detects non-matching traffic the UPF 760 reports the traffic to the SMF 740. The UPF 760 includes the service data flow information of the non-matching traffic detected.

[0112] At 780, the SMF 740 reports the detected information to the PCF 720.

[0113] At 781, the PCF 720 determines if the traffic reported should be sent via a different S-NSSAI or whether traffic should be blocked. The PCF 720 may install rules to the SMF 740 to block such traffic or determine new URSP rules to route traffic via a different S-NSSAI.

[0114] At 782, the PCF 720 provides updated URSP rules to the UE 710 using the UE Configuration Update for transparent policy delivery.

[0115] In an alternative embodiment instead of the PCF 720 to providing rules to the SMF 740 to report traffic not allowed via an S-NSSAI, DNN as in step 776, the PCF 720 may interface directly with the UPF 760 and subscribe to the UPF 760 (via a new Service Based Interface operation and new interface) to report the non-allowed traffic. The PCF 720 includes in the request the Allowed Traffic (e.g. Traffic Descriptor of the URSP rule) and an indication to report traffic that does not match the Traffic Descriptor.

[0116] The inventors have considered whether and how the 5GC can be made aware whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on the URSP rule provisioned by 5GC. Further, they have considered whether there are any actions the 5GS can take after 5GC is aware whether the UE enforces a URSP rule for specific application traffic or not. If any, what action 5GC should take?

[0117] Some of the solutions presented herein comprise that when the PCF determines that the UE requests establishment of a PDU session to an S-NSSAI/DNN that is usually triggered due to a URSP rule, then the PCF indicates to the SMF to report if the UE routes traffic that is not intended to be routed via the requested PDU session. The SMF may configure the UPF to report traffic not intended via the specific S- NSSAI/DNN.

[0118] A PCF may initiate usage monitoring to identify if the UE uses the URSP rules correctly when the UE requests establishment of a PDU session to a DNN/S-NSSAI that is usually triggered due to a URSP rule.

[0119] There is provided a PCF in a first mobile communication network arranged to: Receive a first request from a first network function [SMF] wherein the request includes a request for SM policies for a device requesting establishment of a PDU session of an S- NSSAI/DNN combination; Determine to identify if UE routes application traffic according to a provisioned URSP rule; Determine a first list of service data flows that are allowed to be routed via the PDU session; Respond to first network function to provide session management policies for the PDU session including an indication to report traffic not intended via the PDU session wherein the request includes to report Any traffic except for the traffic intended to be routed to the PDU session; Receive information from the first network with a list of service data flows that are routed incorrectly by the device via the PDU session.

[0120] The PCF may determine that the PDU session is established based on a UE Route Selection Policies.

[0121] The PCF may determine that the PDU session is established due to a URSP rule based on a URSP indication received in the first request.

[0122] The PCF may determine the PDU session is established due to a URSP rule based on the S-NSSAI and/ or DNN received in the first request.

[0123] The PCF may determine if a UE routes application traffic according to a provisioned URSP rule based on configuration information received in the UDR, or a local configuration.

[0124] The PCF determines a first list of service data flows that are allowed to be routed via the PDU session by retrieving the corresponding URSP rule associated with the S- NSSAI/DNN of the PDU session

[0125] The PCF determines the service data flows allowed to be routed via the PDU session by retrieving the URSP rule from the UDR (or from the AM PCF).

[0126] The PCF sends a request to the UDR to the retrieve the URSP rule including a URSP rule identifier received in the first request.

[0127] It should be noted that the above-mentioned methods and apparatus illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.

[0128] Further, while examples have been given in the context of particular communications standards, these examples are not intended to be the limit of the communications standards to which the disclosed method and apparatus may be applied. For example, while specific examples have been given in the context of 3GPP, the principles disclosed herein can also be applied to another wireless communications system, and indeed any communications system which uses routing rules.

[0129] The method may also be embodied in a set of instructions, stored on a computer readable medium, which when loaded into a computer processor, Digital Signal Processor (DSP) or similar, causes the processor to carry out the hereinbefore described methods.

[0130] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. An apparatus in a wireless communication network, the apparatus comprising: a receiver arranged to receive a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session; a processor arranged to identify a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session; a transmitter arranged to send to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data; the receiver further arranged to receive from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

2. The apparatus of claim 1, wherein the processor is further arranged to determine whether the wireless communication device routes service data flows in accordance with the route selection policy rule.

3. The apparatus of claim 1 or 2, wherein the traffic reporting rules request that traffic sent via the data session that is not intended for the data session is reported to the apparatus.

4. The apparatus of any of claims 1, 2 or 3, wherein the processor is arranged to identify the route selection policy rule that is associated with the data session based upon a route selection policy rule indication received in the first request.

5. The apparatus of any of claims 1, 2 or 3, wherein the processor is arranged to identify the route selection policy rule that is associated with the data session based upon a network slice identifier or a data network name (DNN).

6. The apparatus of any preceding claim, wherein the first list of service data flows that are allowed to be routed via the data session is determined by retrieving the identified route selection policy rule associated with a network slice identifier or a data network name (DNN) of the data session.

7. The apparatus of any preceding claim, wherein the identified route selection policy rule that is associated with the data session is retrieved from the UDR.

8. The apparatus of any preceding claim, wherein the transmitter is further arranged to send a request to a UDR to retrieve the route selection policy rule, the request including a route selection policy rule identifier received in the first request.

9. A method in an apparatus in a wireless communication network, the method comprising: receiving a first request from a first network function wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session; identifying a route selection policy rule associated with the data session and to determine a first list of service data flows that are allowed to be routed via the data session; sending to the first network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data; receiving from the first network function a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

10. A first network function in a wireless communication network, the first network function comprising: a transmitter arranged to send a first request to a second network function, wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session; a receiver arranged to receive from the second network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data; the transmitter further arranged to send an indication to the second network function of a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.

11. The first network function of claim 10, wherein the traffic reporting rules comprises an indication to report any traffic except for the traffic intended to be routed to the data session.

12. The first network function of claim 10 or 11, wherein the identified route selection policy rule that is associated with the data session is retrieved from the UDR.

13. The first network function of claims 10, 11 or 12, wherein the transmitter is further arranged to send node-level rules to a user plane function (UPF), the node-level rules defining traffic that is allowed over the data session.

14. The first network function of claim 13, wherein the receiver is further arranged to receive a report of non-allowed traffic from the UPF.

15. A method in a first network function of a wireless communication network, the method comprising: sending a first request to a second network function, wherein the first request comprises a request for session management policies for a wireless communication device, the wireless communication device having requested establishment of a data session; receiving from the second network function a plurality of session management policies for the data session including traffic reporting rules, the traffic reporting rules defining traffic sent via the data session that is not included in the first list of service data; sending an indication to the second network of a report indicating that traffic is detected in the data connection that is not included in the list of service data flows.