Patent Description:
In a typical wireless communication network, user equipment (UE), also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks belonging to different network operators. The RAN covers a geographical area which is divided into areas or cell areas, with each area or cell area being served by a radio network node, e.g., a Wi-Fi access point or a Radio Base Station (RBS), which in some networks may also be called, for example, a NodeB, eNodeB or a gNodeB. The area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the UE within range of the radio network node.

A Universal Mobile Telecommunications System (UMTS) is a third generation telecommunication network, which evolved from the second generation (<NUM>) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN using Wideband Code Division Multiple Access (WCDMA) and/or High Speed Packet Access (HSPA) for user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for third generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a Radio Network Controller (RNC) or a Base Station Controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and this work continues in the coming 3GPP releases. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a variant of a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs. In general, in E-UTRAN/LTE the functions of an RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially "flat" architecture comprising radio network nodes which can be connected directly to one or more core networks, i.e. they do not need to be connected to the core via RNCs.

With the emerging <NUM> technologies such as New Radio (NR), the use of a large number of transmit- and receive-antenna elements is of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify received signals coming from a selected direction or directions, while suppressing received unwanted signals coming from other directions.

<FIG> depicts various nodes in a <NUM> reference network architecture as defined by 3GPP. Some architectural nodes and aspects in <FIG> that are relevant to this description include: Application Function (AF), Network Exposure Function (NEF), Policy Control Function (PCF), Session Management Function (SMF), User Plane Function (UPF) and Access and Mobility management Function (AMF).

The Application Function (AF) may interact with the 3GPP Core Network, and specifically when referred to in this disclosure, the AF may provision information to a network operator and to subscribe to certain events happening in an operator's network.

The Network Exposure Function (NEF) may support different functionality and as mentioned in this disclosure, the NEF may act as an entry point into the operator's network, so that the AF may interact with the 3GPP Core Network through the NEF.

The Policy Control Function (PCF) may support unified policy framework to govern the network behavior. For example in this disclosure, the PCF may provide PCC rules to the SMF.

The Session Management Function (SMF) may support different functionality, e.g. in this disclosure, the SMF may configure the UPF, e.g. for event reporting. The User Plane Function (UPF) may support handling of user plane traffic based on rules received from the SMF. For example in this disclosure, the UPF may handle packet inspection and different enforcement actions, e.g. event detection and reporting).

The AMF may receive all connection and session related information from the UE, e.g. via interface N1 or N2, but the AMF is responsible mainly for handling connection and mobility management tasks.

3GPP TS <NUM> defines the services offered by the AMF to other Network Functions (NF).

A Network Data Analytics Function (NWDAF) may represent an operator managed network analytics logical function. The NWDAF is part of the architecture specified in 3GPP TS <NUM> and may use various mechanisms and interfaces specified for 5GC and Operations Administration and Maintenance (OAM).

The NWDAF may interact with different entities for different purposes such as:.

It will now be described how optimization of user plane traffic can be addressed according to existing procedures.

There are multiple traffic algorithms to optimize the user plane traffic payload which contribute to improve the Quality of Experience (QoE) and ensure the required Quality of Service (QoS):.

Some available congestion mechanisms include: TCP Cubic, BBR, TCP Reno, TCP New Reno, TCP Tahoe and Yeah.

The above-mentioned <NUM> New Radio (NR) will now be discussed.

Previous releases, e.g. <NUM>, <NUM>, <NUM>, can be useful in the same portions of the spectrum, e.g. with reorganized frequency bands. The <NUM> frequency band plans are more complex, as the frequency spectrum for sub-<NUM> <NUM> spans from <NUM> to <NUM>, and millimeter-wave <NUM> frequencies span from <NUM> to <NUM>, and also include unlicensed spectrum.

According to 3GPP TS <NUM>-<NUM> the frequency ranges in which NR can operate according to this version of the specifications are identified as shown in Table <NUM> below.

Accordingly, the congestion control schemes in prior art are not completely equipped to handle the highly volatile millimetre Wave (mmWave). The mmWawe spectrum refers to a band of spectrum between <NUM> and <NUM> channels. A common congestion control protocol that can be used for most of the expected data traffic is TCP Cubic. TCP Cubic treats packet loss as the signal for congestion in the network. When introducing link outages and capacity variations, which are fairly common in mmWave channels, TCP Cubic fails. When bottleneck buffers are large, loss-based congestion control, like TCP Cubic, keeps the buffers full, causing so-called buffer bloat, and when the buffers are small, loss-based congestion control can further reduce throughput by multiplicative decrease depending on packet loss. If a greater amount of packet loss occurs, throughput will be reduced.

The role and purpose of congestion control is to regulate the amount of injected traffic in the network according to its congestion state. However, in wireless communications, traditional congestion control protocols, such as TCP New Reno, are unable to differentiate between losses attributed to congestion and those attributed to transmission errors caused by a decay in channel quality.

Radio Link Control (RLC) buffer size may scale proportionally to Bandwidth-Delay Product (BDP) to achieve maximum TCP goodput, i.e. throughput of useful data. However, it is very challenging to properly dimension the buffers for mmWave links, given the rapid bandwidth variations between Line-Of-Sight (LOS) and Non-Line-Of-Sight (NLOS) conditions, and to protect from link losses without introducing buffer bloat.

<CIT> relates to AF protocol data unit (PDU) session management and subscription procedures. A method for PDU session management includes initiating a PDU session for an AF within an application server (AS) that is not part of a cellular network and sending configuration information to a network exposer function (NEF) to communicate directly with a network function (NF) of the cellular network to provide services for the PDU session. The method additionally includes receiving authorization from the NEF and communicating directly with the cellular network NF to provide the PDU services during the PDU session.

The present invention is defined by the subject-matter of independent claims <NUM>, <NUM>, <NUM>, <NUM> and <NUM> that enables how to handle communication in a communication network in an efficient manner. Further detailed embodiments are defined in the dependent claims.

According to a first aspect of embodiments herein, the object is achieved by a method performed an AF node for handling a data session for a UE in a communication network. The AF node obtains information about usage of a first frequency for the UE from an AMF node. The AF node then applies a first congestion mechanism based on the obtained information about usage of the first frequency. The AF node further obtains information about usage of a second frequency for the UE from the AMF node. The AF node then further applies a second congestion mechanism in response to the obtained information about usage of the second frequency.

According to another aspect of embodiments herein, the object is achieved by a method performed by an AMF node for handling a data session for a UE in a communication network. The AMF node provides information about usage of a first frequency for the UE to an AF node. The AMF node then detects that usage of the frequency of the UE changes. The AMF node further provides information about usage of a second frequency for the UE to the AF node.

According to yet another aspect of embodiments herein, the object is achieved by an AF node for handling a data session for a UE in a communication network. The AF node is configured to obtain information about usage of a first frequency for the UE from an AMF node. The AF node is further configured to apply a first congestion mechanism based on the obtained information about usage of the first frequency. The AF node is further configured to obtain information about usage of a second frequency for the UE from the AMF node. The AF node is further configured to apply a second congestion mechanism in response to the obtained information about usage of the second frequency.

According to still another aspect of embodiments herein, the object is achieved by an AMF node for handling a data session of a UE in a communication network. The AMF node is configured to provide information about usage of a first frequency for the UE to an AF node. The AMF node is further configured to detect that usage of the frequency of the UE changes. The AMF node is further configured to provide information about usage of a second frequency for the UE to the AF node.

According to another aspect of embodiments herein, the object is achieved by a system for handling a data session for a UE in a communication network.

It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method above, as performed by the network node or the UE. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the method above, as performed by the network node or the UE.

With the realisation that by obtaining information about usage of a first frequency for the UE from an AMF node, the AF node can apply a first congestion mechanism based on the obtained information about usage of the first frequency. By obtaining information about usage of a second frequency for the UE from the AMF node, the AF node can apply a second congestion mechanism in response to the obtained information about usage of the second frequency. Thereby the communication in the wireless communications network in handled in an efficient matter.

<FIG> is a schematic overview depicting a communications network <NUM> wherein embodiments herein may be implemented. The communication network <NUM> is able to provide wireless services for communication devices e.g. a User Equipment (UE) <NUM>, such as a mobile station, a non-access point (non-AP) STA, a STA, a wireless device and/or a wireless terminal. It should be understood by those skilled in the art that "UE" is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Internet of Things operable device, Device to Device (D2D) terminal, mobile device e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or any device communicating within a cell or service area.

Network nodes operate in the core network, such as an Application Function node (AF) <NUM>, an Access and Mobility management Function node (AMF) <NUM>, a Network Exposure Function node (NEF) <NUM> and a User Plane Function (UPF) node <NUM>. These nodes have basically the following functions and tasks.

The AF node <NUM> may support application influence on traffic routing, accessing NEF, interaction with policy framework for policy control.

The AMF node <NUM> may support termination of Non-access stratum (NAS) signalling, NAS ciphering and integrity protection, registration management, connection management, mobility management, access authentication and authorization and security context management.

The NEF node <NUM> may support exposure of capabilities and events, secure provision of information from external application to 3GPP network and translation of internal/external information.

The UPF node <NUM> may support packet routing and forwarding, packet inspection, Quality of Service (QoS) handling and may be an anchor point for intra- and inter-RAT mobility.

There are also network nodes, in addition to those cited above, for providing radio coverage over a geographical area by means of antenna beams. The geographical area may be referred to as a cell, a service area, beam or a group of beams. These network nodes may in this case be a transmission and reception point e.g. a radio access network node such as a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE within the cell <NUM> served by the radio network node <NUM> depending e.g. on the radio access technology and terminology used.

The procedures and activities according to embodiments herein are chiefly performed by the AF node <NUM> and the AMF node <NUM>, as described herein. The communications network <NUM> may use <NUM> NR for radio access but may further use a number of other different technologies, such as, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

The communication network <NUM> comprises one or more CNs <NUM> and one or more RANs <NUM>. The UE <NUM> is connected via one or more RANs <NUM>, to the one or more CNs <NUM>.

As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud <NUM> as shown in <FIG> may be used for performing or partly performing the methods.

In an example scenario of the handling of a data session for the UE <NUM> in the communication network <NUM> the AF node <NUM> may subscribe to changes in the radio frequency by subscribing to radio frequency events in the AMF node <NUM> through the NEF node <NUM>. Radio frequency events may relate to access mobility of the UE <NUM> such as location changes, the UE <NUM> moving in or out of a subscribed area of interest, time zone changes, access type changes, registration state changes, connectivity state changes, UE <NUM> loss of communication and UE <NUM> reachability status. The AMF node <NUM> may thereby send information about those events to the AF node <NUM>, via the NEF node <NUM>, so that the AF node <NUM> can apply the corresponding congestion window based on this information.

An example of how a data session could be handled for the UE <NUM> in the communication network <NUM> will now be described with reference to <FIG>, thereafter methods will be described from the view of the AF node <NUM> and AMF node <NUM> respectively with reference to <FIG> and <FIG>. <FIG> is a combined signalling scheme and flowchart of a procedure where some embodiments herein are used. The method e.g. comprises the following actions:.

Example embodiments of a method performed by the AF node <NUM> for handling the data session for the UE <NUM> in the communication network <NUM> will now be described with reference to a flowchart depicted in <FIG>. The method comprises the following actions, which actions may be taken in any suitable order.

The AF node <NUM> obtains information about usage of the first frequency for the UE <NUM> from the AMF node <NUM>. The AF node <NUM> and the AMF node <NUM> may communicate via the NEF node <NUM>. The obtaining information about usage of the first frequency may comprise transmitting, towards the NEF node <NUM>, the subscription request to the UE frequency event, and receiving, from the NEF node <NUM>, information about usage of the first frequency for the UE <NUM>. The subscription request may comprise the UE identifier and the event identifier. This action corresponds to the above actions <NUM> and <NUM>.

The AF node <NUM> then applies the first congestion mechanism based on the obtained information about usage of the first frequency. This action corresponds to the above action <NUM>.

The AF node <NUM> obtains information about usage of the second frequency for the UE <NUM> from the AMF node <NUM>. The obtaining information about usage of the second frequency for the UE <NUM> may comprise receiving, from the NEF node <NUM>, information about usage of the second frequency for the UE <NUM>. This action corresponds to the above action <NUM>.

The AF node <NUM> then applies the second congestion mechanism in response to the obtained information about usage of the second frequency. This action corresponds to the above action <NUM>.

Example embodiments of a method performed by the AMF node <NUM> for handling the data session for the UE <NUM> in the communication network <NUM> will now be described with reference to a flowchart depicted in <FIG>. The method comprises the following actions, which actions may be taken in any suitable order.

The AMF node <NUM> may receive, from the NEF node <NUM>, a subscription request to a UE frequency event. The subscription request may comprise the UE identifier and the event identifier. This action corresponds to the above action <NUM>.

The AMF node <NUM> provides information about usage of the first frequency for the UE <NUM> to the AF node <NUM>. As mentioned before, the AF node <NUM> and the AMF node <NUM> may communicate via the NEF node <NUM>. The providing information about usage of the first frequency may comprise transmitting, towards the NEF node <NUM>, information about usage of the first frequency for the UE <NUM>. This action corresponds to the above action <NUM> and <NUM>.

The AMF node <NUM> detects that usage of the frequency of the UE <NUM> changes. This action corresponds to the action <NUM>.

The AMF node <NUM> provides information about usage of the second frequency for the UE <NUM> to the AF node <NUM>. The providing information about usage of the second frequency may comprise transmitting, towards the NEF node <NUM>, information about usage of the second frequency for the UE <NUM>. This action corresponds to the above action <NUM> and <NUM>.

Embodiments herein such as mentioned above will now be further described and exemplified. The text below is applicable to and may be combined with any suitable embodiment described above.

An, example of a method according to some embodiments, is shown in the combined signalling scheme and flowchart of <FIG> illustrates the example where the AF node <NUM> subscribes to the UE frequency event and comprises the steps <NUM>-<NUM> where the order of the steps may vary in different implementations:
Preconditions: The UE <NUM> has a PDU session already established. A single UE <NUM> is shown for the sake of simplicity.

Step <NUM>. The AF node <NUM> which may be a content provider such as e.g. Vimeo, may subscribe to the UE frequency. In order to do so, it triggers a Nnef_AnalyticsExposure Subscribe (HTTP POST) message including the following information:.

The AF node <NUM> subscribes to changes of the frequency of the UE <NUM>, e.g. the subscriber's frequency. The AF node <NUM> has different congestion schemes according to the frequency of the UE <NUM>. One congestion window for FR1 and for FR2, as was shown in Table <NUM> above.

Step <NUM>. The NEF node <NUM> may answer the AF node <NUM> with a Nnef_AnalyticsExposure <NUM> OK message.

Step <NUM>-<NUM>. Optionally, in case the NEF node <NUM> does not know the AMF node <NUM> to which the UE <NUM> is attached, the NEF node <NUM> can request for the AMF node <NUM> from a Unified Data Repository (UDR). The UDR is a converged repository of subscriber information and can be used to service a number of network functions. The UDR may then respond with the AMF node <NUM>.

Step <NUM>. The NEF node may subscribe to changes of frequency in the AMF node <NUM> using the Namf_EventExposureService with an event called Frequency. The AMF node <NUM> may provide a new event to be provided by Namf_EventExposure Service.

The definition of this event is the following:
Event: Frequency.

A Network Function (NF) may subscribe to the event Frequency to receive the event report of a UE or group of UEs when an AMF detects that a target UE has changed the frequency, by default the so-called arfcnDL parameter in accordance with 3GPP TS <NUM>.

Step <NUM>. The AMF node <NUM> may answer to the NEF node <NUM> e.g. with frequency band FR1, FR2 or values provided by arfcnDL.

Step <NUM>. The AMF node <NUM> notifies the frequency of the UE <NUM>. In this example in <FIG> the frequency of the UE120 is FR1, not mmWave.

Step <NUM>. The NEF node <NUM> may notify the AF node <NUM> of the UE identifier, e.g. UE-ID, and the frequency band of the UE <NUM>. Optionally, the NEF node <NUM> may provide a recommended congestion window with some parameters. In this particular case, the congestion mechanism TCP cubic with an initial congestion window = <NUM>. The AF may apply the TCP Cubic congestion mechanism due to that the UE <NUM> is using this frequency.

Step <NUM>. The UE <NUM> enters in a zone where high frequency, such as mmWave, is provided or the radio network provides a higher frequency, so the UE <NUM> changes from FR1 to FR <NUM> frequency. The AMF node <NUM> notifies to NEF node <NUM> of the new frequency of the UE <NUM>. In this example it is FR2.

Step <NUM>. The NEF node <NUM> may notify the AF node <NUM> of the frequency band of the UE <NUM>. Optionally, the NEF node <NUM> can provide the best recommended congestion window with some parameters. In this particular case, the congestion mechanism Yeah with an initial congestion window = r0. The AF node <NUM> may apply, e.g. the congestion mechanism Yeah, due to that the UE <NUM> is using this frequency band. The Yeah congestion mechanism is used as it may be better in mmWave scenarios.

The AMF node <NUM> may send information about those events to the UPF node <NUM> so that the UPF node can apply corresponding optimizations based on this information.

Another example according to some embodiments is shown in the combined signalling scheme and flowchart in <FIG> and <FIG>, where <FIG> is a continuation of <FIG> and <FIG> concern a case where the UPF node <NUM> subscribes to a UE frequency event and comprises the steps as described below. <FIG> and <FIG> comprise the steps <NUM>-<NUM> where the order of the steps may vary in different implementations.

Precondition: An optimization information storage/retrieval policy may be pre-configured in the UDR as subscriber policy data, e.g. UE <NUM> policy data. This example shows per subscriber policies, but this flow information storage policy may also be applied to a certain application, to a group of UEs, e.g. subscribers, to a certain network slice or globally e.g. on a per node or network basis. In this example the behaviour in case handover occurs in a traffic optimization, is shown.

Steps <NUM>-<NUM>. At a Packet Forwarding Control Protocol (PFCP) Association procedure between UPF and SMF entities, it is proposed to extend the existing mechanism to report UPF capabilities with a new capability Frequency Information for Optimization (FIOP), see Table <NUM> below in bold).

Step <NUM>. The UE <NUM> may trigger a PDU session establishment, by means of sending a PDU Session Establishment Request to the AMF node <NUM>.

Step <NUM>. The AMF node <NUM> may select an SMF to manage the PDU session, the SMF selection function in the AMF node <NUM> selects an SMF instance based on the available SMF instances obtained from NRF or on the configured SMF information in the AMF node <NUM>, and triggers a Nsmf PDU Session Create message.

Step <NUM>. The SMF may trigger an Npcf_SMPolicyControl_Create Request message to retrieve Session Management (SM) policies for the user PDU session.

Step <NUM>) The PCF triggers a so-called Nudr_Query Request message, including a subscriber identifier, e.g. UE identifier, to retrieve the policy data for the UE's <NUM> PDU session.

Step <NUM>. The UDR answers with a Nudr_Query Response message, including the Subscriber Policy Data, which includes a new handover information for optimization policies. As an example, a binary flag as handover information policies may be assumed:.

This value may be extended with more granular information in case it is needed to check frequency at other levels such as Radio Resource Unit (RRU) set of NG-RAN nodes, etc..

In <FIG> and <FIG> it may be assumed that optimization will be performed at the UPF node <NUM>. This example also assumes the optimization with frequency information policy applied on a per subscriber's PDU session basis. It is also possible to configure different optimization with frequency information policies for each application.

Step <NUM>. The PCF may generate the corresponding PCC rule/s based on Subscriber Policy Data, and may also include the optimization with handover information (TRUE), which in this example applies on a per PDU session basis.

Step <NUM>. The SMF may select the UPF and triggers a PFCP Session Establishment procedure towards the UPF to provision Packet Detection Rules (PDRs), and the corresponding enforcement actions: QoS Enforcement Rule (QER) Forwarding Action Rules (FARs), Usage Reporting Rules (URRs), etc., for the PDU session. Specifically, the SMF may provision the handover information. In order to do this, it is proposed to extend the PFCP protocol by adding a new "Frequency Information" IE at "PFCP Session Establishment/Modification Request", as shown in Table <NUM> and Table <NUM> below in bold:.

There may be similar attributes for a session modification message.

Step <NUM>. The SMF answers to the AMF node <NUM> request.

Step <NUM>. The UE <NUM> has a PDU session established.

Steps <NUM>-<NUM>. Optionally, in case the UPF node <NUM> does not know the AMF node <NUM> to which the UE <NUM> is attached, the UPF node <NUM> may ask for the AMF node <NUM> from the UDR. The UDR may then answer with the AMF node <NUM>.

Step <NUM>. The UPF node <NUM> may subscribe to the Namf_EventExposure Service. In this case, a new event is exposed with this service. It is the handover of cells performed by the UE <NUM>. The definition of this event is the following:
The AMF node <NUM> may provide a new event to be provided by Namf_EventExposure Service.

An NF subscribes to this event to receive the event report of a UE or group of UEs when the AMF node <NUM> detects that a target UE has changed the frequency, by default the arfcnDL parameter, as described in 3GPP TS <NUM>.

Step <NUM>. The AMF node <NUM> may confirm that the subscription is correct.

Step <NUM>. The AMF may notify that the UE <NUM> has changed the frequency, using the Namf_EventExposure Service. The UPF node <NUM> may adapt its optimization to this UE <NUM> based on this information, such as e.g. modifying its buffer size or changing parameters in the AQM algorithm.

<FIG> is a block diagram depicting the AF node <NUM> for handling the data session for the UE <NUM> in the communication network <NUM>, according to embodiments herein.

The AF node <NUM> may comprise processing circuitry <NUM>, e.g. one or more processors, configured to perform the methods herein.

The AF node <NUM> may comprise an obtaining unit <NUM>. The AF node <NUM>, the processing circuitry <NUM>, and/or the obtaining unit <NUM> is configured to obtain information about usage of the first frequency for the UE <NUM> from the AMF node <NUM>.

The AF node <NUM> and the AMF node <NUM> may communicate via the NEF node <NUM>.

The obtaining information about usage of the first frequency may be adapted to comprise to transmit, towards the NEF node <NUM>, the subscription request to the UE frequency event, wherein the subscription request comprises the UE identifier and the event identifier, and to receive, from the NEF node <NUM>, information about usage of the first frequency for the UE <NUM>.

The AF node <NUM>, the processing circuitry <NUM>, and/or the obtaining unit <NUM> is configured to obtain information about usage of the second frequency for the UE <NUM> from the AMF node <NUM>. The obtaining information about usage of the second frequency for the UE <NUM> may be adapted to comprise to receive, from the NEF node <NUM>, information about usage of the second frequency for the UE <NUM>.

The AF node <NUM> may comprise an applying unit <NUM>. The AF node <NUM>, the processing circuitry <NUM>, and/or the applying unit <NUM> is configured to apply the first congestion mechanism based on the obtained information about usage of the first frequency of the UE <NUM>.

The AF node <NUM>, the processing circuitry <NUM>, and/or the applying unit <NUM> is configured to apply the second congestion mechanism in response to the obtained information about usage of the second frequency of the UE <NUM>.

The AF node <NUM> further comprises a memory <NUM>. The memory <NUM> comprises one or more units to be used to store data on, such as frequency information, UE identifier and event identifier information, input/output data, metadata, etc. and applications to perform the methods disclosed herein when being executed, and similar. The AF node <NUM> may further comprise a communication interface comprising e.g. one or more antenna or antenna elements.

The methods according to the embodiments described herein for the AF node <NUM> are respectively implemented by means of e.g. a computer program product <NUM> or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the AF node <NUM>. The computer program product <NUM> may be stored on a computer-readable storage medium <NUM>, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium <NUM>, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the AF node <NUM>. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.

<FIG> is a block diagram depicting the AMF node <NUM> for handling the data session for the UE <NUM> in the communication network <NUM>, according to embodiments herein.

The AMF node <NUM> may comprise processing circuitry <NUM>, e.g. one or more processors, configured to perform the methods herein.

The AMF node <NUM> may comprise a receiving unit <NUM>. The AMF node <NUM>, the processing circuitry <NUM>, and/or the receiving unit <NUM> may be configured to receive from the NEF node <NUM>, the subscription request to the UE frequency event, wherein the subscription request comprises the UE identifier and the event identifier.

The AMF node <NUM> may comprise a providing unit <NUM>. The AMF node <NUM>, the processing circuitry <NUM>, and/or the providing unit <NUM> is configured to provide information about usage of the first frequency for the UE to the AF node <NUM>.

The providing information about usage of the first frequency may be adapted to comprise to transmit, towards the NEF node <NUM>, information about usage of the first frequency.

The AMF node <NUM>, the processing circuitry <NUM>, and/or the providing unit <NUM> is configured to provide information about usage of the second frequency for the UE <NUM> to the AF node <NUM>. The providing information about usage of the second frequency may be adapted to comprise to transmit, towards the NEF node <NUM>, information about usage of the second frequency.

The AMF node <NUM> may comprise a detecting unit <NUM>. The AMF node <NUM>, the processing circuitry <NUM>, and/or the detecting unit <NUM> is configured to detect that usage of the frequency of the UE <NUM> changes.

The AMF node <NUM> further comprises a memory <NUM>. The memory <NUM> comprises one or more units to be used to store data on, such as frequency information, UE identifier and event identifier information, input/output data, metadata, etc. and applications to perform the methods disclosed herein when being executed, and similar. The AMF node <NUM> may further comprise a communication interface comprising e.g. one or more antenna or antenna elements.

The methods according to the embodiments described herein for the AMF node <NUM> are respectively implemented by means of e.g. a computer program product <NUM> or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the AMF node <NUM>. The computer program product <NUM> may be stored on a computer-readable storage medium <NUM>, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium <NUM>, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the AMF node <NUM>. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.

The system for handling a data session for the UE <NUM> in the communication network <NUM> is illustrated in <FIG>. The system may comprise the AF node <NUM> and the AMF node <NUM>, shown in <FIG> and <FIG> respectively. The system may also comprise the UPF node <NUM>. The UPF node <NUM> may comprise processing circuitry <NUM>, e.g. one or more processors, configured to perform the methods herein.

The UPF node <NUM> may comprise a transmitting unit <NUM>. The UPF node <NUM>, the processing circuitry <NUM>, and/or the transmitting unit <NUM> may be configured to transmit, towards the AMF node <NUM>, a subscription request to a UE frequency event, wherein the subscription request comprises a UE identifier and an event identifier.

The UPF node <NUM> may comprise an obtaining unit <NUM>. The UPF node <NUM>, the processing circuitry <NUM>, and/or the obtaining unit <NUM> may be configured to obtain, from the AMF node <NUM>, information about usage of the frequency for the UE <NUM>.

The UPF node <NUM> may comprise an optimizing unit <NUM>. The UPF node <NUM>, the processing circuitry <NUM>, and/or the optimizing unit <NUM> may be configured to optimize UE traffic in accordance with the received information about usage of the frequency for the UE <NUM>.

In some embodiments a more general term "network node" is used and it can correspond to any type of radio-network node or any network node, which communicates with a wireless device and/or with another network node. Examples of network nodes are gNodeB, eNodeB, NodeB, MeNB, SeNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc..

In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc..

Embodiments are applicable to any radio access technology (RAT) or multi-RAT systems, where the devices receives and/or transmit signals, e.g. data, such as New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a UE or network node, for example.

Alternatively, several of the functional elements of the processing units discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term "processor" or "controller" as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and/or program or application data. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

With reference to <FIG>, in accordance with an embodiment, a communication system includes a telecommunication network <NUM> such as the wireless communications network <NUM>, e.g. a NR network, such as a 3GPP-type cellular network, which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of base stations 3212a, 3212b, 3212c, such as the radio network node <NUM>, access nodes, AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first user equipment (UE) e.g. the wireless devices <NUM> such as a Non-AP STA <NUM> located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE <NUM> e.g. the first or second radio node <NUM>, <NUM> or such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a.

The host computer <NUM> and the connected UEs <NUM>, <NUM> are configured to communicate data and/or signalling via the OTT connection <NUM>, using the access network <NUM>, the core network <NUM>, any intermediate network <NUM> and possible further infrastructure (not shown) as intermediaries.

The wireless connection <NUM> between the UE <NUM> and the base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and power consumption and thereby provide benefits such as user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.

In certain embodiments, measurements may involve proprietary UE signalling facilitating the host computer's <NUM> measurements of throughput, propagation times, latency and the like.

The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to <FIG> and <FIG>. In a first action <NUM> of the method, the host computer provides user data. In an optional subaction <NUM> of the first action <NUM>, the host computer provides the user data by executing a host application. In a second action <NUM>, the host computer initiates a transmission carrying the user data to the UE. In an optional third action <NUM>, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth action <NUM>, the UE executes a client application associated with the host application executed by the host computer.

The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to <FIG> and <FIG>. In a first action <NUM> of the method, the host computer provides user data. In an optional subaction (not shown) the host computer provides the user data by executing a host application. In a second action <NUM>, the host computer initiates a transmission carrying the user data to the UE. In an optional third action <NUM>, the UE receives the user data carried in the transmission.

The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to <FIG> and <FIG>. In an optional first action <NUM> of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second action <NUM>, the UE provides user data. In an optional subaction <NUM> of the second action <NUM>, the UE provides the user data by executing a client application. In a further optional subaction <NUM> of the first action <NUM>, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third subaction <NUM>, transmission of the user data to the host computer. In a fourth action <NUM> of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to <FIG> and <FIG>. In an optional first action <NUM> of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second action <NUM>, the base station initiates transmission of the received user data to the host computer. In a third action <NUM>, the host computer receives the user data carried in the transmission initiated by the base station.

Claim 1:
A method performed by an Application Function, AF, node (<NUM>), for handling a data session for a User Equipment, UE, (<NUM>) in a communication network (<NUM>), the method comprising:
obtaining (<NUM>) information about usage of a first frequency for the UE from an Access and Mobility management Function, AMF, node (<NUM>);
the method characterized in:
applying (<NUM>) a first congestion mechanism based on the obtained information about usage of the first frequency;
obtaining (<NUM>) information about usage of a second frequency for the UE from the AMF node (<NUM>), wherein the information about usage of the second frequency comprises a detected changed UE frequency; and
applying (<NUM>) a second congestion mechanism in response to the obtained information about usage of the second frequency.