Expanded service quality monitoring

Abstract

A method is described for a first core network node configured to communicate with a second core network node. This method includes receiving a subscription request from the second core network node to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application. The subscription request includes an instruction to receive a QoS monitoring report for QoS flows associated with a default QoS rule if no policy control billing (PCC) rule is identified for the application, or if no PCC rule is found that enables QoS monitoring for the application. This method also includes configuring a third core network node acting as a user plane function (UPF) to include an instruction in the QoS monitoring report indicating that QoS monitoring is performed for QoS flows associated with a default QoS rule.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more particularly to configurations for supporting enhanced Quality of Service (QoS) monitoring.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for the 4th Generation (4G) wireless communication system (also known as Long Term Evolution (LTE)), the 5th Generation (5G) wireless communication system (also known as New Radio (NR)), and the 6th Generation (6G) wireless communication network. Such systems provide, among other features, broadband communication between network nodes such as base stations and mobile wireless devices (WDs) (which may include user equipment (UE)), as well as communication between network nodes and between WDs. The terms WD and UE may be used interchangeably in this disclosure.

[0003] FIG. 1 is a schematic diagram showing an exemplary 5G reference non-roaming architecture defined by 3GPP.

[0004] Some exemplary architectural aspects of 5G include · Network Data Analytics Function (NWDAF) · Application Function (AF) · Unified Data Management (UDM) · Policy Control Function (PCF) · Session Management Function (SMF) · User Plane Function (UPF) including.

[0005] One or more of the above functions may be implemented, for example, in a network node, a core network node, a base station, a core node, a virtual node, a server, a host computer, a cloud node, a cloud server, a data center, or the like.

[0006] NWDAF In some systems, NWDAF represents an operator-managed network analysis logic function. NWDAF is part of some 5GC architectures and uses mechanisms and interfaces designated for 5GC and operational administration maintenance (OAM).

[0007] NWDAF interacts with different entities for various purposes. • Data collection based on event subscriptions, provided by AMF, SMF, PCF, UDM, AF (directly or via Network Exposure Function (NEF)), and OAM. • Retrieving information from a data repository (for example, an integrated data repository (UDR) via a UDM for subscriber relationship information), • Retrieval of information regarding NF (for example, NRF for NF relational information and NSSF for slice relational information), • On-demand provision of analytics to consumers, and • The following two types of data, 〇 Collected data (for example, event public data), 〇 Analysis report Data about this is stored in the analytical data repository function (ADRF).

[0008] AF In some existing systems, AF can interact with the 3GPP core network and allow external parties to use public application programming interfaces (APIs) provided by the network operator.

[0009] UDM UDM includes support for the following features: • Generation of 3GPP authentication and Key Agreement (AKA) authentication certificates. • User identification information handling (for example, storing and managing subscription persistent identifiers (SUPIs) for each subscriber in a 5G system). • Support for decrypting Privacy-Protected Subscription Identifiers (SUCIs). • Access permissions based on subscription data (e.g., roaming restrictions). • WD(UE) Serving NF registration management (for example, storing Serving AMF for WD(UE), storing Serving SMF for WD(UE) Packet Data Unit (PDU) sessions). For example, supporting service / session continuity by maintaining SMF / DNN allocation for ongoing sessions. • Support for sending mobile incoming messages via Short Message Service (MT-SMS). • Lawful interception capabilities (for example, in the case of outbound roaming where UDM is the sole point of contact for lawful interception (LI)). • Subscription management. · SMS management. • 5G virtual network (5G-VN) group management handling. • Support for external parameter provisioning (expected WD(UE) behavior parameters or network configuration parameters). • Disaster roaming support. • Support for controlling time synchronization services based on subscription data.

[0010] To provide these functionalities, a UDM may use subscription data (including authentication data) that can be stored in a UDR, for example, in which case the UDM implements application logic and does not require internal user data storage. Several different UDMs may serve the same user in different transactions.

[0011] PCF In some existing systems, the Policy Control Function (PCF) supports an integrated policy framework to govern network behavior. Specifically, the PCF provides policy and billing control (PCC) rules to the PCEF (Policy and Billing Enforcement Function), i.e., the SMF / UPF that enforces policy and billing decisions according to the provisioned PCC rules.

[0012] The PCF may generate an authorized QoS monitoring policy for service data flows based on QoS monitoring requests received from the AF (as described in 3GPP standards, for example, section 6.1.3.21 of 3GPP TS23.503). The PCF includes the authorized QoS monitoring policy in the PCC rule and provides it to the SMF.

[0013] SMF In some existing systems, the Session Management Function (SMF) supports different functions; for example, the SMF receives PCC rules from the PCF and configures the UPF accordingly.

[0014] The SMF configures the UPF to perform QoS monitoring on QoS flows and to report the monitoring results with parameters determined by the SMF based on authorized QoS monitoring policies received from the PCF and / or local settings.

[0015] UPF In some existing systems, User Plane Functions (UPF) support the handling of user plane traffic, including packet inspection, packet routing and forwarding, traffic usage reporting, and QoS handling.

[0016] The UPF supports event disclosure, including the disclosure of network information, i.e., QoS monitoring information specified in (one or more) 3GPP specifications such as 3GPP TS23.501, section 5.8.2.18, and events specified in (one or more) 3GPP specifications such as section 5.2.26.2 of 3GPP TS23.502 V18.5.0.

[0017] The following problems are identified in some existing systems. · When a consumer (e.g., NWDAF) subscribes to QoS monitoring events for an application, if the PDU session has not installed a PCC rule for that application with a QoS monitoring policy (i.e., QoS monitoring is not enabled for that application), an error is returned. This error means that the subscription has not been created, and thus the NF consumer needs to send a new subscription to monitor the application traffic. ● When a consumer (e.g., NWDAF) infers application traffic sent through a QoS flow related to a default QoS rule, the consumer can initiate a new subscription for that QoS flow. However, ■ Measuring some QoS parameters on that QoS flow may not be important (e.g., the data rate is measured considering all applications sharing the QoS flow). ■ The consumer assumption may not be correct, and the application traffic may not be operating if a PCC rule with QoS requirements but without a QoS monitoring policy binds the application traffic to another QoS flow on that QoS flow. The NWDAF should not subscribe because the measurement will not correspond to the application traffic. ● If the consumer determines not to start a new subscription immediately and to wait, there is no mechanism for the consumer to know when the corresponding PCC rule with the QoS monitoring policy is installed (i.e., when the application traffic is bound to a dedicated QoS flow for which QoS monitoring is enabled). It is unclear how a new subscription is triggered in the consumer. · Further, when a consumer (e.g., NWDAF) indirectly sends an original subscription via the UDM (for a user or a group of users rather than for a specific PDU session) and an error is returned to the UDM, ● If the UDM does not create a subscription and returns the error to the consumer, an error in one PDU session will affect subscriptions to all other PDU sessions of the target user or group of users. ● If the UDM creates a subscription and does not send the error to the consumer, the UDM inherits the responsibility of resending the subscription for a specific PDU session (the error indicates that the subscription was not created by the service producer), and the UDM inherits the problems described above.

SUMMARY OF THE INVENTION

[0018] Some embodiments advantageously provide a method, system, and apparatus for supporting enhanced Quality of Service (QoS) monitoring.

[0019] Some embodiments of the present disclosure may solve one or more of the problems identified above by an existing system, may be based on an extension of an existing mechanism for QoS monitoring, and / or may provide a mechanism, method, apparatus, etc. that enables a mobile network operator (MNO) to optimize network resources, for example, as follows. • The consumer (for example, a core network node with NWDAF, or any other NWDAF that may be implemented on any other core network node) is configured to include information (e.g., instructions, messages, signaling, etc.) corresponding to and / or containing fallback instructions when subscribing to QoS monitoring events for a particular application, for example, if a PDU session does not have installed PCC rules for that application for which QoS monitoring has been enabled. • The provider (i.e., an SMF that may be implemented in a core network node with SMF) may create a subscription and be configured to proceed to the NG-RAN (e.g., a network node in the access network) and / or (e.g., an SMF that may be implemented in a core network node with UPF) when applicable, as in the case of a fallback instruction, which is, for example, ○ Activate QoS monitoring on QoS flows related to default QoS rules, and / or ○ Create a subscription and / or trigger monitoring when a PCC rule enabling QoS monitoring is installed. Includes. In some embodiments, the QoS monitoring report may include an indication of whether QoS monitoring was performed with respect to QoS flows associated with a default QoS rule, which may be an alternative form of QoS monitoring on QoS flows bound to PCC rules for that application with a QoS monitoring policy.

[0020] Some embodiments of the present disclosure provide extensions to QoS monitoring procedures, for example, enabling a consumer (e.g., an NWDAF which may be implemented in a core network node with an NWDAF) to delegate the decision of what to do in case of an error (e.g., activate QoS monitoring for QoS flows related to default QoS rules), and / or enabling the consumer to configure itself to do so, and / or enabling the consumer to decide whether a QoS monitoring report refers to QoS flows for default QoS rules, or QoS flows dedicated to applications triggered by PCC rules that enable QoS monitoring provided by a PCF (e.g., implemented in a core network node with a PCF).

[0021] Embodiments of this disclosure may offer one or more of the following advantages over existing systems: • Some embodiments may enable network operators to optimize network resources in an efficient and rational manner, for example, by: ● Consumer implementations are reasonable and may be more efficient compared to existing systems. ● Consumers (for example, NWDAF which may be implemented on core network nodes with NWDAF) can still control fallbacks (for example, QoS monitoring may be performed with respect to QoS flows related to default QoS rules only when those measurements are relevant to the consumer), but consumers delegate subscription reactivation to SMF (for example, implemented on core network nodes with SMF). ■ In some embodiments, the consumer may be configured to indicate whether QoS monitoring should be enabled with respect to QoS flows associated with the default QoS rule, as a fallback mechanism. ◆ In some embodiments, the QoS monitoring report may include instructions for QoS monitoring as applied to QoS flows related to default QoS rules (for example, to allow the consumer to determine whether fallback occurred). ■ In some embodiments, the consumer may be configured to indicate whether the provider should keep the subscription open (even if, for example, no reports are sent) until the QoS flow is bound to an application that has QoS monitoring enabled and is dedicated to that application. In some embodiments, the MNO can achieve significant system savings, for example, by reducing signaling overhead in QoS monitoring procedures.

[0022] In some embodiments, a system and / or method is provided that enables an NWDAF or other consumer (for example, which may be implemented in a core network node with an NWDAF) to handle QoS monitoring (on app-ids, while QoS enforcement is actually driven by a PCF) in a smooth manner (for example, without blind polling or retries).

[0023] In one embodiment, a method is described in a first core network node configured to communicate with a second core network node. This method includes receiving a subscription request from the second core network node to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application. The subscription request includes an instruction to receive a QoS monitoring report for QoS flows associated with a default QoS rule if no policy control billing (PCC) rule is identified for the application or no PCC rule is found that enables QoS monitoring for the application. This method also includes configuring a third core network node acting as a user plane function (UPF) to include an instruction in the QoS monitoring report indicating that QoS monitoring is performed for QoS flows associated with a default QoS rule.

[0024] In some embodiments, the first core network node is configured as a Session Management Function (SMF) node.

[0025] In some other embodiments, the method further includes determining that for one or more identified PDU sessions, there are no PCC rules enabled for QoS monitoring of the application.

[0026] In some embodiments, the method further includes, in response to a subscription request, sending a response to a second core network node indicating acceptance of the subscription request when there are no active PCC rules with QoS monitoring for the application.

[0027] In some embodiments, configuring a third core network node further includes sending an instruction to the third core network node to instruct the third core network node to add an instruction to the QoS monitoring report that QoS monitoring is performed with respect to QoS flows related to default QoS rules.

[0028] In another embodiment, a first core network node is described that is configured to communicate with a second core network node. The first core network node is configured to receive a subscription request from the second core network node to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application. The subscription request includes an instruction to receive a QoS monitoring report for QoS flows associated with a default QoS rule if no policy control billing (PCC) rule is identified for the application, or if no PCC rule is found that enables QoS monitoring for the application. The first core network node is also configured to configure a third core network node acting as a user plane function (UPF) to include an instruction in the QoS monitoring report indicating that QoS monitoring is performed for QoS flows associated with a default QoS rule.

[0029] In some embodiments, the first core network node is configured as a Session Management Function (SMF) node.

[0030] In some other embodiments, the first core network node is configured to determine that for one or more identified PDU sessions, there are no PCC rules enabled for QoS monitoring of the application.

[0031] In some embodiments, the first core network node is configured to respond to a subscription request by sending a response to the second core network node indicating acceptance of the subscription request when there are no active PCC rules with QoS monitoring for the application.

[0032] In some embodiments, configuring a third core network node further includes sending an instruction to the third core network node to instruct the third core network node to add an instruction to the QoS monitoring report that QoS monitoring is performed with respect to QoS flows related to default QoS rules.

[0033] In one embodiment, a method is described in a second core network node configured to communicate with a first core network node. The method includes determining a subscription request to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application. The subscription request includes instructions indicating that the second core network node has requested to receive QoS monitoring reports for QoS flows associated with a default QoS rule, if no policy control billing (PCC) rule is identified for the application, or if no PCC rule is found that enables QoS monitoring for the application. The method also includes sending the subscription request to the first core network node.

[0034] In some embodiments, the method further includes receiving an acceptance response from a first core network node when there are no active PCC rules with QoS monitoring for the application.

[0035] In some other embodiments, the method further includes receiving a QoS monitoring report from a third core network node acting as a user plane function (UPF), which includes a default instruction indicating that QoS monitoring is performed with respect to QoS flows associated with default QoS rules.

[0036] In some embodiments, the second core network node is configured as a Network Data Analysis Function (NWDAF) node or an Integrated Data Management (UDM) node, and the first core network node is a Session Management Function (SMF).

[0037] In another embodiment, a second core network node is described, configured to communicate with a first core network node. The second core network node is configured to determine a subscription request to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application. The subscription request includes instructions indicating that the second core network node has requested to receive QoS monitoring reports for QoS flows associated with default QoS rules, if no policy control billing (PCC) rules are identified for the application, or if no PCC rules enabling QoS monitoring for the application are found. The second core network node is further configured to send subscription requests to the first core network node.

[0038] In some embodiments, the second core network node is further configured to receive acceptance responses from the first core network node when there are no active PCC rules with QoS monitoring for the application.

[0039] In some other embodiments, the second core network node is further configured to receive QoS monitoring reports from a third core network node acting as a User Plane Function (UPF), which include default instructions indicating that QoS monitoring is performed with respect to QoS flows related to default QoS rules.

[0040] In one embodiment, a computer program is described and, when executed on one or more processors of a core network node, includes instructions that cause one or more processors to perform the methods described in this section.

[0041] When considered in conjunction with the attached drawings, a more complete understanding of these embodiments, as well as their associated advantages and features, will be more readily apparent by referring to the following detailed description. [Brief explanation of the drawing]

[0042] [Figure 1] This is a schematic diagram of an exemplary network architecture showing an exemplary 3GPP communication system. [Figure 2] This is a schematic diagram of an exemplary network architecture illustrating a communication system connected to a host computer via an intermediate network, based on the principles described herein. [Figure 3] This is a block diagram of a host computer communicating with a wireless device via a network node, at least partially over a wireless connection, according to some embodiments of the present disclosure. [Figure 4] This flowchart illustrates an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for running a client application on a wireless device, according to some embodiments of the present disclosure. [Figure 5] This flowchart illustrates an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data in a wireless device, according to some embodiments of the present disclosure. [Figure 6] This flowchart illustrates an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data from a wireless device on a host computer, according to some embodiments of the present disclosure. [Figure 7] This flowchart illustrates an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data on a host computer, according to some embodiments of the present disclosure. [Figure 8]This is a flowchart illustrating an exemplary process in a core network node (for example, a core network node including NWDAF for implementing NWDAF functionality) to support enhanced Quality of Service QoS monitoring according to some embodiments of the present disclosure. [Figure 9] This is a flowchart illustrating an exemplary process in a separate core network node (for example, a core network node containing UPF and / or SMF for implementing UPF and / or SMF functionality) to support enhanced quality of service (QoS) monitoring according to some embodiments of the present disclosure. [Figure 10] This is a flowchart of an exemplary process in a core network node according to some embodiments of the present disclosure. [Figure 11] This is a flowchart illustrating an exemplary process in another core network node according to some embodiments of the present disclosure. [Figure 12] This is a flowchart of an exemplary process in a communications system according to some embodiments of the present disclosure (for example, a direct subscription embodiment). [Figure 13] This is a flowchart of another exemplary process in a communications system according to some embodiments of the present disclosure (for example, an indirect subscription embodiment). [Modes for carrying out the invention]

[0043] Before describing exemplary embodiments in detail, it should be noted that embodiments exist primarily as combinations of device components and processing steps related to supporting enhanced Quality of Service (QoS) monitoring. Accordingly, where appropriate, components are represented in the drawings by conventional symbols, and only their specific details relevant to understanding the embodiments are shown, so as not to obscure this disclosure with details that would be readily apparent to those skilled in the art who are interested in the description herein. Similar numbers refer to similar elements throughout the description.

[0044] As used herein, relational terms such as “first” and “second,” “upper” and “lower” may be used simply to distinguish one entity or element from another, 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 specific embodiments and does not limit the concepts described herein. As used herein, the singular forms “a,” “an” and “the” also include the plural form unless the context otherwise explicitly indicates. Furthermore, as used herein, the terms “comprises,” “comprising,” “includes,” and / or “including” specify the presence of the described feature, complete, step, action, element, and / or component, but do not exclude the presence or addition of one or more other features, complete, step, action, element, component, and / or groups thereof.

[0045] In the embodiments described herein, joining terms such as “in communication with” may be used to indicate electrical or data communication that can be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will understand that multiple components can interact with each other, and that modifications and variations are possible for achieving electrical and data communication.

[0046] In some embodiments described herein, terms such as “coupled” and “connected” may be used herein to indicate a connection, though not necessarily directly, and may include wired and / or wireless connections.

[0047] As used herein, the term “network node” can refer to any type of network node present in a radio network, which may further comprise any of the following: base stations (BS), radio base stations, base transceiver stations (BTS), base station controllers (BSC), radio network controllers (RNC), g-node B (gNB), evolved node B (eNB or e-node B), node B, MSR radio nodes such as multi-standard radio (MSR) BS, multi-cell / multicast coordinating entities (MCE), radio access backhaul integrated transmission (IAB) nodes, relay nodes, donor node control relays, radio access points (AP), transmit points, transmit nodes, remote radio units (RRU), remote radio heads (RRH), core network nodes (e.g., mobile management entities (MME), self-organizing network (SON) nodes, coordinating nodes, positioning nodes, MDT nodes, etc.), external nodes (e.g., third-party nodes, nodes outside the current network), nodes in distributed antenna systems (DAS), spectrum access system (SAS) nodes, element management systems (EMS), etc. Network nodes may also include test equipment. The term “wireless node” as used herein may also be used to refer to wireless devices (WDs) or wireless network nodes, etc.

[0048] In some embodiments, the term “core network node” is used, which may be any type of network node, core node, virtual node, centralized unit (CU), cloud node, cloud server, host computer, etc., that provides one or more core network functions, or other 3GPP network functions such as PCF, AMF, etc.

[0049] In some embodiments, the non-limiting terms "wireless device (WD)" and "user equipment (UE)" are used interchangeably. A WD as used herein can be any type of wireless device capable of communicating with a network node or another WD via wireless signals, such as a wireless device (WD). A WD can also be a wireless communication device, a target device, a D2D (device to device) WD, a machine-type WD or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device.

[0050] In some embodiments, the general term “wireless network node” is used. A wireless network node can be any type of wireless network node, which may comprise any of the following: base stations, wireless base stations, base station transceiver stations, base station controllers, network controllers, RNCs, evolved node B (eNB), node B, gNB, multicell / multicast cooperative entity (MCE), IAB node, relay node, access point, wireless access point, remote radio unit (RRU), or remote radio head (RRH).

[0051] This disclosure may use terminology from a specific radio system, such as 3GPP LTE and / or New Radio (NR), but it should be noted that this should not be considered to limit the scope of this disclosure to the aforementioned systems only. However, other radio systems, including Wideband Code Division Multiple Access (WCDMA), Global Interoperability for Microwave Access (WiMAX), Ultra Mobile Broadband (UMB), and GSM (Global System for Mobile Communications), may also benefit from leveraging the ideas covered within this disclosure.

[0052] As used herein, the term “consumer” may refer to any entity, device, and / or network function that uses resources in a communications system, such as a core network node implementing network functions in a 3GPP 5G NR system. In some embodiments herein, an NWDAF or UDM is used as an example of a consumer, but embodiments of this disclosure are not limited to NWDAF-type or UDM-type consumers, and other types of network functions or processes or core network nodes or network nodes may be considered “consumers” as used herein.

[0053] Furthermore, the term “provider” as used herein may refer to any entity, device, and / or network function that uses resources in a communication system, such as a core network node that implements network functions in a 3GPP 5G NR system. In some embodiments herein, an SMF is used as an example of a producer, but embodiments of this disclosure are not limited to SMF-type consumers, and other types of network functions or processes or core network nodes or network nodes may be considered “producers” as used herein.

[0054] It should be further noted that the functions described herein as being performed by wireless devices or network nodes may be distributed across multiple wireless devices and / or network nodes. In other words, the functions of network nodes and wireless devices described herein are not limited to being performed by a single physical device, but can actually be distributed across several physical devices.

[0055] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as they would ordinarily be understood by those skilled in the art to which this disclosure belongs. Terms used herein should be interpreted as having the meanings of those terms in the context of this specification and the related art, and not in an ideal or overly formal sense unless expressly provided herein.

[0056] Some embodiments provide configurations to support enhanced Quality of Service (QoS) monitoring.

[0057] Next, referring to the drawings, similar elements are referred to by similar reference numbers, and Figure 2 shows a schematic diagram of a communication system 10, such as a 3GPP type cellular network capable of supporting standards such as LTE and / or NR (5G), comprising an access network 12 such as a wireless access network and a core network 14, according to one embodiment. The core network 14 comprises one or more core network nodes 15 that can provide one or more core network functions (collectively referred to as core network nodes 15).

[0058] The access network 12 comprises multiple network nodes 16a, 16b, 16c (collectively referred to 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 (collectively referred to as coverage area 18).

[0059] Each network node 16a, 16b, and 16c is connectable to the core network 14 (and / or core network node 15) via a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to the corresponding network node 16a or to be paged by the corresponding network node 16a. A second WD 22b in coverage area 18b is connectable wirelessly to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless device 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only one WD is in a coverage area, or where only one WD is connected to the corresponding network node 16. For convenience, only a single core network node 15, two WDs 22, and three network nodes 16 are shown, but it should be noted that the communication system may include many more WDs 22 and network nodes 16.

[0060] Furthermore, it is conceivable that WD22 may be configured to communicate simultaneously with two or more network nodes 16 and two or more types of network nodes 16, as well as / or separately with them. For example, WD22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, WD22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0061] 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 implementation server, a distributed server, or as a processing resource in a server farm. The host computer 24 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. 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 a public network, a private network, or a hosted network, or a combination of two or more of these. The intermediate network 30 may be a backbone network or the internet, if any. In some embodiments, the intermediate network 30 may comprise two or more subnets (not shown).

[0062] In some embodiments, the host computer 24 may provide one or more core network node 15 functions.

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

[0064] The core network node 15 may be configured to include a PCF 31, which is set up to support enhanced quality of service (QoS) monitoring, as described herein. For example, in some embodiments, the core network node 15 is a PCF 31 or a PCF node 31.

[0065] The core network node 15 may be configured to include a UPF32, which is set up to support enhanced quality of service (QoS) monitoring, as described herein. For example, in some embodiments, the core network node 15 is a UPF32 or a UPF node 32.

[0066] The core network node 15 may be configured to include an SMF33 configured to support enhanced quality of service (QoS) monitoring, as described herein. For example, in some embodiments, the core network node 15 is an SMF33 or an SMF node 33.

[0067] The core network node 15 may be configured to include a UDM 34 configured to support enhanced quality of service (QoS) monitoring, as described herein. For example, in some embodiments, the core network node 15 is a UDM 34 or a UDM node 34.

[0068] The core network node 15 may be configured to include an NWDAF 35 configured to support enhanced quality of service (QoS) monitoring, as described herein. For example, in some embodiments, the core network node 15 is an NWDAF 35 or an NWDAF node 35.

[0069] The core network node 15 may be configured to include a core network (CN) management unit 36 ​​configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, such as core network node functions which may include one or more functions from among PCF31, UPF32, SMF33, UDM34, and NWDAF35.

[0070] It should be understood that one or more of the functions 31-35 (alternatively referred to as "units") may reside in a single core network node 15, or they may be distributed among one or more core network nodes 15, (one or more) host computers 24, cloud servers, data centers, etc.

[0071] Next, an exemplary implementation of the WD22, core network node 15, network node 16, and host computer 24 described in the previous paragraph, according to one embodiment, will be described with reference to Figure 3. In the communication system 10, the host computer 24 includes hardware (HW) 38, including a communication interface 40 configured to set up and maintain wired or wireless connections to the interfaces of different communication devices of the communication system 10. The host computer 24 further includes a processing circuit 42 which may have memory and / or processing capabilities. The processing circuit 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor and memory such as a central processing unit, the processing circuit 42 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 44 may be configured to access memory 46 (for example, to write to memory 46 and / or read from memory 46), and memory 46 may include any kind of volatile and / or non-volatile memory, such as 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).

[0072] The processing circuit 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 carried out, for example, by the host computer 24. The processor 44 corresponds to one or more processors 44 for carrying out the host computer 24 functions described herein. The host computer 24 includes memory 46 configured to store data, programmatic software code, and / or other information described herein. In some embodiments, the software 48 and / or host application 50 may include instructions that, when executed by the processor 44 and / or processing circuit 42, cause the processor 44 and / or processing circuit 42 to carry out the processes described herein with respect to the host computer 24. The instructions may be software related to the host computer 24.

[0073] Software 48 may be executable by processing circuit 42. Software 48 includes a host application 50. The host application 50 may be able to operate to provide services to remote users, such as a WD22 connected via an OTT connection 52 that terminates at the host computer 24. When providing services to remote users, the host application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information as described herein as implementing the functions described. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, and control the core network node 15, network node 16 and / or wireless device 22, transmit to the core network node 15, network node 16 and / or wireless device 22, and / or receive from the core network node 15, network node 16 and / or wireless device 22. The processing circuitry 42 of the host computer 24 may include a cloud configuration unit 54 configured to enable the service provider to observe / monitor / control the core network node 15, network node 16 and / or wireless device 22, to transmit to the core network node 15, network node 16 and / or wireless device 22, to receive from the core network node 15, network node 16 and / or wireless device 22, and so on. For example, in a context supporting enhanced quality of service (QoS) monitoring, as described herein, the cloud configuration unit 54 may be configured to perform and / or support one or more functions of any one or more of the following: PCF 31, UPF 32, SMF 33, UDM 34, and NWDAF 35.

[0074] The communication system 10 further includes a network node 16 provided within the communication system 10, the network node 16 including hardware 58 that enables the network node 16 to communicate with the host computer 24 and WD22. The hardware 58 may include a communication interface 60 for setting up and maintaining wired or wireless connections with the interfaces of different communication devices of the communication system 10, and a wireless interface 62 for setting up and maintaining at least a wireless connection 64 with WD22 located in the coverage area 18 served by the network node 16. The wireless interface 62 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include them. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24 and / or (one or more) core network nodes 15. The connection 66 may be direct, or the connection 66 may pass through the core network 14 of the communication system 10 and / or one or more intermediate networks 30 outside the communication system 10.

[0075] In the embodiments shown, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. More specifically, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 68 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 70 may be configured to access the memory 72 (e.g., write to and / or read from the memory 72), and the memory 72 may include any kind of volatile and / or non-volatile memory, for example, 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).

[0076] Therefore, the network node 16 further has software 74 stored either internally in memory 72 or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by processing circuit 68. Processing circuit 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 carried out by the network node 16, for example. Processor 70 corresponds to one or more processors 70 for carrying out the network node 16 functions described herein. 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 circuit 68, cause the processor 70 and / or processing circuit 68 to carry out the processes described herein with respect to the network node 16.

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

[0078] The WD22 hardware 80 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and memory 88. More specifically, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 86 may be configured to access memory 88 (e.g., write to memory 88 and / or read from memory 88), and memory 88 may include any kind of volatile and / or non-volatile memory, such as 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).

[0079] Therefore, the WD22 may further include software 90, which may be stored, for example, in memory 88 in the WD22 or in external memory accessible by the WD22 (e.g., a database, storage array, network storage device, etc.). The software 90 may be executable by processing circuit 84. The software 90 may include a client application 91. The client application 91 may operate to provide services to human or non-human users via the WD22 with the support of a host computer 24. On the host computer 24, a running host application 50 may communicate with the running client application 91 via an OTT connection 52 that terminates in the WD22 and the host computer 24. When providing services to a user, the client application 91 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 91 may interact with the user to generate the user data that the client application 91 provides.

[0080] The processing circuit 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 carried out, for example, by the WD22. The processor 86 corresponds to one or more processors 86 for carrying out the WD22 functions described herein. The WD22 includes memory 88 configured to store data, programmatic software code, and / or other information described herein. In some embodiments, the software 90 and / or client application 91 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to carry out the processes described herein with respect to the WD22.

[0081] The communication system 10 further includes a core network node 15 provided within the communication system 10, the core network node 15 including hardware 92 that enables the core network node 15 to communicate with the host computer 24, the network node 16, and the WD 22. The hardware 92 may include a communication interface 93 for setting up and maintaining wired or wireless connections to the interfaces of different communication devices of the communication system 10. The communication interface 93 may be configured to facilitate connections 66 to the host computer 24, the network node 16, the WD 22, and / or (one or more) other core network nodes 15. The connections 66 may be direct, or the connections 66 may pass through the access network 12 and / or core network 14 of the communication system 10, and / or one or more intermediate networks 30 outside the communication system 10.

[0082] In the embodiments shown, the hardware 92 of the core network node 15 further includes a processing circuit 94. The processing circuit 94 may include a processor 96 and a memory 98. More specifically, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 94 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 96 may be configured to access the memory 98 (e.g., write to and / or read from the memory 98), and the memory 98 may include any kind of volatile and / or non-volatile memory, for example, 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).

[0083] Therefore, the core network node 15 further has software 100 stored, for example, internally in memory 98 or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by the core network node 15 via an external connection. The software 100 may be executable by processing circuit 94. Processing circuit 94 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 carried out, for example, by the core network node 15. Processor 96 corresponds to one or more processors 96 for carrying out the core network node 15 functions described herein. Memory 98 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 100 may include instructions that, when executed by the processor 96 and / or processing circuit 94, cause the processor 96 and / or processing circuit 94 to carry out the processes described herein with respect to the core network node 15. Furthermore, the processor 96 may be configured to include a CN management unit 36 ​​configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, such as core network node functions which may include one or more functions among PCF31, UPF32, SMF33, UDM34, and NWDAF35.

[0084] In Figure 3, the core network node 15 is shown to include a PCF 31, a UPF 32, an SMF 33, a UDM 34, an NWDAF 35, and a CN management unit 36, but one or more of these units and / or nodes and / or functions may be configured in one or more separate core network nodes 15.

[0085] In some embodiments, the internal workings of the core network node 15, network node 16, WD22, and host computer 24 may be as shown in Figure 3, and separately, the surrounding network topology may be as shown in Figure 2.

[0086] In Figure 3, the OTT connection 52 is depicted abstractly to illustrate communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to the intermediary devices and the precise routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the WD22, the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may also make decisions to dynamically change the routing (for example, based on network load balancing considerations or reconfiguration).

[0087] The wireless connection 64 between WD22 and network node 16 follows the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to WD22 using an OTT connection 52 in which the wireless connection 64 may form the final segment. More precisely, some teachings of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed file size limits, better responsiveness, and extended battery life.

[0088] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors, which are improved in one or more embodiments. Further optional network functions may be provided for reconfiguring the OTT connection 52 between the host computer 24 and the WD22 in response to variations in the measurement results. The measurement procedure and / or network function 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 WD22, or both. In embodiments, a sensor (not shown) may be deployed in or in relation to a communication device through which the OTT connection 52 passes, and the sensor may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above, or values ​​of other physical quantities through which the software 48, 90 can calculate or estimate the monitored quantities. Reconfiguring the OTT connection 52 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration may not need to affect the network node 16, and may be unknown to or imperceptible to the network node 16. Several such procedures and functions are known and practiced in the art. In some embodiments, the measurement may involve proprietary WD signaling that facilitates the measurement of the host computer 24, such as throughput, propagation time, and latency. In some embodiments, the measurement may be implemented such that software 48, 90 monitors propagation time, errors, etc., and software 48, 90 uses an OTT connection 52 to send messages, in particular empty or "dummy" messages.

[0089] Accordingly, in some embodiments, the host computer 24 includes a processing circuit 42 configured to provide user data and a communication interface 40 configured to forward the user data to the cellular network for transmission to the WD22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to perform the functions and / or methods described herein for preparing / starting / maintaining / supporting / terminating transmissions to the WD22 and / or preparing / terminating / maintaining / supporting / terminating transmissions from the WD22, and / or the processing circuit 68 of the network node 16 is configured to perform them.

[0090] In some embodiments, the host computer 24 includes a processing circuit 42 and a communication interface 40, the communication interface 40 being configured to receive user data originating from transmissions from the WD 22 to the network node 16. In some embodiments, the WD 22 includes a radio interface 82 and / or processing circuit 84 configured to perform the functions and / or methods described herein for preparing / starting / maintaining / supporting / terminating transmissions to the network node 16 and / or preparing / terminating / maintaining / supporting / terminating transmissions from the network node 16 and / or the core network node 15, and / or to perform them.

[0091] Figures 2 and 3 show various "functions" (also called "units") within each processor, such as PCF31, UPF32, SMF33, UDM34, and NWDAF35. These units can be implemented such that parts of the unit are stored in corresponding memory within the processing circuit. In other words, units can be implemented in hardware or as a combination of hardware and software within the processing circuit.

[0092] Figure 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figures 2 and 3, according to one embodiment. The communication system may include a host computer 24, a core network node 15, a network node 16, and a WD 22, which may be described with reference to Figure 3. In a first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides user data by running a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission to carry the user data to the WD 22 (block S104). In an optional third step, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, WD22 executes a client application, such as a client application 91, which is related to the host application 50 executed by the host computer 24 (block S108).

[0093] Figure 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of Figure 2, according to one embodiment. The communication system may include a host computer 24, a core network node 15, a network node 16, and a WD22, which may be described with reference to Figures 2 and 3. In a first step of the method, the host computer 24 provides user data (block S110). In an optional substep (not shown), the host computer 24 provides user data by running a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission to carry the user data to the WD22 (block S112). The transmission may proceed via the network node 16, as taught in the embodiments described throughout this disclosure. In an optional third step, the WD22 receives the user data carried in the transmission (block S114).

[0094] Figure 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 2, according to one embodiment. The communication system may include a host computer 24, a core network node 15, a network node 16, and a WD 22, which may be described with reference to Figures 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (block S116). In an optional substep of the first step, the WD 22 runs a client application 91 that provides user data in response to the received input data provided by the host computer 24 (block S118). In an optional second step, either additionally or alternatively, the WD 22 provides user data (block S120). In an optional substep of the second step, the WD provides user data by running a client application, such as the client application 91 (block S122). When providing user data, the executed client application 91 may further consider user input received from the user. Regardless of the specific format in which the user data is provided, WD22 may initiate transmission of the user data to the host computer 24 in an optional third substep (block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from WD22 in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

[0095] Figure 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 2, according to one embodiment. The communication system may include a host computer 24, a core network node 15, a network node 16, and a WD 22, which may be described with reference to Figures 2 and 3. In an optional first step of the method, the network node 16 receives user data from the WD 22 (block S128), in accordance with the teachings of the embodiments described throughout this disclosure. In an optional second step, the network node 16 initiates a 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 S132).

[0096] Figure 8 is a flowchart of an exemplary process in a first core network node 15 (for example, a core network node including an NWDAF 35 for implementing NWDAF functionality) to support extended QoS monitoring. One or more blocks described herein may be implemented by one or more elements of the first core network node 15, such as by one or more of the processing circuits 94 (including PCF 31, UPF 32, SMF 33, UDM 34, and / or NWDAF 35), the processor 96, and / or the communication interfaces 93. The first core network node 15 is configured to receive or determine session management function (SMF) instance identifiers associated with the wireless device 22 and the application (block S134). The first core network node 15 is configured to determine a subscription request to subscribe to quality of service (QoS) monitoring events for an SMF instance (block S136), where the subscription request includes a fallback instruction indicating that if no policy-controlled billing (PCC) rule is found that enables QoS monitoring for the application, the SMF instance should perform QoS monitoring with respect to QoS flows associated with default QoS rules. The first core network node 15 is configured to send the subscription request to the second core network node 15 (block S138).

[0097] In some embodiments, the first core network node 15 is further configured to receive QoS monitoring reports from a third core network node 15 (for example, acting as an Up Packet Forwarding (UPF) function node), where reports including default instructions indicate that QoS monitoring is performed with respect to QoS flows associated with default QoS rules.

[0098] In some embodiments, the first core network node 15 functions as a Network Data Analysis Function (NWDAF) node. In some embodiments, the second core network node 15 may function as a Session Management Function (SMF) node. In some embodiments, the third core network node 15 may function as a UPF node. In some embodiments, the first, second, and / or third core network nodes 15 may be implemented in the same node, device, server, etc., or in two or more different and / or distributed nodes, devices, servers, etc.

[0099] Figure 9 is a flowchart of an exemplary process in a first core network node 15 (for example, a core network node including an SMF 33 for implementing SMF functionality) to support extended QoS monitoring. One or more blocks described herein may be implemented by one or more elements of the first core network node 15, such as by one or more of the processing circuits 94 (including PCF 31, UPF 32, SMF 33, UDM 34, and / or NWDAF 35), processor 96, and / or communication interfaces 93. The first core network node 15 is configured to receive a subscription request from a second core network node 15 to subscribe to quality of service (QoS) monitoring events for an SMF instance (block S140), where the subscription request includes a fallback instruction requesting that QoS monitoring be performed with respect to QoS flows related to a default QoS rule if no policy control billing (PCC) rule is found that enables QoS monitoring for an application related to a wireless device 22. The first core network node 15 is configured to establish QoS monitoring operation based on a fallback instruction when there is no PCC rule that enables QoS monitoring for the application (block S142).

[0100] In some embodiments, the second core network node 15 may function as a session management function (SMF) node.

[0101] In some embodiments, the first core network node 15 is further configured to send an acknowledgment response to the first core network node 15 when there are no active PCC rules with QoS monitoring for the application.

[0102] In some embodiments, the first core network node 15 is further configured to perform QoS monitoring based on fallback instructions for QoS flows related to default quality of service (QoS) rules, and to configure the third core network node 15 to act as an uppacket forwarding (UPF) function to include default instructions in the QoS monitoring report, where default instructions indicate that QoS monitoring is performed for QoS flows related to default QoS rules.

[0103] In some embodiments, the first core network node 15 functions as a Network Data Analysis Function (NWDAF) node. In some embodiments, the second core network node 15 may function as a Session Management Function (SMF) node. In some embodiments, the third core network node 15 may function as a UPF node. In some embodiments, the first, second, and / or third core network nodes 15 may be implemented in the same node, device, server, etc., or in two or more different and / or distributed nodes, devices, servers, etc.

[0104] Figure 10 is a flowchart of an exemplary process in a first core network node 15 (for example, a core network node including an SMF 33 for implementing SMF functionality) to support extended QoS monitoring. One or more blocks described herein may be implemented by one or more elements of the first core network node 15, such as by one or more of the processing circuits 94 (including the SMF 33 and / or CN management unit 36), the processor 96, and / or the communication interface 93. The first core network node 15 is configured to receive a subscription request from the second core network node 15 to subscribe to QoS monitoring events for application-bound quality of service (QoS) flows (block S144). The subscription request includes an instruction to receive QoS monitoring reports for QoS flows associated with default QoS rules if no policy control billing (PCC) rules are identified for the application or no PCC rules that enable QoS monitoring for the application are found. The first core network node 15 is further configured to configure the third core network node 15, which acts as a user plane function (UPF) 32, to include in the QoS monitoring report an instruction indicating that QoS monitoring is performed with respect to QoS flows related to default QoS rules (block S146).

[0105] In some embodiments, the first core network node is configured as a Session Management Function (SMF) 33 node.

[0106] In some other embodiments, the method further includes determining that for one or more identified PDU sessions, there are no PCC rules enabled for QoS monitoring of the application.

[0107] In some embodiments, the method further includes, in response to a subscription request, sending a response to a second core network node indicating acceptance of the subscription request when there are no active PCC rules with QoS monitoring for the application.

[0108] In some embodiments, configuring the third core network node 15 further includes sending an instruction to the third core network node 15 to instruct the third core network node 15 to add an instruction to the QoS monitoring report that QoS monitoring is performed with respect to QoS flows related to the default QoS rules.

[0109] Figure 11 is a flowchart of an exemplary process in a second core network node 15 (for example, a core network node including an NWDAF 35 for implementing NWDAF functionality, or a UDM 34 for implementing UDM functionality) to support extended QoS monitoring. One or more blocks described herein may be implemented by one or more elements of the second core network node 15, such as by one or more of the processing circuitry 94, processor 96, and / or communication interface 93 (including UDM 34, and / or NWDAF 35, and / or CN management unit 36, etc.). The second core network node 15 is configured to determine a subscription request to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application (block S148). The subscription request includes instructions indicating that the second core network node 15 has requested to receive QoS monitoring reports for QoS flows associated with a default QoS rule if no policy control billing (PCC) rule is identified for the application, or if no PCC rule is found that enables QoS monitoring for the application. The second core network node 15 is configured to send a subscription request to the first core network node 15 (block S150).

[0110] In some embodiments, the method further includes receiving an acceptance response from the first core network node 15 when there is no active PCC rule with QoS monitoring for the application.

[0111] In some other embodiments, the method further includes receiving a QoS monitoring report from a third core network node 15 acting as a user plane function (UPF) 32, which includes a default instruction indicating that QoS monitoring is performed with respect to QoS flows associated with default QoS rules.

[0112] In some embodiments, the second core network node is configured as a Network Data Analysis Function (NWDAF) 35 node or an Integrated Data Management (UDM) 34 node, and the first core network node is a Session Management Function (SMF) 33.

[0113] Having described the schematic process flow of the configuration of this disclosure and provided examples of hardware and software configurations for implementing the processes and functions of this disclosure, the following sections provide configuration details and examples for supporting enhanced QoS monitoring. In one or more embodiments, the term UE is used and may refer to WD22. For example, a UE identifier (UE-ID) may refer to a WD22 identifier.

[0114] In one or more embodiments, the term “instruction” may refer to information, data, signaling, resources, one or more bits, etc., that may be used to indicate a state, a request, or any other information. Examples of instructions may include, but are not limited to, instructions such as a fallback instruction or a default indication.

[0115] In one or more embodiments, the default instruction may refer to an instruction for an action, such as an action being enforced and / or monitoring being performed.

[0116] In some embodiments, the term "fallback instruction" (or "fallback command") may refer to an instruction and / or request that QoS monitoring be performed with respect to a QoS flow. A QoS flow may, for example, be related to a default QoS rule if no policy-controlled billing (PCC) rule is found that enables QoS monitoring for an application associated with WD22.

[0117] In some embodiments, the term default value is used and may refer to a default QoS rule or any other default value. In one or more embodiments, a default QoS rule refers to any value as described in the following sections.

[0118] QoS Parameters - Default Values For each PDU session setup, the SMF33 retrieves from the UDM34 the subscribed session-AMBR (Aggregate Maximum Bitrate) value, as well as the subscribed default values ​​for the 5G QoS identifier (5QI) and allocation and retention priority (ARP), and optionally the 5QI priority level. The subscribed default 5QI value may be a non-GBR 5QI from a standardized value range.

[0119] 5QI priority levels may be added to subscription information to achieve a standardized or pre-configured 5QI priority level override in scenarios where, for example, dynamic PCCs are not deployed or PCFs are unavailable or unreachable.

[0120] SMF may change the subscribed values ​​for default 5QI and ARP, and the 5QI priority level, if received, based on interaction with PCF, or, if dynamic PCC is not deployed, based on local settings, in order to set QoS parameters for QoS flows associated with default QoS rules.

[0121] For one or more QoS flows of a PDU session other than the QoS flow associated with the default QoS rule, SMF may set the ARP priority level, ARP preemption capability, and ARP preemption vulnerability to their respective values ​​in the one or more PCC rules bound to that QoS flow. If dynamic PCC is not deployed, SMF may set the ARP priority level, ARP preemption capability, and ARP preemption vulnerability based on the local configuration.

[0122] Local settings in SMF33 can, for example, utilize subscribed values ​​for ARP priority levels and apply locally configured values ​​for ARP preemption capability and ARP preemption vulnerability.

[0123] If dynamic PCC is not deployed, SMF may have a data network name (DNN) based configuration to enable the establishment of guaranteed bitrate (GBR) QoS flows as QoS flows associated with default QoS rules. This configuration includes standardized GBR 5QI as well as guaranteed flow bitrate (GFBR) and maximum flow bitrate (MFBR) for uplink (UL) and downlink (DL).

[0124] Interacting with the Extended Packet System (EPS) is not possible for PDU sessions involving GBR QoS flows as QoS flows related to default QoS rules.

[0125] SMF may change the subscribed session-AMBR value (for UL and / or DL) based on interaction with PCF, or, if dynamic PCC is not deployed, based on local settings, in order to set the session-AMBR value for PDU sessions.

[0126] Publication of events from UPF for UPF data collection In some embodiments, a subscription to QoS monitoring events can target application-bound QoS flows by including an application identifier. In this case, in the subscription request and / or when a PCC rule changes, SMF33 may identify an active PCC rule that includes a DataCollection_ApplicationIdentifier that matches that application identifier. SMF33 enables this consumer (e.g., NWDAF) to receive QoS monitoring reports enabled by that PCC rule. The consumer may indicate that if there is no measurement available for the application identifier (i.e., no PCC rule is identified), the consumer can receive QoS flow performance information for QoS flows associated with a default QoS rule. In this case, SMF33 may instruct UPF to perform QoS monitoring for QoS flows associated with a default QoS rule and include instructions for the QoS flows associated with the default QoS rule. UPF32 may then include instructions for the QoS flows associated with the default QoS rule in the Nupf_EventExposure_Notify service operation when sending the report. In some cases, SMF33 may accept the request and indicate in its response that reporting may be activated when measurement is made possible by the PCC rules, or SMF33 may reject the subscription request for that application identifier.

[0127] One or more embodiments provide direct / indirect subscriptions to providers, such as a core network node 15 configured as or acting as an SMF33.

[0128] Figure 12 is an exemplary sequence diagram illustrating one exemplary embodiment of a direct subscription to SMF33 when the QoS monitoring event consumer is NWDAF35. The exemplary steps are described in detail below.

[0129] Step S200) Before subscribing to QoS monitoring events, NWDAF35 is configured to request a list of SMF33 instances that serve (one or more) PDU sessions for target WD22 from UDM34. To do this, NWDAF35 may be configured to send a request message (for example, a Nudm_UEContextMgt_Get request message) to UDM34 that includes the following parameters: • UE-ID (SUPI) (i.e., WD22 identifier). • smf-registration (to request SMF registration for UE-ID). Optional: Data network name (DNN), Serving network slice selection support information (S-NSSAI).

[0130] Step S202) UDM34 determines SMF registration for UE-ID (SUPI) using the matching filters described above (e.g., DNN, S-NSSAI).

[0131] Step S204) UDM34 responds to the message in step S200 by sending a response message containing a list of SMF instances registered for the UE-ID (SUPI) (smfRegistrationInfo(List)).

[0132] In some embodiments, NWDAF35 may be configured to target a group of users (e.g., WD22), and UDM34 may be configured to return a list of SMF instances for all WD identifiers (e.g., UE-ID) in the group.

[0133] Step S206) Based on the list of SMF instances retrieved in step S204 above, NWDAF35 may be configured to subscribe to (one or more) QoS monitoring events by triggering a message containing one or more of the following parameters (e.g., a subscription request message, an Nsmf_EE_Subscribe request message, etc.): • WD identifier (e.g., UE-ID, SUPI, or PDU session ID). • Event = QoS Monitoring. • SubsDetail(App-Id) as a subscription detail; in this case, for example, NWDAF35 might request to monitor QoS for a particular application (App-Id). • FallBackInstruction. This could correspond to an instruction that instructs SMF33 to fall back if a PCC rule is not found for an application identifier (e.g., App-Id) for which QoS monitoring is enabled, or if one exists. In this exemplary procedure, the fallback corresponds to performing QoS monitoring for QoS flows related to the default QoS rule.

[0134] Step S208) SMF33 is configured to identify the targeted PDU session.

[0135] Step S210) For the above PDU session, SMF33 is configured to check whether QoS monitoring is enabled as requested (i.e., for the PCC rule for the target App-Id). In this illustrative sequence diagram, SMF33 determines that there is no active QoS monitoring policy in the PCC rule (if any) for the application identifier (e.g., App-Id).

[0136] Step S212) Based on the FallBackInstruction received in step S206 above, SMF33 sends a response message in response to the request message in step S206, with a successful response (accepting the request). This may be an alternative to the procedure in which SMF33 rejects a request when there is no active PCC rule with a QoS monitoring policy for the application identifier (e.g., App-Id).

[0137] Step S214) Based on the FallBackInstruction received in step S206 above, SMF33 may enable QoS monitoring with respect to the QoS flow associated with the default QoS rule.

[0138] In some embodiments, NWDAF35 may be configured to instruct SMF33 to keep the subscription created (even if no reports are sent) until the QoS flow is bound to an application for which QoS monitoring is enabled and becomes dedicated to that application. In this case, SMF33 may be configured to create the subscription, and the procedure continues from step S218.

[0139] In instructions to UPF32, SMF33 may be configured to provide information that UPF32 needs to add to its report (e.g., "DefaultIndication") to indicate that a fallback action is being enforced and that QoS monitoring is being performed with respect to QoS flows related to the default QoS rules.

[0140] Step S216) UPF32 reports QoS monitoring to the consumer (e.g., NWDAF35) by triggering a notification message (e.g., a Nupf_EE_Notify message) that includes one or more of the following pieces of information: • QoS monitoring reports, and / or • DefaultIndication indicates that this report refers to QoS flows related to default QoS rules.

[0141] Steps S218 and S220) Policy association updates may occur, in which case QoS monitoring may be enabled for PCC rules regarding application identifiers (e.g., App-Id), and in which case the PFCP session may be updated accordingly, etc. SMF33 may not need to provide information for UPF32 to include in its report.

[0142] Step S222) UPF32 may be configured to report QoS monitoring to a consumer (e.g., NWDAF35) by triggering a notification message (e.g., a Nupf_EE_Notify message) containing the following information: · QoS monitoring report.

[0143] This report does not include the DefaultIndication (which may have been included in the previous report in step S216), which may be because this report refers to the QoS flow for the application identifier (e.g., App-Id) and does not refer to the QoS flow related to the default QoS rule.

[0144] Indirect subscription Figure 13 is a sequence diagram showing another exemplary embodiment of an indirect subscription to SMF33 via UDM34 when the QoS monitoring event consumer is, for example, NWDAF35. The steps are detailed below.

[0145] Step S300) A consumer (e.g., NWDAF35) subscribes to QoS monitoring events (e.g., indirectly via UDM34) by triggering a request message (e.g., Nudm_EE_Subscribe request message) that includes one or more of the following parameters: • WD identifier (e.g., UE-ID, SUPI, etc.). • Event = QoS Monitoring. • SubsDetail(App-Id) as a subscription detail; in this case, NWDAF35 may be configured to request QoS monitoring for a certain application (for example, one with a corresponding App-Id). • FallBackInstruction. This may correspond to an instruction that, when present (for example, if there are no PCC rules, or if PCC rules with QoS monitoring are not enabled), instructs the SMF33 to fall back to performing QoS monitoring with respect to QoS flows associated with the default QoS rules. • Expiration time.

[0146] Step S302) UDM34 may be configured to allow subscriptions and remembers these subscriptions for the requested WD identifier (e.g., UE-ID, SUPI, etc.).

[0147] Step S304) UDM34 may be configured to determine whether one or more SMF33 instances are registered with UDM34 for a WD identifier (e.g., UE-ID, SUPI, etc.).

[0148] Step S306) For each SMF instance in step S304 above, UDM34 may be configured to send subscriptions to QoS monitoring events on behalf of NWDAF35 by triggering a request message (e.g., a subscription request message, an Nsmf_EE_Subscribe request message) that includes one or more of the following parameters: • WD identifier (e.g., UE-ID, SUPI, etc.) • Event = QoS Monitoring. • SubsDetail(App-Id) as a subscription detail; in this case, NWDAF35 may be configured to request QoS monitoring for a particular application (e.g., corresponding to the App-Id). • FallBackInstruction. This may correspond to an instruction that, if present, instructs SMF33 to fall back to performing QoS monitoring with respect to QoS flows associated with the default QoS rules. If the consumer (e.g., NWDAF35) does not provide a FallBackInstruction in the message in step S300 above, UDM34 may optionally be configured to add them (e.g., locally).

[0149] Step S308) SMF33 may be configured to determine the PDU session based on a WD identifier (e.g., UE-ID, SUPI, etc.).

[0150] Step S310) For one or more of the above PDU sessions, SMF33 may be configured to verify whether QoS monitoring is enabled as requested (i.e., there is a QoS monitoring policy for the PCC rule for the target App-Id). In this illustrative sequence diagram, SMF33 may be configured to verify that there is no PCC rule for the application identifier (e.g., App-Id) or that there is no QoS monitoring policy for QoS flows bound to a PCC rule for the application identifier (e.g., App-Id).

[0151] Step S312) Based on the FallBackInstruction received in Step 4 above, SMF33 may be configured to respond to the request message in Step S306 with a successful response (for example, accepting the request). This may be an alternative form of the procedure in which SMF33 may be configured to reject the request (when there is no active QoS monitoring for the App-Id).

[0152] Step S314) UDM34 may be configured to respond to the request message in step 1 with a successful response (accepting the request).

[0153] Step S316) Based on the FallBackInstruction received in step S306 above, SMF33 may be configured to enable QoS monitoring with respect to the QoS flow associated with the default QoS rule.

[0154] In some embodiments, NWDAF35 may be configured to instruct SMF33 to keep the subscription created (even if no reports are sent) until the QoS flow is bound to an application for which QoS monitoring is enabled and becomes dedicated to that application. In this case, SMF33 may be configured to create the subscription, and the procedure continues from step S320.

[0155] In instructions to UPF32, SMF33 may be configured to provide information to UPF32, for example, UPF32 may add to its report (e.g., "DefaultIndication") to indicate that a fallback action is being enforced and that QoS monitoring is being performed with respect to QoS flows related to the default QoS rules.

[0156] Step S318) UPF32 may be configured to report QoS monitoring to a consumer (e.g., NWDAF35) by triggering a Nupf_EE_Notify message containing the following information: • QoS monitoring reports, and / or • DefaultIndication may indicate that this report refers to the default QoS flow.

[0157] Steps S320 and S322) Policy association updates may occur, in which case QoS monitoring is enabled for PCC rules for App-Id including QoS monitoring policies, and thus the PFCP session may be updated accordingly. In some embodiments, SMF33 may not need to provide information for UPF32 to include in its report.

[0158] Step S324) UPF32 may be configured to report QoS monitoring to a consumer (e.g., NWDAF35) by triggering a Nupf_EE_Notify message containing the following information: · QoS monitoring report.

[0159] This report does not include the DefaultIndication (which may have been included in the previous report in step S318), meaning that this report refers to the QoS flow for the application identifier (e.g., App-Id) and does not refer to the default QoS flow.

[0160] Embodiments of the present disclosure may be described, for example, in 3GPP TS23.502 V18.5.0 as follows. • A consumer (e.g., NWDAF35) includes instructions during its subscription to QoS monitoring events for a particular application to enable the use of QoS monitoring for the default QoS flow as a fallback mechanism. • QoS monitoring reports that include instructions for QoS monitoring applied to the default QoS flow (as an alternative form of QoS monitoring when PCC rules are applied to that application).

[0161] The following is a non-limiting list of exemplary embodiments. 1. The first core network node, Receiving or determining Session Management Function (SMF) instance identifiers related to wireless devices and applications, Determining a subscription request to subscribe to Quality of Service (QoS) monitoring events for an SMF instance, wherein the subscription request includes a fallback instruction indicating that if no policy control billing (PCC) rule is found that enables QoS monitoring for the application, the SMF instance should perform QoS monitoring with respect to QoS flows associated with default QoS rules. This causes the subscription request to be sent to the second core network node. A first core network node equipped with a processing circuit configured to perform the following. 2. The first core network node as described in Example 1, wherein the first core network node functions as a Network Data Analysis Function (NWDAF) node. 3. The processing circuit is: Receiving a QoS monitoring report from a third core network node acting as an Uppacket Forwarding (UPF) function, wherein the report includes a default instruction indicating that QoS monitoring is performed with respect to QoS flows related to the default QoS rules. A first core network node, as described in Example 1 or 2, further configured to perform the following actions. 4. A method implemented in the first core network node, the method is: Receiving or determining Session Management Function (SMF) instance identifiers related to wireless devices and applications, Determining a subscription request to subscribe to Quality of Service (QoS) monitoring events for an SMF instance, wherein the subscription request includes a fallback instruction indicating that if no policy control billing (PCC) rule is found that enables QoS monitoring for the application, the SMF instance should perform QoS monitoring with respect to QoS flows associated with default QoS rules. Sending a subscription request to the second core network node and Methods that include... 5. The method described in Example 4, wherein the first core network node acts as a Network Data Analysis Function (NWDAF) node. 6. The method is, Receiving a QoS monitoring report from a third core network node acting as an Uppacket Forwarding (UPF) function, wherein the report includes a default instruction indicating that QoS monitoring is performed with respect to QoS flows related to the default QoS rules. The method as described in Example 4 or 5, further including the method described in Example 4 or 5. 7. The first core network node, Receiving a subscription request from a second core network node to subscribe to Quality of Service (QoS) monitoring events for a Session Management Function (SMF) instance, wherein the subscription request includes a fallback instruction requesting that if no policy control billing (PCC) rule enabling QoS monitoring is found for an application associated with a wireless device, QoS monitoring should be performed with respect to the QoS flow associated with the default QoS rule. When there is no PCC rule that enables QoS monitoring for an application, establish QoS monitoring operation based on a fallback instruction. A first core network node equipped with a processing circuit configured to perform the following. 8. The first core network node described in Example 7, which acts as a Session Management Function (SMF) node. 9. The processing circuit is, When there is no active PCC rule with QoS monitoring for the application, it causes the sending of an acceptance response to the first core network node. A first core network node, as described in Example 7 or 8, further configured to perform the following actions. 10. The processing circuit is, QoS monitoring is performed based on fallback instructions for QoS flows related to default Quality of Service (QoS) rules, This involves configuring a third core network node acting as an uppacket forwarding (UPF) function to include default instructions in QoS monitoring reports, wherein the default instructions indicate that QoS monitoring is performed with respect to QoS flows related to default QoS rules. A first core network node, as described in any one of Examples 7 through 9, is further configured to perform the following actions. 11. The processing circuit, When a policy association update is received that enables QoS monitoring for PCC rules about an application, update the QoS monitoring to mention the QoS flow for the application, but not the QoS flow associated with the default QoS rule. A first core network node, as described in any one of Examples 7 through 10, is further configured to perform the following actions. 12. A method implemented in a first core network node, the method being: Receiving a subscription request from a second core network node to subscribe to Quality of Service (QoS) monitoring events for a Session Management Function (SMF) instance, wherein the subscription request includes a fallback instruction requesting that if no policy control billing (PCC) rule enabling QoS monitoring is found for an application associated with a wireless device, QoS monitoring should be performed with respect to the QoS flow associated with the default QoS rule. When there is no PCC rule that enables QoS monitoring for an application, establish QoS monitoring operation based on a fallback instruction. Methods that include... 13. The method described in Example 12, wherein the first core network node acts as a Session Management Function (SMF) node. 14. The method is, When there are no active PCC rules with QoS monitoring for an application, send an acceptance response to the first core network node. The method described in Example 12 or 13, further including the method described in Example 12 or 13. 15. The method is, QoS monitoring is performed based on fallback instructions for QoS flows related to default Quality of Service (QoS) rules, This involves configuring a third core network node acting as an uppacket forwarding (UPF) function to include default instructions in QoS monitoring reports, wherein the default instructions indicate that QoS monitoring is performed with respect to QoS flows related to default QoS rules. The method according to any one of Examples 12 to 14, further including the method described in any one of Examples 12 to 14. 16. The processing circuit, When a policy association update is received that enables QoS monitoring for PCC rules about an application, update the QoS monitoring to mention the QoS flow for the application, but not the QoS flow associated with the default QoS rule. The method described in any one of Examples 12 to 15, further configured to perform the following actions.

[0162] As will be understood by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media for storing executable computer programs. Accordingly, the concepts described herein may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware embodiments, all of which may be generally referred to herein as “circuits” or “modules.” Any process, step, action, and / or function described herein may be carried out by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure may take the form of a computer program product on a tangible computer-readable storage medium having computer program code embodied in a medium that can be executed by a computer. Any suitable tangible computer-readable medium may be used, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0163] Several embodiments have been described herein with reference to flowcharts and / or block diagrams illustrating methods, systems, and computer program products. It will be understood that each block in a flowchart and / or block diagram, as well as combinations of blocks in a flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a dedicated computer, or other programmable data processing device for creating a machine (thereby creating a dedicated computer), and so those instructions executed via the processor of the computer or other programmable data processing device create means for implementing a function / action specified in one or more blocks of a flowchart and / or block diagram.

[0164] These computer program instructions may also be stored in computer-readable memory or storage medium that can be directed to a computer or other programmable data processing device to function in a particular manner, and so the instructions stored in computer-readable memory may produce a product that includes instruction means for implementing a function / action specified in one or more blocks of a flowchart and / or block diagram.

[0165] Computer program instructions can also be loaded into a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device in order to create a computer implementation process; therefore, instructions executed on a computer or other programmable device provide steps for implementing a function / action specified in one or more blocks of a flowchart and / or block diagram.

[0166] It should be understood that the functions / actions mentioned within a block may occur in a different order than those shown in the illustrative diagram of the operation. For example, depending on the functions / actions involved, two blocks shown consecutively may, in effect, be executed substantially concurrently, or blocks may sometimes be executed in reverse order. Some of the diagrams include arrows on the communication path to indicate the primary direction of communication, but it should be understood that communication may occur in the opposite direction to the illustrated arrows.

[0167] Computer program code for performing the operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java®, or C++. However, computer program code for performing the operations of the disclosure may also be written in a conventional procedural programming language such as the C programming language. The program code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or wide area network (WAN), or the connection may be made to an external computer (for example, via the Internet using an Internet service provider).

[0168] Many different embodiments have been disclosed herein in relation to the above description and drawings. It will be understood that a literal description and illustration of every combination and partial combination of these embodiments would be excessively repetitive and obscure. Therefore, all embodiments may be combined in some way and / or in combination, and this specification, including the drawings, should be construed as constituting a complete written description of all combinations and partial combinations of the embodiments described herein, and all combinations and partial combinations of the modes and processes of making and using them, and shall support any claims for any such combination or partial combination.

[0169] The abbreviations that may be used in the above explanation include the following: AF Application Function AMF access and mobility features API Application Programming Interface MNO Mobile Network Operator NEF Network Publishing Function PCF Policy Control Function PFCP Packet Flow Control Protocol QoS (Quality of Service) RAN (Radio Access Network) SMF session management function S-NSSAI Serving Network Slice Selection Support Information SUPI Subscription Persistence Identifier UDM (User Data Management) UDR User Data Repository UE User Equipment UPF User Plane Functionality

[0170] It will be understood by those skilled in the art that the embodiments described herein are not limited to those specifically shown and described herein. Furthermore, it should be noted that not all of the accompanying drawings are to a constant scale unless otherwise stated above. In light of the above teachings, various modifications and variations are possible without departing from the following claims.

Claims

1. A method in a first core network node (15) configured to communicate with a second core network node (15), wherein the method is: The second core network node (15) receives a subscription request to subscribe to QoS monitoring events for quality of service (QoS) flows bound to an application (S144), wherein the subscription request includes an instruction to receive QoS monitoring reports for QoS flows associated with a default QoS rule if no policy control billing (PCC) rule is identified for the application or no PCC rule is found that enables QoS monitoring for the application (S144), Configure the third core network node (15), which acts as a user plane function (UPF) (32), to include in the QoS monitoring report an instruction indicating that QoS monitoring is performed with respect to the QoS flow related to the default QoS rule (S146) and Methods that include...

2. The method according to claim 1, wherein the first core network node (15) is configured as a session management function (SMF) (33) node.

3. The aforementioned method, To determine that for one or more identified PDU sessions, there are no PCC rules that enable QoS monitoring for the said application. The method according to claim 1 or 2, further comprising:

4. The aforementioned method, In response to the subscription request, if there is no active PCC rule with QoS monitoring for the application, a response indicating acceptance of the subscription request is sent to the second core network node (15). The method according to any one of claims 1 to 3, further comprising:

5. The method according to any one of claims 1 to 4, wherein configuring the third core network node (15) further includes sending an instruction to the third core network node (15) to instruct the third core network node (15) to add an instruction to the QoS monitoring report that QoS monitoring is performed with respect to the QoS flow relating to the default QoS rule.

6. A first core network node (15) configured to communicate with a second core network node (15), wherein the first core network node (15) is configured to perform one or more steps corresponding to any one of claims 1 to 5.

7. A method in a second core network node (15) configured to communicate with a first core network node (15), wherein the method is: Determining a subscription request to subscribe to QoS monitoring events for Quality of Service (QoS) flows bound to an application (S148), wherein the subscription request includes an instruction indicating that the second core network node (15) has requested to receive QoS monitoring reports for QoS flows related to a default QoS rule if no policy control billing (PCC) rule is identified for the application or no PCC rule is found that enables QoS monitoring for the application. Sending the subscription request to the first core network node (15) (S150) Methods that include...

8. The aforementioned method, When there is no active PCC rule with QoS monitoring for the aforementioned application, an acceptance response is received from the first core network node (15). The method according to claim 7, further comprising:

9. The aforementioned method, Receiving a QoS monitoring report from a third core network node (15) acting as a user plane function (UPF) (32), which includes a default instruction indicating that QoS monitoring is performed with respect to the QoS flow related to the default QoS rule. The method according to claim 7 or 8, further comprising:

10. The method according to any one of claims 7 to 9, wherein the second core network node (15) is configured as a network data analysis function (NWDAF) (35) node or an integrated data management (UDM) (34) node, and the first core network node (15) is a session management function (SMF) (33).

11. A second core network node (15) configured to communicate with a first core network node (15), wherein the second core network node (15) is configured to perform one or more steps corresponding to any one of claims 7 to 10.

12. A computer program that, when executed on one or more processors (96) of a first core network node (15), includes instructions that cause the one or more processors (96) to perform the method described in any one of claims 1 to 5.

13. A computer program that, when executed on one or more processors (96) of a second core network node (15), includes instructions that cause the one or more processors (96) to perform the method described in any one of claims 7 to 10.

Images