Application function node, access and mobility management function node, system and method in a communication network

Abstract

A method performed by an application function, AF, node (131) for handling a data session of a user equipment, UE, (120) in a communications network. The AF node obtains, from an access and mobility management function, AMF, node (132), information about usage of a first frequency of the UE. 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, from the AMF node, information about usage of a second frequency of the UE. The AF node then applies a second congestion mechanism in response to the obtained information about usage of the second frequency.

Description

Technical Field

[0001] The embodiments described herein relate to application function nodes, access and mobility management function nodes, systems, and methods therein. Specifically, they relate to processing data sessions in a communication network. Background Technology

[0002] In a typical wireless communication network, User Equipment (UE) (also referred to as wireless communication device, mobile station, site (STA), and / or wireless device) communicates with one or more core networks belonging to different network operators via a Radio Access Network (RAN). RAN coverage is divided into geographical areas of regions or cell areas, each serviced by a radio network node (e.g., a Wi-Fi access point or radio base station (RBS)). In some networks, radio network nodes may also be referred to as, for example, NodeB, eNodeB, or gNodeB. A region or cell area is a geographical area where radio coverage is provided by a radio network node. Radio network nodes communicate with UEs within their range via an air interface operating on radio frequencies.

[0003] Universal Mobile Telecommunications System (UMTS) is a third-generation telecommunications network evolved from the second-generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN for user equipment using Wideband Code Division Multiple Access (WCDMA) and / or High-Speed ​​Packet Access (HSPA). In a forum known as the 3rd Generation Partnership Project (3GPP), telecommunications providers propose and agree on standards for third-generation networks, particularly UTRAN standards, and investigate enhanced data rates and radio capacity. In some RANs, such as those in UMTS, several radio network nodes can connect (e.g., via terrestrial lines or microwave) to a controller node (e.g., a Radio Network Controller (RNC) or Base Station Controller (BSC)). The controller node monitors and coordinates the various activities of the multiple radio network nodes connected to it. The RNC is typically connected to one or more core networks.

[0004] Specifications for Evolved Packet Systems (EPS) have been completed within 3GPP, and this work continues in future 3GPP releases. EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) (also known as Long Term Evolution (LTE) Radio Access Network) and the Evolved Packet Core (EPC) (also known as the System Architecture Evolution (SAE) Core Network). E-UTRAN / LTE is a variant of 3GPP radio access technology where radio network nodes are directly connected to the EPC core network (rather than the RNC). Generally, in E-UTRAN / LTE, the RNC's functionality is distributed between the radio network nodes (e.g., eNodeBs in LTE) and the core network. Therefore, the EPS RAN has a basically "flat" architecture, consisting of radio network nodes directly connected to one or more core networks, meaning they do not need to be connected to the core via an RNC.

[0005] Emerging 5G technologies, such as New Radio (NR), show great interest in using a large number of transmit and receive antenna elements because this allows for the utilization of beamforming, such as transmit-side beamforming and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signal in one or more selected directions while suppressing transmitted signals in other directions. Similarly, on the receiver side, the receiver can amplify the received signal from one or more selected directions while suppressing unwanted received signals from other directions.

[0006] Figure 1 It depicts various nodes in the 5G reference network architecture defined by 3GPP. Figure 1 Some of the architectural nodes and aspects related 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).

[0007] Application functions (AFs) can interact with the 3GPP core network, and specifically, as mentioned in this disclosure, AFs can provide information to network operators and subscribe to certain events occurring in the operator's network.

[0008] Network Exposure Function (NEF) can support different functions, and as mentioned in this disclosure, NEF can act as an entry point into the operator's network, so that AF can interact with the 3GPP core network through NEF.

[0009] The Policy Control Function (PCF) can support a unified policy framework for managing network behavior. For example, in this disclosure, the PCF can provide PCC rules to the SMF.

[0010] The Session Management Function (SMF) can support various functions; for example, in this disclosure, the SMF can be configured with a User Plane Function (UPF), such as for event reporting. The User Plane Function (UPF) can support processing user plane services based on rules received from the SMF. For example, in this disclosure, the UPF can handle packet inspection and various execution actions, such as event detection and reporting.

[0011] The AMF can receive all connection and session-related information from the UE, for example, via interface N1 or N2, but the AMF is primarily responsible for handling connection and mobility management tasks.

[0012] 3GPP TS 29.518 defines the services provided by the AMF to other network functions (NFs).

[0013] Network Data Analysis Function (NWDAF) can represent the network analysis logic functions managed by the operator. NWDAF is part of the architecture specified in 3GPP TS 23.501 and can use various mechanisms and interfaces specified for 5GC and Operations Management and Maintenance (OAM).

[0014] NWDAF can interact with different entities for different purposes, for example:

[0015] - Event subscription-based data collection provided directly by AMF, SMF, PCF, Unified Data Management (UDM), AF or via NEF and OAM;

[0016] - Retrieve information from a data repository (e.g., from a unified data repository (UDR)) via UDM to obtain subscriber-related information;

[0017] - Retrieve information about network nodes (NFs), such as the Network Repository Function (NRF) for NF-related information and the Network Slice Selection Function (NSSF) for slice-related information; and

[0018] - Provide analytics to consumers on demand.

[0019] The following describes how to optimize user plane services based on existing processes.

[0020] There are various business algorithms available to optimize user plane service payloads, which helps improve Quality of Experience (QoE) and ensure the required Quality of Service (QoS):

[0021] - Transmission Control Protocol (TCP) Optimization: Most applications today are based on TCP transmission, and TCP services currently account for over 90% of mobile broadband networks. TCP was developed in the 1970s and was originally designed for wired communication, not wireless communication. Therefore, TCP may not be suitable for wireless networks, as transmission errors are often handled as congestion events by the protocol. For these reasons, various improvements to TCP have been proposed, such as improved TCP congestion control algorithms (e.g., TCP Cubic, Google's BBR), network-side TCP proxy-based solutions, AQM-based solutions (e.g., CoDel), and transparent solutions based on TCP connection splitting (e.g., TCP ACK regulators or transparent buffers). Most TCP optimizations aim to improve user experience by increasing TCP throughput, especially for demanding services such as video streaming.

[0022] - Domain Name System (DNS) optimization. Every type of business requires DNS requests. A DNS optimizer can improve the time it takes to retrieve content.

[0023] - The optimizer ensures peak single-user throughput for augmented reality (AR) applications, as supporting AR applications typically requires high throughput.

[0024] - Fast UDP Internet Connection (QUIC) optimization is similar to TCP optimization, but attempts to improve QUIC throughput.

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

[0026] We will now discuss the 5G New Radio (NR) mentioned above.

[0027] Previous versions (such as 4G, 3G, 2G) can be useful in the same spectrum portion with recombined bands. 5G band planning is more complex because the spectrum range for sub-6GHz 5G is 450MHz to 6GHz, and the frequency range for millimeter-wave 5G is 24.250GHz to 52.600GHz, and also includes unlicensed spectrum.

[0028] According to 3GPP TS 38.101-3, the frequency range that NR can operate in according to this version of the specification is shown in Table 1 below.

[0029] Table 1: Definition of Frequency Range

[0030]

[0031] Therefore, existing congestion control schemes are not fully capable of handling the highly volatile millimeter wave (mmWave) spectrum. The millimeter wave spectrum refers to the spectral band between 30 GHz and 300 GHz channels. A common congestion control protocol that can be used for most anticipated data services is TCP Cubic. TCP Cubic treats packet loss as a sign of network congestion. TCP Cubic fails when link outages and capacity changes, which are quite common in millimeter wave channels, are introduced. When the bottleneck buffer is large, loss-based congestion control (such as TCP Cubic) keeps the buffer full, resulting in so-called buffer bloating. When the buffer is small, loss-based congestion control can further reduce throughput by a multiplicative decrease depending on the amount of packet loss. If a larger number of packet losses occur, the throughput will decrease even further.

[0032] The role and purpose of congestion control is to regulate the amount of injected traffic in a network based on its congestion status. However, in wireless communication, traditional congestion control protocols (e.g., TCP New Reno) cannot distinguish between data loss attributable to congestion and data loss attributable to transmission errors caused by channel quality degradation.

[0033] The size of the Radio Link Control (RLC) buffer can be scaled proportionally to the Bandwidth-Delay Product (BDP) to achieve maximum TCP effective throughput, i.e., the throughput of useful data. However, given the rapid bandwidth variations between line-of-sight (LOS) and non-line-of-sight (NLOS) conditions, correctly determining the buffer size for millimeter-wave links and preventing link loss without introducing buffer bloat is very challenging. Summary of the Invention

[0034] The purpose of the embodiments in this article is to process communications in a communication network in an efficient manner.

[0035] According to a first aspect of the embodiments herein, this objective is achieved by a method executed by an AF node for processing a data session of a UE in a communication network. The AF node obtains information from an AMF node regarding the UE's use of a first frequency. The AF node then applies a first congestion mechanism based on the obtained information regarding the use of the first frequency. The AF node also obtains information from the AMF node regarding the UE's use of a second frequency. The AF node then further applies a second congestion mechanism in response to the obtained information regarding the use of the second frequency.

[0036] According to another aspect of the embodiments herein, this objective is achieved by a method performed by an AMF node for processing a data session of a UE in a communication network. The AMF node provides the AF node with information about the UE's use of a first frequency. The AMF node then detects a change in the UE's frequency usage. The AMF node also provides the AF node with information about the UE's use of a second frequency.

[0037] According to another aspect of the embodiments herein, this objective is achieved by an AF node for processing data sessions of a UE in a communication network. The AF node is configured to: obtain information about the UE's use of a first frequency from an AMF node. The AF node is also configured to: apply a first congestion mechanism based on the obtained information about the first frequency's use. The AF node is further configured to: obtain information about the UE's use of a second frequency from an AMF node. The AF node is also configured to: apply a second congestion mechanism in response to the obtained information about the second frequency's use.

[0038] According to another aspect of the embodiments herein, this objective is achieved by an AMF node for processing data sessions of a UE in a communication network. The AMF node is configured to: provide information to the AF node regarding the use of a first frequency by the UE. The AMF node is also configured to: detect changes in the frequency use of the UE. The AMF node is further configured to: provide information to the AF node regarding the use of a second frequency by the UE.

[0039] According to another aspect of the embodiments herein, this objective is achieved by a system for processing data sessions of a UE in a communication network.

[0040] This document also provides a computer program product including instructions that, when executed on at least one processor, cause at least one processor to perform the methods described above, which are executed by a network node or a UE. This document also provides a computer-readable storage medium storing a computer program product including instructions that, when executed on at least one processor, cause at least one processor to perform the methods according to the methods described above, which are executed by a network node or a UE.

[0041] By obtaining information about the UE's first frequency usage from the AMF node, the AF node can apply a first congestion mechanism based on this information. Similarly, by obtaining information about the UE's second frequency usage from the AMF node, the AF node can apply a second congestion mechanism in response to this information. This allows for efficient processing of communications within the wireless communication network. Attached Figure Description

[0042] Examples of embodiments described herein are described in more detail with reference to the accompanying drawings, in which:

[0043] Figure 1 It is a schematic overview diagram depicting the 5G reference network architecture;

[0044] Figure 2 This is a schematic block diagram illustrating an embodiment of a communication network;

[0045] Figure 3 These are combined signaling schemes and flowcharts based on some embodiments of this document;

[0046] Figure 4 It is a flowchart depicting an embodiment of a method in an application function node;

[0047] Figure 5 It is a flowchart depicting an embodiment of a method in an access and mobility management node;

[0048] Figure 6 These are combined signaling schemes and flowcharts based on some embodiments of this document;

[0049] Figure 7A and Figure 7B These are combined signaling schemes and flowcharts based on some embodiments of this document;

[0050] Figure 8 This is a schematic block diagram illustrating an embodiment of an application function node;

[0051] Figure 9 This is a schematic block diagram illustrating an embodiment of an access and mobility management function node;

[0052] Figure 10 This is a schematic block diagram illustrating an embodiment of the system;

[0053] Figure 11 The diagram schematically illustrates a telecommunications network connected to a host computer via an intermediate network;

[0054] Figure 12 This is a general block diagram of a host computer communicating with user equipment via a base station through a partially wireless connection; and

[0055] Figures 13 to 16 This is a flowchart illustrating a method implemented in a communication system that includes a host computer, a base station, and user equipment. Detailed Implementation

[0056] Figure 2This is a schematic overview diagram depicting a communication network 100 that can implement the embodiments described herein. The communication network 100 is capable of providing wireless services to communication devices (e.g., user equipment (UE) 120, such as mobile stations, non-access point (non-AP) STAs, STAs, wireless devices, and / or wireless terminals). Those skilled in the art will understand that "UE" is a non-limiting term that 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., smartphone, laptop, mobile phone, sensor, relay, mobile tablet, or any device communicating within a cell or service area).

[0057] Network nodes operate within the core network, such as Application Functional Node (AF) 131, Access and Mobility Management Functional Node (AMF) 132, Network Exposure Functional Node (NEF) 133, and User Plane Functional Node (UPF) 134. These nodes essentially have the following functions and tasks.

[0058] AF node 131 can support the application of service routing, access NEF, and interact with the policy framework for policy control.

[0059] AMF Node 132 can support Non-Access Stratum (NAS) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management.

[0060] NEF Node 133 can support the exposure of capabilities and events, the secure provision of information from external applications to the 3GPP network, and the conversion of internal / external information.

[0061] UPF node 134 can support packet routing and forwarding, packet inspection, quality of service (QoS) processing, and can serve as an anchor point for mobility within and between RATs.

[0062] In addition to those mentioned above, there are network nodes used to provide radio coverage over a geographic area by means of antenna beams. The geographic area may be referred to as a cell, service area, beam, or beam group. In this context, these network nodes can be transmitting and receiving points, such as radio access network nodes, like base stations, such as radio base stations, such as NodeB, evolved Node B (eNB, eNode B), NR Node B (gNB), base transceiver station, radio remote unit, access point base station, base station router, transmitting device of a radio base station, stand-alone access point, wireless local area network (WLAN) access point, access point station (AP STA), access controller, UE acting as an access point or peer in device-to-device (D2D) communication, or any other network element capable of communicating with a UE within cell 11 served by radio network node 110, according to, for example, the radio access technology and terminology used.

[0063] As described herein, the processes and activities according to the embodiments herein are primarily performed by AF node 131 and AMF node 132. The communication network 100 may use 5G NR for radio access, but may also use many other different technologies such as Wi-Fi (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rate GSM Evolution (GSM / EDGE), Global Microwave Access Interoperability (WiMax), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0064] The communication network 100 includes one or more CNs 140 and one or more RANs 150. The UE 120 is connected to one or more CNs 140 via one or more RANs 150.

[0065] As an alternative, for example, including Figure 2 The distributed nodes (DNs) and functions in the cloud 130 shown can be used to perform or partially perform the method.

[0066] In an example scenario where a data session is processed for a UE 120 in communication network 100, AF node 131 can subscribe to changes in radio frequencies by subscribing to radio frequency events in AMF node 132 via NEF node 133. These radio frequency events can be related to the access mobility of UE 120, such as location changes, UE 120 moving into or out of a subscribed area of ​​interest, time zone changes, access type changes, registration status changes, connection status changes, UE 120 losing communication, and UE 120 reachability status. AMF node 132 can then send information about these events to AF node 131 via NEF node 133, allowing AF node 131 to apply the corresponding congestion window based on this information.

[0067] Now refer to Figure 3 An example describing how to process a data session for UE 120 in communication network 100 will be provided below. Figure 4 and Figure 5 The method is described from the perspective of AF node 131 and AMF node 132. Figure 3 This document presents a combined signaling scheme and flowchart using some embodiments of the process described herein. The method includes, for example, the following actions:

[0068] Action 301. To determine which frequency UE 120 is using, AF node 131 obtains information about UE 120's first frequency usage from AMF node 132. Therefore, AF node 131 sends a subscription request for UE frequency events to NEF node 133. The subscription request includes the UE identifier and the event identifier. AF node 131 sends the subscription request to NEF node 133 because AF node 131 and AMF node 132 can communicate with each other via NEF node 133.

[0069] Action 302. NEF node 133 therefore receives a subscription request for UE frequency events from AF node 131 and sends the subscription request to AMF node 132.

[0070] Action 303. AMF node 132 receives a subscription request for UE frequency events from NEF node 133. Since the AF node is now subscribed to the UE frequency, AMF node 132 then provides information to AF node 131 regarding the use of the first frequency by UE 120. Because AF node 131 and AMF node 132 communicate via NEF node 133, AMF node 132 sends information about the use of the first frequency by UE 120 to NEF node 133.

[0071] Action 304. NEF node 133 receives information about the use of the first frequency of UE 120 from AMF node 132 and sends the received information about the use of the first frequency of UE 120 to AF node 131.

[0072] Action 305. Since AF node 131 now has information about the first frequency used by UE 120, AF node 131 knows what frequency UE 120 is using. The AF node then applies the first congestion mechanism based on the information obtained about the first frequency usage.

[0073] Action 306. AMF node 132 then detects a change in the frequency usage of UE 120. This change may be due, for example, to frequency availability and / or unavailability, or because some applications in UE 120 may require a higher frequency for more bandwidth. The frequency used by UE 120 is typically controlled by a radio scheduling function in the network, which can change the frequency usage of the UE for any reason.

[0074] Action 307. When AMF node 133 detects that the frequency of UE 120 has changed, AMF node 132 provides the changed UE frequency (e.g., information about the UE's use of a second frequency) to AF node 131. Similarly, as described above, since AMF node 132 and AF node 131 communicate via NEF node 133, the AMF node sends information about the UE 120's use of a second frequency to NEF node 133.

[0075] Action 308. NEF node 133 receives information from AMF node 132 regarding the use of the second frequency by UE 120, and then sends that information to AF node 131.

[0076] Action 309. AF node 131 has now obtained information from AMF node 132 regarding the use of the second frequency by UE 120, and therefore applies the second congestion mechanism in response to the obtained information.

[0077] Now refer to Figure 4 The flowchart depicted herein illustrates an example embodiment of a method performed by AF node 131 for processing a data session of UE 120 in communication network 100. The method includes actions that can be performed in any suitable order.

[0078] Action 401

[0079] AF node 131 obtains information about the use of the first frequency by UE 120 from AMF node 132. AF node 131 and AMF node 132 can communicate via NEF node 133. Obtaining information about the use of the first frequency may include: sending a subscription request for UE frequency events to NEF node 133; and receiving information about the use of the first frequency by UE 120 from NEF node 133. The subscription request may include a UE identifier and an event identifier. This action corresponds to actions 301 and 304 described above.

[0080] Action 402

[0081] AF node 131 then applies the first congestion mechanism based on the obtained information about the use of the first frequency. This action corresponds to action 305 described above.

[0082] Action 403

[0083] AF node 131 obtains information about the use of the second frequency by UE 120 from AMF node 132. Obtaining information about the use of the second frequency by UE 120 may include receiving information about the use of the second frequency by UE 120 from NEF node 133. This action corresponds to action 308 described above.

[0084] Action 404

[0085] AF node 131 then applies a second congestion mechanism in response to the obtained information about the use of the second frequency. This action corresponds to action 309 described above.

[0086] Now refer to Figure 5 The flowchart depicted herein illustrates an example embodiment of a method performed by AMF node 132 for processing a data session of UE 120 in communication network 100. The method includes actions that can be performed in any suitable order.

[0087] Action 501

[0088] AMF node 132 can receive a subscription request for UE frequency events from NEF node 133. This subscription request may include a UE identifier and an event identifier. This action corresponds to action 302 described above.

[0089] Action 502

[0090] AMF node 132 provides AF node 131 with information regarding the use of a first frequency by UE 120. As previously mentioned, AF node 131 and AMF node 132 can communicate via NEF node 133. Providing information regarding the use of the first frequency may include sending information about the use of the first frequency by UE 120 to NEF node 133. This action corresponds to actions 303 and 304 described above.

[0091] Action 503

[0092] AMF node 132 detected a change in the frequency used by UE 120. This action corresponds to action 306.

[0093] Action 504

[0094] AMF node 132 provides information to AF node 131 regarding the use of the second frequency by UE 120. Providing information regarding the use of the second frequency may include sending information regarding the use of the second frequency by UE 120 to NEF node 133. This action corresponds to actions 307 and 308 described above.

[0095] The embodiments described herein as described above will now be further described and illustrated. The following text applies to any suitable embodiments described above and can be combined with them.

[0096] Figure 6 The combined signaling scheme and flowchart illustrate examples of methods according to some embodiments. Figure 6 An example of AF node 131 subscribing to UE frequency events is shown, including steps 1 through 10, wherein the order of the steps may differ in different implementations:

[0097] Prerequisites: UE 120 has an established PDU session. For simplicity, a single UE 120 is shown.

[0098] Step 1. AF node 131, which could be a content provider (e.g., Vimeo), can subscribe to UE frequencies. For this, it triggers an Nnef_AnalyticsExposure subscription (HTTP POST) message including the following information:

[0099] - Identifiers for (new) analyses of interest, such as Analytic-ID=UE frequency.

[0100] - The identifier of UE 120, such as UE-ID. This subscription can involve a single UE or a group of UEs.

[0101] AF node 131 monitors the frequency (e.g., the subscriber's frequency) of the UE 120 it subscribes to. AF node 131 has different congestion schemes depending on the frequency of UE 120. There is one congestion window for FR1 and one congestion window for FR2, as shown in Table 1 above.

[0102] Step 2. NEF node 133 can respond to AF node 131 with the Nnef_AnalyticsExposure 200 OK message.

[0103] Steps 3 and 4. Optionally, if NEF node 133 is unaware of the AMF node 132 to which UE 120 is attached, NEF node 133 may request AMF node 132 from the Unified Data Repository (UDR). The UDR is an aggregate repository of subscriber information and can be used to provide services for various network functions. The UDR can then respond using AMF node 132.

[0104] Step 5. The NEF node can subscribe to changes in frequency in the AMF node 132 using the Namf_EventExposureService, which has events referred to as frequencies. The AMF node 132 can provide new events to be provided by the Namf_EventExposure service.

[0105] The event is defined as follows:

[0106] Event: Frequency

[0107] Network Functions (NFs) can subscribe to event frequencies to receive event reports from a UE or group of UEs when the AMF detects that the target UE has changed its frequency, by default according to the so-called arfcnDL parameter in 3GPP TS 28.541.

[0108] UE type: one UE, UE group.

[0109] Report type: One-time report, Continuous report

[0110] Input: UE ID. Optional: NG-RAN node, or RRU, N3IWF, UE-IP

[0111] Notification: UE-ID, frequency band (e.g., FR1, FR2), or a value provided by the arfcnDL parameter. Optionally, a recommended congestion control mechanism with some parameters may be provided.

[0112] Step 6. AMF node 132 may respond to NEF node 133, for example, with frequency bands FR1, FR2 or values ​​provided by arfcnDL.

[0113] Step 7. AMF node 132 notifies UE 120 of the frequency. Figure 6 In this example, the frequency of UE 120 is FR1, not millimeter wave.

[0114] Step 8. NEF node 133 can notify AF node 131 of the UE identifier (e.g., UE-ID) and the frequency band of UE 120. Optionally, NEF node 133 can provide a recommended congestion window with some parameters. In this particular case, a congestion mechanism TCP cubic with an initial congestion window of 10 is used. Since UE 120 is using this frequency, AF can apply the TCPCubic congestion mechanism.

[0115] Step 9. UE 120 enters an area providing high frequencies such as millimeter waves or a higher frequency provided by a radio network, therefore UE 120 changes from frequency FR1 to frequency FR2. AMF node 132 notifies NEF node 133 of UE 120's new frequency. In this example, the new frequency is FR2.

[0116] Step 10. NEF node 133 can notify AF node 131 of the frequency band of UE 120. Optionally, NEF node 133 can provide an optimal recommended congestion window with some parameters. In this particular case, a congestion mechanism Yeah with an initial congestion window = r0 is used. Since UE 120 is using this frequency band, AF node 131 can apply, for example, congestion mechanism Yeah. Since congestion mechanism Yeah works better in millimeter wave scenarios, it is used.

[0117] AMF node 132 can send information about those events to UPF node 134, so that the UPF node can apply the corresponding optimizations based on that information.

[0118] Figure 7B and Figure 7A The combined signaling scheme and flowchart in the document illustrate another example according to some embodiments, wherein, Figure 7B yes Figure 7A The continuation of. Figure 7A and Figure 7B This involves the case of UPF node 134 subscribing to UE frequency events and includes the steps described below. Figure 7A and Figure 7B This includes steps 1 through 17, the order of which may vary in different implementations.

[0119] Prerequisites: Optimization information storage / retrieval policies can be pre-configured in the UDR as subscriber policy data, such as UE 120 policy data. This example illustrates a per-subscriber policy; however, the flow information storage policy can also be applied to an application, a UE group (e.g., a subscriber), a network slice, or globally, for example, on a per-node or network basis. This example illustrates the behavior in the event of a handover during service optimization.

[0120] Steps 1 to 2. During the Packet Forwarding Control Protocol (PFCP) association process between UPF and SMF entities, it is recommended to extend the existing mechanism to report UPF capabilities with new capabilities for optimized Frequency Information (FIOP) (see bold in Table 2 below).

[0121] Table 2: UP Functional Features

[0122]

[0123]

[0124] Step 3. UE 120 can trigger PDU session establishment by sending a PDU session establishment request to AMF node 132.

[0125] Step 4. AMF node 132 can select an SMF to manage the PDU session. The SMF selection function in AMF node 132 selects an SMF instance based on the available SMF instance obtained from NRF or based on the SMF information configured in AMF node 132, and triggers an Nsmf PDU session creation message.

[0126] Step 5. SMF can trigger the Npcf_SMPolicyControl_Create request message to retrieve the Session Management (SM) policy for the user PDU session.

[0127] Step 6) The PCF triggers a so-called Nudr_Query request message that includes the subscriber identifier (e.g., the UE identifier) ​​to retrieve policy data for the PDU session of UE 120.

[0128] Step 7. The UDR responds with a Nudr_Query response message that includes subscriber policy data, which contains new switching information for optimizing the policy. As an example, a binary flag can be assumed as the switching information policy:

[0129] - TRUE: Tracking frequency for optimization

[0130] - FALSE: Frequency not considered

[0131] When it is necessary to examine frequencies at other levels (e.g., the radio resource unit (RRU) set of an NG-RAN node), more granular information can be used to extend this value.

[0132] exist Figure 7A and Figure 7B In this example, it can be assumed that optimization will be performed at UPF node 134. This example also assumes that a frequency-information-based optimization strategy is applied on a per-subscriber PDU session basis. Different frequency-information-based optimization strategies can also be configured for each application.

[0133] Step 8. The PCF can generate corresponding PCC rules based on subscriber policy data, and can also include optimizations with switching information (TRUE), which in this example is applied on a per-PDU session basis.

[0134] Step 9. The SMF can select a UPF and trigger the PFCP session establishment process to provide Packet Detection Rules (PDR) and corresponding execution actions: QoS Enforcement Rules (QER), Forwarding Action Rules (FAR), Usage Reporting Rules (URR), etc., for the PDU session. Specifically, the SMF can provide handover information. For this purpose, it is recommended to extend the PFCP protocol by adding a new "Frequency Information" IE at the "PFCP Session Establishment / Modification Request" section, as shown in bold in Tables 3 and 4 below:

[0135] Table 3: QER IE within the PFCP session establishment request

[0136]

[0137]

[0138]

[0139]

[0140] Table 4: Frequency Information IE

[0141]

[0142] In this example:

[0143] - Frequency information configuration file=FR1

[0144] Session modification messages can have similar attributes.

[0145] Step 11. SMF responds to AMF node 132's request.

[0146] Step 12. UE 120 has an established PDU session.

[0147] Steps 13 to 14. Optionally, if UPF node 134 is unaware of the AMF node 132 to which UE 120 is attached, UPF node 134 may request AMF node 132 from UDR. UDR may then respond using AMF node 132.

[0148] Step 15. UPF node 134 can subscribe to the Namf_EventExposure service. In this case, new events are exposed using this service. It is a cell handover performed by UE 120. The event is defined as follows:

[0149] AMF node 132 can provide new events, which can be provided by the Namf_EventExposure service.

[0150] Event: Frequency

[0151] The NF subscribes to this event to receive event reports from the UE or UE group when the AMF node 132 detects that the target UE has changed its frequency. By default, the arfcnDL parameter is as described in 3GPP TS 28.541.

[0152] UE type: one UE, UE group.

[0153] Report type: One-time report, continuous report.

[0154] Input: UE ID. Optional: NG-RAN node, or RRU, N3IWF, UE-IP.

[0155] Notification; UE-ID, frequency (FR1, FR2, or a value provided by the arfcnDL parameter)

[0156] Step 16. AMF node 132 can confirm that the subscription is correct.

[0157] Step 17. AMF can use the Namf_EventExposure service to notify UE 120 that the frequency has changed. UPF node 134 can then use this information to optimize itself to suit UE 120, for example, by modifying its buffer size or changing parameters in the AQM algorithm.

[0158] Figure 8 This is a block diagram depicting an AF node 131 for processing data sessions of a UE 120 in a communication network 100, according to embodiments of the present invention.

[0159] AF node 131 may include processing circuitry 801 configured to perform the methods described herein, such as one or more processors.

[0160] AF node 131 may include acquisition unit 802. AF node 131, processing circuitry 801 and / or acquisition unit 802 are configured to acquire information about the use of a first frequency of UE 120 from AMF node 132.

[0161] AF node 131 and AMF node 132 can communicate via NEF node 133.

[0162] Obtaining information about the use of the first frequency may be adapted to include: sending a subscription request for a UE frequency event to NEF node 133, wherein the subscription request includes a UE identifier and an event identifier; and receiving information about the use of the first frequency by UE 120 from NEF node 133.

[0163] AF node 131, processing circuit 801, and / or acquisition unit 802 are configured to: obtain information about the use of the second frequency of UE 120 from AMF node 132. Obtaining information about the use of the second frequency of UE 120 may be adapted to include: receiving information about the use of the second frequency of UE 120 from NEF node 133.

[0164] AF node 131 may include application unit 803. AF node 131, processing circuit 801 and / or application unit 803 are configured to apply a first congestion mechanism based on information obtained about the use of a first frequency of UE 120.

[0165] AF node 131, processing circuit 801 and / or application unit 803 are configured to apply a second congestion mechanism in response to information obtained about the use of the second frequency of UE 120.

[0166] AF node 131 also includes memory 805. Memory 805 includes one or more units for storing data such as frequency information, UE identifier and event identifier information, input / output data, metadata, etc.; and applications for executing the methods disclosed herein when executed. AF node 131 may also include a communication interface, such as including one or more antennas or antenna elements.

[0167] The methods described herein with respect to AF node 131 are implemented, for example, by means of a computer program product 806 or a computer program, which includes instructions, i.e., software code portions, that, when executed on at least one processor, cause the at least one processor to perform the actions described herein performed by AF node 131. Computer program product 806 may be stored on a computer-readable storage medium 807 (e.g., a disk, a Universal Serial Bus (USB) disk, etc.). The computer-readable storage medium 807 on which the computer program product is stored may include instructions that, when executed on at least one processor, cause the at least one processor to perform the actions described herein performed by AF node 131. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium.

[0168] Figure 9 This is a block diagram depicting an AMF node 132 for processing data sessions of a UE 120 in a communication network 100, according to embodiments of this document.

[0169] AMF node 132 may include processing circuitry 901, such as one or more processors, configured to perform the methods described herein.

[0170] AMF node 132 may include a receiving unit 902. AMF node 132, processing circuitry 901 and / or receiving unit 902 may be configured to receive subscription requests for UE frequency events from NEF node 133, wherein the subscription request includes a UE identifier and an event identifier.

[0171] AMF node 132 may include a providing unit 903. AMF node 132, processing circuitry 901 and / or providing unit 903 are configured to provide AF node 131 with information about the UE's use of a first frequency.

[0172] AF node 131 and AMF node 132 can communicate via NEF node 133.

[0173] Providing information about the use of the first frequency may be adapted to include: sending information about the use of the first frequency to NEF node 133.

[0174] AMF node 132, processing circuit 901, and / or providing unit 903 are configured to provide AF node 131 with information regarding the use of the second frequency by UE 120. Providing information regarding the use of the second frequency may be adapted to include sending information regarding the use of the second frequency to NEF node 133.

[0175] AMF node 132 may include detection unit 904. AMF node 132, processing circuit 901 and / or detection unit 904 are configured to detect a change in the frequency usage of UE 120.

[0176] AMF node 132 also includes memory 905. Memory 905 includes one or more units for storing data such as frequency information, UE identifier and event identifier information, input / output data, metadata, etc.; and applications for executing the methods disclosed herein when executed. AMF node 132 may also include a communication interface, which may include, for example, one or more antennas or antenna elements.

[0177] The methods described herein with respect to the embodiments of AMF node 132 are implemented, for example, by means of a computer program product 906 or a computer program, which includes instructions, i.e., software code portions, that, when executed on at least one processor, cause the at least one processor to perform the actions described herein performed by AMF node 132. Computer program product 906 may be stored on a computer-readable storage medium 907 (e.g., a disk, a Universal Serial Bus (USB) disk, etc.). The computer-readable storage medium 907 on which the computer program product is stored may include instructions that, when executed on at least one processor, cause the at least one processor to perform the actions described herein performed by AMF node 132. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium.

[0178] Figure 10 The diagram illustrates a system for processing data sessions of a UE 120 in a communication network 100. This system may include components such as... Figure 8 and Figure 9 The system is illustrated with AF node 131 and AMF node 132. The system may also include UPF node 134. UPF node 134 may include processing circuitry 1001 configured to perform the methods described herein, such as one or more processors.

[0179] UPF node 134 may include a transmitting unit 1002. UPF node 134, processing circuitry 1001 and / or transmitting unit 1002 may be configured to send a subscription request for UE frequency events to AMF node 132, wherein the subscription request includes a UE identifier and an event identifier.

[0180] UPF node 134 may include acquisition unit 1003. UPF node 134, processing circuit 1001 and / or acquisition unit 1003 may be configured to acquire information about the frequency usage of UE 120 from AMF node 132.

[0181] UPF node 134 may include optimization unit 1004. UPF node 134, processing circuit 1001 and / or optimization unit 1004 may be configured to optimize UE services based on received information about the frequency usage of UE 120.

[0182] In some embodiments, the more general term "network node" is used, which can correspond to any type of radio network node or any network node that communicates with wireless devices and / or with another network node. Examples of network nodes are gNodeB, eNodeB, NodeB, MeNB, SeNB, network nodes belonging to a primary cell group (MCG) or secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio nodes such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node control relay, base transceiver station (BTS), access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio headend (RRH), nodes in a distributed antenna system (DAS), etc.

[0183] In some embodiments, the non-limiting term wireless device or user equipment (UE) is used, and it refers to any type of wireless device that communicates with a network node in a cellular or mobile communication system and / or with another wireless device. Examples of UEs are target devices, device-to-device (D2D) UEs, UEs with proximity capabilities (aka ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communication, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, etc.

[0184] The embodiments are applicable to any radio access technology (RAT) or multi-RAT system in which devices receive 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 GSM Evolution (GSM / EDGE), Global Microwave Access Interoperability (WiMax), or Ultra Mobile Broadband (UMB), and the above are only some of the possible implementations.

[0185] Those skilled in communication design will readily understand that functional devices or circuits can be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, some 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 having suitable hardware and / or software interfaces. For example, several functions may be implemented on a processor shared with other functional components of the UE or network node.

[0186] Alternatively, some functional elements in the processing unit under discussion may be provided using dedicated hardware, while others may be provided using hardware for executing software in combination with suitable software or firmware. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include (but are not limited to) digital signal processor (DSP) hardware and / or program or application data. Other conventional and / or custom hardware may also be included. Designers of communication equipment will understand the trade-offs in cost, performance, and maintenance among these design options.

[0187] It will be understood that the foregoing description and figures represent non-limiting examples of the methods and apparatus taught herein. Therefore, the apparatus and techniques taught herein are not limited to the foregoing description and figures. Rather, the embodiments herein are limited only by the appended claims and their legal equivalents.

[0188] Further expansion and changes

[0189] refer to Figure 11 According to an embodiment, the communication system includes a telecommunications network 3210 (e.g., an NR network such as a 3GPP-type cellular network) such as a wireless communication network 100. The telecommunications network 3210 includes an access network 3211 (e.g., a radio access network) and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c, such as radio network node 110, access node, AP STA, NB, eNB, gNB, or other types of wireless access points, each base station defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connected to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE) 3291 (e.g., a wireless device 120, such as a non-AP STA) located in the coverage area 3213c is configured to wirelessly connect to or be paged by the corresponding base station 3212c. A second UE 3292 (e.g., a first radio node 110 or a second radio node 120 or a non-AP STA) in coverage area 3213a is wirelessly connected to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 3212.

[0190] Telecommunication network 3210 is connected to host computer 3230, which may be implemented as a standalone server, a cloud-based server, a distributed server, or as a processing resource in a server cluster. Host computer 3230 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 3221 and 3222 between telecommunication network 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230, or may be made via optional intermediate network 3220. Intermediate network 3220 may be one or more of public, private, or bearer networks; intermediate network 3220 (if present) may be a backbone network or the Internet; specifically, intermediate network 3220 may include two or more subnetworks (not shown).

[0191] Figure 11 The communication system as a whole establishes a connection between one of the connected UEs 3291 and 3292 and the host computer 3230. This connection can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291 and 3292 are configured to transmit data and / or signaling via the OTT connection 3250 using access network 3211, core network 3214, any intermediate network 3220, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 3250 can be transparent in the sense that the participating communication devices traversing the OTT connection 3250 are unaware of the routing of uplink and downlink communications. For example, it may not be necessary to notify the base station 3212 of the past routes of input downlink communications containing data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, base station 3212 does not need to be aware of future routes for uplink communication originating from UE 3291 to host computer 3230.

[0192] Reference Figure 12This section describes example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments. In the communication system 3300, the host computer 3310 includes hardware 3315, which includes a communication interface 3316 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300. The host computer 3310 also includes processing circuitry 3318, which may have storage and / or processing capabilities. Specifically, the processing circuitry 3318 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer 3310 also includes software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. Host application 3312 is operable to provide services to a remote user (e.g., UE 3330), which is connected via an OTT connection 3350 terminated at both UE 3330 and host computer 3310. When providing services to the remote user, host application 3312 can provide user data transmitted using the OTT connection 3350.

[0193] The communication system 3300 also includes a base station 3320 provided in the telecommunications system. The base station 3320 includes hardware 3325 enabling it to communicate with a host computer 3310 and a UE 3330. Hardware 3325 may include: a communication interface 3326 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 3300; and a radio interface 3327 for establishing and maintaining connections with at least the coverage area served by the base station 3320. Figure 12 The wireless connection 3370 of UE3330 (not shown in the diagram) is provided. Communication interface 3326 can be configured to facilitate connection 3360 to host computer 3310. Connection 3360 can be direct, or it can be via the core network of the telecommunications system (…). Figure 12 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 3325 of base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. Base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0194] The communication system 3300 also includes the previously mentioned UE 3330. Its hardware 3335 may include a radio interface 3337 configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area currently occupied by the UE 3330. The hardware 3335 of the UE 3330 also includes processing circuitry 3338, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 3330 also includes software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 is operable to provide services to human or non-human users via the UE 3330 with the support of a host computer 3310. In host computer 3310, host application 3312 can communicate with client application 3332 via OTT connection 3350 terminated at UE 3330 and host computer 3310. When providing services to a user, client application 3332 can receive request data from host application 3312 and provide user data in response to the request data. OTT connection 3350 can transmit both request data and user data. Client application 3332 can interact with the user to generate the user data it provides.

[0195] Notice, Figure 12 The host computer 3310, base station 3320, and UE 3330 shown can be respectively connected to... Figure 11 The host computer 3230, base stations 3212a, 3212b, and 3212c are identical to one of the UEs 3291 and 3292. That is to say, the internal operation of these entities can be as follows: Figure 12 As shown, and independently, the surrounding network topology can be Figure 11 The network topology.

[0196] exist Figure 12 The OTT connection 3350 has been abstractly depicted to illustrate communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine this route, which can be configured to be hidden from the UE 3330, the service provider operating the host computer 3310, or both. During OTT connection 3350 activity, the network infrastructure can also make decisions to dynamically change the route (e.g., based on load balancing considerations or network reconfiguration).

[0197] The wireless connection 3370 between UE 3330 and base station 3320 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UE 3330 using OTT connection 3350, wherein wireless connection 3370 forms the final segment of OTT connection 3350. More precisely, the teachings of these embodiments can improve data rates, latency, and power consumption, thereby providing benefits such as user latency, relaxed file size limits, better responsiveness, and extended battery life.

[0198] For the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments, a measurement process may be provided. Optional network functions may also exist for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to changes in measurement results. The measurement process and / or the network functions for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310, in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication equipment traversed by the OTT connection 3350; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities that the software 3311, 3331 can use to calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 3350 may include message formatting, retransmission settings, preferred routing, etc.; this reconfiguration does not need to affect the base station 3320 and may be unknown or imperceptible to the base station 3320. Such processes and functions may be known and practiced in the art. In a particular embodiment, the measurement may involve proprietary UE signaling that facilitates the host computer 3310 in measuring throughput, propagation time, latency, etc. This measurement may be implemented by software 3311, 3331 enabling the use of OTT connection 3350 to send messages (specifically, empty messages or "fake" messages) while monitoring propagation time, errors, etc.

[0199] Figure 13 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. 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 a reference. Figure 11 and Figure 12 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 13The diagram is referenced. In the first action 3410 of the method, the host computer provides user data. In an optional sub-action 3411 of the first action 3410, the host computer provides user data by executing a host application. In the second action 3420, the host computer initiates a transmission carrying user data to the UE. In an optional third action 3430, in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth action 3440, the UE executes a client application associated with a host application executed by the host computer.

[0200] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. 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 a reference. Figure 11 and Figure 12 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 14 The diagram is referenced. In the first action 3510 of the method, the host computer provides user data. In an optional sub-action (not shown), the host computer provides user data by executing a host application. In the second action 3520, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be via a base station. In an optional third action 3530, the UE receives the user data carried in the transmission.

[0201] Figure 15 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. 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 a reference. Figure 11 and Figure 12 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 15The diagram is referenced. In an optional first action 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second action 3620, the UE provides user data. In an optional sub-action 3621 of the second action 3620, the UE provides user data by executing a client application. In another optional sub-action 3611 of the first action 3610, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in an optional third sub-action 3630. In a fourth action 3640 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0202] Figure 16 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. 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 a reference. Figure 11 and Figure 12 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 16 The diagram is referenced. In an optional first action 3710 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In an optional second action 3720, the base station initiates a transmission of the received user data to a host computer. In a third action 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0203] When the words “include” or “contain” are used, they should be interpreted as non-restrictive, meaning “consisting of at least…”.

[0204] The embodiments described herein are not limited to the preferred embodiments described above. Various alternatives, modifications, and equivalents may be used.

Claims

1. A method performed by an application function, AF, node (131) for handling a data session of a user equipment, UE, (120) in a communications network (100), the method comprising: obtaining (401) information about usage of a first frequency of the UE from an access and mobility management function, AMF, node (132); applying (402) a first congestion mechanism based on the obtained information about usage of the first frequency; obtaining (403) information about usage of a second frequency of the UE from the AMF node (132), wherein the information about usage of the second frequency comprises a detected changed UE frequency; and applying (404) a second congestion mechanism different from the first congestion mechanism in response to the obtained information about usage of the second frequency. The AF node and the AMF node communicate via a network exposure function, NEF, node (133).

2. The method of claim 1, wherein, Obtaining information about usage of the first frequency comprises sending a subscription request for UE frequency events to the NEF node (133), wherein the subscription request comprises a UE identifier and an event identifier; and receiving information about usage of the first frequency of the UE from the NEF node (133).

3. The method of claim 2, wherein, Obtaining information about usage of the second frequency of the UE comprises receiving information about usage of the second frequency of the UE from the NEF node (133).

4. The method of claim 2 or 3, wherein, 5. A method performed by an access and mobility management function, AMF, node (132) for handling a data session of a user equipment, UE, (120) in a communications network (100), the method comprising: providing (502) information about usage of a first frequency of the UE to an application function, AF, node (131) for the AF node (131) to apply a first congestion mechanism; detecting (503) a change in usage of a frequency of the UE; providing (504) information about usage of a second frequency of the UE to the AF node (131) for the AF node (131) to apply a second congestion mechanism different from the first congestion mechanism, wherein the information about usage of the second frequency comprises a detected changed UE frequency. The AF node and the AMF node communicate via a network exposure function, NEF, node (133).

6. The method of claim 5, wherein, 7. The method of claim 6, further comprising: receiving (501) a subscription request for UE frequency events from the NEF node (133), wherein the subscription request comprises a UE identifier and an event identifier. Providing information about usage of the first frequency comprises sending information about usage of a first frequency of the UE to the NEF node (133).

8. The method of claim 6 or 7, wherein, Providing information about usage of the second frequency comprises sending information about usage of the second frequency of the UE to the NEF node (133).

9. The method of claim 6, wherein, The AF node is configured to:

10. An application function, AF, node (131) for handling a data session of a user equipment, UE, (120) in a communications network (100), wherein, obtain information about usage of a first frequency of the UE from an access and mobility management function, AMF, node (132); ​ applying a first congestion mechanism based on the obtained information about the usage of the first frequency by the UE; obtaining information about the usage of a second frequency by the UE from the AMF node (132), wherein the information about the usage of the second frequency comprises a detected changed UE frequency; and applying a second congestion mechanism different from the first congestion mechanism in response to the obtained information about the usage of the second frequency by the UE.

11. The AF node (131) according to claim 10, wherein The AF node and the AMF node communicate via a Network Exposure Function, NEF, node (133).

12. The AF node (131) according to claim 11, wherein The obtaining of information about the usage of the first frequency is adapted to comprise sending a subscription request for a UE frequency event to the NEF node (133), wherein the subscription request comprises a UE identifier and an event identifier; and receiving information about the usage of the first frequency by the UE from the NEF node (133).

13. The AF node (131) according to claim 11 or 12, wherein, The obtaining of information about the usage of the second frequency by the UE is adapted to comprise receiving information about the usage of the second frequency by the UE from the NEF node (133).

14. An Access and Mobility Management Function, AMF, node (132) for handling a data session of a User Equipment, UE, (120) in a communications network (100), wherein The AMF node is configured to: provide information about the usage of a first frequency by the UE to an Application Function, AF, node (131) to cause the AF node (131) to apply a first congestion mechanism; detect a change in the usage of a frequency by the UE; provide information about the usage of a second frequency by the UE to the AF node (131) to cause the AF node (131) to apply a second congestion mechanism different from the first congestion mechanism, wherein the information about the usage of the second frequency comprises a detected changed UE frequency.

15. The AMF node (132) of claim 14, wherein, The AF node and the AMF node communicate via a Network Exposure Function, NEF, node (133).

16. The AMF node (132) of claim 15, wherein, The AMF node is further configured to: receive a subscription request for a UE frequency event from the NEF node (133), wherein the subscription request comprises a UE identifier and an event identifier.

17. The AMF node (132) according to any one of claims 15 or 16, wherein, The providing of information about the usage of the first frequency is adapted to comprise sending information about the usage of the first frequency to the NEF node (133).

18. The AMF node (132) of claim 15, wherein, The providing of information about the usage of the second frequency is adapted to comprise sending information about the usage of the second frequency to the NEF node (133).

19. A system (140) for handling a data session of a user equipment, UE, (120) in a communications network (100), wherein The system comprises an Application Function, AF, node (131) and an Access and Mobility Management Function, AMF, node (132), wherein the AF node is configured according to any of claims 10 to 13, and wherein the AMF node is configured according to any of claims 14 to 18.

20. The system (140) of claim 19, wherein, The system further comprises a User Plane Function, UPF, node (134) configured to: send a subscription request for a UE frequency event to the AMF node (132), wherein the subscription request comprises a UE identifier and an event identifier; obtain information about the usage of a frequency by the UE from the AMF node (132); optimize UE traffic in dependence on the received information about the usage of the frequency by the UE.

21. 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 any one of claims 1-9, respectively performed by an AF node (131) or an AMF node (132).

22. A computer-readable storage medium having stored the 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 any one of claims 1-9, respectively performed by an AF node (131) or an AMF node (132).

Images