Alternate marking for quality of service (QOS) flow measurements

Abstract

A method, system and apparatus are disclosed. In at least one embodiment, a Session Management Function, SMF, configured for performing Quality of Service, QoS, Monitoring in a telecommunication network is provided. SMF is configured to configure at least one of a wireless device, a network node, and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions. SMF is configured to receive, from at least one of the wireless device, a network node, and UPF PSA, measurement data generated based on the instructions. SMF is configured to calculate at least one metric based on the received measurement data.

Description

[0001] ALTERNATE MARKING FOR QUALITY OF SERVICE (QOS) FLOW MEASUREMENTS

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to alternate marking for QoS flow measurements.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] FIG. 1 shows an example of a non-roaming 5G system architecture, including:

[0007] • Unified Data Management (UDM)

[0008] • Policy Control Function (PCF)

[0009] • Session Management Function (SMF)

[0010] • User Pl ane Functi on (UPF )

[0011] • Application Function (AF)

[0012] • Radio Access Network (RAN)

[0013] PCF

[0014] The Policy Control Function (PCF) supports a unified policy framework to govern the network behavior. Specifically, the PCF provides Policy and Charging Control (PCC) rules to the Policy and Charging Enforcement Function (PCEF), i.e., the SMF / UPF that enforces policy and charging decisions according to provisioned PCC rules.

[0015] The PCF may generate the authorized Quality of Service (QoS) Monitoring policy for a service data flow based on the QoS Monitoring request received from the AF. The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF.

[0016] SMF

[0017] The SMF supports different functionalities. SMF is in charge of Session Management e.g., PDU Session Establishment, modify and release, including setting up and maintaining the tunnel between UPF and AN node. SMF receives PCC rules for the Session from the PCF and configures the UPF accordingly using Packet Detection Rules (PDRs) and other rules associated with QoS, forwarding or reporting instructions among others.

[0018] Based on the PCC Rules, SMF determines which QoS Flows that may need to be established between the wireless device and the UPF and instructs wireless device and Access Network (AN) (via AMF) and UPF accordingly. Also, if PCC Rules include an authorized QoS Monitoring policy, the SMF configures UPF and AN (when needed) to perform QoS monitoring for the QoS Flow and to report the monitoring results.

[0019] UPF

[0020] The UPF supports handling of user plane traffic according to Rules received from SMF, including packet inspection, packet routing and forwarding, traffic usage reporting, QoS handling for user plane, e.g., UL / DL rate enforcement and QoS Flow marking.

[0021] The UPF supports event exposure, including exposure of network information, i.e., the QoS monitoring information, like QS Flow delay information or data rates.

[0022] AF

[0023] The AF interacts with the 3 GPP Core Network to provide services like, for example, Application Function influence on traffic routing (and / or service chaining) and interaction with the Policy and charging control framework. AF may be defined only with respect to its interaction with the 3GPP Core Network.

[0024] Based on operator deployment, Application Functions considered to be trusted by the operator can be allowed to interact directly with relevant Network Functions. Application Functions not allowed by the operator to directly access the Network Functions shall use the external exposure framework and interact via the Network Exposure Function (NEF).

[0025] RAN

[0026] A RAN is the part of a mobile network that connects end-user devices, like smartphones, to the cloud. This is achieved by sending information via radio waves between end-user devices and RAN, and finally between the RAN and the core network which connects to the data network (e g., to the global internet).

[0027] RAN may be made up of three elements: Antennas (which convert electrical signals into radio waves, Radios (which transform digital information into signals that can be sent wirelessly) and Signal Processing functions that make wireless communication possible. Network nodes integrate them and may be called eNodeB or eNB (Evolved Node B) in 4G, and gNodeB or gNB (Next Generation Node B) in 5G. FIG. 2 is a non-roaming 5G system architecture (as specified in, e.g., 3GPP Technical Specification (TS) 38.300).

[0028] Xn is defined between two NG-RAN nodes. Xn consists of a user plane protocol stack and a control plane protocol stack.

[0029] • The user plane provides non-guaranteed delivery of user plane PDUs and supports the following functions: Data forwarding and flow control;

[0030] • The control plane interface supports the following functions: Xn interface management, wireless device mobility management (including context transfer and RAN paging) and Dual connectivity.

[0031] At intra-NR RAN handover, the preparation and execution phase of the handover is performed without involvement of the 5GC, i.e., the messages are directly exchanged between the network nodes (e.g., gNBs) over Xn. It is the source gNB that initiates HO with a request to the target gNB, whereas it is the target gNB that triggers the release of the resources at the source gNB.

[0032] During HO preparation, U-plane tunnels are established between the source gNB and the target gNB so that during HO execution, user data can be forwarded from the source gNB to the target gNB; When DAPS handover, the source gNBs continues in to send downlink user data to the wireless device and receiving uplink user data from the wireless device for some time, and the wireless device with DAPS maintains separate security and (de)compression functions for each gNB, but common functions for reordering, duplicate detection and discard.

[0033] PDU Session Service and Session Continuity Modes

[0034] 5G standards define three different Session and Service Continuity (SSC) modes of operation for the update of a PDU Session. SSC modes condition the impacts in the synchronization of the metrics between the wireless device and the PSA. SSC Modes are explained below so as why they may not impact the method:

[0035] • For SSC mode 1 PDU Sessions, the UPF acting as PDU Session Anchor (PSA) is maintained regardless of the user mobility and access technology, i.e., there is no change of the PSA for the entire life of the PDU session.

[0036] • For SSC mode 2 (aka break before you make) PDU Sessions, the UPF PSA can change. Upon SMF request, wireless device triggers the release of the ongoing PDU session and initiates a new PDU Session establishment with a new PDU Session ID.

[0037] • For SSC mode 3 (aka make before you break) PDU Sessions, the UPF PSA can change. This scenario is similar to the SSC mode 2, with the difference that the new session is established by wireless device before it releases the previous one (both coexist for a certain time and traffic is gradually moved over to the new PDU Session as new transport connections get established).

[0038] PDU Session with multiple PSAs

[0039] The SMF may control the data path of a PDU Session so that the PDU Session may simultaneously correspond to multiple N6 interfaces and provide different accesses to the same DataNetwork (DN). The UPF that terminates each of these interfaces is said to support PDU Session Anchor (PSA) functionality. The SMF applies selective traffic routing (by using UL Classifier functionality or IPv6 multi-homing) functionality chained in the user plane (as shown in FIG. 3, which depicts PDU Session with chained UPFs).

[0040] • Uplink Classifier (UL-CL): there is an intermediate UPF that classifies and steers traffic according to SMF provided rules based on traffic destination (traffic destination in UL, traffic origin in DL). Whether there are one or more UPF PSAs behind the ULCL is transparent to the wireless device. Furthermore, the ULCL can be inserted in the path keeping UE unaware of this change. Whether and when traffic steering of certain service data flows switches PSA during the PDU Session life is transparent to the wireless device as well.

[0041] • Branching Point (BP): there is an intermediate UPF that classifies and steers traffic according to SMF provided rules based on the Multi-Homing IPv6-prefix of the traffic (traffic origin in UL, traffic destination in DL). The wireless device is instructed by the network to use one or another prefix depending on the application (or traffic destination), wireless device is aware of the differentiated steering. IP Prefixes can be handled by wireless device as different IP connections. Whether and when traffic steering of certain service data flows changes PSA during the PDU Session is controlled by wireless device by selecting the prefix.

[0042] QoS Flow

[0043] The 5G QoS model is based on QoS Flows. The 5G QoS model supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows).

[0044] The QoS Flow is the finest granularity of QoS differentiation in the PDU Session. User Plane traffic on the same QoS Flow within a PDU Session receives the same traffic forwarding treatment (e g. scheduling, admission threshold). Within the 5GS, a QoS Flow is controlled by the SMF and may be pre-configured or established via the PDU Session Establishment or modify procedure. SMF performs QoS Flow binding, and it associates a PCC rule to a QoS Flow within a PDU Session.

[0045] A QoS Flow is associated with QoS requirements as specified by QoS parameters and QoS characteristics. Any QoS Flow may be characterized by:

[0046] A QoS profile provided by the SMF to the AN via the AMF (or preconfigured in the AN);

[0047] One or more QoS rule(s) and optionally QoS Flow level QoS parameters associated with these QoS rule(s) which can be provided by the SMF to the UE via the AMF and / or derived by the UE by applying Reflective QoS control; and

[0048] One or more UL and DL PDR(s) provided by the SMF to the UPF.

[0049] Within the 5GS, a QoS Flow associated with the default QoS rule may be required to be established for a PDU Session and remains established throughout the lifetime of the PDU Session providing the wireless device with connectivity. This QoS Flow should be a Non-GBR QoS Flow.

[0050] A QoS Flow ID (QFI) is used to identify a QoS Flow in the 5G System. The QFI is carried in without any changes to the end-to-end (e2e) packet header and it is unique within a PDU Session.

[0051] FIG. 4 shows the principle for classification and User Plane marking for QoS Flows and mapping to AN Resources n UE, Access Network and UPF, e.g., as shown in 3GPP TS 23.501.

[0052] QoS Monitoring

[0053] 5GS QoS monitoring performs measurement and reporting of QoS parameters. It can be enabled by an AF request on behalf of a 3rd party application and / or by operator policies configured in the PCF.

[0054] The QoS parameter(s) that can be measured at this stage by means of QoS monitoring are UL packet delay, DL packet delay, round trip packet delay, Congestion and Data Rate.

[0055] 5GS QoS monitoring for service data flow(s) may be triggered by an AF request for measurements of one or more QoS parameters. PCF generates the authorized QoS Monitoring policy for a service data flow based on the QoS Monitoring request received and it includes it in the PCC rule with service data flow policy control and charging instructions to the SMF. The SMF configures the UPF to perform QoS monitoring for the QoS Flow and to report the monitoring results. The SMF may also configure RAN to measure QoS parameters if UPF needs RAN to provide the measurements. QoS Monitoring may impact the QoS Flow binding in SMF (e.g., as described above). 5GS QoS Monitoring sets as condition that the service data flow does not share QoS Flow with any other traffic.

[0056] Alternate Marking Method

[0057] General

[0058] The Alternative-Marking method may be based on a specified, e g., by the Internet Engineering Task Force (IETF) Request for Comments (RFC) 7799, technique to perform packet loss, delay, and jitter measurements on live traffic. The method primarily addresses packet-loss measurement, but it may be extended to one-way or two-way delay and delay variation (i.e. jitter) measurements as well. It can be considered Passive or Hybrid according to, e.g., IETF RFC 7799.

[0059] The Alternate-marking method consist of splitting the traffic to monitor into blocks which are marked (or colored). Entities along the path monitor these marks and provide information that is then correlated to obtain the desired measurements.

[0060] Each change of color represents a sort of auto-synchronization signal that enhances the consistency of the monitoring along the path. Whenever the color changes, the previous block terminates and the new one begins. Hence, all the packets belonging to the same block will have the same color, and packets of different consecutive blocks will have different colors.

[0061] FIG. 5 shows how a flow appears when it is split into traffic blocks with colored packets.

[0062] The IETF Alternative-Marking method RFC specifies two possibilities: traffic split into fix-time blocks and traffic split into blocks with a fixed number of packets. The selection of the length of the blocks is a trade-off: the longer the block, the less frequent measurements, but also the simpler the data collection and more robustness if out of order packets.

[0063] The RFC does not specify how traffic should be marked (neither on which protocol layer nor with which information elements).

[0064] The RFC specifies flow-based and link-based monitoring. Flow based monitoring requires to know in advance the path followed by the packet flows.

[0065] Alternate Marking Method can be used to obtain end-to-end and hop-by-hop measurements as shown in FIG. 6. The end points perform the marking. To obtain end-to- end measurements, it may be sufficient to enable the monitoring on these end point; intermediate entities should not alter the colors / marks though. For measurements taken hop- by-hop along the path, it may be necessary to enable the monitoring on every hop between the end points.

[0066] Packet Loss Measurement

[0067] Packet loss is calculated as the difference between the packets counted for a given block in the receiver entity and the sender entity. For that, each of the entities keeps different counts per color (e.g., C(A)packets_sent, C(B) packets _sent, C(A) packets _received, C(B) packets _received):

[0068] Packet Loss

[0069] As an example, UL packet Loss between R1 and R3 in FIG. 6 can be determined using the formula above if R1 provides C(A) packets_sent and C(B) packets _sent, and R3 provides: C(A) packets _received, C(B) packets _received.

[0070] Delay Measurement

[0071] For packet delay, the RFC proposes two different methods to obtain one-way delay measurement, which can then be used to calculate two-way delay; one using the blocks colored for packet loss and calculate the mean delay of the block (Single-Marking Methodology), and second using an additional bit to do a second coloring (Double-Marking Methodology). The Double-Marking may be more robust as it overcomes the limitations of; out-of-order packets, and packets losses present on first method.

[0072] Single-Marking Methodology

[0073] In its simplest form, the alternation of colors can be used as a time reference to calculate the delay. Whenever the color changes (which means that a new block has started), an entity can store the timestamp of the first packet of the new block; that timestamp can be compared with the timestamp of the same packet on the next entity along the path to compute packet delay. The method requires that the clocks on the network entities are in sync. Furthermore, a measurement might be valid only if no packet loss occurs and if packet out of order can be avoided; otherwise, the first packet of a block could be different for these entities. Since packet mis-ordering is generally undetectable, that is part of the intrinsic error in this measurement.

[0074] In order to overcome this problem, an approach based on the concept of mean delay can be considered. The mean delay is calculated by considering instead the average arrival time of the packets within a single block. Each entity locally stores a timestamp for each packet within a single block: summing all the timestamps and dividing by the total number of packets received, the average arrival time for that block of packets can be calculated. By subtracting the average arrival times of two adjacent devices, it is possible to calculate the mean delay between them. This method gets more reliable reducing the block size, but it is limited because the method does not result in the provision of information about the delay value's distribution for the duration of the block. It may be useful to know more about the statistical distribution of delay values as; minimum, maximum or median.

[0075] Double-Marking Methodology

[0076] To overcome the above limitations double marking can be used. Basically, the idea is to use the first marking to create the alternate flow (and to measure packet loss and optionally, mean delay) and, within this colored flow, a second marking to select the packets for measuring delay / jitter. The second marking creates a new set of marked packets that are fully identified over the network so that a network device can store the timestamps of these packets. These timestamps can be compared with the timestamps of the same packets on the next node to compute packet delay values for each packet. Double marking can be used to get more statistics of delay extent data, e.g., percentiles, variance, and median delay values. But it may be recommended to avoid the conventional range (maximum-minimum). The frequency of the second marking is an important design parameter. An efficient and robust mode is to select a single packet with the second marking for each block.

[0077] Delay variation measurement (jitter)

[0078] The alternation of colors, for a Single-Marking Method, can be used as a time reference to measure delay variations. In case of Double Marking, the time reference is given by the second-marked packets. The concept of mean delay can also be applied to delay variation.

[0079] Network metrics are quantitative measurements that can be used to evaluate and monitor the performance and reliability of a computer network. They can be used by network administrators to identify performance bottlenecks, diagnose issues, and optimize network settings to improve network performance and provide a better user experience. These metrics provide valuable insights into various aspects of network behavior. Packet loss is considered a network key performance indicator (KPI).

[0080] But, whereas 3GPP has specified 5GS QoS Monitoring to measure and collect very relevant measurements (e.g., as described above), that functionality has not addressed packet loss measurements. Because of increasing encryption, measuring packet loss is not so straight forward: no single network entity can determine it by its own. Besides that, 5GS QoS Monitoring is based on 3GPP specific measuring mechanisms which are less likely to benefit from advances in the area. As currently defined, the measured delay in 5GC and the measured delay in the access are not aligned. Time stamps are exchanged in the user plane that add quite some overhead as well. RAN measurements are costly. Relevance of Active measurements (between RAN and PC) for a service data traffic as measurements taken using the service data traffic itself, etc.

[0081] SUMMARY

[0082] Some embodiments advantageously provide methods, systems, and apparatuses for alternate marking for QoS flow measurements.

[0083] Various embodiments described herein relate to enhancements to 5GS QoS Monitoring with Packet Loss measurements The Measurements are for well-defined traffic flows on a 5GS UP path (between wireless device and UPF PSA). The measurements are obtained according to specifications such as, e.g., the IETF Alternate Marking Method RFC 9341, on the QoS Flow bound to the target traffic. For that, SMF may provision wireless device and UPF PSA with Alternate Marking instructions, and SMF receives their marking and counting information to calculate packet loss metrics. SMF reports packet Loss according to request in the PCC Rule.

[0084] Some embodiments may also provide delay and jitter measurements using, e.g., the Alternate-Marking method as described in IETF RFC 9341 to obtain them.

[0085] Some embodiments may be extended to provide the Packet loss, delay and jitter metrics on a per hop on the UP path.

[0086] Some embodiments relate to a measurement system for, e.g., a wireless device, a network node, at least one UPF and an SMF. Some embodiments relate to a 5G deployment where multiple QoS flows are used to transmit the different types of traffic between a wireless device and a UPF. The measurement system may enable measurements of performance measurements such as packet loss, packet delay and packet delay variation, e.g., by use of the Alternate Marking method described in IETF RFC 9341.

[0087] Some embodiments relate to deployment in a 5G environment of procedures for:

[0088] • Configuration of the various measurement nodes. o Alternate marking parameters. o Measurement granularity (e.g., per QoS flow).

[0089] • Reporting of measurement data to an SMF. Some embodiments relate to how the measurement bits are allocated in the 3 GPP user plane protocols so that marking of packets and measurements can be done per QoS flow.

[0090] Some embodiments relate to the enhancement of the 5GS to be able to provide additional network measurements (e.g. Packet Loss). This functionality may be included as an enhancement to 5GS QoS Monitoring, which allows the use of existing mechanisms and data structures, and may overall minimize the impact on the system.

[0091] For packet delay measurements, this method may not need to generate ad-hoc messages to measure the channel as QoS Monitoring feature does, instead, measurements can be done directly from the traffic packets. Some embodiments may relate to passive approaches instead of active approaches, and hence provide measurement results obtained from the actual user plane traffic. The additions to user plane may be minimal.

[0092] Thus, some embodiments may enable obtaining most relevant measurements from all domains (as compared to applying per-domain technologies).

[0093] According to one aspect of the present disclosure, a Session Management Function, SMF, configured for performing Quality of Service, QoS, Monitoring in a telecommunication network is provided. The SMF is configured to: configure at least one of a wireless device , a network node , and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions; receive, from at least one of the wireless device, network node, and UPF PSA , measurement data generated based on the instructions; and calculate at least one metric based on the measurement data.

[0094] According to one or more embodiments of this aspect, the measurement data includes at least one of: packet loss, one-way delay, two-way delay, and jitter.

[0095] According to one or more embodiments of this aspect, the at least one metric is calculated on at least one of a per-hop basis and an end-to-end basis.

[0096] According to one or more embodiments of this aspect, the SMF is further configured to expose the at least one metric to at least one other entity in the telecommunication network.

[0097] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0098] According to one or more embodiments of this aspect, the instructions corresponding to packet marking comprise at least one of: a target QoS Flow ID; a time block size; coloring and counting instructions indicating that at least one of: the UE is to mark uplink packets with color in uplink and count downlink packets in a downlink; the UPF PSA is to count in uplink and color in downlink; an intermediate is to monitor and relay packet coloring to a next hop; and the intermediate node is to count in uplink and downlink.

[0099] According to one or more embodiments of this aspect, the measurement data comprises at least one of: a block number; a count of the number of packets in the block; and at least one timestamp, the at least one timestamp being usable by the SMF to calculate at least one of delay, mean-block-delay when a color is used for packet marking, and second- color-delay when the color and at least a second color are used for packet marking.

[0100] According to one or more embodiments of this aspect, the instructions corresponding to packet marking indicate to use an explicit block counter, the explicit block counter including a first bit that flips with a first frequency and a second bit that flips with a second frequency half that of the first frequency.

[0101] According to another aspect of the present disclosure, a method performed by a Session Management Function, SMF, configured for performing Quality of Service, QoS, Monitoring in a telecommunication network is provided. The method includes: configuring at least one of a wireless device , a network node , and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packet counting instructions; receiving , from at least one of the wireless device , network node , and UPF PSA , measurement data generated based on the instructions; and calculating at least one metric based on the measurement data.

[0102] According to one or more embodiments of this aspect, the at least measurement data includes at least one of: packet loss, one-way delay, two-way delay, and jitter.

[0103] According to one or more embodiments of this aspect, the at least one metric is calculated on at least one of a per-hop basis and an end-to-end basis.

[0104] According to one or more embodiments of this aspect, the method further includes exposing the at least one metric to at least one other entity in the telecommunication network.

[0105] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0106] According to one or more embodiments of this aspect, the instructions corresponding to packet marking comprise at least one of: a target QoS Flow ID; a time block size; coloring and counting instructions indicating that at least one of: the UE is to mark uplink packets with color in uplink and count downlink packets in a downlink; the UPF PSA is to count in uplink and color in downlink; an intermediate is to monitor and relay packet coloring to a next hop; and the intermediate node is to count in uplink and downlink.

[0107] According to one or more embodiments of this aspect, the measurement data comprises at least one of: a block number; a count of the number of packets in the block; and at least one timestamp, the at least one timestamp being usable by the SMF to calculate at least one of delay, mean-block-delay when a color is used for packet marking, and second- color-delay when the color and at least a second color are used for packet marking.

[0108] According to one or more embodiments of this aspect, the instructions corresponding to packet marking indicate to use an explicit block counter, the explicit block counter including a first bit that flips with a first frequency and a second bit that flips with a second frequency half that of the first frequency.

[0109] According to another aspect of the present disclosure, a network node configured to communicate with a Session Management Function, SMF, is provided. The network node is configured to: receive first measurement data; receive, from the SMF, instructions corresponding to packet marking, the instructions indicating whether to generate additional measurement data; generate, based on the instructions, the additional measurement data; and transmit the first measurement data and, when generated, the additional measurement data.

[0110] According to one or more embodiments of this aspect, the marking and counting information includes an array of metrics indexed by a block number.

[0111] According to one or more embodiments of this aspect, the network node is further configured to, based on whether the instructions correspond to a hop-by-hop monitoring configuration: relay coloring of a packet to a next hop, the coloring corresponding to a fixedtime block to which the packet belongs; and when indicated by the instructions, perform counting in uplink, UL, and downlink, DL.

[0112] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0113] According to another aspect of the present disclosure, a method performed by a network node configured to communicate with a Session Management Function, SMF, is provided. The method includes: receiving first measurement data; receivin , from the SMF, instructions corresponding to packet marking, the instructions indicating whether to generate additional measurement data; generating , based on the instructions, the additional measurement data; and transmitting the first measurement data and, when generated, the additional measurement data.

[0114] According to one or more embodiments of this aspect, the marking and counting information includes an array of metrics indexed by a block number.

[0115] According to one or more embodiments of this aspect, the method further includes, based on whether the instructions correspond to a hop-by-hop monitoring configuration: relaying coloring to a next hop; and when indicated by the instructions, performing counting in uplink, UL, and downlink, DL.

[0116] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0117] According to another aspect of the present disclosure, a wireless device configured to communicate with a Session Management Function, SMF, is provided. The wireless device is configured to: receive, from the SMF, instructions corresponding to packet marking; perform packet marking of a data packet in uplink, UL, based on the instructions; generate counting information of the data packet in UL and downlink, DL; generate measurement data based on the instructions and at least one of the packet marking and the counting information; and transmit the measurement data to the SMF.

[0118] According to one or more embodiments of this aspect, the counting information includes an array of measurement data indexed by a block number.

[0119] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0120] According to another aspect of the present disclosure, a method performed by a wireless device configured to communicate with a Session Management Function, SMF, is provided. The method includes: receiving, from the SMF, instructions corresponding to packet marking; performing packet marking of a data packet in uplink, UL, based on the instructions; generating counting information of the data packet in UL and downlink, DL; generating measurement data based on the instructions and at least one of the packet marking and the counting information; and transmitting the measurement data to the SMF.

[0121] According to one or more embodiments of this aspect, the counting information includes an array of metrics indexed by a block number.

[0122] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane. According to another aspect of the present disclosure, a User Plane Function Packet Data Unit Session Anchor, UPF PSA, configured to communicate with a Session Management Function, SMF, is provided. The User Plane Function Packet Data Unit Session Anchor, UPF PSA, is configured to: receive, from the SMF, instructions corresponding to packet marking; perform packet marking of a data packet in downlink, DL, based on the instructions; generate counting information of the data packet in uplink, UL, and DL; generate measurement data based on the instructions and at least one of the packet marking and the counting information; and transmit the measurement data to the SMF.

[0123] According to one or more embodiments of this aspect, the marking and counting information includes an array of metrics indexed by a block number.

[0124] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0125] According to another aspect of the present disclosure, a method performed by a User Plane Function Packet Data Unit Session Anchor, UPF PSA, configured to communicate with a Session Management Function, SMF, is provided. The method includes: receiving, from the SMF, instructions corresponding to packet marking; performing packet marking of a data packet in downlink, DL, based on the instructions; generating counting information of the data packet in uplink, UL, and DL; generating measurement data based on the instructions and at least one of the packet marking and the counting information; and transmitting the measurement data to the SMF.

[0126] According to one or more embodiments of this aspect, the marking and counting information includes an array of metrics indexed by a block number.

[0127] According to one or more embodiments of this aspect, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0128] According to another aspect of the present disclosure, a method for Quality of Service, QoS, Monitoring in a telecommunication network, the network including a Session Management Function, SMF, a wireless device, a network node, and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, is provided. The method includes: configuring, by the SMF , each of the wireless device , network node , and UPF PSA with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions; performing packet marking by one of: the wireless device in the uplink, UL; and the UPF PSA , in the downlink, DL; performing counting by the wireless device , UPF PSA , and, when indicated by the instructions, the network node ; transmitting , by at least one of the wireless device , network node , and UPF PSA , measurement data based on the counting, the measurement data being transmitted to the SMF ; and calculating , by the SMF , at least one metric based on the measurement data.

[0129] BRIEF DESCRIPTION OF THE DRAWINGS

[0130] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0131] FIG. 1. is a schematic diagram of an example non roaming 5G system architecture;

[0132] FIG. 2 is a schematic diagram of an example non-roaming 5G system architecture;

[0133] FIG. 3 is a schematic diagram of a PDU Session with chained UPFs;

[0134] FIG. 4 is a flowchart illustrating classification and User Plane marking for QoS Flows and mapping to AN Resources;

[0135] FIG. 5 is a flowchart illustrating how a flow appears when it is split into traffic blocks with colored packets;

[0136] FIG. 6 is a block diagram of Alternate Making Method measurement modes;

[0137] FIG. 7 is a flowchart illustrating a measurement system according to some embodiments of the present disclosure;

[0138] FIG. 8 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0139] FIG. 9 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0140] FIG. 10 is a block diagram of an SMF according to some embodiments of the present disclosure;

[0141] FIG. 11 is a block diagram of a UPF PSA according to some embodiments of the present disclosure,

[0142] FIG. 12 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

[0143] FIG. 13 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0144] FIG. 14 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0145] FIG. 15 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0146] FIG. 16 is a flowchart of an example process in an SMF according to some embodiments of the present disclosure;

[0147] FIG. 17 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0148] FIG. 18 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0149] FIG. 19 is a flowchart of an example process in a UPF PSA according to some embodiments of the present disclosure;

[0150] FIG. 20 is another flowchart of an example process in an SMF according to some embodiments of the present disclosure;

[0151] FIG. 21 is another flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0152] FIG. 22 is another flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0153] FIG. 23 is a flowchart of an example process in a UPF PSA according to some embodiments of the present disclosure;

[0154] FIG. 24 is a flowchart of an example process according to some embodiments of the present disclosure,

[0155] FIG. 25 is a flowchart of QoS Flows in PDU Sessions with multiple PSAs according to some embodiments of the present disclosure;

[0156] FIG. 26 is a flowchart of an example procedure for external / internal exposure of new 5GS QoS parameter measurements according to some embodiments of the present disclosure; FIG. 27 is a flowchart of an example procedure for 5GS Monitoring using Alternate- Marking Method Solution according to some embodiments of the present disclosure;

[0157] FIG. 28. is a flowchart of an example procedure for configuration of UP entities to enable Alternate Marking Method based measurement according to some embodiments of the present disclosure;

[0158] FIG. 29 is a flowchart of an example procedure for Collection of Alternate Marking Method metrics from the UP entities according to some embodiments of the present disclosure;

[0159] FIG. 30 is a block diagram of an example GTP-U PDU Session Container structure according to some embodiments of the present disclosure;

[0160] FIG. 31 is a block diagram of an example Explicit Block Counter (EBC) according to some embodiments of the present disclosure;

[0161] FIG. 32 is a block diagram of an example of an updated PDU Session container where an Alternate Marking octet is added according to some embodiments of the present disclosure; and

[0162] FIG. 33 is a flowchart of an example Inter-network node handover procedure according to some embodiments of the present disclosure.

[0163] DETAILED DESCRIPTION

[0164] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to alternate marking for QoS flow measurements. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0165] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0166] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0167] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0168] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0169] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0170] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0171] Further, in some embodiments, the term “Access Domain” may refer to a network path between wireless device and network node.

[0172] In some embodiments, the term “Transport Domain” many refer to a network path between network node and UPF (which may also be referred to as N3 / N9 interfaces).

[0173] In some embodiments, the term “End-to-End Domain” may refer to a Network path between wireless device and UPF PSA.

[0174] In some embodiments, the term “Metrics” may refer to the information produced by individual user plane entities from monitoring the user plane traffic. Metrics may be used as input to calculate the QoS parameter measurements according to, e g., the Alternate Marking Method.

[0175] In some embodiments, the term “Measurements” may refer to QoS parameter values (or transmission KPI values) for a target service traffic and may influence the user Quality of Experience (QoE) for the service.

[0176] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0177] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B . In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0178] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0179] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0180] Some embodiments provide alternate marking for QoS flow measurements.

[0181] FIG. 7 shows an example measurement system comprising wireless device, network node, UPF and SMF. The wireless device and UPF color packets per QoS flow in accordance with the Alternate Marking method. All of the user plane nodes may record statistics related to colored packets and report to the SMF. By combining measurements from all the measurement nodes along the path between the UPF and the wireless device, the SMF can derive measurements from multiple domains.

[0182] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 8 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0183] Also, it is contemplated that a WD 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE / E- UTRAN and a gNB for NR / NG-RAN.

[0184] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0185] The communication system of FIG. 8 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0186] A network node 16 is configured to include a marking and counting unit 32 which is configured to perform one or more network node 16 functions described herein, including functions related to alternate marking for QoS flow measurements. A wireless device 22 is configured to include a marking and counting unit 34 which is configured to perform one or more wireless device 22 functions described herein, including functions related to alternate marking for QoS flow measurements. A UPF PSA 120 is configured to include a marking and counting unit 134 which is configured to perform one or more UPF PSA 120 functions described herein, including functions related to alternate marking for QoS flow measurements. An SMF 100 is configured to include a configuration unit 114 which is configured to perform one or more SMF 100 functions described herein, including functions related to alternate marking for QoS flow measurements.

[0187] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0188] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24. The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a control unit 54 configured to enable the service provider to observe / monitor / control / transmit to / receive from the network node 16 and / or the wireless device 22.

[0189] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0190] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72 In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0191] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include marking and counting unit 32 configured to perform one or more network node 16 functions described herein, including functions related to alternate marking for QoS flow measurements.

[0192] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0193] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0194] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a marking and counting unit 34 configured to perform one or more wireless device 22 functions described herein, including functions related to alternate marking for QoS flow measurements.

[0195] In some embodiments, the inner workings of the network node 16, WD 22, SMF 100, UPF PSA 120 and host computer 24 may be as shown in FIGS. 9-11 and independently, the surrounding network topology may be that of FIG. 8.

[0196] In FIG. 9, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0197] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0198] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc

[0199] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

[0200] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0201] FIG. 10 shows an SMF 100 according to one or more embodiments. The hardware 102 of the SMF 100 includes processing circuitry 108. The processing circuitry 108 may include a processor 112 and a memory 110. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 108 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 112 may be configured to access (e.g., write to and / or read from) the memory 110, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). The hardware 102 may include a communication interface 104 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 106 for setting up and maintaining at least a wireless connection.

[0202] Thus, the SMF 100 further has software 116 stored internally in, for example, memory 110, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the SMF 100 via an external connection. The software 116 may be executable by the processing circuitry 108. The processing circuitry 108 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e g., by SMF 100. Processor 112 corresponds to one or more processors 112 for performing SMF 100 functions described herein. The memory 110 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 116 may include instructions that, when executed by the processor 112 and / or processing circuitry 108, causes the processor 112 and / or processing circuitry 108 to perform the processes described herein with respect to SMF 100. For example, processing circuitry 108 of the SMF 100 may include configuration unit 114 configured to perform one or more SMF 100 functions described herein, including functions related to alternate marking for QoS flow measurements.

[0203] FIG. 11 shows a UPF PSA 120 according to one or more embodiments. The hardware 122 of the UPF PSA 120 includes processing circuitry 128. The processing circuitry 128 may include a processor 132 and a memory 130. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 128 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 132 may be configured to access (e.g., write to and / or read from) the memory 130, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). The hardware 122 may include a communication interface 124 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 126 for setting up and maintaining at least a wireless connection.

[0204] Thus, the UPF PSA 120 further has software 136 stored internally in, for example, memory 130, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UPF PSA 120 via an external connection. The software 136 may be executable by the processing circuitry 128. The processing circuitry 128 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UPF PSA 120. Processor 132 corresponds to one or more processors 132 for performing UPF PSA 120 functions described herein. The memory 130 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 136 may include instructions that, when executed by the processor 132 and / or processing circuitry 128, causes the processor 132 and / or processing circuitry 128 to perform the processes described herein with respect to UPF PSA 120. For example, processing circuitry 128 of the UPF PSA 120 may include marking and counting unit 134 configured to perform one or more UPF PSA 120 functions described herein, including functions related to alternate marking for QoS flow measurements.

[0205] Although FIGS. 8-11 show various “units” such as marking and counting unit 32, marking and counting unit 34, marking and counting unit 134, and configuration unit 114 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0206] FIG. 12 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 8-11, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 9. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S104). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

[0207] FIG. 13 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 8, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 8-11. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S 112). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

[0208] FIG. 14 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 8, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 8-11. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional sub step of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block S 118). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0209] FIG. 15 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 8, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 8-11. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130) In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

[0210] FIG. 16 is a flowchart of an example process in an SMF 100 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of SMF 100 such as by one or more of processing circuitry 108 (including the configuration unit 114), processor 112, radio interface 106 and / or communication interface 104. SMF 100 is configured to configure (Block S134) at least one of a wireless device 22, a network node 16, and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120) with marking instructions. SMF 100 is configured to receive (Block S136), from at least one of the wireless device 22, a network node 16, and UPF PSA 120, marking and counting information based on the marking instructions. SMF 100 is configured to calculate (Block S138) at least one metric based on the marking and counting information.

[0211] In some embodiments, the at least one metric comprises at least one of: packet loss, one-way delay, two-way delay, and jitter. In some embodiments, the metric is calculated on a per-hop basis.

[0212] FIG. 17 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the marking and counting unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to receive (Block S140), from the SMF 100, marking instructions. Network node 16 is configured to generate (Block SI 42), marking and counting information based on the marking instructions. Network node 16 is configured to transmit (Block S 144) the marking and counting information to the SMF 100.

[0213] In some embodiments, the marking and counting information comprises an array of metrics indexed by a block number.

[0214] In some embodiments, network node 16 is configured to, based on whether the marking instructions correspond to a hop-by-hop monitoring configuration, at least one of: relay coloring of a packet to a next hop, the coloring corresponding to a fixed-time block to which the packet belongs; and perform counting in uplink, UL, and downlink, DL

[0215] FIG. 18 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the marking and counting unit 34), processor 86, radio interface 82 and / or communication interface 60. Wireless device 22 is configured to receive (Block SI 46), from the SMF 100, marking instructions. Wireless device 22 is configured to generate (Block S148), marking and counting information based on the marking instructions. Wireless device 22 is configured to transmit (Block SI 50) the marking and counting information to the SMF 100.

[0216] In some embodiments, the marking and counting information comprises an array of metrics indexed by a block number. In some embodiments, wireless device 22 is further configured to: perform coloring in the uplink, UL, based on the marking instructions; and perform counting in the downlink, DL, based on the marking instructions.

[0217] FIG. 19 is a flowchart of an example process in a UPF PSA 120 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of UPF PSA 120 such as by one or more of processing circuitry 128 (including the marking and counting unit 134), processor 132, radio interface 126 and / or communication interface 124. UPF PSA 120 is configured to receive (Block S152), from the SMF 100, marking instructions. UPF PSA 120 is configured to generate (Block SI 54), marking and counting information based on the marking instructions. UPF PSA 120 is configured to transmit (Block SI 56) the marking and counting information to the SMF 100.

[0218] FIG. 20 is a flowchart of another example process in an SMF 100 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of SMF 100 such as by one or more of processing circuitry 108 (including the configuration unit 114), processor 112, radio interface 106 and / or communication interface 104. SMF 100 is configured to configure (Block S158) at least one of a wireless device 22, a network node 16, and a UPF PSA 120 with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions. SMF 100 is configured to receive (Block SI 60), from at least one of the wireless device 22, network node 16, and UPF PSA 120, measurement data generated based on the instructions. SMF 100 is configured to calculate (Block SI 62) at least one metric based on the received measurement data .

[0219] In some embodiments, the measurement data comprises at least one of: packet loss, one-way delay, two-way delay, and jitter. In some embodiments, the at least one metric is calculated on at least one of a per-hop basis and an end-to-end basis. In some embodiments, the SMF is further configured to expose the measurement data to at least one other entity in the telecommunication network. In some embodiments, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0220] In some embodiments, the instructions corresponding to packet marking comprise at least one of: a target QoS Flow ID; a time block size; coloring and counting instructions indicating that at least one of: the UE is to mark uplink packets with color in uplink and count downlink packets in a downlink; the UPF PSA is to count in uplink and color in downlink; an intermediate is to monitor and relay packet coloring to a next hop; and the intermediate node is to count in uplink and downlink. In some embodiments, the measurement data comprises at least one of: a block number;a count of the number of packets in the block; and at least one timestamp, the at least one timestamp being usable by the SMF to calculate at least one of delay, mean-block- delay when a color is used for packet marking, and second-color-delay when the color and at least a second color are used for packet marking.

[0221] In some embodiments, the instructions corresponding to packet marking indicate to use an explicit block counter, the explicit block counter including a first bit that flips with a first frequency and a second bit that flips with a second frequency half that of the first frequency.

[0222] FIG. 21 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the marking and counting unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to receive (Block S164) first measurement data. Network node 16 is configured to receive (Block SI 66), from the SMF 100, instructions corresponding to packet marking, the instructions indicating whether to generate additional measurement data. Network node 16 is configured to generate (Block SI 68), based on the instructions, the additional measurement data. Network node 16 is configured to transmit (Block SI 69) the first measurement data and, when generated, the additional measurement data.

[0223] In some embodiments, the marking and counting information comprises an array of metrics indexed by a block number. In some embodiments, network node 16 is configured to, based on whether the instructions correspond to a hop-by-hop monitoring configuration: relay coloring to a next hop; and when indicated by the instructions, perform counting in uplink, UL, and downlink, DL. In some embodiments, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0224] FIG. 22 is a flowchart of another example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the marking and counting unit 34), processor 86, radio interface 82 and / or communication interface 60. Wireless device 22 is configured to receive (Block S170), from the SMF 100, instructions corresponding to packet marking. Wireless device 22 is configured to perform (Block S 171) packet marking of a data packet in uplink, UL, based on the instructions. Wireless device 22 is configured to generate (Block S172) counting information of the data packet in UL and downlink, DL. Wireless device 22 is configured to generate (Block S 173), measurement databased on the instructions and at least one of the packet marking and the counting information. Wireless device 22 is configured to transmit (Block S174) the measurement data to the SMF 100.

[0225] In some embodiments, the counting information comprises an array of measurement dataindexed by a block number. In some embodiments, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0226] FIG. 23 is a flowchart of another example process in a UPF PSA 120 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of UPF PSA 120 such as by one or more of processing circuitry 128 (including the marking and counting unit 134), processor 132, radio interface 126 and / or communication interface 124. UPF PSA 120 is configured to receive (Block S176), from the SMF 100, instructions corresponding to packet marking. UPF PSA 120 is configured to perform (Block S178) packet marking of a data packet in downlink, DL, based on the instructions. UPF PSA 120 is configured to generate (Block S180) counting information of the data packet in uplink, UL, and DL. UPF PSA 120 is configured to generate (Block SI 82) measurement databased on the instructions and at least one of the packet marking and the counting information. UPF PSA 120 is configured to transmit (Block SI 84) the measurement data to the SMF 100.

[0227] In some embodiments, the marking and counting information comprises an array of metrics indexed by a block number. In some embodiments, the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

[0228] FIG. 24 is a flowchart of another example process for QoS monitoring. The process includes configuring (Block S 186), by the SMF 100, each of the wireless device 22, network node 16, and UPF PSA 120 with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions. The process includes performing (Block SI 88) packet marking by one of: the wireless device 22 in the uplink, UL; and the UPF PSA 120, in the downlink, DL. The process includes performing (Block SI 90) counting by the wireless device 22, UPF PSA 120, and, when indicated by the instructions, the network node 16. The process includes transmitting (Block SI 92), by at least one of the wireless device 22, network node 16, and UPF PSA 120, measurement databased on the counting, the measurement data being transmitted to the SMF 100. The process includes calculating (Block S194), by the SMF 100, at least one metric based on the measurement data. Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for alternate marking for QoS flow measurements. One or more wireless device 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, marking and counting unit 34, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, marking and counting unit 32, etc. One or more SMF functions described below may be performed by one or more of processing circuitry 108, processor 112, configuration unit 114, etc. One or more UPF PSA functions described below may be performed by one or more of processing circuitry 128, processor 132, marking and counting unit 134, etc.

[0229] Some embodiments relate to a measurement system that enables measurements of QoS parameters for certain service data flows such as packet loss, packet delay and packet delay variation, e.g., by use of the Alternate Marking Method described in IETF RFC 9341.

[0230] The target setting for this invention is a 5G deployment where the service data flows are transmitted over QoS flows established by SMF following a user plane data path managed also by SMF.

[0231] Some embodiments relate to the 5GS SMF, acting as the “brain” of the measurement system, and the 5GS user plane path: the end points, namely wireless device and UPF-PSA and the intermediate hops, namely network node and optionally, other UPFs chained along the path.

[0232] Some embodiments relate to procedures for:

[0233] • Exposure of these measurements to 5GS internal and external nodes

[0234] • Configuration of the various nodes contributing to the measurements, o Alternate marking parameters. o Measurement granularity (e.g., per QoS flow).

[0235] • Collection of data for the measurement by SMF.

[0236] And from the definition of the Information Elements (IEs) where bits can be allocated in the 3GPP user plane protocols so that marking of packets (and measurements) can be done per QoS flow.

[0237] The Alternate Marking Method may be applied at QoS Flow level. Only the target service data flows may be bound to the monitored QoS Flow and contribute to the measurement. The 5GS user plane entities are requested to mark traffic, count packets per block and / or relay the Alternate Marking Method marks to next hop according to Alternate Marking Method. SMF receives metrics from the user plane entities that it correlates to produce the measurements.

[0238] In the case of chained UPFs the monitored QoS Flows may need to be established E2E, that is different QoS Flows are used for the different data paths.

[0239] FIG. 25 shows QoS Flows in PDU Sessions with multiple PSAs.

[0240] Some embodiments relate to how the measurement bits are allocated in the 3 GPP user plane protocols so that packet marking, and measurements can be done per QoS flow.

[0241] Some embodiments relate to consistently maintaining alignment among all entities involved. This may include determining which traffic to monitor and which traffic block the information corresponds to, throughout the entire process, including during and after UP path changes. Therefore, mobility may be taken into consideration.

[0242] External / Internal exposure of new 5GS QoS parameter measurements

[0243] Some embodiments relate to enhancements to 3 GPP 5GS QoS Monitoring to allow intemal / external exposure of additional QoS parameter measurements. These new measurements are calculated and reported by SMF upon request.

[0244] Some embodiments may not impact the procedures to request and expose QoS parameter measurements. The message data structures may be impacted so that the new measurements can be requested using QoS Monitoring and reported in QoS Monitoring events.

[0245] An example procedure for external / internal exposure of new 5GS QoS parameter measurements is shown in FIG. 26, where the dotted lines are used when there are two or more alternatives.

[0246] 5GS QoS Monitoring functionality may be extended with additional QoS parameter measurements determined by 5GS using the Alternate-Marking Method, at this stage namely:

[0247] 1. UL and DL Packet Loss

[0248] 2. UL and DL Delay*

[0249] 3. UL and DL Delay variation (jitter)

[0250] *From 3GPP Rel’ 16, 5GS calculates UL / DL Delay and RTT using a 3GPP specific mechanism. Delay measurement would not be new but obtained using this method.

[0251] To externally expose the new QoS parameter measurements (to an AF:

[0252] As in the baseline procedures, whether AF sends the requests directly to PCF (option a. in the procedure in FIG. 26.) or via NEF (option b. in the procedure in FIG. 9.) depends on whether AF is trusted or not trusted. In the second case, the role of NEF is to authorize the AF request and to complement it as needed with locally configured information before sending it to PCF :

[0253] • The QoS Monitoring request to NEF (by AF) and to PCF (by AF / NEF) is enhanced to support the additional QoS parameter measurements. The corresponding report notification by PCF (to AF / NEF) and by NEF (to AF) is also enhanced to support the additional measurements.

[0254] • Based on the AF / NEF request or local policy, PCF determines a QoS Monitoring Policy that it sends to SMF in updated PCC Rules.

[0255] • The QoS Monitoring Policy is enhanced to support the additional QoS parameter measurements.

[0256] To internally expose the new QoS parameter measurements to a 5GC consumer NF (cNF):

[0257] As in the baseline procedures, internal consumers (e.g., NWDAF) can request QoS parameter measurements subscribing to QoS Monitoring event exposure to SMF (option c. in FIG. 26):

[0258] • The QoS Monitoring request in the subscription to SMF event exposure is enhanced to support the additional measurements.

[0259] The request triggers in SMF QoS parameter measurement for the targeted service data flow with collaboration of the UP entities in the service data flow path.

[0260] In SMF, at certain point in time, a reporting trigger is met. For the reporting of the measurements internally (within 5GC) or externally (to AF):

[0261] As in the baseline procedures reporting can be done directly by SMF to AF / NEF (also referred to as SMF direct reporting), but it could be via PCF if, for example, PCF also consumes the reports. The alternatives have been labelled in procedure in FIG. 26, a. (direct reporting to AF), b (reporting via NEF) and c. (reporting to internal consumers):

[0262] • The SMF notifications to PCF, AF / NEF or other consumer NFs (e.g., NWDAF) are enhanced to also support the new QoS parameter measurements. The notifications by PCF to AF / NEF and by NEF to AF are also enhanced to support the new QoS parameter measurements.

[0263] QoS parameter measurement procedure

[0264] General

[0265] An overview of 5GS Monitoring using Alternate-Marking Method Solution according to some embodiments is shown in FIG. 27. Upon request, SMF calculates the measurements for a certain Service Data Flow using the Alternate Marking Method and with the contribution of two or more entities in the traffic UP path.

[0266] Some embodiments apply the flow-based variant of this method, which may require knowing the path followed by the target traffic flows. Such embodiments may allow both end-to-end (UE - UPF PSA) monitoring and hop-by-hop monitoring along that path.

[0267] High level overview of example embodiments:

[0268] 1. The new QoS parameter measurement based on the Alternate Marking Method is part of a request to SMF.

[0269] 2. The request triggers SMF to determine the QoS Flow to monitor (i.e. the QoS Flow that is bound to the target Service Data Flow), the data path and UP entities that shall contribute to the measurement and how they should contribute, and SMF provisions these entities with instructions both for QoS Flow packet marking (aka coloring), packet marking relay and packet counting, and for reporting of corresponding information.

[0270] 3. The UP entities proceed according to the instructions, including reporting to SMF.

[0271] 4. With the information reported for the QoS Flow, SMF calculates the measurement requested for the Service data Flow.

[0272] 5. SMF reports the measurements as requested.

[0273] Node configuration to enable Alternate Marking Method based measurement by SMF

[0274] A description follows as to how SMF performs configuration of the required nodes (i.e., the data path UP entities) to enable Alternate Marking Method based measurement.

[0275] During the PDU Session Establishment / Modification procedure (e.g., as specified in 3GPP TS 23.502), Policy Control and Charging (PCC) Rules are sent by PCF to SMF in SM policy Association Establishment / Modification message. The description below describes steps in the procedure.

[0276] A PCC Rule with a QoS Monitoring Policy for one of the Alternate Marking Method based measurements in a PCC Rule triggers in SMF the following actions (see, e g., FIG. 28, which shows configuration of UP entities to enable Alternate Marking Method based measurement):

[0277] 1. SMF determines the QoS Flow bound to the PCC Rule and whether it is only bound to this PCC Rule (i.e. not shared with other PCC Rules). Else it modifies the binding to satisfy this condition.

[0278] 2. SMF determines the data path of the PCC Rule target data flows and the UP entities that shall be configured in order to provide the requested QoS parameter measurement (i.e., the wireless device 22 and UPF PSA, and RAN (e.g., network node 16) and optionally other UPFs that constitute the 5GC user plane for the target data flows).

[0279] 3. SMF determines the Alternate Marking Method instructions corresponding to each UP entity involved: o Target QoS Flow QFI o Time Block size o Coloring / Counting instructions

[0280] □ Wireless device 22 may need be instructed to Color in UL and Count in DL

[0281] □ UPF PSA may need to be instructed to Count in UL and Color in DL

[0282] □ Intermediate nodes may only be instructed to monitor and relay the coloring (UL and DL) to next hop if end-to-end monitoring, but

[0283] □ Intermediate nodes may also be instructed to count in UL and DL if hop-by-hop monitoring

[0284] These instructions may specify which bits need be colored / counted / relayed on each traffic direction. As an alternative, these instructions may just indicate the target measurements. With this alternative, the actions requested from each UP entity (and the specific bits involved) may be locally configured or coded (e.g., if standardized) in the UP entities themselves according to the target measurement(s).

[0285] SMF also determines the Alternate Marking Method metrics reporting instructions corresponding to each UP entity involved: o Triggers for reporting, e.g., (time periodicity, periodicity (e.g., number of blocks), UP path update event.. .) o Destination of reporting (i.e., SMF).

[0286] 4. SMF provisions the UPF(s) by means of PFCP Session Establishment / Update. SMF updates the PFCP Session PDRs and QERs if the traffic binding to QoS Flow has been modified.

[0287] SMF includes the Alternate Marking Method instructions, including metric reporting instructions, corresponding to the UPF(s) o This information is provided as QoS Monitoring per QoS Flow Control Information (in Session Reporting Rules for the target QoS Flow QFI).

[0288] O As an alternative, in addition, instructions to UPF may be provided as part of FAR associated to the PDRs for the service data flow.

[0289] 5. SMF invokes Namf_Communication_N lN2MessageTransfer towards AMF according to the corresponding procedures SMF sends the following via AMF :

[0290] To the wireless device 22, using NAS-SM, SMF sends any updates on the PDU Session QoS rule(s) and / or QoS Flow descriptions associated with these QoS rule(s).

[0291] SMF includes the Alternate Marking Method instructions and Alternate Marking Method metric reporting instructions corresponding to the wireless device 22 in the information that is sent to the wireless device 22 (N1 SM Container) o This information is provided as QoS Flow Description information of the target QoS Flow.

[0292] To the RAN (e.g., network node 16), using N2 SM information, SMF sends any updates on the PDU Session QoS Flows and QoS parameters to be applied to the QoS flows.

[0293] SMF includes the Alternate Marking Method instructions and optionally (if hop-by-hop mode) Alternate Marking Method metric reporting instructions corresponding to the RAN (e.g., network node 16) in the information that is sent to the RAN (N2 SM information) o This information is provided as QoS parameters to be applied to the target QoS flow.

[0294] When user traffic starts on the QoS Flow, the different UP entities along the data Path follow the instructions received for the QoS Flow.

[0295] Procedures for Data Collection

[0296] A description follows for how SMF receives from the UP entities the Alternate Marking Method information requested to calculate the new QoS parameter measurements.

[0297] The UP entities in the data path report their Alternate Marking Method metric information to SMF as instructed by SMF. At some point in time, there is an event that triggers them to report their Alternate Marking Method metric information to SMF, so that SMF can correlate the information of the metrics to produce the requested measurements.

[0298] A description of the reporting by the relevant UP entities follows (it is also shown in FIG. 29, which depicts Collection of Alternate Marking Method metrics from the UP entities):

[0299] It should be noted that the order of the reporting may be other than the one described here. In some embodiments, only wireless device 22 and UPF PSA may have been instructed to report in the case of end-to-end metrics. RAN (e.g., network node 16) and intermediate UPFs may have been instructed to report if hop-by-hop metrics.

[0300] An Event (e.g., received reporting instructions) triggers UPF to report to SMF

[0301] UPF reports the Alternate Marking Method metric information in PF CP Session Reports to SMF.

[0302] O The information is provided in enhanced Session Reporting Reports An Event (e.g., received reporting instructions) triggers wireless device 22 to report to SMF

[0303] Wireless device 22 reports the Alternate Marking Method metric information for the PDU Session and QoS Flow in a NAS SM message (PDU Session Modification Request) to AMF

[0304] AMF sends the information to SMF using an Nsmf PDU Session_UpdateSM Context operation

[0305] An Event (e.g., received reporting instructions) triggers RAN (e.g., network node 16) to report to SMF

[0306] RAN (e g., network node 16) reports the Alternate Marking Method metric information for the PDU Session and QoS Flow in an N2 message with SM information that is sent to AMF.

[0307] AMF sends the information to SMF in an Nsmf_PDU Session_UpdateSM Context operation.

[0308] The SMF Update SM Context service operation is used by all procedures which require providing N1 or N2 SM information to the SMF (e g., wireless device 22 requested PDU Session Establishment procedure); Some embodiments may use it as well to report per QoS Flow information.

[0309] SMF measurement calculation

[0310] As described herein, SMF instructs, independently, each of the nodes depending on their role in the data path and requested measurement: to count, to color and / or to relay the traffic color. As described herein, in some embodiments:

[0311] • For end-to-end measurements, only wireless device 22 and PSA count / color packets

[0312] • For hop-by-hop measurements, only wireless device 22 and PSA color packets, but all the nodes of the path count packets, i.e., wireless device 22, RAN (e.g., network node 16) and UPF(s).

[0313] The instructed nodes may report to SMF array of metrics indexed by block number: • Block Number: the block number is derived by each of the nodes from the packets depending to the number of bits used.

[0314] • Packet count: number of observed packets in the block

[0315] • Delay timestamp: timestamp for delay calculation; mean-block-delay- timestamp when just one color is used, or second-color-delay -timestamp when second color is supported.

[0316] SMF may have to correlate the metrics from the different nodes, the report of the metrics shall be indexed by PDU session QFI and block number, e g.:

[0317] • PDU Session X o QFI Y

[0318] ■ Block Number

[0319] • Packet Count

[0320] • Delay Timestamp o QFI Z

[0321] ■ Block Number

[0322] • Packet Count

[0323] • Delay Timestamp

[0324] SMF receives the metrics of the nodes in the traffic path and calculates the requested measurements. As described above, the measurements that can be obtained from the parameters observed with the Alternative-Marking-Method are:

[0325] • Packet Loss is calculated as the difference between the Packet Count in the received and the sender node. SMF may decide to calculate the Packet Loss per block or as an average of the full reporting period.

[0326] • Packet Delay is calculated as the difference between the Delay Timestamp in the received and the sender node. SMF may decide to calculate the Packet Delay per block or as an average of the full reporting period.

[0327] • Jitter is directly calculated as a statistic from the Packet Delay and there are different modes of measuring it, e.g., mean deviation or mean absolute deviation.

[0328] When measurements are done hop-by-hop, the SMF may still report the measurements per hop, per domain (i.e., Access Domain and Transport Domain) or end-to- end depending on consumer request.

[0329] Protocol Extensions for Marking Bits

[0330] To perform measurements for individual QoS flows it may need to be possible to associate the marking bits with a QFI value. Packets are associated with QFI values in two separate protocol layers depending on which domain between a wireless device 22 and a UPF the packet is currently traversing.

[0331] In the Access Domain, functions of the SDAP sublayer on the user plane protocol stack include: the Mapping between a QoS flow and a data radio bearer, and the of the Marking QoS flow ID (QFI) in both DL and UL packets (as specified in, e.g., 3GPP TS 38.300). Some embodiments extend the SDAP protocol, e.g., as specified in 3GPP TS 38.323, to convey the necessary bits for Alternate Marking. The SDAP layer as it is currently specified consists of a single octet with the following structure:

[0332] • Bits 1-6 encode the QFI, valued 0-63.

[0333] • The seventh bit is used as an indicator for reflective QoS.

[0334] • The eighth bit is used for padding.

[0335] In some embodiments, the padding bit of the SDAP octet is used for alternate marking. This incurs a minimal change to the structure of the SDAP layer. It may, however, limit the Alternate Marking system to the use of a single bit only.

[0336] As specified in, e.g., IETF RFC 9341, it can be useful to make use of two coloring bits for certain measurements. An alternative embodiment where multiple measurement bits are supported would instead use the 8thbit in the SDAP octet as a measurement byte indicator. If the indicator is set, there will be another octet following the initial SDAP octet, this allows for up to 8 measurement bits, at the cost of an additional one-byte overhead per packet.

[0337] In the Transport Domain it is proposed to extend the GTP-U PDU Session Container to convey the necessary bits for alternate marking. A GTP-U PDU Session Container structure is shown in FIG. 30.

[0338] The first bit of the first octet is defined as a Spare field and may be set to 0 and not be processed by receivers. This value can be repurposed for an extension that supports alternate marking. Options for repurposing the Spare bit include:

[0339] 1. Use the bit to convey the Alternate marking bit. This solution is limited to 1 - bit marking only but does not require extension of the packet format.

[0340] 2. Define the bit as an Alternate Marking Flag If the flag is present the PDU session container is extended with one octet. This octet would support both one- and two- bit marking schemes. One bit of that octet could be used for indicating marking scheme type. 5 -bits could be used to improve measurement robustness or as Spare values for future use.

[0341] Explicit Block Counter In some embodiments where an entire octet is used to convey the alternate marking bits, there may be 6 bits available for use beyond the basic packet coloration. One such use is an Explicit Block Counter (EBC). The EBC may be used to ensure synchronization across nodes. There can be frequent network node 16 handovers when users are mobile. When the measurement nodes report their packet counts and associated statistics, they can indicate which block the counting corresponds to, based on the value of the EBC. This may make the process of correlation straight forward in the SMF, even when the network topology is highly dynamic.

[0342] According to the UP path change scenario analysis, at least for end-to-end measurements, it is possible for wireless device 22 and UPF PSA keep synchronized block counter and provide information that refers to same block and can be correlated. However, this solution may not be robust enough if severe loss (e.g., when two consecutive blocks are lost and that goes undetected by one end point). If there is such risk, explicit block counter may be used.

[0343] The original Alternate Marking method could be said to have a block counter of size

[0344] 2. By allocating one more marking bit that changes at half the frequency of the first bit the block counter is of size 4. Depending on the desired level of robustness additional bits can be added.

[0345] FIG. 31 shows an EBC of size two where the first bit consists of the regular alternate marking bit and a second bit that flips at half the frequency of the first.

[0346] FIG. 32 shows an example of an updated PDU Session container where an Alternate Marking octet is added.

[0347] The example embodiment of FIG. 32 defines the following elements:

[0348] 1. AMP - Alternate Marking Packet, indicates whether an Alternate Marking octet is present.

[0349] 2. C2 - Represents the second color in the two-color Alternate Marking Scheme.

[0350] 3. Cl - Corresponds to the first color in the Alternate Marking scheme.

[0351] 4. EBC - A single bit EBC, allows for explicit block counting up to 4.

[0352] 5. Spare - reserved bits, could be used for increased EBC size or reserved for future extensions.

[0353] Enhancements on UPF Selection

[0354] In some embodiments, UPF is enhanced to support a feature called “Alternate- Marking Method.” The feature can be enabled / disabled on a per subscriber, on a per group of subscribers, on a per global (network) basis or on a per DNN basis.

[0355] In the PF CP Association procedure, UPF reports to SMF a new UP function feature (ALTMM, Alternate-Marking Method). This allows SMF to select a UPF supporting this capability on a per PFCP session basis.

[0356] Table 1: UP Function Features

[0357] The UPF can also indicate to the NRF the support of the new feature in the UPF profile.

[0358] User Mobility

[0359] General

[0360] In mobile networks, user mobility and some other events may cause a change of the service flow data path while it is being monitored. The following cases have been considered to check the robustness of the solution, leading in some cases to solution enhancements:

[0361] • Change of PSA, for the different the SSC modes

[0362] • Change of data path when multiple PSAs (by insertion of BP / ULCL and / or routing update)

[0363] • Change on the access domain (e.g., inter gNB HO). A base procedure for the analysis is specified in, e g., clause 9.2.3. of 3GPP TS 38.300.

[0364] Two types of measuring scenarios are addressed: end-to-end and hop-by-hop.

[0365] It should be noted that “Synchronized from traffic start” is used in some embodiments, such as those discussed below. It means that, assuming no full block is lost, for these entities (end points of a data path), all entities see same block as first block and so the first block entity sends and the other entity receives (and the other way around) of the traffic monitored is the same.

[0366] End-to-end measurements

[0367] In some embodiments, in the case of end-to-end measurements, coloring and counting of packets may occur only in the wireless device 22 and the UPF PSA. Both entities may need to be aligned during and after the data path change. The rest of entities in between may still be affected by the change — they do not store an Alternate Marking Method context, but instructions to relay the marking of the monitored QoS Flow.

[0368] In some embodiments, with system and node configuration and the indicated Xn protocol enhancement described herein, the end-to-end measurement may continue to work also with User Mobility. SMF plays a fundamental role in the coordination of instructions to the different entities and interpretation of the information received.

[0369] Change of PSA (SSC modes)

[0370] The PDU Session SSC mode conditions the type of PSA changes that are possible.

[0371] • If SSC mode 1, the PSA will not change during the PDU Session lifetime.

[0372] • If SSC mode 2 or SSC Mode 3: the PSA may change. As long as the Alternate Marking Method context is bound to the QoS Flow within the PDU Session, both the UE and the PSA will maintain separated contexts for the former and new PDU Sessions and they will be, in principle, synchronized from traffic start.

[0373] Change of data path when multiple PSAs

[0374] The service data flow path may change because of the insertion of BP / ULCL and / or a routing update (e.g., to steer the service data flow to a different PSA).

[0375] As earlier described, the solution requires that QoS Flows are established End-to- end (see FIG. 25) and the QoS Flows on the new data path may need to be established (including configuration with the alternate marking instructions) before the service data flow switches PSA: o If Branching point (BP), wireless device 22 may be instructed on which IP prefixes that shall be used for each traffic destination using IPv6 RA, and UPF BP is instructed on the routing to apply for the IP prefixes. A new IPv6 RA can provide the wireless device 22 with updated instructions any time. When different E2E QoS Flows are used for the Different IP prefixes (and paths), both the wireless device 22 and the UPF PSA will maintain separated contexts for the former and new path and they will be, in principle, synchronized from traffic start. o If Uplink Classifier (ULCL), UPF ULCL is instructed on which traffic destinations go to which route (PSA). When different E2E QoS Flows are used for the different paths, both the wireless device 22 and the UPF PSA can maintain separated contexts for former and new path. To dynamically change the PSA of certain traffic (e.g. to certain destination), one option is to instruct wireless device 22 to switch QFI for the traffic destination. If ULCL traffic steering control is based on QFI matching rules (rather than destinations), UPF ULCL does not require updated instructions for the new steering, the path switch is triggered from wireless device 22 and the metrics at both ends are, in principle, synchronized from traffic start. If wireless device 22 is configured with reflective QoS flow, the path switch needs to be triggered on the UPF ULCL updating the steering instructions. First downlink packet on the new QFI can trigger in wireless device 22 the update of the traffic filter to QFI mapping and so, the counting context switching. Some counting misalignment in uplink can be expected.

[0376] In some cases, 3 GPP procedures may perform the switch instructing the UPF ULCL to change the routing for the traffic destination without wireless device 22 involvement.

[0377] UP path changes in the access domain (intra-NR RAN HO)

[0378] The role of network node 16 in end-to-end measurements is to relay the marking information received to next node in the path, that is to wireless device 22 in DL and to UPF in UL as previously described.

[0379] The network node 16 may require specific instructions for relay or it may be specified (and designed) to always relay certain IES. In any case, when the source network node 16 issues the HO request to the target network node 16 over Xn, the information it conveys includes the current QoS flow to DRB mapping rules applied to the wireless device 22, and other PDU session related information including the slice information and QoS flow level QoS profile(s).

[0380] The alternate Marking Method instructions, if any, corresponding to the QoS Flows to monitored are transferred from source network node 16 to target network node 16 in the Handover request (see step 1 in procedure in FIG. 33, which depicts Inter-network node 16 handover procedures as specified in, e.g., 3GPP TS 38.300). Instructions, if any, are for the relay of the traffic marking.

[0381] Hop-by-hop Measurements

[0382] In the case of hop-by-hop measurements, the impact of mobility procedures in intermediate UP path entities also need be considered, since they also keep an Alternate Marking Method context for the target QoS flow and PDU Session.

[0383] See below the analysis performed. With the proposed system and node configuration and the indicated Xn protocol enhancement, the end-to-end measurement may continue to work also when User Mobility. SMF may play a fundamental role in the coordination of instructions to the different entities and interpretation of the information received.

[0384] UP Path change and SSC Modes

[0385] The outcome of the end-to-end analysis for different SSC modes applies the same: there is a new Alternate Marking Method context for the QoS Flow on the new PDU Session also in the intermediate UP entities and they are synchronized from traffic start.

[0386] UP Path change and Chained UPF(s)

[0387] The outcome of the end-to-end analysis applies the same: all entities in the user plane path may be kept synchronized if end to end QoS Flows are established. The QoS Flows on the new data path need to be established (including configuration with the alternate marking instructions) before the PSA for the service data flows changes, or the path to the PSA changes. As described above, the path change can be triggered on the wireless device 22 or on the UPF ULCL (with reflective QoS), but in the second case some misalignment in the uplink metrics can be expected.

[0388] Up Path change due to intra-NG Handover (HO)

[0389] The outcome of the end-to-end analysis applies in this case as well:

[0390] The alternate Marking Method instructions for the QoS Flows to monitor are transferred from source network node 16 to target network node 16 in the Handover request (see FIG. 33). For Hop-by-hop metrics, there are instructions for counting and for metric reporting.

[0391] In some cases, it may be challenging not to lose the synchronization of the counting in R(AN) with rest of UP entities for the QoS Flow as transmission with wireless device 22 stops being over source network node 16 to be over target network node 16.

[0392] During the handover procedure source network node 16 provides information to target network node 16 of the transmission status (as specified, e g., in clause 9.2.3 of 3GPP 38.300).

[0393] The status information for the QoS Flow to monitor may be extended with Alternate Marking Method state information that allows target network node 16 to get synchronized In the case of DAPS, there may be several transmission state updates exchanged. They may need to include the alternate marking method state information.

[0394] The state information may consist of the block number and corresponding block metric for the last PDCP SDU seen on each QoS Flow monitored, for uplink and downlink directions. Target network node 16 may perform according to the instructions received (counting and reporting) as soon as it starts sending data to the wireless device 22. If DAPS applies, the source network node 16 continues counting and reporting until handover success is indicated by the target network node 16.

[0395] In the case of RAN Split architecture, functionalities described herein may be performed by the Central Unit (CU).

[0396] CU may be split into CP and UP. In this case:

[0397] SMF provides RAN (e.g., network node 16) with Alternate Marking Method instructions and Alternate Marking Method information reporting instructions which triggers CU-CP to send to CU-UP over El the corresponding instructions as additional QoS parameters for the target QoS Flow.

[0398] CU-UP reports the metrics as instructed to CU-CP over El . CU-CP performs then the reporting towards the 5GC.

[0399] In some embodiments, the Alternate marking method applied in hop-by-hop mode considers wireless device 22-CU to be one hop.

[0400] Example embodiments include:

[0401] Example 1: A Session Management Function, SMF, 100 configured for performing Quality of Service, QoS, Monitoring in a telecommunication network, the SMF 100 comprising processing circuitry 108 configured to: configure at least one of a wireless device 22, a network node 16, and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, 120 with marking instructions; receive, from at least one of the wireless device 22, a network node 16, and UPF PSA 120, marking and counting information based on the marking instructions; and calculate at least one metric based on the marking and counting information.

[0402] Example 2: The SMF of Example 1, wherein the at least one metric comprises at least one of: packet loss, one-way delay, two-way delay, and jitter.

[0403] Example 3: The SMF of any one of Examples 1-2, wherein the metric is calculated on a per-hop basis.

[0404] Example 4: A method performed by a Session Management Function, SMF, 100 configured for performing Quality of Service, QoS, Monitoring in a telecommunication network, method comprising: configuring (Block S134) at least one of a wireless device 22, a network node 16, and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, 120 with marking instructions; receiving (Block SI 36), from at least one of the wireless device 22, a network node 16, and UPF PSA 120, marking and counting information based on the marking instructions; and calculating (Block SI 38) at least one metric based on the marking and counting information.

[0405] Example 5: The method of Example 4, wherein the at least one metric comprises at least one of: packet loss, one-way delay, two-way delay, and jitter.

[0406] Example 6: The method of any one of Examples 4-5, wherein the metric is calculated on a per-hop basis.

[0407] Example 7: A network node 16 configured to communicate with a Session Management Function, SMF, 100, the network node 16 comprising processing circuitry 68 configured to: receive, from the SMF 100, marking instructions; generate marking and counting information based on the marking instructions; and transmit the marking and counting information to the SMF.

[0408] Example 8: The network node 16 of Example 7, wherein the marking and counting information comprises an array of metrics indexed by a block number.

[0409] Example 9: The network node 16 of any one of Examples 7-8, wherein the processing circuitry 68 is further configured to, based on whether the marking instructions correspond to a hop-by-hop monitoring configuration, at least one of: relay coloring to a next hop; and perform counting in uplink, UL, and downlink, DL.

[0410] Example 10: A method performed by a network node 16 configured to communicate with a Session Management Function, SMF, 100, method comprising: receiving (Block SI 40), from the SMF 100, marking instructions; generating (Block SI 42), marking and counting information based on the marking instructions; and transmitting (Block S144) the marking and counting information to the SMF 100.

[0411] Example 11: The method of Example 10, wherein the marking and counting information comprises an array of metrics indexed by a block number.

[0412] Example 12: The method of any one of Examples 10-11, further comprising: based on whether the marking instructions correspond to a hop-by-hop monitoring configuration, at least one of: relaying coloring to a next hop; and performing counting in uplink, UL, and downlink, DL.

[0413] Example 13: A wireless device 22 configured to communicate with a Session Management Function, SMF, 100, the wireless device 22 comprising processing circuitry (4 configured to: receive, from the SMF 100, marking instructions; generate marking and counting information based on the marking instructions; and transmit the marking and counting information to the SMF.

[0414] Example 14: The wireless device 22 of Example 13, wherein the marking and counting information comprises an array of metrics indexed by a block number.

[0415] Example 15: The wireless device 22 of any one of Examples 13-14, wherein the processing circuitry 84 is further configured to: perform coloring in the uplink, UL, based on the marking instructions; and perform counting in the downlink, DL, based on the marking instructions.

[0416] Example 16: A method performed by a wireless device 22 configured to communicate with a Session Management Function, SMF, 100, method comprising: receiving (Block SI 46), from the SMF 100, marking instructions; generating (Block SI 48), marking and counting information based on the marking instructions; and transmitting (Block SI 50) the marking and counting information to the SMF 100.

[0417] Example 17: The method of Example 16, wherein the marking and counting information comprises an array of metrics indexed by a block number.

[0418] Example 18: The method of any one of Examples 16-17, further comprising: performing coloring in the uplink, UL, based on the marking instructions; and performing counting in the downlink, DL, based on the marking instructions.

[0419] Example 19: A User Plane Function Packet Data Unit Session Anchor, UPF PSA, 120 configured to communicate with a Session Management Function, SMF, 100, the User Plane Function Packet Data Unit Session Anchor, UPF PSA, 120 comprising processing circuitry 128 configured to: receive, from the SMF 100, marking instructions; generate marking and counting information based on the marking instructions; and transmit the marking and counting information to the SMF.

[0420] Example 20: The UPF PSA 120 of Example 19, wherein the marking and counting information comprises an array of metrics indexed by a block number. Example 21: The UPF PSA 120 of any one of Examples 19-20, wherein the processing circuitry 128 is further configured to: perform counting in the uplink, UL, based on the marking instructions; and perform coloring in the downlink, DL, based on the marking instructions.

[0421] Example 22: A method performed by a User Plane Function Packet Data Unit Session Anchor, UPF PSA, 120 configured to communicate with a Session Management Function, SMF, 100, method comprising: receiving (Block SI 52), from the SMF 100, marking instructions; generating (Block SI 54), marking and counting information based on the marking instructions; and transmitting (Block SI 56) the marking and counting information to the SMF 100.

[0422] Example 23: The method of Example 22, wherein the marking and counting information comprises an array of metrics indexed by a block number.

[0423] Example 24: The method of any one of Examples 22-23, further comprising: performing counting in the uplink, UL, based on the marking instructions; and performing coloring in the downlink, DL, based on the marking instructions.

[0424] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0425] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special 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 flowchart and / or block diagram block or blocks.

[0426] These computer program instructions may also be stored in a computer readable memory or storage 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 memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

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

[0428] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. 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. 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.

[0429] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++ However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0430] Abbreviations that may be used in the preceding description include:

[0431] Abbreviation Explanation

[0432] 5GC 5G Core

[0433] 5GS 5G System

[0434] AF Application Function

[0435] AF Application Function

[0436] AKA also known as

[0437] AMF Access and Mobility Function

[0438] AN Access Network

[0439] AS Application Server cNF Consumer Network Function

[0440] DAPS Dual Active Protocol Stack

[0441] DL Downlink

[0442] DN Data Network

[0443] E2E End to end

[0444] EBM Explicit Block Metric eNB Evolved Node B

[0445] FAR Forwarding Action Rule

[0446] GBR Guaranteed Bit Rate gNB Next Generation Node B

[0447] GTP GPRS Tunnelling Protocol

[0448] HO Handover

[0449] HO Handover

[0450] IE Information Element

[0451] IETF Internet Engineering Task Force

[0452] KPI Key performance indicator MNO Mobile Network Operator

[0453] NAS Network Access Stratum

[0454] NAS Non-access stratum

[0455] NEF Network Exposure Function

[0456] NR New Radio

[0457] NWDAF Network Data Analytics Function

[0458] PC Packet Core

[0459] PCC Policy and Charging Control

[0460] PCEF Policy and Charging Enforcement Function

[0461] PCF Policy Control Function

[0462] PDR Packet Detection Rule

[0463] PDU Packet Data Unit

[0464] PFCP Packet Flow Control Protocol

[0465] PSA PDU Session Anchor

[0466] QER QoS Enforcement Rule

[0467] QFI QoS Flow ID

[0468] QoS Quality of Service

[0469] RAN Radio Access Network

[0470] RFC Request for Comments

[0471] RTT Round-trip time

[0472] SDAP Service Data Adaptation Protocol

[0473] SDAP Service Data Adaption Protocol

[0474] SM Session Management

[0475] SMF Session Management Function

[0476] SSC Session and Service Continuity

[0477] SUPI Subscription Concealed Identifier

[0478] UDM Unified Data Management

[0479] UE User Equipment

[0480] UL Uplink

[0481] UP User Plane

[0482] UPF User Pl ane F uncti on

[0483] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A Session Management Function, SMF, (100) configured for performing Quality of Service, QoS, Monitoring in a telecommunication network, the SMF (100) comprising processing circuitry (108) configured to: configure at least one of a wireless device (22), a network node (16), and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120) with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions; receive, from at least one of the wireless device (22), network node (16), and UPF PSA (120), measurement data generated based on the instructions; and calculate at least one metric based on the measurement data.

2. The SMF (100) of Claim 1, wherein the measurement data comprises at least one of: packet loss, one-way delay, two-way delay, and jitter.

3. The SMF (100) of any one of Claims 1-2, wherein the at least one metric is calculated on at least one of a per-hop basis and an end-to-end basis.

4. The SMF (100) of any one of Claims 1-3, wherein the SMF is further configured to expose the at least one metric to at least one other entity in the telecommunication network.

5. The SMF (100) of any one of Claims 1-4, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

6. The SMF (100) of any one of Claims 1-5, wherein the instructions corresponding to packet marking comprise at least one of: a target QoS Flow ID; a time block size; coloring and counting instructions indicating that at least one of: the UE is to mark uplink packets with color in an uplink and count downlink packets in a downlink; the UPF PSA is to count in the uplink and color in the downlink;an intermediate is to monitor and relay packet coloring to a next hop; and the intermediate node is to count in the uplink and the downlink.

7. The SMF (100) of any one of Claims 1-6, wherein the measurement data comprises at least one of: a block number; a count of the number of packets in the block; and at least one timestamp, the at least one timestamp being usable by the SMF to calculate at least one of delay, mean-block-delay when a color is used for packet marking, and second-color-delay when the color and at least a second color are used for packet marking.

8. The SMF (100) of any one of Claims 1-7, wherein the instructions corresponding to packet marking indicate to use an explicit block counter, the explicit block counter including a first bit that flips with a first frequency and a second bit that flips with a second frequency half that of the first frequency.

9. A method performed by a Session Management Function, SMF, (100) configured for performing Quality of Service, QoS, Monitoring in a telecommunication network, method comprising: configuring (S158) at least one of a wireless device (22), a network node (16), and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120) with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packet counting instructions; receiving (SI 60), from at least one of the wireless device (22), network node (16), and UPF PSA (120), measurement data generated based on the instructions; and calculating (SI 62) at least one metric based on the measurement data.10 The method of Claim 9, wherein the at least measurement data comprises at least one of: packet loss, one-way delay, two-way delay, and jitter.

11. The method of any one of Claims 9-10, wherein the at least one metric is calculated on at least one of a per-hop basis and an end-to-end basis.

12. The method of any one of Claims 9-11, further comprising exposing the at least one metric to at least one other entity in the telecommunication network.

13. The method of any one of Claims 9-12, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

14. The SMF (100) of any one of Claims 9-13, wherein the instructions corresponding to packet marking comprise at least one of: a target QoS Flow ID; a time block size; coloring and counting instructions indicating that at least one of: the UE is to mark uplink packets with color in an uplink and count downlink packets in a downlink; the UPF PSA is to count in the uplink and color in the downlink; an intermediate is to monitor and relay packet coloring to a next hop; and the intermediate node is to count in the uplink and the downlink.

15. The SMF (100) of any one of Claims 9-14, wherein the measurement data comprises at least one of: a block number; a count of the number of packets in the block; and at least one timestamp, the at least one timestamp being usable by the SMF to calculate at least one of delay, mean-block-delay when a color is used for packet marking, and second-color-delay when the color and at least a second color are used for packet marking.

16. The SMF (100) of any one of Claims 9-15, wherein the instructions corresponding to packet marking indicate to use an explicit block counter, the explicit block counter including a first bit that flips with a first frequency and a second bit that flips with a second frequency half that of the first frequency.

17. A network node (16) configured to communicate with a Session Management Function, SMF, (100), the network node (16) comprising processing circuitry (68) configured to:receive first measurement data; receive, from the SMF (100), instructions corresponding to packet marking, the instructions indicating whether to generate additional measurement data; generate, based on the instructions, the additional measurement data; and transmit the first measurement data and, when generated, the additional measurement data.

18. The network node (16) of Claim 17, wherein the marking and counting information comprises an array of metrics indexed by a block number.

19. The network node (16) of any one of Claims 17-18, wherein the processing circuitry (68) is further configured to, based on whether the instructions correspond to a hop-by-hop monitoring configuration: relay coloring of a packet to a next hop, the coloring corresponding to a fixed-time block to which the packet belongs; and when indicated by the instructions, perform counting in uplink, UL, and downlink, DL.

20. The network node (16) of any one of Claims 17-19, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

21. A method performed by a network node (16) configured to communicate with a Session Management Function, SMF, (100), the method comprising: receiving (SI 66) first measurement data; receiving (SI 64), from the SMF (100), instructions corresponding to packet marking, the instructions indicating whether to generate additional measurement data; generating (S168), based on the instructions, the additional measurement data; and transmitting (SI 69) the first measurement data and, when generated, the additional measurement data.

22. The method of Claim 21, wherein the marking and counting information comprises an array of metrics indexed by a block number.

23. The method of any one of Claims 21-22, further comprising: based on whether the instructions correspond to a hop-by-hop monitoring configuration: relaying coloring of a packet to a next hop, the coloring corresponding to a fixedtime block to which the packet belongs; and when indicated by the instructions, performing counting in uplink, UL, and downlink, DL.

24. The method of any one of Claims 21-23, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

25. A wireless device (22) configured to communicate with a Session Management Function, SMF, (100), the wireless device (22) comprising processing circuitry (84) configured to: receive, from the SMF (100), instructions corresponding to packet marking; perform packet marking of a data packet in uplink, UL, based on the instructions; generate counting information of the data packet in UL and downlink, DL; generate measurement data based on the instructions and at least one of the packet marking and the counting information; and transmit the measurement data to the SMF.

26. The wireless device (22) of Claim 25, wherein the counting information comprises an array of measurement data indexed by a block number.

27. The wireless device (22) of any one of Claims 25-26, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

28. A method performed by a wireless device (22) configured to communicate with a Session Management Function, SMF, (100), the method comprising: receiving (S170), from the SMF (100), instructions corresponding to packet marking; performing (S171) packet marking of a data packet in uplink, UL, based on the instructions; generating (SI 72) counting information of the data packet in UL and downlink, DL;generating (S 173) measurement data based on the instructions and at least one of the packet marking and the counting information; and transmitting (S174) the measurement data to the SMF (100).

29. The method of Claim 28, wherein the counting information comprises an array of metrics indexed by a block number.

30. The method of any one of Claims 28-29, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

31. A User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120) configured to communicate with a Session Management Function, SMF, (100), the User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120) comprising processing circuitry (128) configured to: receive, from the SMF (100), instructions corresponding to packet marking; perform packet marking of a data packet in downlink, DL, based on the instructions; generate counting information of the data packet in uplink, UL, and DL; generate measurement data based on the instructions and at least one of the packet marking and the counting information; and transmit the measurement data to the SMF.

32. The UPF PSA (120) of Claim 31, wherein the marking and counting information comprises an array of metrics indexed by a block number.

33. The UPF PSA (120) of any one of Claims 31-32, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

34. A method performed by a User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120) configured to communicate with a Session Management Function, SMF, (100), the method comprising: receiving (S176), from the SMF (100), instructions corresponding to packet marking; performing (SI 78) packet marking of a data packet in downlink, DL, based on the instructions;generating (SI 80) counting information of the data packet in uplink, UL, and DL; generating (SI 82) measurement data based on the instructions and at least one of the packet marking and the counting information; and transmitting (SI 84) the measurement data to the SMF (100).

35. The method of Claim 34, wherein the marking and counting information comprises an array of metrics indexed by a block number.

36. The method of any one of Claims 34-35, wherein the packet marking is associated with a QoS Flow ID, QFI, value in a user plane.

37. A method for Quality of Service, QoS, Monitoring in a telecommunication network, the network including a Session Management Function, SMF, (100), a wireless device (22), a network node (16), and a User Plane Function Packet Data Unit Session Anchor, UPF PSA, (120), the method comprising: configuring (SI 86), by the SMF (100), each of the wireless device (22), network node (16), and UPF PSA (120) with instructions corresponding to packet marking, the instructions including at least one of packet marking instructions and packing counting instructions; performing (SI 88) packet marking by one of: the wireless device (22) in the uplink, UL; and the UPF PSA (120), in the downlink, DL; performing (S190) counting by the wireless device (22), UPF PSA (120), and, when indicated by the instructions, the network node (16); transmitting (SI 92), by at least one of the wireless device (22), network node (16), and UPF PSA (120), measurement data based on the counting, the measurement data being transmitted to the SMF (100); and calculating (SI 94), by the SMF (100), at least one metric based on the measurement data.

Images