Inter-network congestion reporting

Abstract

There are provided measures for inter-network congestion reporting. Such measures may comprise receiving, (e.g., at a network gateway entity providing access to the network for a network external entity external to the network), a report from a first network external entity, the report reporting an indication of congestion in a downlink direction from the first network to a terminal device, and sending information corresponding to the congestion indication to a network entity in the first network.

Description

Technical Field

[0001] Various exemplary embodiments of the subject disclosure relate to inter-network congestion reporting. More specifically, various exemplary embodiments relate to measures (including methods, apparatuses, and computer program products) for implementing inter-network congestion reporting. Background Art

[0002] A communication system may be viewed as a facility that enables communication sessions between two or more entities (such as communication devices, base stations and / or other nodes) by providing a bearer between the various entities involved in the communication path.

[0003] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards, such as those provided by 3GPP, satellite-based communication systems, and different wireless local networks. The wireless local network may be implemented, for example, as a wireless local area network (WLAN). Wireless systems may typically be divided into cells and are therefore often referred to as cellular systems.

[0004] Communication systems and associated equipment typically operate according to a given standard or specification that sets out what the various entities associated with the system are permitted to do and how it should be achieved. Communication protocols and / or parameters that will be used for the connection are also typically defined. An example of a set of standards is the so-called 5G standards. Summary of the invention

[0005] Various example embodiments are intended to address at least some of the problems and / or issues and disadvantages explicitly described herein or otherwise apparent to those skilled in the relevant art in view of the subject disclosure.

[0006] Several aspects of various example embodiments are detailed below.

[0007] According to one aspect, a method is provided, comprising: detecting a congestion indication in a downlink direction from a first network to a terminal device, and reporting the congestion information to a network entity of the first network.

[0008] According to one aspect, a method is provided, comprising: receiving a report from an entity outside a first network, the report reporting a congestion indication in a downlink direction from the first network to a terminal device, and sending information corresponding to the congestion indication to a network entity in the first network.

[0009] According to one aspect, a method is provided, comprising receiving information indicating a congestion indication in a downlink direction from a first network to a terminal device, and sending the information to a first network entity configured for downlink packet congestion notification marking.

[0010] According to one aspect, a method is provided, comprising: sending to a user plane functional entity a configuration for accepting congestion information reported by a network entity, and / or sending to the network entity a configuration for reporting congestion information to the user plane functional entity.

[0011] According to one aspect, a method is provided, comprising: receiving information indicating a congestion indication in a downlink direction from a first network to a terminal device, and based on the received information, explicitly congestion notification marking downlink packets in the downlink direction.

[0012] According to one aspect, a method is provided, comprising receiving information indicating a congestion indication in a downlink direction from a first network to a terminal device, and sending the information to an application function entity.

[0013] According to one aspect, an apparatus is provided, comprising: a detection circuit configured to detect a congestion indication in a downlink direction from a first network to a terminal device, and a reporting circuit configured to report the congestion information to a network entity of the first network.

[0014] According to one aspect, an apparatus is provided, comprising: a receiving circuit configured to receive a report from an entity outside a first network, the report reporting a congestion indication in a downlink direction from the first network to a terminal device, and a sending circuit configured to send information corresponding to the congestion indication to a network entity in the first network.

[0015] According to one aspect, an apparatus is provided, comprising: a receiving circuit configured to receive information indicating congestion in a downlink direction from a first network to a terminal device, and a sending circuit configured to send the information to a first network entity configured for downlink packet congestion notification marking.

[0016] According to one aspect, a device is provided, comprising: a sending circuit configured to: send a configuration for accepting congestion information reported by a network entity to a user plane functional entity, and / or send a configuration for reporting congestion information to the user plane functional entity to the network entity.

[0017] According to one aspect, an apparatus is provided, comprising: a receiving circuit configured to receive information indicating congestion in a downlink direction from a first network to a terminal device, and a marking circuit configured to perform an explicit congestion notification marking on a downlink packet in the downlink direction according to the received information.

[0018] According to one aspect, an apparatus is provided, comprising: a receiving circuit configured to receive information indicating congestion indication in a downlink direction from a first network to a terminal device, and a sending circuit configured to send the information to an application function entity.

[0019] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor together with the at least one memory and the computer program code being configured to cause the apparatus to perform: detecting a congestion indication in a downlink direction from a first network to a terminal device, and reporting the congestion information to a network entity of the first network.

[0020] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor, together with the at least one memory and the computer program code, being configured to cause the apparatus to execute: receiving a report from an entity outside a first network, the report reporting a congestion indication in a downlink direction from the first network to a terminal device, and sending information corresponding to the congestion indication to a network entity in the first network.

[0021] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured for communicating with at least another apparatus, the at least one processor together with the at least one memory and the computer program code being configured to cause the apparatus to perform: receiving information indicating congestion indication in a downlink direction from a first network to a terminal device, and sending the information to a first network entity, the first network entity being configured for downlink packet congestion notification marking.

[0022] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor together with the at least one memory and the computer program code being configured to cause the apparatus to execute: sending a configuration for accepting congestion information reported by a network entity to a user plane function entity, and / or sending a configuration for reporting congestion information to the user plane function entity to the network entity.

[0023] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor together with the at least one memory and the computer program code being configured to cause the apparatus to execute: receiving information indicating congestion indication in a downlink direction from a first network to a terminal device, and based on the received information, performing explicit congestion notification marking on downlink packets in the downlink direction.

[0024] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor together with the at least one memory and the computer program code being configured to cause the apparatus to execute: receiving information indicating congestion indication in a downlink direction from a first network to a terminal device, and sending the information to an application function entity.

[0025] According to one aspect, a computer program product is provided, which includes a computer executable computer program code. When the program is run on a computer (for example, a computer of an apparatus according to any one of the above-mentioned apparatus-related aspects disclosed in the present subject matter), the computer executable computer program code is configured to cause the computer to execute a method according to any one of the above-mentioned method-related aspects disclosed in the present subject matter.

[0026] Such a computer program product may include (or be embodied as) a (tangible) computer-readable (storage) medium or the like on which the computer-executable computer program code is stored, and / or the program may be directly loaded into the internal memory of the computer or its processor.

[0027] Any of the above aspects or other aspects described herein facilitate optimizing the provision and utilization of congestion reporting possibilities, thereby addressing at least part of any problems and shortcomings identified herein or otherwise apparent to those skilled in the relevant art in view of the subject disclosure.

[0028] In some example embodiments, inter-network congestion reporting is provided. More specifically, measures and mechanisms for implementing inter-network congestion reporting are provided.

[0029] Therefore, optimization may be achieved through methods, apparatuses, and computer program products that enable / implement inter-network congestion reporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In the following, some example embodiments will be described in more detail by way of non-limiting and illustrative examples with reference to the accompanying drawings, in which:

[0031] Figure 1 is a block diagram illustrating an apparatus according to some example embodiments;

[0032] Figure 2 is a block diagram illustrating an apparatus according to some example embodiments;

[0033] Figure 3 is a block diagram illustrating an apparatus according to some example embodiments;

[0034] Figure 4 is a block diagram illustrating an apparatus according to some example embodiments;

[0035] Figure 5 is a block diagram illustrating an apparatus according to some example embodiments;

[0036] Figure 6 is a block diagram illustrating an apparatus according to some example embodiments;

[0037] Figure 7 is a block diagram illustrating an apparatus according to some example embodiments;

[0038] Figure 8 is a block diagram illustrating an apparatus according to some example embodiments;

[0039] Fig. 9 is a schematic diagram of a process according to some example embodiments;

[0040] Fig.10 is a schematic diagram of a process according to some example embodiments;

[0041] Fig.11 is a schematic diagram of a process according to some example embodiments;

[0042] Fig.12 is a schematic diagram of a process according to some example embodiments;

[0043] Fig.13 is a schematic diagram of a process according to some example embodiments;

[0044] Fig.14 is a schematic diagram of a process according to some example embodiments;

[0045] Fig.15 A schematic diagram showing an example of a system environment with signaling variations;

[0046] Fig.16 A schematic diagram illustrating an example of a system environment with signaling variations according to some example embodiments;

[0047] Fig.17 A schematic diagram illustrating an example of a protocol stack according to some example embodiments;

[0048] Fig.18 A schematic diagram illustrating a signaling sequence according to some example embodiments;

[0049] Fig.19 A schematic diagram illustrating an example of a protocol stack according to some example embodiments;

[0050] Fig. 20 A schematic diagram illustrating an example of a system environment with signaling variations according to some example embodiments; and

[0051] Fig.21 is a block diagram that alternatively illustrates an apparatus according to some example embodiments. DETAILED DESCRIPTION

[0052] The subject disclosure is described herein with reference to specific non-limiting and illustrative examples. It will be appreciated by those skilled in the art that the subject disclosure is by no means limited to these examples and can be applied more broadly.

[0053] It will be noted that the following description of the subject disclosure and its various embodiments refers to specifications used as non-limiting and illustrative examples of certain network configurations and deployments. That is, the subject disclosure and its various example embodiments are described relative to 3GPP specifications used as non-limiting and illustrative examples of certain network configurations and deployments. Therefore, the description of such example embodiments provided herein specifically refers to terms directly related thereto. Such terms are used only in the context of non-limiting and illustrative examples and are not intended to limit the subject disclosure in any way. Rather, any other communication or communication-related system deployment, etc. may also be utilized.

[0054] In the following, multiple variations and / or alternatives are used to describe various example embodiments and implementations of the subject disclosure and its various aspects. It will generally be noted that, subject to certain constraints, all described variations and / or alternatives may be provided individually or in any combination (also including combinations of individual features of the various variations and / or alternatives).

[0055] As used herein, “at least one of: <a list of two or more elements / elements>” and “at least one of <a list of two or more elements / elements>” and similar expressions (wherein a list of two or more elements / elements is connected by “and” or “or”) refer to at least any one element / element, or at least any two or more elements / elements, or at least all elements / elements.

[0056] An apparatus configured for congestion handling and communications related to congestion handling is provided. As described in further detail herein, in a particular inter-network scenario where congestion is not arranged, one or more problems may arise in reporting and handling congestion. Inter-network congestion reporting may provide advantages and optimizations for certain use cases.

[0057] According to some example embodiments, measures and mechanisms for (enabling / realizing) inter-network congestion reporting are provided.

[0058] The Low Latency Low Loss Scalable Throughput (L4S) service may allow network managers to configure their routers' Active Queue Management (AQM) to mark packets based on Congestion Experienced (CE) when a queuing delay threshold is exceeded.

[0059] In turn, L4S-compliant transport / higher layers may be able to infer the amount of congestion by the ratio of normal packets to CE-marked packets, and thus may be able to reduce the sending rate accordingly.

[0060] During normal operation, this approach will completely avoid packet drops caused by congestion and keep utilization high and latency low.

[0061] The Explicit Congestion Notification (ECN) algorithm has (only) one responsibility, namely to inform the sender of the congestion generated at the router. Therefore, ECN is a congestion notification or congestion signaling algorithm. ECN notifies the sender of the congestion so that appropriate measures can be taken to avoid the congestion. ECN marking can be used for L4S services.

[0062] To support Extended Reality (XR) in 3rd Generation Partnership Project (3GPP) networks, mechanisms are studied to enable codec / rate adaptation to meet service requirements.

[0063] Two ways in which congestion information can be communicated back to the application (for rate adaptation) can be considered.

[0064] Option 1 (by enabling L4S): Fifth Generation (5G) systems may use ECN marking for L4S purposes for uplink and / or downlink Quality of Service (QoS) flows via one of the following two methods: An explicit indication of the QoS flow level may be provided to the Packet Data Unit (PDU) Session Anchor (PSA) User Plane Function (UPF) to enable ECN marking for L4S purposes.

[0065] - Method 1: To support L4S, a Next Generation Radio Access Network (NG-RAN) performs ECN marking for uplink and downlink in an Internet Protocol (IP) layer of received packets.

[0066] -Method 2: PSA UPF performs ECN marking for the uplink (UL) and downlink (DL) IP layers of received packets based on the latest reported congestion information from NG-RAN via the General Packet Radio System (GPRS) Tunneling Protocol User Plane (GTP-U) header. PSA UPF stops ECN marking when there is no congestion or the congestion ends.

[0067] Option 2 (via openness based on application programming interface (API)): The 5G system can also support opening congestion level information to application function (AF) based on API.

[0068] The host may need to utilize an identifier (e.g., ECT) to distinguish between L4S and classic / non-L4S traffic packets so that the network can recognize / identify and classify them into separate processes.

[0069] Regarding Extended Reality and Media Services (XRM), L4S for non-3GPP access (trusted, untrusted, wired) may become relevant.

[0070] Assume and consider the following scenario: a user equipment (UE) (as an example of a terminal or terminal device) is using a 5G core (5GC) and a non-3GPP access to access an XRM service, and the non-3GPP access is experiencing congestion.

[0071] Fig.15 A schematic diagram of an example of a system environment with signaling variants is shown, and in particular such a scenario is shown.

[0072] Assume that non-3GPP WLAN devices (e.g., WiFi routers) have L4S capabilities, and if the non-3GPP access is experiencing congestion, there is no solution that enables the non-3GPP access to report the congestion information to the 5GC so that the 5GC can take appropriate actions (e.g., L4S mechanism).

[0073] Therefore, a way is sought to enable the L4S marking mechanism for XRM services in non-3GPP access. In addition, a way is sought so that non-3GPP access nodes can send congestion information to UPF for L4S marking. This approach is not only sought for XRM service scenarios, but the solution provided below is also applicable to scenarios including non-XRM services.

[0074] Fig.16 A schematic diagram showing an example of a system environment with signaling variations according to some example embodiments, and in particular showing XRM DL traffic and L4S congestion information flows via non-3GPP access according to some example embodiments.

[0075] like Fig.16 As shown in , XRM DL traffic is flowing to the UE via a non-3GPP access. It is further assumed that the non-3GPP access node (eg, a WLAN router) has L4S capabilities.

[0076] According to some example embodiments, a WLAN router / entity (ie, a non-3GPP access entity) reports congestion information to the 5GC via a Non-3GPP Interworking Function (N3IWF), which is an example of a gateway entity.

[0077] According to some example embodiments, whenever a L4S enabled WLAN router / entity experiences congestion, the WLAN router / entity enables outer IP packets with ECN marking towards the N3IWF.

[0078] According to some example embodiments, the N3IWF may be able to read / decode the ECN indication / packet (set by the WLAN) in the UL direction and determine that the WLAN is experiencing congestion in the DL direction.

[0079] According to some example embodiments, the N3IWF in turn reports congestion information (eg, the number of packets to be L4S ECN marked) to the Session Management Function (SMF) via the Access and Mobility Management Function (AMF).

[0080] According to some example embodiments, the SMF in turn forwards the congestion information to the UPF.

[0081] According to other example embodiments, the N3IWF may report congestion information directly to the UPF via GTP-U.

[0082] According to other example embodiments, before the SMF may trigger the L4S marking indication to the UPF, the SMF may query the N3IWF whether the N3IWF can read / decode the ECN indication (set by the WLAN).

[0083] According to other example embodiments, the congestion information sent from the WLAN / N3IWF can also be sent to the AF using API-based openness (option-2 mentioned above). In this case, when the UPF receives the information from the N3IWF, it does not mark the packet, but forwards the congestion information to the AF (e.g., using UPF openness and service-based architecture (SBA) enhancement (UPEAS) signaling).

[0084] According to other example embodiments, the entry point considered above is not an untrusted non-3GPP entity requiring a N3IWF as a gateway, but a trusted non-3GPP entity requiring a Trusted Non-3GPP Gateway Function (TNGF) as a gateway entity.

[0085] Several example embodiments are described in greater detail below.

[0086] Figure 11 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 10 providing (mobile) access to a network (e.g., a 3GPP network), such as a network external entity (e.g., a non-3GPP access entity) outside the network, such as a WLAN / WiFi router, comprising a detection circuit 11 and a reporting circuit 12. The detection circuit 11 detects a congestion indication in a downlink direction from a first network to a terminal device. The reporting circuit 12 reports the congestion information to a network entity of the first network. Fig. 9 is a schematic diagram of a process according to some example embodiments. Figure 1 The device can perform Fig. 9 method, but not limited to this method. Fig. 9 The method can be Figure 1 The present invention is performed by a device, but is not limited to being performed by the device.

[0087] like Fig. 9 As shown in , the process according to some example embodiments includes the following operations: detecting (S91) a congestion indication in a downlink direction from a first network to a terminal device, and reporting (S92) the congestion information to a network entity of the first network.

[0088] Figure 2 is a block diagram illustrating an apparatus according to some example embodiments. In particular, Figure 2 Shows Figure 1 Thus, according to Figure 2 The device may further include a marking circuit 21 and / or a determination circuit 22.

[0089] In an example embodiment, Figure 1 (or Figure 2 ) can be shared between two physically separate devices forming an operational entity. Therefore, it can be considered that the apparatus shows an operational entity including one or more physically separate devices for performing at least some of the described processes.

[0090] according to Fig. 9 A variation of the process shown in provides details of the reporting operation (S92), which are independent of each other. According to some example embodiments, such reporting operation (S92) may include the following operations: performing explicit congestion notification marking on uplink packets to the network entity of the first network.

[0091] According to other example embodiments, the uplink packet is an external Internet Protocol packet of a protocol stack structure, the protocol stack structure comprising at least an external Internet Protocol packet and an internal Internet Protocol packet contained in the corresponding external Internet Protocol packet.

[0092] according to Fig. 9 A variation of the process shown in provides additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: determining a number of explicit congestion notification markings based on the level of the congestion indication and the rate of downlink packets from the first network.

[0093] According to other example embodiments, the first network is a 3GPP network. According to such example embodiments, the method may be operated at or by an untrusted non-3GPP access entity. According to such example embodiments, the network entity is a non-3GPP interworking function entity.

[0094] According to other example embodiments, the first network is a 3GPP network. According to such example embodiments, the method may be operated at or by a trusted non-3GPP access entity. According to such example embodiments, the network entity is a trusted non-3GPP gateway function entity.

[0095] Figure 3 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 30 that provides access to a network (e.g., a 3GPP network) for a network external entity (e.g., a non-3GPP access entity) outside the network, such as a network gateway entity (e.g., a non-3GPP to 3GPP access entity), such as N3IWF, TNGF, including a receiving circuit 31 and a sending circuit 32. The receiving circuit 31 receives a report from an entity external to a first network, which reports a congestion indication in a downlink direction from the first network to a terminal device. The sending circuit 32 sends information corresponding to the congestion indication to a network entity in the first network. Fig.10 is a schematic diagram of a process according to some example embodiments. Figure 3 The device can perform Fig.10 method, but not limited to this method. Fig.10 The method can be Figure 3 The present invention is performed by a device, but is not limited to being performed by the device.

[0096] like Fig.10 As shown in , the process according to some example embodiments includes the following operations: receiving (S101) a report from an entity outside a first network, which reports a congestion indication in a downlink direction from the first network to a terminal device, and sending (S102) information corresponding to the congestion indication to a network entity in the first network.

[0097] Figure 4 is a block diagram illustrating an apparatus according to some example embodiments. In particular, Figure 4 Shows Figure 3 Thus, according to Figure 4 The device may further include a determination circuit 41 and / or a designation circuit 42.

[0098] In an example embodiment, Figure 3 (or Figure 4 ) can be shared between two physically separate devices forming an operational entity. Therefore, it can be considered that the apparatus shows an operational entity including one or more physically separate devices for performing at least some of the described processes.

[0099] according to Fig.10 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the congestion indication is an explicit congestion notification marking of uplink packets to the network entity of the first network, and the method according to some example embodiments may include the following operations: determining a rate of the explicit congestion notification marking of the uplink packets.

[0100] according to Fig.10 A variation of the process shown in provides details of the sending operation (S102), which are independent of each other. According to some example embodiments, such a sending operation (S102) may include the following operations: based on the rate, specifying the information corresponding to the congestion indication.

[0101] According to other example embodiments, the uplink packet is an external Internet Protocol packet of a protocol stack structure, the protocol stack structure comprising at least an external Internet Protocol packet and an internal Internet Protocol packet contained in the corresponding external Internet Protocol packet.

[0102] according to Fig.10 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a query about the ability to detect the congestion indication, and sending information about the ability to detect the congestion indication.

[0103] according to Fig.10 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a low-latency low-loss scalable throughput indication indicating that at least one protocol data unit session is a low-latency low-loss scalable throughput service, wherein, with respect to the determination, the method only considers that the at least one protocol data unit session is a low-latency low-loss scalable throughput service.

[0104] According to other example embodiments, the first network is a 3GPP network. According to such example embodiments, the method may be operated at or by a non-3GPP interworking function entity. According to such example embodiments, the entity external to the first network is an untrusted non-3GPP access entity. According to such example embodiments, the network entity is an access and mobility management function entity or a session management function entity or a user plane function entity.

[0105] According to other example embodiments, the first network is a 3GPP network. According to such example embodiments, the method may be operated at or by a trusted non-3GPP gateway functional entity. According to such example embodiments, the entity external to the first network is a trusted non-3GPP access entity. According to such example embodiments, the network entity is an access and mobility management functional entity or a session management functional entity or a user plane functional entity.

[0106] according to Fig.10 A variation of the process shown in provides additional operations, which are independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a configuration for reporting congestion information to the user plane function entity, wherein the network entity is the user plane function entity.

[0107] Figure 5 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 50, such as a network entity (e.g., in a first network), such as an AMF, SMF, comprising a receiving circuit 51 and a sending circuit 52. The receiving circuit 51 receives information indicating a congestion indication in a downlink direction from the first network to a terminal device. The sending circuit 52 sends the information to the first network entity, which is configured for downlink packet congestion notification marking. Fig.11 is a schematic diagram of a process according to some example embodiments. Figure 5 The device can perform Fig.11 method, but not limited to this method. Fig.11 The method can be Figure 5 The present invention is performed by a device, but is not limited to being performed by the device.

[0108] like Fig.11 As shown in , the process according to some example embodiments includes the following operations: receiving (S111) information indicating congestion indication in a downlink direction from a first network to a terminal device, and sending (S112) the information to a first network entity, which is configured for downlink packet congestion notification marking.

[0109] In an example embodiment, Figure 5 At least some functions of the apparatus shown in the embodiment may be shared between two physically separate devices forming an operational entity. Therefore, the apparatus may be considered to illustrate an operational entity comprising one or more physically separate devices for performing at least some of the described processes.

[0110] According to further example embodiments, the information corresponds to an explicit congestion notification marking of an uplink packet towards a second network entity of the first network.

[0111] according to Fig.11 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: sending a query to a third network entity about the ability of the third network entity to detect an indication of the congestion indication in the uplink traffic in the downlink direction, and receiving information about the ability of the third network entity to detect the indication.

[0112] according to Fig.11 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: sending a low-latency low-loss scalable throughput indication to the first network entity indicating that at least one protocol data unit session is a low-latency low-loss scalable throughput service. Alternatively or additionally, according to this variation, the method according to some example embodiments may include the following operations: sending a low-latency low-loss scalable throughput indication to the third network entity indicating that at least one protocol data unit session is a low-latency low-loss scalable throughput service.

[0113] According to other example embodiments, the first network is a 3GPP network. According to such example embodiments, the method may be operated at or by an access and mobility management function entity or a session management function entity as the second network entity. According to such example embodiments, the first network entity is a user plane function entity. According to such example embodiments, the third network entity is an untrusted non-3GPP access entity.

[0114] According to other example embodiments, the first network is a 3GPP network. According to such example embodiments, the method may be operated at or by an access and mobility management function entity or a session management function entity as the second network entity. According to such example embodiments, the first network entity is a user plane function entity. According to such example embodiments, the third network entity is a trusted non-3GPP access entity.

[0115] according to Fig.11 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: sending a configuration for accepting congestion information reported by the third network entity to the user plane function entity. Alternatively or additionally, according to this variation, the method according to some example embodiments may include the following operations: sending a configuration for reporting congestion information to the user plane function entity to the third network entity.

[0116] Figure 6 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 60, such as a network entity (e.g., in a first network), such as an AMF, SMF, comprising a sending circuit 61. The sending circuit 61 sends a configuration for accepting congestion information reported by the network entity to a user plane functional entity. Alternatively or additionally, the sending circuit 61 sends a configuration for reporting congestion information to the user plane functional entity to the network entity. Fig.12 is a schematic diagram of a process according to some example embodiments. Figure 6 The device can perform Fig.12 method, but not limited to this method. Fig.12 The method can be Figure 6 The present invention is performed by a device, but is not limited to being performed by the device.

[0117] like Fig.12 As shown in , the process according to some example embodiments includes the following operations: sending (S121) a configuration for accepting congestion information reported by a network entity to a user plane functional entity, and / or sending (S122) a configuration for reporting congestion information to the user plane functional entity to the network entity.

[0118] In an example embodiment, Figure 6 At least some functions of the apparatus shown in the embodiment may be shared between two physically separate devices forming an operational entity. Therefore, the apparatus may be considered to illustrate an operational entity comprising one or more physically separate devices for performing at least some of the described processes.

[0119] Figure 7 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 70, such as a network entity configured for downlink packet congestion notification marking, such as a UPF, comprising a receiving circuit 71 and a marking circuit 72. The receiving circuit 71 receives information indicating a congestion indication in a downlink direction from a first network to a terminal device. The marking circuit 72 performs explicit congestion notification marking on downlink packets in the downlink direction according to the received information. Fig.13 is a schematic diagram of a process according to some example embodiments. Figure 7 The device can perform Fig.13 method, but not limited to this method. Fig.13 The method can be Figure 7 The present invention is performed by a device, but is not limited to being performed by the device.

[0120] like Fig.13 As shown in , the process according to some example embodiments includes the following operations: receiving (S131) ​​information indicating congestion indication in a downlink direction from a first network to a terminal device, and based on the received information, explicitly marking a downlink packet in the downlink direction with a congestion notification (S132).

[0121] In an example embodiment, Figure 7 At least some functions of the apparatus shown in the embodiment may be shared between two physically separate devices forming an operational entity. Therefore, the apparatus may be considered to illustrate an operational entity comprising one or more physically separate devices for performing at least some of the described processes.

[0122] According to further example embodiments, the information corresponds to an explicit congestion notification marking of uplink packets towards a network entity of the first network.

[0123] According to other example embodiments, said information corresponds to a rate or a number of said explicit congestion notification markings of said downlink packets.

[0124] according to Fig.13 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a low-delay low-loss scalable throughput indication indicating that at least one protocol data unit session is a low-delay low-loss scalable throughput service.

[0125] according to Fig.13 A variation of the process shown in , provides additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a configuration for accepting reported congestion information.

[0126] Figure 8 8 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 80, such as a network entity configured for downlink packet congestion notification marking, such as a UPF, comprising a receiving circuit 81 and a sending circuit 82. The receiving circuit 81 receives information indicating a congestion indication in a downlink direction from a first network to a terminal device. The sending circuit 82 sends the information to an application function entity. Fig.14is a schematic diagram of a process according to some example embodiments. Figure 8 The device can perform Fig.14 method, but not limited to this method. Fig.14 The method can be Figure 8 The present invention is performed by a device, but is not limited to being performed by the device.

[0127] like Fig.14 As shown in , the process according to some example embodiments includes the following operations: receiving (S141) information indicating congestion indication in a downlink direction from a first network to a terminal device, and sending (S142) the information to an application function entity.

[0128] In an example embodiment, Figure 8 At least some functions of the apparatus shown in the embodiment may be shared between two physically separate devices forming an operational entity. Therefore, the apparatus may be considered to illustrate an operational entity comprising one or more physically separate devices for performing at least some of the described processes.

[0129] According to further example embodiments, the information corresponds to an explicit congestion notification marking of uplink packets towards a network entity of the first network.

[0130] According to other example embodiments, said information corresponds to a rate or a number of said explicit congestion notification markings of said downlink packets.

[0131] according to Fig.14 A variation of the process shown in , providing additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a low-delay low-loss scalable throughput indication indicating that at least one protocol data unit session is a low-delay low-loss scalable throughput service.

[0132] according to Fig.14 A variation of the process shown in , provides additional operations, which are themselves independent of each other. According to this variation, the method according to some example embodiments may include the following operations: receiving a configuration for accepting reported congestion information.

[0133] Several of the example embodiments summarized and detailed above are now described in more specific terms.

[0134] Fig.17 A schematic diagram showing an example of a protocol stack according to some example embodiments, and in particular showing a non-3GPP protocol stack for the control plane and the user plane of a N3IWF.

[0135] Regarding the control plane (CP) protocol stack, it will be noted that at the end of the registration process, a signaling IPsec SA is established between the UE and the N3IWF, after which the UE establishes a Transmission Control Protocol (TCP) / IP connection with the N3IWF for non-access stratum (NAS) message transport via the internal IP address and the signaling IPsec SA. IPsec tunnel mode is employed for the signaling SA to protect and encrypt the original IP signaling packets and the port numbers used for the communication of such IP packets.

[0136] Regarding the user plane (UP) protocol stack, it will be noted that the UP protocol stack involves protocols in the UE, WLAN, N3IWF, and UPF for transmitting UP traffic between the UE and the data network. The IPsec tunnel mode is adopted for the established sub-SA to protect and encrypt the original IP user data packets and the port number used for the communication of such IP packets.

[0137] It will also be noted that the IP between the WLAN and the N3IWF is referred to as the external IP, and the IP layer between the UE and the N3IWF is referred to as the internal IP. According to some example embodiments, the external IP packets are used to indicate / send congestion information (regarding ECN marked packets) between the WLAN and the N3IWF.

[0138] Fig.18 A schematic diagram of a signaling sequence according to some example embodiments is shown, and in particular a call flow related to L4S congestion in non-3GPP access is shown.

[0139] according to Fig.18 In some example embodiments shown in , the WLAN experiences congestion. The WLAN router marks the outer IP (only the layer between WLAN and N3IWF, and transparent to AMF / UPF) packets with the ECN bit.

[0140] The marking percentage may be calculated according to the congestion level and the UE DL traffic rate, etc.

[0141] According to some example embodiments, a PDU session specific external IP address may be configured (eg, a separate IPSec tunnel for each PDU session of the UE).

[0142] According to some example embodiments, the N3IWF reads / decodes the ECN indication / packet (set by the WLAN) in the UL direction and determines that the WLAN is experiencing congestion in the DL direction. This functionality is not a standard feature in the N3IWF node and must be enabled.

[0143] According to some example embodiments, the N3IWF is also capable of identifying / recognizing the L4S service / PDU session (SMF sends L4S indication).

[0144] In this regard, according to some example embodiments, the SMF queries the N3IWF whether the N3IWF can read / decode the ECN indication (set by the WLAN), and thus ensures that the N3IWF can read / decode the ECN indication.

[0145] According to some example embodiments, the SMF enables L4S detection and marking mechanisms in the network.

[0146] This can be done in two ways:

[0147] Mode 1. According to some example embodiments, when N3IWF reports congestion information (e.g., the number of packets to be L4S ECN marked) to SMF via AMF (e.g., using PDU session resource establishment via N1N2Msg),

[0148] -SMF sends L4S indication to N3IWF and UPF (e.g. to indicate which PDU sessions are L4S services),

[0149] -SMF then forwards the congestion information to UPF,

[0150] -UPF performs ECN marking on DL packets according to the congestion information (percentage of packets to be marked for this DL PDU session),

[0151] - Alternatively, the UPF forwards the congestion information to the AF using the above mentioned API open option.

[0152] Mode 2. According to some example embodiments, the SMF configures the N3IWF to report congestion information to the UPF. The SMF also configures the UPF to initiate ECN marking when it receives congestion information from the N3IWF. Therefore, according to some example embodiments, the N3IWF can report congestion information directly to the UPF via GTP-U. When the UPF receives the congestion information, it ECN marks the DL packet (alternatively, the UPF forwards the congestion information to the AF using the above-mentioned API open option). The N3IWF marks a specific GTP-U header (i.e., a specific PDU session) that is indicated by the SMF during the creation of the PDU session resources as carrying L4S services. The N3IWF accepts ECN marking from the WLAN only for those IPSec SA tunnels that are mapped to PDUs carrying L4S services.

[0153] According to some of the example embodiments, ECN marked packets arrive at the UE (application client), and the UE (application client) informs the sender application (AS) about the congestion level.

[0154] Fig.19A schematic diagram of an example of a protocol stack according to some example embodiments is shown, and in particular a (5GC) non-3GPP protocol stack for TNGF is shown.

[0155] That is, some example embodiments are also applicable to the scenario where the TNGF represents a gateway to which the non-3GPP entity sends congestion information. Therefore, the above process / principle can also be used in this case.

[0156] Fig. 20 A schematic diagram showing an example of a system environment with signalling variations according to some example embodiments is shown, and in particular the following scenario deviating from the above-described non-3GPP entry scenario is shown.

[0157] In this scenario, the UE is connected to a 5G residential gateway (5G-RG) device via a WiFI access point (AP) or via an Ethernet (802.11) connection, which in turn is connected to the N3IWF via an access network (AN) and a wired access gateway function (W-AGF).

[0158] In this case, according to some example embodiments, congestion information is sent to 5GC via 5G-RG. Therefore, the above process / principle can also be used in this case.

[0159] In addition, in the scenario where the UE is connected to the 5GC via a fixed network residential gateway (FN-RG) device (i.e., FN-RG->wired AN->W-AGF->N3IWF->5GC / UPF), the above process / principle can also be used in this case.

[0160] The above-mentioned processes and functions may be implemented by corresponding functional elements, processors or the like as described below.

[0161] In the above description of the network entity, only the units relevant to understanding the various aspects of the present subject disclosure are described using functional blocks. The network entity may include other units for its corresponding operations. However, the description of these units is omitted in this specification. The arrangement of the functional blocks of the device is not to be construed as limiting the present subject disclosure, and these functions may be performed by one block or further divided into sub-blocks.

[0162] When it is stated in the above description that an apparatus, i.e. a network node or entity (or some other component) is configured to perform a certain function, this will be interpreted as equivalent to the following description: it is stated that one (i.e., at least one) processor or corresponding circuit (possibly in cooperation with a computer program code stored in a memory of the corresponding apparatus) is configured to cause the apparatus to perform at least the functions thus mentioned. In addition, such functions will be interpreted as equivalent to being implementable by specially configured circuits or components for performing the corresponding functions (i.e., the expression "a unit configured to..." is interpreted as equivalent to expressions such as "components for...").

[0163] exist Fig.21 , an alternative schematic diagram of an apparatus according to some example embodiments is shown. Fig.21 As shown in, according to some example embodiments, the device (network node or entity) 10' (corresponding to the network node or entity 10) includes a processor 211, a memory 212 and an interface 213, which are connected via a bus 214 or the like. In addition, the device (network node or entity) 30' (corresponding to the network node or entity 30) includes a processor 211, a memory 212 and an interface 213, which are connected via a bus 214 or the like. In addition, the device (network node or entity) 50' (corresponding to the network node or entity 50) includes a processor 211, a memory 212 and an interface 213, which are connected via a bus 214 or the like. In addition, the device (network node or entity) 60' (corresponding to the network node or entity 60) includes a processor 211, a memory 212 and an interface 213, which are connected via a bus 214 or the like. In addition, the device (network node or entity) 70' (corresponding to the network node or entity 70) includes a processor 211, a memory 212 and an interface 213, which are connected via a bus 214 or the like. In addition, the device (network node or entity) 80' (corresponding to the network node or entity 80) includes a processor 211, a memory 212 and an interface 213, which are connected via a bus 214 or the like. These devices can be connected to another device via a link 215, such as one of the corresponding other devices 10, 30, 50, 60, 70, 80.

[0164] The processor 211 and / or the interface 213 may also include a modem or the like to facilitate communication via a (hardwired or wireless) link, respectively. The interface 213 may include a suitable transceiver coupled to one or more antennas or communication components for communicating (hardwired or wireless) with a linked or connected device, respectively. The interface 213 is typically configured to communicate with at least one other device (i.e., its interface).

[0165] The memory 212 may store a corresponding program considered to include program instructions or computer program codes that, when executed by a corresponding processor, enable a corresponding electronic device or apparatus to operate in accordance with various example embodiments of the present subject disclosure.

[0166] Generally, the corresponding devices / apparatuses (and / or parts thereof) may represent components for performing corresponding operations and / or displaying corresponding functions, and / or the corresponding devices (and / or parts thereof) may have functions for performing corresponding operations and / or displaying corresponding functions.

[0167] When it is stated in the subsequent description that a processor (or some other component) is configured to perform a certain function, this will be interpreted as equivalent to the following description: it states that at least one processor (possibly in cooperation with computer program code stored in the memory of the corresponding device) is configured to cause the device to perform at least the function mentioned thereby. In addition, such functions will be interpreted as equivalent to being implementable by components specially configured for performing the corresponding functions (i.e., the expression "the processor is configured to [cause the device] to perform xxx" is interpreted as equivalent to expressions such as "components for xxx").

[0168] According to some example embodiments, an apparatus representing a network node or entity 10 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communication with at least one other apparatus. The processor (i.e., at least one processor 211 together with at least one memory 212 and computer program code) is configured to perform: detecting a congestion indication in a downlink direction from a first network to a terminal device (the apparatus thus comprises corresponding components for detecting), and reporting the congestion information to a network entity of the first network (the apparatus thus comprises corresponding components for reporting).

[0169] According to some example embodiments, an apparatus representing a network node or entity 30 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communicating with at least another apparatus. The processor (i.e., at least one processor 211 together with at least one memory 212 and computer program code) is configured to perform: receiving a report from an entity external to a first network, the report reporting a congestion indication in a downlink direction from the first network to a terminal device (the apparatus thus comprises corresponding components for receiving), and sending information corresponding to the congestion indication to a network entity in the first network (the apparatus thus comprises corresponding components for sending).

[0170] According to some example embodiments, the apparatus representing a network node or entity 50 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (i.e., at least one processor 211 together with at least one memory 212 and computer program code) is configured to perform: receiving information indicating a congestion indication in a downlink direction from a first network to a terminal device (the apparatus thus comprises corresponding components for receiving), and sending said information to a first network entity configured for downlink packet congestion notification marking (the apparatus thus comprises corresponding components for sending).

[0171] According to some example embodiments, the apparatus representing a network node or entity 60 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured to communicate with at least another apparatus. The processor (i.e., at least one processor 211 together with at least one memory 212 and computer program code) is configured to perform: sending a configuration for accepting congestion information reported by a network entity to a user plane functional entity (the apparatus therefore comprises corresponding components for sending), and / or sending a configuration for reporting congestion information to the user plane functional entity to the network entity.

[0172] According to some example embodiments, the apparatus representing a network node or entity 70 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communication with at least another apparatus. The processor (i.e., at least one processor 211 together with at least one memory 212 and computer program code) is configured to perform: receiving information indicating a congestion indication in a downlink direction from a first network to a terminal device (the apparatus thus comprises corresponding components for receiving), and based on the received information, performing explicit congestion notification marking on downlink packets in the downlink direction (the apparatus thus comprises corresponding components for (explicit congestion notification) marking).

[0173] According to some example embodiments, the apparatus representing a network node or entity 80 comprises at least one processor 211, at least one memory 212 comprising computer program code, and at least one interface 213 configured for communication with at least one other apparatus. The processor (i.e., at least one processor 211 together with at least one memory 212 and computer program code) is configured to perform: receiving information indicating a congestion indication in a downlink direction from a first network to a terminal device (the apparatus thus comprises corresponding components for receiving), and sending said information to an application function entity (the apparatus thus comprises corresponding components for sending).

[0174] For further details on the operability / functionality of the individual devices, reference is made to the above referenced Figures 1 to 20 Description of any of the items.

[0175] For purposes of the present subject disclosure as described above, it should be noted that:

[0176] - the method steps, which may be implemented as software code portions and executed using a processor at a network server or network entity (as an example of a device, apparatus and / or its modules, or therefore as an example of an entity comprising apparatus and / or modules), are independent of the software code and may be specified using any known or future developed programming language, as long as the functionality defined by the method steps is preserved;

[0177] - generally, any method step is suitable for being implemented as software or by hardware without changing the concept of the exemplary embodiments and their modification in terms of the implemented functions;

[0178] - the method steps and / or devices, units or parts that may be implemented as hardware components at the apparatus defined above or any module thereof (e.g., a device that performs the functions of the apparatus according to the embodiments described above) are hardware independent and may be implemented using any known or future developed hardware technology or any mixture of these technologies, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using, for example, ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field Programmable Gate Array) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;

[0179] - devices, units or components (e.g., the network entities or network registers defined above, or any of their corresponding units / components) may be implemented as separate devices, units or components, but this does not exclude that they may be implemented in a distributed manner throughout the system, as long as the functionality of the devices, units or components is preserved;

[0180] - the device (such as user equipment and network entity / network register) may be represented by a semiconductor chip, a chipset or a (hardware) module comprising such a chip or chipset; however, this does not exclude the possibility that the functionality of the device or module is not implemented by hardware but is implemented as software in a (software) module, such as a computer program or computer program product comprising executable software code portions for execution / running on a processor;

[0181] - A device may be regarded as an apparatus or an assembly of more than one apparatus, whether functionally cooperating with each other or functionally independent of each other but for example in the same apparatus housing.

[0182] In general, it should be noted that the corresponding functional blocks or elements according to the above aspects can be implemented in hardware and / or software by any known means, respectively, provided that they are only suitable for performing the functions of the corresponding parts. The method steps can be implemented in separate functional blocks or by separate devices, or one or more method steps can be implemented in a single functional block or by a single device.

[0183] Generally, any method step is suitable for implementation as software or by hardware without changing the concepts disclosed in the subject matter. Devices and components may be implemented as separate devices, but this does not exclude that they may be implemented in a distributed manner throughout the system, as long as the functionality of the device is preserved. This and similar principles will be considered to be known to the skilled person.

[0184] Software in the sense of the present subject disclosure comprises the software code itself, including code means or portions or a computer program or computer program product for performing the corresponding functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium (such as a computer-readable (storage) medium on which the corresponding data structures or code means / portions are stored) or embodied in a signal or chip (possibly during its processing).

[0185] The subject disclosure also covers any combination of the above method steps and operations, and any conceivable combination of the above nodes, devices, modules, or elements, as long as the concepts of the above methods and structural arrangements are applicable.

[0186] In view of the above, measures for inter-network congestion reporting are provided. Such measures may include: receiving a report from an entity external to a first network (e.g., at a network gateway entity that provides access to the network for network external entities external to the network), the report reporting a congestion indication in a downlink direction from the first network to a terminal device, and sending information corresponding to the congestion indication to a network entity in the first network.

[0187] Although the subject disclosure is described above with reference to various exemplary embodiments according to the accompanying drawings, it will be understood that the subject disclosure is not limited thereto. Rather, it will be apparent to those skilled in the art that the subject disclosure may be modified in many ways without departing from the various exemplary embodiments disclosed herein.

[0188] List of acronyms and abbreviations

[0189] 3GPP Third Generation Partnership Project

[0190] 5G Fifth Generation

[0191] 5GC 5G Core

[0192] 5G-RG 5G Residential Gateway

[0193] AF Application Function

[0194] AMF Access and Mobility Management Function

[0195] AN Access Network

[0196] AP Access Point

[0197] API Application Programming Interface

[0198] AQM Active Queue Management

[0199] Congestion experienced by CE

[0200] CP Control Plane

[0201] DL Downlink

[0202] ECN Explicit Congestion Notification

[0203] ECT ECN-capable transport

[0204] FN-RG Fixed Network Residential Gateway

[0205] GPRS General Packet Radio System

[0206] GTP-U GPRS Tunneling Protocol User Plane

[0207] IP Internet Protocol

[0208] IPSec IP Security

[0209] L4S Low latency, low loss, scalable throughput

[0210] NAS Non-Access Stratum

[0211] NG-RAN Next Generation Radio Access Network

[0212] N3IWF non-3GPP interworking function

[0213] PCC Policy and Charging Control

[0214] PCF Policy Control Function

[0215] PDU Protocol / Packet Data Unit

[0216] PSA PDU Session Anchor

[0217] QoS Quality of Service

[0218] RTP Real Time Protocol

[0219] SBA Service-Based Architecture

[0220] SMF session management functions

[0221] TCP Transmission Control Protocol

[0222] TNGF Trusted Non-3GPP Gateway Function

[0223] UE User Equipment

[0224] UL Uplink

[0225] UP User Plane

[0226] UPEAS UPF opening and SBA enhancement

[0227] UPF user plane function

[0228] W-AGF Wired Access Gateway Function

[0229] XR

[0230] XRM Extended Reality and Media Services

Claims

1. A method comprising: detecting an indication of congestion in a downlink direction from the first network to the terminal device, and Report the congestion information to a network entity of the first network.

2. The method according to claim 1, wherein: Regarding the reporting, the method further comprises: Uplink packets to the network entity of the first network are explicitly marked for congestion notification.

3. A method comprising: receiving a report from an entity external to the first network, the report reporting an indication of congestion in a downlink direction from the first network to a terminal device, and Sending information corresponding to the congestion indication to a network entity in the first network.

4. The method according to claim 3, wherein: The congestion indication is an explicit congestion notification marking of uplink packets to the network entity of the first network, and the method further comprises: A rate of the explicit congestion notification marking of the uplink packets is determined.

5. A method comprising: receiving information indicating an indication of congestion in a downlink direction from the first network to the terminal device, and The information is sent to a first network entity, the first network entity being configured for downlink packet congestion notification marking.

6. The method according to claim 5, wherein: The information corresponds to an explicit congestion notification marking of an uplink packet to a second network entity of the first network.

7. A method comprising: Sending to the user plane functional entity a configuration for accepting congestion information reported by the network entity, and / or Sending to the network entity a configuration for reporting congestion information to the user plane function entity.

8. A method comprising: receiving information indicating an indication of congestion in a downlink direction from the first network to the terminal device, and Downlink packets in the downlink direction are marked with explicit congestion notification based on the received information.

9. A method comprising: receiving information indicating an indication of congestion in a downlink direction from the first network to the terminal device, and The information is sent to the application function entity.

10. An apparatus comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another device, The at least one processor together with the at least one memory and the computer program code is configured to cause the apparatus to perform the method according to any one of claims 1 to 9.

11. A computer program product comprising computer executable computer program code, which, when the program is run on a computer, is configured to cause the computer to perform the method according to any one of claims 1 to 9.

Images