EP4690686A1

EP4690686A1 - Notification to a user of a user equipment

Info

Publication number: EP4690686A1
Application number: EP24712094.2A
Authority: EP
Inventors: Marcus IHLAR; Maria Luisa Mas Rosique; Miguel Angel MUÑOZ DE LA TORRE ALONSO
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-03-24
Filing date: 2024-03-21
Publication date: 2026-02-11
Also published as: WO2024200194A1

Abstract

Methods and apparatus are provided. In some examples, a method performed by a Policy Control Function (PCF) for causing a notification to be provided to a user of a User Equipment (UE) is provided. The UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method comprises determining a notification to be provided to the user of the UE, and causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE, and wherein causing the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control (PCC) rule or an update to a PCC rule. (Fig. 4)

Description

NOTIFICATION TO A USER OF A USER EQUIPMENT

Technical Field

Example embodiments of this disclosure relate to a notification to a user of a user equipment, for example providing the notification or causing the notification to be provided.

Background

Figure 1 depicts the 5th Generation (5G) reference architecture as defined by the 3rd Generation Partnership Project (3GPP), and includes the following components.

• UDR (Unified Data Repository): The 5G system architecture allows the UDM (Unified Data Management), PCF (Policy Control Function) and NEF (Network Exposure Function) to store data in the UDR.

• PCF (Policy Control Function): The Policy Control Function (PCF) supports unified policy framework to govern the network behaviour.

• SMF (Session Management Function): The Session Management function (SMF) supports different functionalities, e.g. SMF receives PCC rules from the PCF and configures the UPF accordingly.

• UPF (User Plane Function): The User Plane function (UPF) supports handling of user plane traffic based on the rules received from the SMF, e.g. packet inspection and different enforcement actions such as traffic redirection or QoS handling.

Traffic encryption is growing significantly in mobile networks, and at the same time encryption mechanisms are growing in complexity. In particular, most applications today are not based on Hypertext Transfer Protocol (HTTP) cleartext, but instead they are based on Hypertext Transfer Protocol Secure (HTTPS), using Transport Layer Security (TLS).

Additionally, a significant part of the traffic is based on QUIC transport (e.g. YouTube, Facebook, etc), which has an encryption level higher than TLS. In the future, it is foreseen that most applications will be based on QUIC transport. Additionally, Apple’s Private Relay is already deployed and represents the highest level of encryption (similar to a VPN tunnel).

Network operators today require application/service awareness in order to apply differentiated traffic management actions, e.g. Redirection, Charging, QoS, etc. Differentiated traffic management by a mobile network operator (MNO) is now challenged due to Apple’s iCloud+ Private Relay, a dual-proxy solution based on Multiplexed Application Substrate over QIIIC Encryption (MASQUE) technology being standardized in the Internet Engineering Task Force (IETF). Private Relay has been deployed and advertised by Apple as a new security feature available since operating system iOS version 15 (mid Sept 2021).

Private Relay is a new internet privacy service that allows users to connect to and browse the web in a more secure and private way. When browsing with Safari web browser, Private Relay ensures all traffic leaving a user’s device is encrypted, so no one between the user and the website they are visiting can access and read it, not even Apple or the user’s network provider. All the user’s requests are then sent through two separate internet relays. The first (referred to as an ingress proxy in some examples) assigns the user an anonymous IP address that maps to their region but not their actual location. The second (referred to as an egress proxy in some examples) decrypts the web address they want to visit and forwards them to their destination. This separation of information protects the user’s privacy because no single entity can identify both the users and which sites they visit.

Apple’s Private Relay works with two QUIC/MASQUE proxies (acting as relays), as depicted in Figure 2, which shows an example of a Private Relay high level architecture. The ingress proxy assigns the user (or the device/UE) an anonymous IP address, which may maps to their region but not their actual location. It has visibility of the user IP address. The egress proxy decrypts the web address they want to visit and forwards them to their destination. It has visibility of the User traffic destination.

QUIC is a UDP (User Datagram Protocol)-based stream-multiplexed and secure transport protocol with integrity protected header and encrypted payload. Unlike the traditional transport protocol stack with TCP (Transmission Control Protocol), which resides in the operating system kernel, QUIC can easily be implemented in user space, i.e. in the application layer. As a consequence, this improves flexibility in terms of transport protocol evolution with implementation of new features, congestion control, deploy ability and adoption.

QUIC is standardized in the IETF. QUIC is likely to become the main transport protocol in the Internet’s user plane. It is expected that most applications running today over HTTP/HTTPS will migrate to QUIC, driven by latency improvements and stronger security. Notably, compared to HTTPS, encryption in QUIC covers both the transport protocol headers as well as the payload, as opposed to TLS over TCP, e.g. HTTPS, which protects only the payload. Conceptionally, a proxy is an intermediary program acting as both server and client, creating or simply relaying requests on behalf of other entities. Requests are serviced internally or by passing them on, with possible translation, to other servers. There are several types of proxies, such as the following:

• A "transparent proxy" is a proxy that does not modify the request or response beyond what is required for proxy authentication and identification.

• A "non-transparent proxy" is a proxy that modifies the request or response to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reduction, or anonymity filtering.

• A "reverse proxy" basically is a proxy that pretends to be the actual server (as far as any client or client proxy is concerned), but it passes on the request to the actual server that is usually sitting behind another layer of firewalls.

• A “Performance Enhancement Proxy (PEP)” is used to improve the performance of protocols on network paths where native performance suffers due to characteristics of a link or subnetwork on the path.

IETF has a Working Group called MASQUE, aimed to develop mechanism(s) that allow configuring and concurrently running multiple proxied stream- and datagram-based flows inside an HTTPS connection. These mechanism(s) are collectively called MASQUE. The group will specify HTTP and/or HTTP/3 extensions to enable this functionality. Two RFCs have already been produced ([1][2]).

Through MASQUE:

• Application creates a secure connection to a on-path network proxy

• Establish secure E2E connection to the server (s) via the proxy

• Application data is secured E2E and protected from unauthorized used in the network

• Content provider and Mobile Network Operator has a secure channel to exchange information about application and policy real-time.

The application client explicitly opens QUIC tunnel connection to proxy and request forwarding and uses HTTP CONNECT-like protocol and a custom protocol to request or negotiate forwarding, authentication, and configuration. QUIC proxy provides secure forwarding and performance enhancement services, e.g. congestion control support (mobile/satellite), access policy enforcement, load balancing/mobility, multi-hop chaining/onion routing. QIIIC proxy may optionally also open a tunnel to server (if supported by server).

By using the above mechanisms, the client and/or server (usually the client) explicitly contacts a proxy (e.g. a QIIIC Proxy) in order to expose information between the Content Provider (Application Client and/or Server) and the Mobile Network Operator (e.g. QIIIC Proxy at UPF). Figure 3 shows an example of Client/Server and Proxy interaction and shows an inner connection which carries (encrypted) application traffic between client and server (not visible to the proxy), while the outer connection can be used to expose information between the Content Provider (Application Client and/or Server) and the Mobile Network Operator (e.g. QIIIC Proxy at UPF).

The Masque working group has defined the Capsule (or CAPSULE) protocol to transmit reliable pieces of information that relates to a flow of datagrams [1], A capsule consists of a capsule type and capsule payload. New capsules can be standardized in IETF as extensions to protocols making use of HTTP datagrams.

Today, Mobile Network Operators (MNOs) apply different traffic management actions, one of them being user notification, which is supported in UPF as traffic redirection (e.g. HTTP based redirection), in order to notify the user when the user’s data allowance quota has been fully consumed, or when the network wants to notify the user of any event (e.g. user entering roaming which might be subject to extra charging). However, HTTP based redirection has issues. For example, it is currently not possible for a UPF to apply redirection for HTTPS traffic (HTTP/HTTP2 over TLS). The same happens for QUIC based applications (HTTP3 over QUIC) like YouTube. Most applications today are encrypted (HTTPS/TLS or QUIC), and for those, traffic redirection triggered by UPF is not possible. In addition, DNS traffic is encrypted (e.g. DoH or DoT) so it is not even possible to trigger redirection based on DNS inspection at UPF. HTTP redirection cannot be applied to applications which are not based on HTTP. Browsers support HTTP redirection, but some applications do not support it (e.g. they might ignore the HTTP 3xx message triggered by UPF).

Summary

One aspect of the present disclosure provides a method performed by a Policy Control Function, PCF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method comprises determining a notification to be provided to the user of the UE, and causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule.

Another aspect of the present disclosure provides a method performed by a Session Management Function, SMF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method comprises determining a notification to be provided to the user of the UE, and causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

A further aspect of the present disclosure provides a method performed by a User Plane Function, UPF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method comprises determining a notification to be provided to the user of the UE, and causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

A still further aspect of the present disclosure provides a method performed by an ingress proxy for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an the ingress proxy. The method comprises determining a notification to be provided to the user of the UE, and causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

Another aspect of the present disclosure provides apparatus in a Policy Control Function, PCF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus comprises a processor and a memory. The memory containing instructions executable by the processor such that the apparatus is operable to determine a notification to be provided to the user of the UE, and cause a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule.

Another aspect of the present disclosure provides apparatus in a Session Management Function, SMF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus comprises a processor and a memory. The memory containing instructions executable by the processor such that the apparatus is operable to determine a notification to be provided to the user of the UE, and cause (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

Another aspect of the present disclosure provides apparatus in a User Plane Function, UPF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus comprises a processor and a memory. The memory containing instructions executable by the processor such that the apparatus is operable to determine a notification to be provided to the user of the UE, and cause a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

Another aspect of the present disclosure provides apparatus in an ingress proxy for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to the ingress proxy. The apparatus comprises a processor and a memory. The memory containing instructions executable by the processor such that the apparatus is operable to determine a notification to be provided to the user of the UE, and cause a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

Another aspect of the present disclosure provides apparatus in a User Equipment (UE) for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus comprises a processor and a memory. The memory containing instructions executable by the processor such that the apparatus is operable to send, to a first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE, receive, from the first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE, and provide the notification to the user of the UE.

Another aspect of the present disclosure provides apparatus in a Policy Control Function, PCF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus is configured to determine a notification to be provided to the user of the UE, and cause a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule. Another aspect of the present disclosure provides apparatus in a Session Management Function, SMF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus is configured to determine a notification to be provided to the user of the UE, and cause (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

Another aspect of the present disclosure provides apparatus in a User Plane Function, UPF, for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The apparatus comprises a processor and a memory. The memory containing instructions executable by the processor such that the apparatus is configured to determine a notification to be provided to the user of the UE, and cause a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

Another aspect of the present disclosure provides apparatus in an ingress proxy for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to the ingress proxy. The apparatus is configured to determine a notification to be provided to the user of the UE, and cause a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Causing the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

Another aspect of the present disclosure provides apparatus in a User Equipment (UE) for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QIIIC Encryption (MASQUE) connection to an ingress proxy. The apparatus is configured to send, to a first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE, receive, from the first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE, and provide the notification to the user of the UE.

Brief Description of the Drawings

For a better understanding of examples of the present disclosure, and to show more clearly how the examples may be carried into effect, reference will now be made, by way of example only, to the following drawings in which:

Figure 1 depicts the 5G reference architecture as defined by 3GPP;

Figure 2 shows an example of a Private Relay high level architecture;

Figure 3 shows an example of Client/Server and Proxy interaction;

Figure 4 is a flow chart of an example of a method performed by a Policy Control Function (PCF) for causing a notification to be provided to a user of a User Equipment (UE);

Figure 5 is a flow chart of an example of a method performed by a Session Management Function (SMF) for causing a notification to be provided to a user of a User Equipment (UE);

Figure 6 is a flow chart of an example of a method performed by a User Plane Function (UPF) for causing a notification to be provided to a user of a User Equipment (UE);

Figure 7 is a flow chart of an example of a method performed by an ingress proxy for causing a notification to be provided to a user of a User Equipment (UE);

Figure 8 is a flow chart of an example of a method performed by a User Equipment (UE) for providing a notification to a user of the UE;

Figure 9 shows an example of a proposed mechanism for User Notification in Dual Proxy deployments;

Figure 10 shows a first part of a sequence diagram of an example of a method of causing a notification to be provided to a user of a UE and providing a notification to a user of the UE;

Figure 11 shows a second part of the sequence diagram of the example of a method of causing a notification to be provided to a user of a UE and providing a notification to a user of the UE; Figure 12 shows a third part of a sequence diagram of the example of the method of causing a notification to be provided to a user of a UE and providing a notification to a user of the UE;

Figure 13 shows an example of a communication system in accordance with some embodiments;

Figure 14 shows a UE in accordance with some embodiments;

Figure 15 shows a network node in accordance with some embodiments;

Figure 16 is a block diagram of a host;

Figure 17 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

Figure 18 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

Detailed Description

The following sets forth specific details, such as particular embodiments or examples for purposes of explanation and not limitation. It will be appreciated by one skilled in the art that other examples may be employed apart from these specific details. In some instances, detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or more nodes using hardware circuitry (e.g. analog and/or discrete logic gates interconnected to perform a specialized function, Application Specific Integrated Circuits (ASICs), Programmable Logic Arrays (PLAs), etc.) and/or using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, where appropriate the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g. digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions. Though Private Relay is the first MASQUE based dual-proxy deployment, others will likely follow in pursue of improve user privacy. In this disclosure, for a MASQUE based dual-proxy deployment, the ingress proxy may in some examples be referred to as the first MASQUE proxy and the egress proxy as the second MASQUE proxy.

The following problems are identified:

• Mobile Network Operators (MNOs) today apply different traffic management actions, one of them being user notification, which is supported in UPF as traffic redirection (e.g. HTTP based redirection), in order to notify the user e.g. when the subscriber’s quota is consumed or when the network wants to notify the user of any event (e.g. user entering roaming which might be subject to extra charging).

• HTTP based redirection has the following issues: o It is currently not possible for UPF to apply redirection for HTTPS traffic (HTTP/HTTP2 over TLS). The same happens for QUIC based applications (HTTP3 over QUIC) like YouTube. o Most applications today are encrypted (HTTPS/TLS or QUIC), and for those, traffic redirection triggered by UPF is not possible. In addition, DNS traffic is encrypted (e.g. DoH or DoT) so it is not even possible to trigger redirection based on DNS inspection at UPF. o It cannot be applied to applications which are not based on HTTP. o Browsers support HTTP redirection, but some Applications do not support it (e.g. they might ignore the HTTP 3xx message triggered by UPF).

• SMS (or e-mail) based notifications have the following issues: o As reported by different customers, users frequently ignore SMS (or e-mail) notifications at exhaustion of data bundle and are not able to easily purchase or renew their data bundle, which leads to loss of potential revenue for the MNO. There are network operators (especially the ones where the subscriber base is mostly online charging) claiming this solution is not acceptable and asking for a different solution.

Examples of this disclosure provide mechanisms that solve one or more of the above problems, and are based on using the MASQUE connection between the MASQUE client (e.g. at UE OS) and the MASQUE ingress proxy (e.g. at UPF) for MNO to request a user notification (e.g. at exhaustion of data bundle to request the user to refill). Examples of this disclosure may also propose extension of the PCC rules and Packet detection Rules (PDRs) to support user notification policies based on MASQUE, and/or extension of MASQUE (e.g. based on defining new HTTP/3 error codes in the MASQUE connection between the MASQUE client at UE OS and the MASQUE ingress proxy at UPF) for MNO to request the UE to notify the user (e.g. at exhaustion of data bundle to request the user to refill).

Examples of this disclosure may have one or more of the following advantages:

• It allows MNO to support user notification in dual-proxy deployments in a simple and efficient way.

• User privacy is preserved, and operator policies and subscription terms (e.g. data bundles) can still be enforced.

• The solution works when the traffic is encrypted, e.g. QUIC based applications, for which existing mechanisms (e.g. redirect actions) do no work.

Figure 4 is a flow chart of an example of a method 400 performed by a Policy Control Function (PCF) for causing a notification to be provided to a user of a User Equipment (UE). The UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method 400 comprises, in step 402, determining a notification to be provided to the user of the UE. Step 404 of the method 400 comprises causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE, and wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule.

In some examples, determining a notification to be provided to the user of the UE in step 402 comprises determining that a data usage allowance associated with the UE has been exceeded. Determining that a data usage allowance associated with the UE has been exceeded may comprise for example receiving data usage reports from a second network node, which may for example indicate how much data the UE/user has used.

The PCC rule or the update to the PCC rule may include a user notification policy in some examples. The user notification policy may for example identify one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; and/or a Uniform Resource Identifier (URI) of notification information. The PCC rule or the update to the PCC rule may for example for a Protocol Data Unit (PDU) session of the UE. In some examples, the second network node comprises a Session Management Function (SMF). In some examples, them method 400 may comprise, before causing (404) the message to be sent using the MASQUE connection to the UE, obtaining, from a data storage node such as a Unified Data Repository (UDR), an indication that the UE supports a capability of providing the notification to the user of the UE in response to the message sent using the MASQUE connection. Thus, for example, the PCF may not cause the message to be sent using the MASQUE connection to the UE without knowing that the UE supports this capability and can or will provide the notification to the user of the UE.

The notification to the user of the UE may for example comprise a notification that a data usage allowance associated with the UE (e.g. associated with a subscription of the user or being used on the UE) has been exceeded and/or that the user of the UE will incur roaming charges.

Causing the message to be sent, using the MASQUE connection, to the UE in step 404 of the method 400 may in some examples comprises causing a HTTP status code (e.g. an error code) to be sent to the UE. The HTTP status code may for example comprise a predetermined (e.g. standardized) HTTP status code associated with providing the notification to the user of the UE.

Figure 5 is a flow chart of an example of a method 500 performed by a Session Management Function (SMF) for causing a notification to be provided to a user of a User Equipment (UE). The UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method 500 comprises, in step 502, determining a notification to be provided to the user of the UE, wherein determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy. Step 504 of the method 500 comprises causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE, and wherein causing the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

The PCC rule or the update to the PCC rule may in some examples identify one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; and/or a Uniform Resource Identifier (URI) of notification information. Sending the user notification policy to the third network node may comprise for example sending, to the third network node, an update for a Packet Forwarding Control Protocol (PFCP) for the UE and/or one or more Forwarding Action Rules (FARs) for the PFCP session. The third network node may comprise a User Plane Function (UPF) in some examples. The PCC rule or the update to the PCC rule may for example be for a Protocol Data Unit (PDU) session of the UE. In some examples, the second network node comprises a Policy Control Function (PCF).

Causing the message to be sent, using the MASQUE connection, to the UE in step 504 of the method 500 may in some examples comprises causing a HTTP status code (e.g. an error code) to be sent to the UE. The HTTP status code may for example comprise a predetermined (e.g. standardized) HTTP status code associated with providing the notification to the user of the UE.

Figure 6 is a flow chart of an example of a method 600 performed by a User Plane Function (UPF) for causing a notification to be provided to a user of a User Equipment (UE). The UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method 600 comprises, in step 602, determining a notification to be provided to the user of the UE, wherein determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Step 604 of the method 600 comprises causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE, and wherein causing the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

The user notification policy may for example identify one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; and/or a Uniform Resource Identifier (URI) of notification information. Receiving, from the second network node, the user notification policy comprises for example receiving, from the second network node, an update for a Packet Forwarding Control Protocol (PFCP) for the UE and/or one or more Forwarding Action Rules (FARs) for the PFCP session. In some examples, the second network node comprises a Session Management Function (SMF). The method 600 may also in some examples comprise receiving, from the UE, an indication of whether the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or whether the notification will be provided to the user of the UE. Causing the message to be sent, using the MASQUE connection, to the UE may be performed in some examples in response to the indication indicating that the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or indicating that the notification will be provided to the user of the UE. The indication may be received in some examples from the UE in a message for establishing the MASQUE connection to the ingress server, e.g. a HTTP Connect message.

Causing the message to be sent, using the MASQUE connection, to the UE in step 604 of the method 600 may in some examples comprises causing a HTTP status code (e.g. an error code) to be sent to the UE. The HTTP status code may for example comprise a predetermined (e.g. standardized) HTTP status code associated with providing the notification to the user of the UE.

Figure 7 is a flow chart of an example of a method 700 performed by an ingress proxy for causing a notification to be provided to a user of a User Equipment (UE). The UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method 700 comprises, in step 606, determining a notification to be provided to the user of the UE, wherein determining a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy. Step 700 of the method 700 comprises causing a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE, and wherein causing the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy. In some examples, the method 700 may be performed by a UPF, for example where the ingress proxy is implemented by or within the UPF. The user notification policy may identify for example one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; and/or a Uniform Resource Identifier (URI) of notification information. Causing the message to be sent, using the MASQUE connection, to the UE may comprise for example sending the message to the UE according to the user notification policy. The message sent to the UE may identify the user notification policy. In some examples, the second network node comprises a User Plane Function (UPF).

The method 700 may also in some examples comprise receiving, from the UE, an indication of whether the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or whether the notification will be provided to the user of the UE. Causing the message to be sent, using the MASQUE connection, to the UE may be performed in some examples in response to the indication indicating that the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or indicating that the notification will be provided to the user of the UE. The indication may be received in some examples from the UE in a message for establishing the MASQUE connection to the ingress server, e.g. a HTTP Connect message.

Causing the message to be sent, using the MASQUE connection, to the UE in step 704 of the method 700 may in some examples comprises causing a HTTP status code (e.g. an error code) to be sent to the UE. The HTTP status code may for example comprise a predetermined (e.g. standardized) HTTP status code associated with providing the notification to the user of the UE.

Figure 8 is a flow chart of an example of a method 800 performed by a User Equipment (UE) for providing a notification to a user of the UE. The UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy. The method comprises, in step 802, sending, to a first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE. Step 804 of the method 800 comprises receiving, from a first network node (e.g. the ingress proxy referred to above), using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE. Step 806 of the method 800 comprises providing the notification to the user of the UE. In some examples, the first network node performs the method 700 described above, and thus in some examples the first network node is an ingress proxy or UPF (where the ingress proxy is implemented by or within the UPF, for example). The notification may be for example a sound, message displayed on the UE’s screen, haptics, and/or any other suitable notification.

In some examples, the method 800 may comprise receiving, from the first network node, a user notification policy. The user notification policy identifies for example one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; and/or a Uniform Resource Identifier (URI) of notification information. Providing the notification to the user of the UE in step 804 comprises for example providing the notification to the user of the UE according to the user notification policy.

In some examples, receiving, from the first network node, the message and/or providing the notification to the user of the UE may be performed in response to the indication indicating that the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or indicating that the notification will be provided to the user of the UE. The indication is sent to the first network node in a message for establishing the MASQUE connection to the ingress server, in some examples. The message for establishing the MASQUE connection to the ingress server may be a HTTP Connect message for example.

In some examples, the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

The message for causing the UE to provide the notification to the user of the UE may be for example a HTTP status code, e.g. an error code. The HTTP status code may be for example a predetermined (e.g. standardized) HTTP status code associated with providing the notification to the user of the UE.

Specific example embodiments will now be described for illustrative purposes. Figure 9 shows an example of a proposed mechanism for User Notification in Dual Proxy deployments. The proposed mechanism for MNO to notify the user in dual proxy deployments (e.g. Apple’s Private Relay) is based on using the MASQUE (outer) connection between the MASQUE client (at UE OS) and the MASQUE ingress proxy (at UPF), for MNO to request a notification is sent to the user (e.g. at exhaustion of data bundle to request the user to refill).

The proposed example mechanism is as follows:

• Preconditions:

• There is an SLA agreement between the following parties involved in the dualproxy deployment (e.g. Apple’s Private Relay):

• UE OS vendor (e.g. Apple)

• MNO providing the Ingress Proxy in this dual-proxy deployment.

• The UE, which includes a MASQUE client at OS level, e.g. iOS in Apple’s Private Relay, establishes an outer connection to the Mobile Network Operator’s MASQUE Ingress Proxy in UPF. In general, there will be:

• An inner connection between the application client and the egress proxy. This one will be used to transfer application traffic between the endpoints.

• An outer connection between the MASQUE client (at UE) and the MNO’s MASQUE ingress proxy (at UPF).

The outer connection between the MASQUE client and the MASQUE Ingress Proxy (at UPF) is proposed to be used for capability negotiation and it is used to indicate support of User Notification based on MASQUE.

• Whenever user notification needs to be triggered, e.g. PCF or CHF detects that a certain user (UE-ID) has run out of quota:

• PCF updates (towards SMF for UE-ID session) the PCC rules. PCC rules are proposed to be extended with a user notification policy. The user notification policy consists of the following parameters in User-Notification-Information:

■ User-Notification-Source, which can include either:

• Notification message, e.g. “You have run out of quota” so the message is directly conveyed and displayed to the user, without the need to trigger a connection towards a Notification Server (e.g. a top-up server); or • Notification Server URI: Determines the URI where the notification information is available. UE connects to that URI to display the information when the network requests to notify the user. It can instead be a server IP address (e.g. of the network operator’s top-up server).

■ User-Notification-Type: Determines the type of user notification, as follows:

• One-time notification: user notification is triggered only once (e.g. user notification in case of roaming with potential extra charges).

• Continuous notification: notification is triggered (e.g. persistently or repeatedly) until the user takes action and/or it is disabled (e.g. in case the user is out of quota, and needs to be continuously redirected).

■ User-Notification-Access-Control-Policy: Determines the access control policy for the user application traffic, as follows:

• Allow: allows the user application traffic to pass (maybe with downgraded performance) while the User Notification policy is active.

• Block: blocks the user application traffic while the User Notification policy is active. Depending on the use case, blocking may exclude traffic e.g. to a refill portal.

The PCC Rule may contain a full definition of the user notification policy, or an identifier of a user notification policy locally configured in UPF.

• Based on the information received above from PCF, SMF updates the PFCP session towards UPF, specifically the FAR is proposed to be extended with a user notification policy, including the same information (User-Notification- Information) as in the PCC rule above.

• Based on the information received from SMF, UPF indicates to the MASQUE Ingress Proxy (e.g. an internal MASQUE Proxy SF in UPF) that a user notification policy (passing the same information received above from SMF) applies to UE-ID. MASQUE Ingress Proxy applies the following logic:

• The MASQUE Ingress Proxy sends to the MASQUE Client (at UE OS), through the outer connection, a notification request message to request the UE to notify the user (e.g. exhaustion of data bundle to request the user to refill). Specifically, it is proposed to define a series of HTTP error codes for that (where each error code can be mapped to a specific notification which can be locally configured at UE OS). The notification details can be encoded in the payload (e.g. JSON). When there is the desire to notify the user without tearing down the connection, CAPSULES can be used instead.

• Based on the above, MASQUE Client (at UE OS) notifies the user accordingly, e.g. by generating a pop-up window in UE screen displaying the notification message (“You have run out of quota”) or by triggering a connection to the URI (e.g. top-up server) included in the User notification request message.

An example sequence diagram of a method of causing a notification to be provided to a user of a UE and providing a notification to a user of the UE is shown in Figures 10, 11 and 12, and shows an example where user notification is to be triggered when the subscriber’s quota has been consumed. Steps are detailed below.

Preconditions:

• UE OS vendor (e.g. Apple)

• MNO providing the Ingress Proxy in this dual-proxy deployment.

• UE supports MASQUE based notifications. User has given consent to MNO to receive MASQUE based notifications and has activated these notifications in the UE.

Steps 1 to 3) UE triggers PDU Session Establishment procedure. As part of this procedure, SMF creates the policy association with the PCF (Step 3).

Steps 4 and 5) PCF retrieves from UDR the subscriber policy for UE-ID, which is proposed to be extended with an indication indicating User consent to Notification based on MASQUE. Steps 6 and 7) PCF generates PCC rules for the PDU session (including a request for volume reporting).

Steps 8 and 9) SMF triggers PFCP Session Establishment procedure towards UPF to indicate the PDRs and the corresponding enforcement actions (FARs, QERs, URRs, etc) for the PDU session. Specifically, SMF will include a URR including a request for volume reporting. Step 10) User opens an application (e.g. browser). UE enables user privacy based on dual proxy (e.g. Private Relay), so it forwards the application traffic (e.g. browser) towards the Ingress/Egress Proxy.

Step 11) UE sends towards the Ingress Proxy a HTTP CONNECT method including the following information:

• :protocol=connect-udp. This is the new connect-udp. See [2]

• :scheme= https

• :path=/egressproxy.com/443/. This indicates the domain of the egress proxy

• :authority=user-notificationproxy. example.org This indicates the request targets the MASQUE ingress proxy with user-notification support (and UE OS MASQUE client indicates support for user notification through MASQUE).

• stream I d=0

Step 12) UPF detects traffic through Ingress towards Egress Proxy (Egress Proxy based on CONNECT :path header inspection) and stores UE support for MASQUE User Notification (based on CONNECT authority header).

Step 13) UPF answers indicating successful operation.

Step 14) Through the tunnel of the Ingress Proxy connection, UE sends data packets with a CONNECT request to the Egress proxy, i.e. UE sends a HTTP CONNECT method including the following information:

• :protocol=connect-udp. This is the new connect-udp. See [2]

• :scheme= https

• :path=/example.com/443/. This indicates the target host (application server).

• :authority=egressproxy.com. This indicates the domain of the egress proxy.

• streamld=O.

The sequence diagram shown in Figures 10-12 is just an example. Other examples may use other HTTP methods, such as connect-ip or even regular HTTP connect.

Step 15) UPF (MASQUE Ingress Proxy) forwards the CONNECT message to the Egress Proxy. Note the CONNECT request (target domain (example.com) included) is not visible to UPF so the user privacy provided by the dual-proxy deployment is respected.

Step 16) Egress Proxy answers indicating successful operation.

Step 17) UE sends HTTP3 datagrams towards the Application Server. End-to-end data is relayed via the Ingress Proxy to the Egress Proxy and onwards to the target server. The MNO is unaware of the target application, the provider of the Egress Proxy and target server are unaware of the subscriber address. Steps 18 and 19) UPF detects traffic through Ingress towards Egress Proxy and accumulates volume (e.g. number of bytes). When a certain volume threshold is reached, triggers a PFCP Session Report Request message including a URR with the accumulated LIL/DL volume. (E.g. a usage report referred to above.) Step 20) SMF answers with a PFCP Session Report Response message.

Step 21) SMF reports the accumulated LIL/DL volume to PCF in a Npcf_SMPolicyControl_Update Request message.

Step 22) PCF answers back to SMF with a Npcf_SMPolicyControl_Update Response message. Step 23) PCF detects the user has run out of quota (e.g. accumulated volume for the current month exceeds 10 GB) and triggers user notification through MASQUE (based on the indication received and stored at Step 5 above).

For Steps 21-23) Depending on deployment, SMF reporting may be towards the Charging System. PCF may detect that user runs out of quota if notified by Charging System instead. Step 24) PCF updates (towards SMF for UE-ID session through a

Npcf_SMPolicyControl_Update Request) the PCC rules which are proposed to be extended with an enforcement action related to user notification. Specifically, it is proposed to define at [5] a new attribute (userNotificationlnfo attribute) within TrafficControlData, as follows: Table 5.6.2.10-1 : Definition of type TrafficControlData

The userNotificationlnfo attribute (which may be an example of the user notification policy referred to above) consists of the following parameters:

• User-Notification-Source, which can include: • Notification message, e.g. “You have run out of quota” so the message is directly conveyed and displayed to the user, without the need to trigger a connection towards a Notification Server (e.g. a top-up server). The notification message might include a link for the user to click e.g. to facilitate account refill. This is the case shown in the example sequence diagram in Figures 10-12.

• Notification Server URI: Determines the URI where the notification information is available. UE needs to connect to that URI to display the information when the network requests to notify the user. It can instead be a server IP address (e.g. of the network operator’s top-up server).

• User-Notification-Type: Determines the type of user notification as follows:

• One-time notification: user notification needs to be triggered only once (e.g. user notification in case of roaming with potential extra charges).

• Continuous notification: notification needs to be triggered until the user takes action and/or it is disabled (e.g. in case the user is out of quota and needs to be continuously redirected). This is the case shown in the example sequence diagram in Figures 10-12.

• User-Notification-Access-Control-Policy: Determines the access control policy for the user application traffic, as follows:

• Allow: allows the user application traffic to pass while the User Notification policy is active.

• Block: blocks the user application traffic while the User Notification policy is active. This is the case shown in the example sequence diagram in Figures 10-12.

The PCC Rule may contain a full definition of the user notification policy (userNotificationlnfo attribute), or an identifier of a user notification policy locally configured in UPF.

User-Notification-Type and User-Notification-Access are information for the MASQUE Ingress Proxy (e.g. as an embedded SF in UPF) to consume. They provide the proxy notification logic the notification context. The PCC rule still needs to include the corresponding QoS and access control policies.

When access control policy is “Block”, the network shall not block the UE connection attempts with purpose of account refilling (i.e. to refill portal), i.e. connection requests where traffic target, is the refill portal. There are several ways this can be done, for instance the connection towards the top-up server can be established without tunneling through an egress proxy.

To deactivate a continuous notification, the PCC rule may be sent but without the user notification policy.

Step 25) SMF answers PCF with a Npcf_SMPolicyControl_Update Response message indicating successful operation.

Step 26) Based on the information received from PCF, SMF updates the PFCP session towards UPF (through a PFCP Session Modification Request message), specifically with a FAR which is proposed to be extended with an enforcement action related to User Notification, including the information (User-Notification-Information) as in Step 24 above. Specifically, it is proposed to define at [4] a new IE (User Notification IE) in the Forwarding Parameters IE (in Create/Update FAR IE), as follows:

Table 7.5.2.3-2: Forwarding Parameters IE in FAR

Step 27) UPF answers SMF with a PFCP Session Modification Response message indicating successful operation.

Steps 28 and 29) UPF forwards the User Notification Policy to MASQUE Ingress Proxy (e.g. as an embedded SF in UPF), which triggers a message towards UE OS MASQUE Client to request user notification.

Specifically, it is proposed in some examples to terminate the HTTP/3 stream with a new error code. As there are different triggers for user notification (e.g. quota exhausted, user entering roaming, etc), it is proposed to define a series of MASQUE error codes (where each error code can be mapped to a specific notification which can be locally configured at UE OS). In the example shown in the sequence diagram of Figures 10-12, which is for the use case of quota exhaustion, it is proposed to define a new error code (H3_QUOTA_EXHAUSTED with a value of 0x111) in IETF RFC 9114 [3], Other notification details (e.g. NotificationServerllRI, which was included in the User-Notification-Information received in Step 26 above) can be encoded in the payload (e.g. JSON).

Step 30) UE (UE OS MASQUE Client) answers UPF (MASQUE Ingress Proxy) indicating successful operation.

Step 31) UE (UE OS MASQUE Client) terminates the HTTP/3 stream (which means no more end to end traffic will be carried through the dual proxy) and notifies the user accordingly, e.g. by generating a pop-up window in UE screen displaying the notification message (“You have run out of quota, please refill by clicking this link”), where the link is based on the information (NotificationServerURI) provided in the message in Step 29 above.

NOTE: As per [3], in case the HTTP/3 endpoints receive error codes they do not understand, they treat them as a H3_NO_ERROR and shut down the stream. So, even if the UE does not support as such the user notification based on MASQUE (e.g. UE in Step 11 does not include that capability), in case the user runs out of quota, with the proposed mechanism the traffic will be blocked at the source (UE).

UPF informs PCF/SMF when the notification cannot be delivered (no UE support). That indication may be used by PCF e.g. to consider a notification fall back mechanism e.g. e- mail or SMS if available.

In steps 29-31 in sequence diagram above, HTTP3 error codes are used to tear down a MASQUE connection in a way such that the end-user is notified about the circumstance of the stopped connectivity. An alternative to using HTTP error codes is to make use of the CAPSULE protocol defined in [1], In cases where a user notification is desirable but not by tearing down the MASQUE connection (e.g. if User-Notification-Access-Control-Policy is set to “Allow”) a capsule is a good fit. The format of the capsule could consist of a capsule type that defines the kind of message to display and additional data that can be used when displaying the message, e.g. a URL to a top-up server.

Not shown in the example sequence diagram in Figures 10-12, steps 29-31 may repeat at new connection attempts, if User-Notification-Type is continuous notification. Not shown in the example sequence diagram in Figures 10-12, but in case the user decides to refill (e.g. by clicking the link included in the displayed notification message at Step 31), there may be two options to allow the traffic to the top-up URL (NotificationServerURI):

• Option 1 : The client (at UE) accesses this URL directly and not through the dual proxy (e.g. Private Relay).

• Option 2: An explicit egress proxy is used for this traffic (e.g. UPF can be instructed to allow traffic targeting that egress proxy specifically).

The example sequence diagram in Figures 10-12 shows the case of a dual proxy deployment (e.g. Apple’s Private Relay), but examples of this disclosure can also be used in single MASQUE proxy deployments, where MASQUE is introduced for other purposes than privacy. Such examples may have one single MASQUE proxy, e.g. in UPF, and it adopts for this scenario the role played by MASQUE ingress proxy above described.

Finally, the examples of this disclosure do not only apply to 5G network architecture, but the same mechanisms can be applied to 4G, just by replacing:

• PCF by PCRF

• UDR by SPR

• AMF by MME

• SMF by PGW-C or TDF-C

• UPF by PGW-U or TDF-U

Figure 13 shows an example of a communication system QQ100 in accordance with some embodiments. In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ102.

In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system QQ100 of Figure 13 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example illustrated in Figure 13, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

The hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 14 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), ve h i cl e-to- infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 14. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs). The processing circuitry QQ202 may be operable to provide, either alone or in conjunction with other UE QQ200 components, such as the memory QQ210, UE QQ200 functionality.

In the example, the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied. The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems. The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

In some embodiments, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence on the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 14.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. Figure 15 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). The network node QQ300 includes processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308, and/or any other component, or any combination thereof. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, network node QQ300 functionality. For example, the processing circuitry QQ302 may be configured to cause the network node to perform the methods as described with reference to any of Figures 4 to 7. In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

The memory QQ304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

The communication interface QQ306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310.

Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio frontend circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

The antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 15 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

Figure 16 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 13, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and 15, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Figure 17 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 0400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware QQ504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

Figure 18 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 13 and/or UE QQ200 of Figure 11), network node (such as network node QQ110a of Figure 13 and/or network node QQ300 of Figure 15), and host (such as host QQ116 of Figure 13 and/or host QQ400 of Figure 16) discussed in the preceding paragraphs will now be described with reference to Figure 18.

Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 13) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

This disclosure includes the following enumerated embodiments.

Embodiment 1. A method (400) performed by a first network node for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy, the method comprising: determining (402) a notification to be provided to the user of the UE; and causing (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE. Embodiment 2. The method of embodiment 1, wherein determining (402) a notification to be provided to the user of the UE comprises determining that a data usage allowance associated with the UE has been exceeded.

Embodiment 3. The method of embodiment 2, wherein determining that a data usage allowance associated with the UE has been exceeded comprises receiving data usage reports from a second network node.

Embodiment 4. The method of any of embodiments 1 to 3, wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control (PCC) rule or an update to a PCC rule.

Embodiment 5. The method of embodiment 4, wherein the PCC rule or the update to the PCC rule includes a user notification policy.

Embodiment 6. The method of embodiment 5, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier (URI) of notification information.

Embodiment 7. The method of any of embodiments 4 to 6, wherein the PCC rule or the update to the PCC rule is for a Protocol Data Unit (PDU) session of the UE.

Embodiment 8. The method of any of embodiments 4 to 7, wherein the first network node comprises a Policy Control Function (PCF).

Embodiment 9. The method of any of embodiments 3 to 8, wherein the second network node comprises a Session Management Function (SMF).

Embodiment 10. The method of embodiment 1, wherein determining (402) a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control (PCC) rule or an update to a PCC rule.

Embodiment 11. The method of embodiment 10, wherein the PCC rule or the update to the PCC rule includes a user notification policy. Embodiment 12. The method of embodiment 11, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier (URI) of notification information.

Embodiment 13. The method of embodiment 11 or 12, wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to a third network node.

Embodiment 14. The method of embodiment 13, wherein sending the user notification policy to the third network node comprises sending, to the third network node, an update for a Packet Forwarding Control Protocol (PFCP) for the UE and/or one or more Forwarding Action Rules (FARs) for the PFCP session.

Embodiment 15. The method of embodiment 13 or 14, wherein the third network node comprises a User Plane Function (UPF).

Embodiment 16. The method of any of embodiments 10 to 15, wherein the PCC rule or the update to the PCC rule is for a Protocol Data Unit (PDU) session of the UE.

Embodiment 17. The method of any of embodiments 10 to 16, wherein the second network node comprises a Policy Control Function (PCF).

Embodiment 18. The method of any of embodiments 10 to 17, wherein the first network node comprises a Session Management Function (SMF).

Embodiment 19. The method of embodiment 1, wherein determining (402) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy.

Embodiment 20. The method of embodiment 19, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier (URI) of notification information.

Embodiment 21. The method of embodiment 19 or 20, wherein receiving, from the second network node, the user notification policy comprises receiving, from the second network node, an update for a Packet Forwarding Control Protocol (PFCP) for the UE and/or one or more Forwarding Action Rules (FARs) for the PFCP session.

Embodiment 22. The method of any of embodiments 19 to 21 , wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

Embodiment 23. The method of any of embodiments 19 to 22, wherein the first network node comprises a User Plane Function (UPF).

Embodiment 24. The method of any of embodiments 19 to 24, wherein the second network node comprises a Session Management Function (SMF).

Embodiment 25. The method of embodiment 1, wherein determining (402) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy.

Embodiment 26. The method of embodiment 25, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier (URI) of notification information.

Embodiment 27. The method of embodiment 25 or 26, wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

Embodiment 28. The method of any of embodiments 25 to 27, wherein the message sent to the UE identifies the user notification policy. Embodiment 29. The method of any of embodiments 25 to 28, wherein the first network node comprises the ingress proxy and the second network node comprises a User Plane Function (UPF).

Embodiment 30. The method of any of embodiments 25 to 28, wherein the first network node comprises a User Plane Function (UPF) and the second network node comprises a Session Management Function (SMF).

Embodiment 31. The method of any of embodiments 1 to 30, comprising receiving, from the UE, an indication of whether the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or whether the notification will be provided to the user of the UE.

Embodiment 32. The method of embodiment 31 , wherein causing (404) the message to be sent, using the MASQUE connection, to the UE is performed in response to the indication indicating that the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or indicating that the notification will be provided to the user of the UE.

Embodiment 33. The method of embodiment 31 or 32, wherein the indication is received from the UE in a message for establishing the MASQUE connection to the ingress server.

Embodiment 34. The method of embodiment 33, wherein the message for establishing the MASQUE connection to the ingress server comprises a HTTP Connect message.

Embodiment 35. The method of any of embodiments 1 to 34, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

Embodiment 36. The method of any of embodiments 1 to 35, wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises causing a HTTP status code to be sent to the UE.

Embodiment 37. The method of embodiment 36, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE. Embodiment 38. The method of any of embodiments 1 to 37, wherein the UE has a further connection to an egress proxy.

Embodiment 39. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Embodiment 40. A method (500) performed by a User Equipment (UE) for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy, the method comprising: receiving (502), from a first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE; and providing (504) the notification to the user of the UE.

Embodiment 41. The method of embodiment 40, comprising receiving, from the first network node, a user notification policy.

Embodiment 42. The method of embodiment 41 , wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier (URI) of notification information.

Embodiment 43. The method of embodiment 41 or 42, wherein providing (504) the notification to the user of the UE comprises providing the notification to the user of the UE according to the user notification policy.

Embodiment 44. The method of any of embodiments 40 to 43, wherein the first network node comprises the ingress proxy or a User Plane Function (UPF).

Embodiment 45. The method of any of embodiments 40 to 44, comprising sending, to the first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE. Embodiment 46. The method of embodiment 45, wherein receiving (502), from the first network node, the message and/or providing the notification to the user of the UE is performed in response to the indication indicating that the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or indicating that the notification will be provided to the user of the UE.

Embodiment 47. The method of embodiment 45 or 46, wherein the indication is sent to the first network node in a message for establishing the MASQUE connection to the ingress server.

Embodiment 48. The method of embodiment 47, wherein the message for establishing the MASQUE connection to the ingress server comprises a HTTP Connect message.

Embodiment 49. The method of any of embodiments 40 to 48, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

Embodiment 50. The method of any of embodiments 40 to 49, wherein the message for causing the UE to provide the notification to the user of the UE comprises a HTTP status code.

Embodiment 51. The method of embodiment 50, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE.

Embodiment 52. The method of any of embodiments 40 to 52, wherein the UE has a further connection to an egress proxy.

Embodiment 53. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

Embodiment 54. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of embodiments 1 to 53. Embodiment 55. A carrier containing a computer program according to embodiment 54, wherein the carrier comprises one of an electronic signal, optical signal, radio signal or computer readable storage medium.

Embodiment 56. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to embodiment 54.

Embodiment 57. Apparatus in a first network node for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: determine (402) a notification to be provided to the user of the UE; and cause (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE.

Embodiment 58. The apparatus of embodiment 57, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (400) of any of embodiments 2 to 39.

Embodiment 59. Apparatus in a User Equipment (UE) for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: receive (502), from a first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE; and provide (504) the notification to the user of the UE.

Embodiment 60. The apparatus of embodiment 59, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (500) of any of embodiments 41 to 53.

Embodiment 61 . Apparatus in a first network node for causing a notification to be provided to a user of a User Equipment (UE), wherein the UE has a Multiplexed Application Substrate over QIIIC Encryption (MASQUE) connection to an ingress proxy, the apparatus configured to: determine (402) a notification to be provided to the user of the UE; and cause (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE.

Embodiment 62. The apparatus of embodiment 57, wherein the apparatus is configured to perform the method (400) of any of embodiments 2 to 39.

Embodiment 63. Apparatus in a User Equipment (UE) for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption (MASQUE) connection to an ingress proxy, the apparatus configured to: receive (502), from a first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE; and provide (504) the notification to the user of the UE.

Embodiment 64. The apparatus of embodiment 59, wherein the apparatus is configured to perform the method (500) of any of embodiments 41 to 53.

References

1. IETF RFC 9297 “HTTP Datagrams and the Capsule Protocol”

2. IETF RFC 9298 “Proxying UDP in HTTP”

3. IETF RFC 9114 “HTTP/3”

4. 3GPP TS 29.244 v18.0.1 (Dec 2022) “Interface between the Control Plane and the User Plane nodes”

5. 3GPP TS 29.512 v18.0.0 (Dec 2022) “5G System; Session Management Policy Control Service; Stage 3”

It should be noted that the above-mentioned examples illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative examples without departing from the scope of the appended statements. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the statements below. Where the terms, “first”, “second” etc. are used they are to be understood merely as labels for the convenient identification of a particular feature. In particular, they are not to be interpreted as describing the first or the second feature of a plurality of such features (i.e., the first or second of such features to occur in time or space) unless explicitly stated otherwise. Steps in the methods disclosed herein may be carried out in any order unless expressly otherwise stated. Any reference signs in the statements shall not be construed so as to limit their scope.

Claims

1. A method (400) performed by a Policy Control Function, PCF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, (MASQUE, connection to an ingress proxy, the method comprising: determining (402) a notification to be provided to the user of the UE; and causing (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule.

2. The method of claim 1, wherein determining (402) a notification to be provided to the user of the UE comprises determining that a data usage allowance associated with the UE has been exceeded.

3. The method of claim 2, wherein determining that a data usage allowance associated with the UE has been exceeded comprises receiving data usage reports from a second network node.

4. The method of any of claims 1 to 3, wherein the PCC rule or the update to the PCC rule includes a user notification policy.

5. The method of claim 4, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier, URI, of notification information.

6. The method of any of claims 1 to 5, wherein the PCC rule or the update to the PCC rule is for a Protocol Data Unit, PDU, session of the UE.

7. The method of any of claims 1 to 6, wherein the second network node comprises a Session Management Function, SMF.

8. The method of any of claims 1 to 7, comprising, before causing (404) the message to be sent, using the MASQUE connection, to the UE, obtaining, from a data storage node, an indication that the UE supports a capability of providing the notification to the user of the UE in response to the message sent using the MASQUE connection.

9. The method of claim 8, wherein the data storage node comprises a Unified Data Repository, UDR.

10. The method of any of claims 1 to 9, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

11. The method of any of claims 1 to 10, wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises causing a HTTP status code to be sent to the UE.

12. The method of claim 11, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE.

13. A method (500) performed by a Session Management Function, SMF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the method comprising: determining (502) a notification to be provided to the user of the UE; and causing (504) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (502) a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy; and wherein causing (504) the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

14. The method of claim 13, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier, URI, of notification information.

15. The method of claim 13 or 14, wherein sending the user notification policy to the third network node comprises sending, to the third network node, an update for a Packet Forwarding Control Protocol, PFCP, for the UE and/or one or more Forwarding Action Rules, FARs, for the PFCP session.

16. The method of any of claims 13 to 15, wherein the third network node comprises a User Plane Function, UPF, and/or the second network node comprises a Policy Control Function, PCF.

17. The method of any of claims 13 to 16, wherein the PCC rule or the update to the PCC rule is for a Protocol Data Unit, PDU, session of the UE.

18. The method of any of claims 13 to 17, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

19. The method of any of claims 13 to 18, wherein causing (504) the message to be sent, using the MASQUE connection, to the UE comprises causing a HTTP status code to be sent to the UE.

20. The method of claim 19, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE.

21. A method (600) performed by a User Plane Function, UPF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the method comprising: determining (602) a notification to be provided to the user of the UE; and causing (604) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (602) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy; and wherein causing (604) the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

22. The method of claim 21, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier, URI, of notification information.

23. The method of claim 21 or 22, wherein receiving, from the second network node, the user notification policy comprises receiving, from the second network node, an update for a Packet Forwarding Control Protocol, PFCP, for the UE and/or one or more Forwarding Action Rules, FARs, for the PFCP session.

24. The method of any of claims 21 to 23, wherein the second network node comprises a Session Management Function, SMF.

25. The method of any of claims 21 to 24, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

26. The method of any of claims 21 to 25, comprising receiving, from the UE, an indication of whether the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or whether the notification will be provided to the user of the UE.

27. The method of claim 26, wherein causing (604) the message to be sent, using the MASQUE connection, to the UE is performed in response to the indication indicating that the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or indicating that the notification will be provided to the user of the UE.

28. The method of claim 26 or 27, wherein the indication is received from the UE in a message for establishing the MASQUE connection to the ingress server.

29. The method of claim 28, wherein the message for establishing the MASQUE connection to the ingress server comprises a HTTP Connect message.

30. The method of any of claims 21 to 29, wherein causing (604) the message to be sent, using the MASQUE connection, to the UE comprises causing a HTTP status code to be sent to the UE.

31. The method of claim 30, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE.

32. A method (700) performed by an ingress proxy for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to the ingress proxy, the method comprising: determining (702) a notification to be provided to the user of the UE; and causing (704) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (702) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy; and wherein causing (704) the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

33. The method of claim 32, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier (URI) of notification information.

34. The method of claim 32 or 33 wherein the message sent to the UE identifies the user notification policy.

35. The method of any of claims 32 to 34, wherein the second network node comprises a User Plane Function, UPF.

36. The method of any of claims 32 to 35, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

37. The method of any of claims 32 to 36, comprising receiving, from the UE, an indication of whether the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or whether the notification will be provided to the user of the UE.

38. The method of claim 37, wherein causing (704) the message to be sent, using the MASQUE connection, to the UE is performed in response to the indication indicating that the user or the UE accepts messages sent, using the MASQUE connection, for causing the UE to provide notifications to the user of the UE, and/or indicating that the notification will be provided to the user of the UE.

39. The method of claim 37 or 38, wherein the indication is received from the UE in a message for establishing the MASQUE connection to the ingress server.

40. The method of claim 39, wherein the message for establishing the MASQUE connection to the ingress server comprises a HTTP Connect message.

41. The method of any of claims 32 to 40, wherein causing (704) the message to be sent, using the MASQUE connection, to the UE comprises causing a HTTP status code to be sent to the UE.

42. The method of claim 41, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE.

43. A method (800) performed by a User Equipment, UE, for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the method comprising: sending (802), to a first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE; receiving (804), from the first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE; and providing (806) the notification to the user of the UE.

44. The method of claim 43, wherein determining a notification to be provided to the user of the UE comprises receiving, from the first network node, a user notification policy.

45. The method of claim 44, wherein the user notification policy identifies one or more of: a message to be provided to the user of the UE; whether the notification is to be provided only once to the user of the UE; a network access policy for the UE; a Uniform Resource Identifier, URI, of notification information.

46. The method of claim 44 or 45, wherein providing (804) the notification to the user of the UE comprises providing the notification to the user of the UE according to the user notification policy.

47. The method of any of claims 43 to 46, wherein the first network node comprises the ingress proxy or a User Plane Function, UPF.

48. The method of any of claims 43 to 47, wherein receiving (802), from the first network node, the message and/or providing the notification to the user of the UE is performed in response to the indication indicating that the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or indicating that the notification will be provided to the user of the UE.

49. The method of any of claims 43 to 48, wherein the indication is sent to the first network node in a message for establishing the MASQUE connection to the ingress server.

50. The method of claim 49, wherein the message for establishing the MASQUE connection to the ingress server comprises a HTTP Connect message.

51. The method of any of claims 43 to 50, wherein the notification to the user of the UE comprises a notification that a data usage allowance associated with the UE has been exceeded and/or that the user of the UE will incur roaming charges.

52. The method of any of claims 43 to 51 , wherein the message for causing the UE to provide the notification to the user of the UE comprises a HTTP status code.

53. The method of claim 52, wherein the HTTP status code comprises a predetermined HTTP status code associated with providing the notification to the user of the UE.

54. The method of any of claims 43 to 53, wherein the UE has a further connection to an egress proxy.

55. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of claims 1 to 54.

56. A carrier containing a computer program according to claim 55, wherein the carrier comprises one of an electronic signal, optical signal, radio signal or computer readable storage medium.

57. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 55.

58. Apparatus in a Policy Control Function, PCF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: determine (402) a notification to be provided to the user of the UE; and cause (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule.

59. The apparatus of claim 58, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (400) of any of claims 2 to 12.

60. Apparatus in a Session Management Function, SMF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: determine (502) a notification to be provided to the user of the UE; and cause (504) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (502) a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy; and wherein causing (504) the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

61. The apparatus of claim 60, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (500) of any of claims 14 to 20.

62. Apparatus in a User Plane Function, UPF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: determine (602) a notification to be provided to the user of the UE; and cause (604) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (602) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy; and wherein causing (604) the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

63. The apparatus of claim 62, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (600) of any of claims 22 to 31.

64. Apparatus in an ingress proxy for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to the ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: determine (702) a notification to be provided to the user of the UE; and cause (704) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (702) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy; and wherein causing (704) the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

65. The apparatus of claim 64, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (700) of any of claims 33 to 42.

66. Apparatus in a User Equipment, UE, for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: send (802), to a first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE; receive (804), from the first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE; and provide (806) the notification to the user of the UE.

67. The apparatus of claim 66, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method (800) of any of claims 44 to 54.

68. Apparatus in a Policy Control Function, PCF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus configured to: determine (402) a notification to be provided to the user of the UE; and cause (404) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein causing (404) the message to be sent, using the MASQUE connection, to the UE comprises sending, to a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule.

69. The apparatus of claim 68, wherein the apparatus is configured to perform the method (400) of any of claims 2 to 12.

70. Apparatus in a Session Management Function, SMF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus configured to: determine (502) a notification to be provided to the user of the UE; and cause (504) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (502) a notification to be provided to the user of the UE comprises receiving, from a second network node, a Policy and Charging Control, PCC, rule or an update to a PCC rule, wherein the PCC rule or the update to the PCC rule includes a user notification policy; and wherein causing (504) the message to be sent, using the MASQUE connection, to the UE comprises sending a user notification policy to a third network node.

71. The apparatus of claim 70, wherein the apparatus is configured to perform the method (400) of any of claims 14 to 20.

72. Apparatus in a User Plane Function, UPF, for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus configured to: determine (602) a notification to be provided to the user of the UE; and cause (604) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (602) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy; and wherein causing (604) the message to be sent, using the MASQUE connection, to the UE comprises sending the user notification policy to the ingress proxy.

73. The apparatus of claim 72, wherein the apparatus is configured to perform the method (600) of any of claims 22 to 31.

74. Apparatus in an ingress proxy for causing a notification to be provided to a user of a User Equipment, UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to the ingress proxy, the apparatus configured to: determine (702) a notification to be provided to the user of the UE; and cause (704) a message to be sent, using the MASQUE connection, to the UE, wherein the message causes the UE to provide the notification to the user of the UE; wherein determining (702) a notification to be provided to the user of the UE comprises receiving, from a second network node, a user notification policy; and wherein causing (704) the message to be sent, using the MASQUE connection, to the UE comprises sending the message to the UE according to the user notification policy.

75. The apparatus of claim 74, wherein the apparatus is configured to perform the method (400) of any of claims 33 to 42.

76. Apparatus in a User Equipment, UE, for providing a notification to a user of the UE, wherein the UE has a Multiplexed Application Substrate over QUIC Encryption, MASQUE, connection to an ingress proxy, the apparatus configured to: send (802), to a first network node, an indication of whether the user or the UE accepts messages from the first network node, using the MASQUE connection, for causing the UE to provide the notification to the user of the UE, and/or whether the notification will be provided to the user of the UE; receive (804), from the first network node, using the MASQUE connection, a message for causing the UE to provide the notification to the user of the UE; and provide (806) the notification to the user of the UE.

77. The apparatus of claim 76, wherein the apparatus is configured to perform the method (800) of any of claims 44 to 54.