Flow specific congestion handling

Abstract

There are provided measures for flow specific congestion handling. Such measures may comprise determining, for a first congestion notification flag enabled traffic flow, parameter information for modifying a congestion notification flag rate to be applied to the first congestion notification flag enabled traffic flow, and sending a message comprising the parameter information to a network entity.

Description

Technical Field

[0001] Various exemplary embodiments of the subject disclosure generally relate to flow-specific congestion handling. More specifically, various exemplary embodiments relate to measures (including methods, apparatus, and computer program products) for implementing flow-specific congestion handling. 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: determining, for a first congestion notification marking enabled traffic flow, parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking enabled traffic flow, and sending a message to a network entity, the message including the parameter information.

[0008] According to one aspect, a method is provided, comprising: receiving a first message from an application function entity, the first message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled service flow, and sending a second message to a congestion notification marking responsible entity, the second message comprising the parameter information.

[0009] According to one aspect, a method is provided, comprising: receiving a message from a network entity, the message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking-enabled service flow, detecting packet queue delay information related to the first congestion notification marking-enabled service flow, the packet queue delay information indicating a congestion level, and determining the congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow based on the packet queue delay information, a general congestion notification marking rule, and the parameter information.

[0010] According to one aspect, an apparatus is provided, comprising: a decision circuit configured to: for a first congestion notification marking-enabled service flow, decide parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow, and a sending circuit configured to: send a message to a network entity, the message including the parameter information.

[0011] According to one aspect, an apparatus is provided, comprising: a receiving circuit configured to: receive a first message from an application function entity, the first message comprising parameter information for modifying a congestion notification marking rate to be applied to a service flow enabled by a first congestion notification marking, and a sending circuit configured to: send a second message to a congestion notification marking responsible entity, the second message comprising the parameter information.

[0012] According to one aspect, an apparatus is provided, comprising: a receiving circuit configured to: receive a message from a network entity, the message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking-enabled service flow, a detecting circuit configured to: detect packet queue delay information related to the first congestion notification marking-enabled service flow, the packet queue delay information indicating a congestion level, and a determining circuit configured to: determine the congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow based on the packet queue delay information, a general congestion notification marking rule and the parameter information.

[0013] 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: for a first congestion notification marking-enabled service flow, determining parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow, and sending a message to a network entity, the message including the parameter information.

[0014] 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 first message from an application function entity, the first message including parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking-enabled service flow, and sending a second message to a congestion notification marking responsible entity, the second message including the parameter information.

[0015] 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, configured to cause the apparatus to perform: receiving a message from a network entity, the message including parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking-enabled service flow, detecting packet queue delay information related to the first congestion notification marking-enabled service flow, the packet queue delay information indicating a congestion level, and determining the congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow based on the packet queue delay information, a general congestion notification marking rule, and the parameter information.

[0016] 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.

[0017] 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.

[0018] Any of the above aspects or other aspects described herein facilitate optimizing the provision and utilization of congestion reduction control assistance, 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.

[0019] In some example embodiments, flow-specific congestion handling is provided. More specifically, measures and mechanisms for implementing flow-specific congestion handling are provided.

[0020] Thus, optimization may be achieved through methods, apparatus, and computer program products that enable / implement flow-specific congestion handling. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] 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,

[0022] in:

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

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

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

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

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

[0028] Figure 6 is a schematic diagram of a process according to some example embodiments;

[0029] Figure 7 is a schematic diagram of a process according to some example embodiments;

[0030] Figure 8 is a schematic diagram of a process according to some example embodiments;

[0031] Fig. 9 a schematic diagram illustrating a signaling sequence according to some example embodiments; and

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

[0033] 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.

[0034] It will be noted that the following description of the subject disclosure and its various example embodiments refers to specifications used as non-limiting 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 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.

[0035] 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).

[0036] 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.

[0037] An apparatus configured for congestion handling and communications related to congestion handling is provided. As further described in detail herein, one or more problems may arise when congestion is handled differently for different traffic flows that are not configured. Flow-specific congestion handling may provide advantages and optimizations for certain use cases.

[0038] According to some example embodiments, measures and mechanisms for (enabling / realizing) flow specific congestion handling are provided.

[0039] 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.

[0040] 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.

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

[0042] 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.

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

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

[0045] 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.

[0046] - 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.

[0047] -Method 2: PSA UPF performs ECN marking for the uplink (UL) and downlink (DL) IP layers of received packets based on the congestion information most recently reported 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.

[0048] 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.

[0049] QoS flows may be enabled for L4S requirements with ECN marking, e.g. statically when a PDU session is established based on configuration in a Session Management Function (SMF) or Policy Control Function (PCF), or dynamically based on detection of L4S traffic, e.g. via ECN-capable transport (ECT) and / or IP 5-tuple in the IP header, whereby the SMF or PCF triggers establishment of a QoS flow enabled for L4S, or enabled by a request by the AF.

[0050] For some cases, the host will utilize an identifier (e.g., ECT) to distinguish between L4S and classic / non-L4S traffic packets so that the network can classify them into separate processes.

[0051] An application server may provide L4S-capable (multi)media services that may be sent via a single or multiple QoS flows in a 5G system (5GS).

[0052] In the current scheme, when the NG-RAN experiences congestion, it will decide the number / percentage of packets to be (ECN) marked for each incoming QoS (L4S) traffic.

[0053] The percentage per QoS flow can be calculated relative to the packet inflow rate (5G QoS Identifier (5QI) / Bitrate) of the specific QoS flow (e.g., a flow delivering more packets to the network will be marked more and vice versa).

[0054] When there are multiple L4S service flows in 5GS, the following problems may occur:

[0055] - The AF cannot distinguish some L4S services from other services, for example, if the AF wants some priority L4S service flows to be treated differently in terms of marking packets during congestion, or if the AF wants to update the priority treatment of certain L4S services at runtime (e.g., an urgent news feed in the middle of real-time news).

[0056] - In some scenarios, one or more heavy (e.g., high data rate, high throughput, high capacity) application traffic may enter the 5GS and may cause the 5G network to become congested. If the AF wants to set a higher marking probability for these heavily injected flows than for the conventionally marked flows (based on their 5QI or packet error rate (PER) or packet injection rate), this is not possible under the current mechanism.

[0057] - In some scenarios, the affected L4S service flows may belong to the same User Equipment (UE) (e.g., one QoS flow for audio vs. one QoS flow for video for the same PDU session). When congestion occurs, if the AF wants to prioritize (e.g., mark less) video over audio when marking (but, in addition, video should get a higher marking according to 5QI or ARP or packet injection rate), this is not possible with the current mechanism.

[0058] - In some scenarios, QoS flows may belong to different UEs (assuming both UEs are served under the same RAN / UPF) and may therefore need to be handled differently (e.g. one UE is a priority UE / subscriber and may therefore need packets to be marked differently, even after using ARQ / 5QI).

[0059] - UE / subscriber can request and choose the quality of streaming video by selecting "Best Quality" vs. "Best Effort" streaming. Here, "Best Quality" indicates that the user prioritizes the best video quality and packet drops or stops will not cause trouble / concern. On the other hand, "Best Effort" indicates continuous streaming (no gaps) without worrying about video quality. With current L4S mechanisms, this distinction cannot be provided.

[0060] - This chaotic scenario (multiple L4S application flows impacting each other) may persist and / or occur during a certain period of time. If any changes / measures are taken during this period of time without recovery, it may lead to non-optimal conditions for the application flows and the network.

[0061] Therefore, we need to find a way so that the AF can provide some control assistance to the RAN to handle the ECN marking percentage of certain L4S service flows differently for fairness or any other reasons.

[0062] Some example embodiments start from the concept that an AF may be a good candidate that can predict and attempt to provide fairness between L4S application traffic types.

[0063] Thus, according to some example embodiments, the AF predicts and attempts to provide fairness between L4S application traffic types by observing the type of application, the number of such L4S type application traffic flows sent via the 3GPP network at any point in time, any specific differences (e.g., characteristics) of such type of application, the expected duration of such scenario (multiple applications simultaneously), etc.

[0064] According to some example embodiments, the AF understands the characteristics of different application types (eg, L4S type application flows).

[0065] Therefore, according to some example embodiments, the AF indicates to the 5G core (5GC) a "sensitivity parameter" (parameter information) for each L4S type service flow. The sensitivity parameter (or just "sensitivity") can be a multiplier value (e.g., 1 / 2 or 1 / 3, etc.) or a percentage value (e.g., 50%, 30%, etc.).

[0066] According to some example embodiments, the sensitivity parameter will help the intermediate L4S node (NG-RAN) that may perform ECN marking to customize (e.g., increase or decrease) the ECN marking accordingly (e.g., the percentage of packets to be marked).

[0067] For example, for a congestion level of 40%, the RAN will mark X% of the packets of a specific L4S QoS flow (e.g. application service F1). If the sensitivity of F1 is (set to) 90%, the 5GC node can increase the marking percentage to 2*X% or 3*X% (so that the sending host / application will significantly reduce the data rate). If the sensitivity of flow F1 is (set to) 10%, the marking can be kept the same as X% or reduced to 0.5*X% (if the marking percentage of some business flows is reduced, the marking percentage of some other business flows may need to be increased, as the RAN may decide to reduce the overall specific inflow level of packets in various flows).

[0068] According to some example embodiments, the exact correlation between the sensitivity to the congestion level and the marking percentage may be implementation specific.

[0069] In the case of simplification (implementation), sensitivity can also be categorized as a high, medium or low indication (per application flow or QoS flow) rather than a multiplier value or a percentage value.

[0070] According to some example embodiments, the maximum RAN marking percentage will be determined by the RAN. The sensitivity parameter will be aligned with the range of RAN marking percentages.

[0071] According to some example embodiments, multiple flows (belonging to the same UE) may be identified by a common ID to obtain a common relationship.

[0072] According to other example embodiments, the AF defines and indicates a time window for sensitivity indication.

[0073] The sensitivity of the flow remains in effect until the specified time period expires. According to some example embodiments, after the given time period expires, the 5GC removes the sensitivity constraint and operates in normal mode (e.g., no sensitivity-based differential marking / processing) unless the AF sends / updates with a new sensitivity and time window.

[0074] According to some example embodiments, the sensitivity parameter is provided as a list of marking percentages (or other multiplier values ​​or categories), each marking percentage being associated with a congestion value / range and / or a congestion interval.

[0075] An example sensitivity information parameter list may be as follows:

[0076] -{Sensitivity X1, trigger condition: congestion level is higher than Y1% or between Y1% and Y2%},

[0077] -{Sensitivity X2, trigger condition: congestion level is higher than Y2% or between Y2% and Y3%}.

[0078] According to other example embodiments, the AF dynamically changes the sensitivity of a traffic flow and indicates the same to the 5GC in the middle of a session (i.e., after an application traffic flow has started). This may depend on the number of such flows entering the system, or on the congestion behavior of the network - by obtaining direct congestion reports or UL / DL / round trip delay information from the 5GC.

[0079] According to an example embodiment, the AF may send an updated time window before / after the current window expires.

[0080] Such control may be applied to one or more QoS flows or PDU sessions belonging to the same UE.According to some example embodiments, multiple flows (belonging to the same UE) are identified by a common ID to obtain a common relationship.

[0081] According to some example embodiments, the UE may have selected a specific option for L4S sensitivity and informed its application / AF. For example, when watching a streaming video, a user may select "Best Quality" versus "Best Effort" streaming, as described above. Thus, in some example embodiments, the AF may apply a sensitivity index / parameter based on the user's needs. In other words, "Best Quality" will have a lower sensitivity so that the network will not apply L4S markings heavily in times of congestion; instead, it may drop packets. Similarly, in the case of "Best Effort", the sensitivity will be higher, which will result in a large number of L4S markings, and will result in the application controlling the flow rate.

[0082] According to other example embodiments, multiple UE scenarios are considered. For example, one or more QoS flows belonging to one or more UEs may flow through the same RAN and / or UPF. In this case, according to some example embodiments, sensitivity may be applied to further distribute markings among UEs based on the application.

[0083] According to other example embodiments, if application layer forward error correction (AL-FEC) is enabled for an L4S service flow, any auxiliary information from the AF or characteristics of the AL-FEC are considered when determining the sensitivity parameters for that flow. This is because after enabling AL-FEC, the service flow and rate may further change due to redundancy.

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

[0085] Figure 11 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 10 (such as an application function entity, e.g., AF), comprising a decision circuit 11 and a sending circuit 12. The decision circuit 11 decides, for a first congestion notification marking enabled service flow, parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking enabled service flow. The sending circuit 12 sends a message to a network entity, the message including the parameter information. Figure 6 is a schematic diagram of a process according to some example embodiments. Figure 1 The device can perform Figure 6 method, but not limited to this method. Figure 6 The method can be Figure 1 The present invention is performed by a device, but is not limited to being performed by the device.

[0086] like Figure 6 As shown in , the process according to some example embodiments includes the following operations: for a first congestion notification marking-enabled service flow, determining (S61) parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow, and sending (S62) a message to a network entity, the message including the parameter information.

[0087] 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 determination circuit 21.

[0088] 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.

[0089] according to Figure 6 A variation of the process shown in , provides details of the decision operation (S61), which are independent of each other. According to some example embodiments, such a decision operation (S61) may include an operation of determining the parameter information based on at least one of the following:

[0090] - an application type of the application of the traffic flow causing said first congestion notification marking to be enabled,

[0091] - characteristics of said application of the traffic flow causing said first congestion notification marking to be enabled,

[0092] - the number of concurrently existing congestion notification marking enabled traffic flows including the first congestion notification marking enabled traffic flow,

[0093] - the expected duration of the scenario in which the current congestion notification marking is enabled for the traffic flow,

[0094] - user selection of said application in relation to a traffic flow which results in said first congestion notification marking being enabled, or

[0095] -Application layer forward error correction related information.

[0096] According to other example embodiments, the message includes validity time information associated with the parameter information, the validity time information indicating a validity time of the parameter information.

[0097] According to other example embodiments, the parameter information includes multiplier information or percentage information.

[0098] According to other example embodiments, the parameter information includes congestion level information (ie, category information according to classification, for example, "low", "medium", "high").

[0099] According to other example embodiments, the parameter information comprises a list of parameter information elements, each parameter information element of the list being associated with a respective congestion level condition.

[0100] According to other example embodiments, at least two congestion notification marking enabled traffic flows associated with the terminal, including the first congestion notification marking enabled traffic flow, are identified using a single identifier, and the message includes the single identifier associated with the parameter information.

[0101] According to other example embodiments, the message is an update message configured to update the parameter information for the first congestion notification marking enabled traffic flow.

[0102] Figure 3 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 30 (e.g., SMF, PCF, NEF), comprising a receiving circuit 31 and a sending circuit 32. The receiving circuit 31 receives a first message from an application function entity, the first message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled service flow. The sending circuit 32 sends a second message to a congestion notification marking responsible entity, the second message comprising the parameter information. Figure 7 is a schematic diagram of a process according to some example embodiments. Figure 3 The device can perform Figure 7 method, but not limited to this method. Figure 7 The method can be Figure 3 The present invention is performed by a device, but is not limited to being performed by the device.

[0103] like Figure 7 As shown in , the process according to some example embodiments includes the following operations: receiving (S71) a first message from an application function entity, the first message including parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking-enabled service flow, and sending (S72) a second message to a congestion notification marking responsible entity, the second message including the parameter information.

[0104] The second information may be equal to the first information.

[0105] In an example embodiment, Figure 3 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.

[0106] According to other example embodiments, the first message includes validity time information associated with the parameter information, the validity time information indicating a validity time of the parameter information, and the second message includes the validity time information associated with the parameter information.

[0107] According to other example embodiments, the parameter information includes multiplier information or percentage information.

[0108] According to other example embodiments, the parameter information includes congestion level information (ie, category information according to classification, for example, "low", "medium", "high").

[0109] According to other example embodiments, the parameter information comprises a list of parameter information elements, each parameter information element of the list being associated with a respective congestion level condition.

[0110] According to other example embodiments, a single identifier is used to identify at least two congestion notification marking-enabled service flows associated with a terminal, including the first congestion notification marking-enabled service flow, the first message includes the single identifier associated with the parameter information, and the second message includes the single identifier associated with the parameter information.

[0111] According to other example embodiments, the first message is an update message configured to update the parameter information for the first congestion notification marking enabled traffic flow.

[0112] Figure 44 is a block diagram illustrating an apparatus according to some example embodiments. The apparatus may be a network node or entity 40 (such as a congestion notification marking responsible entity, e.g., RAN, UPF), comprising a receiving circuit 41, a detecting circuit 42, and a determining circuit 43. The receiving circuit 41 receives a message from a network entity, the message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled service flow. The detecting circuit 42 detects packet queue delay information related to the first congestion notification marking enabled service flow, the packet queue delay information indicating a congestion level. The determining circuit 43 determines the congestion notification marking rate to be applied to the first congestion notification marking enabled service flow based on the packet queue delay information, a general congestion notification marking rule, and the parameter information. Figure 8 is a schematic diagram of a process according to some example embodiments. Figure 4 The device can perform Figure 8 method, but not limited to this method. Figure 8 The method can be Figure 4 The present invention is performed by a device, but is not limited to being performed by the device.

[0113] like Figure 8 As shown in , a process according to some example embodiments includes the following operations: receiving (S81) a message from a network entity, the message including parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking-enabled service flow, detecting (S82) packet queue delay information related to the first congestion notification marking-enabled service flow, the packet queue delay information indicating a congestion level, and determining (S83) the congestion notification marking rate to be applied to the first congestion notification marking-enabled service flow based on the packet queue delay information, a general congestion notification marking rule and the parameter information.

[0114] Figure 5 is a block diagram illustrating an apparatus according to some example embodiments. In particular, Figure 5 Shows Figure 4 Thus, according to Figure 5 The device may further include a marking circuit 51 , an enabling circuit 52 and / or a disabling circuit 53 .

[0115] In an example embodiment, Figure 4 (or Figure 5 ) 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.

[0116] according to Figure 8A 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: marking packets of the first congestion notification marking-enabled traffic flow based on the congestion notification marking rate to be applied to the first congestion notification marking-enabled traffic flow.

[0117] according to Figure 8 A variation of the process shown in , providing details of the determination operation (S83), which are independent of each other. According to this variation, the message includes validity time information associated with the parameter information, the validity time information indicating the validity time of the parameter information, and according to some example embodiments, this determination operation (S83) may include the following operations: if the parameter information is valid at the current time, enabling consideration of the parameter information, and if the parameter information is invalid at the current time, disabling consideration of the parameter information.

[0118] According to other example embodiments, the parameter information includes multiplier information or percentage information.

[0119] According to other example embodiments, the parameter information includes congestion level information (ie, category information according to classification, for example, "low", "medium", "high").

[0120] According to other example embodiments, the parameter information comprises a list of parameter information elements, each parameter information element of the list being associated with a respective congestion level condition.

[0121] According to other example embodiments, at least two congestion notification marking enabled traffic flows associated with the terminal, including the first congestion notification marking enabled traffic flow, are identified using a single identifier, and the message includes the single identifier associated with the parameter information.

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

[0123] Fig. 9 A schematic diagram of a signaling sequence according to some example embodiments is shown, and in particular the processing of a sensitivity indication by an AF is shown.

[0124] exist Fig. 9In step 1 of , according to some example embodiments, the AF learns / detects that some application types are of L4S type. Alternatively, the AF obtains explicit information from an application server (AS) that such applications / services are enabled with L4S (the AS / application has enabled ECT marking for such application services). By considering the type of application (e.g., application flow characteristics, the number of such L4S type applications, etc.), the AF sets a sensitivity parameter for the application flow (e.g., the sensitivity of F1 is 10% or 90%).

[0125] According to some example embodiments, the sensitivity indication may be sent as a list. For example, the following sensitivity parameter information may be prepared:

[0126] -{Sensitivity X1, trigger condition: congestion level above Y1% or between Y1% and Y2%, time period, application characteristics, correlation ID (optional), UE ID (optional, if the criterion applies to more than one UE)},

[0127] -{Sensitivity X2, trigger condition: congestion level above Y2% or between Y2% and Y3%, time period, application characteristics, correlation ID (optional), UE ID (optional, if the criterion applies to more than one UE)}.

[0128] According to some example embodiments, the AF also provides a time window to indicate activation or application of a sensitivity value.

[0129] exist Fig. 9 In step 2, according to some example embodiments, the AF sends the sensitivity parameters and time window (within which the sensitivity is valid) for a specific flow to the 5GC (SMF / PCF / Network Open Function (NEF)) (it may use the policy authorization create / update process or the QoS request process).

[0130] As an example embodiment, the AF may send the following sensitivity information parameters:

[0131] -{Sensitivity X1, trigger condition: congestion level above Y1% or between Y1% and Y2%, time period, application characteristics, correlation ID (optional), UE ID (optional, if the criterion applies to more than one UE)}.

[0132] According to some example embodiments, for ongoing / existing flows, the AF may send updated sensitivity and time windows.

[0133] exist Fig. 9 In step 3 of , according to some example embodiments, the 5GC further determines who is responsible for ECN marking, in the RAN ( Fig. 9 Step 3b) and / or UPF ( Fig. 9In step 3a), the corresponding forwarding / marking rules are sent / set. This includes that both can also be marked.

[0134] exist Fig. 9 In steps 4 and 5, according to some example embodiments, the RAN( Fig. 9 Steps 4a and 4b) / UPF( Fig. 9 Steps 5a and 5c) of the method further take the sensitivity parameter into account when marking packets of the flow.

[0135] As an example embodiment, for a congestion level of 40%, the RAN / UPF may mark X% of packets for a specific L4S QoS flow (e.g., F1). If the sensitivity parameter (for) F1 is 90%, the 5GC node may increase the marking to 2*X% or 3*X% (so that the sending host / application will significantly reduce the data rate). If the sensitivity of F1 is 10%, the marking may be kept the same as X% or reduced to 0.5*X%. The exact correlation between the sensitivity to the congestion level and the marking percentage may be implementation specific.

[0136] According to some 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 (which implicitly takes into account the sensitivity).

[0137] According to some example embodiments, advantageously, the sensitivity parameters (list) enable the AF to provide additional L4S congestion mechanisms in the network based on applications, taking into account dynamic changes in application characteristics, practical considerations (e.g., emergency news relay), end-user considerations or needs, which cannot be achieved using static L4S markings based entirely on RAN congestion.

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

[0139] 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.

[0140] 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...").

[0141] exist Fig.10 , an alternative schematic diagram of an apparatus according to some example embodiments is shown. Fig.10 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 101, a memory 102 and an interface 103, which are connected via a bus 104 or the like. In addition, according to some example embodiments, the device (network node or entity) 30' (corresponding to the network node or entity 30) includes a processor 101, a memory 102 and an interface 103, which are connected via a bus 104 (or the like). In addition, according to some example embodiments, the device (network node or entity) 40' (corresponding to the network node or entity 40) includes a processor 101, a memory 102 and an interface 103, which are connected via a bus 104 or the like. These devices can be connected to other devices via links 105, for example, other devices other than the example devices 10', 30', 40' (corresponding to the example devices 10, 30, 40).

[0142] The processor 101 and / or the interface 103 may also include a modem or the like to facilitate communication via a (hardwired or wireless) link, respectively. The interface 103 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 103 is typically configured to communicate with at least one other device (i.e., its interface).

[0143] The memory 102 may store a corresponding program, which is 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 according to various example embodiments of the present subject disclosure.

[0144] 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.

[0145] 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").

[0146] According to some example embodiments, an apparatus representing a network node or entity 10 comprises at least one processor 101, at least one memory 102 comprising computer program code, and at least one interface 103 configured for communicating with at least another apparatus. The processor (i.e., the at least one processor 101 together with the at least one memory 102 and the computer program code) is configured to perform: for a first congestion notification marking enabled traffic flow, determining parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking enabled traffic flow (the apparatus thus comprises corresponding means for determining), and sending a message to a network entity, the message comprising the parameter information (the apparatus thus comprises corresponding means for sending).

[0147] According to some example embodiments, an apparatus representing a network node or entity 30 comprises at least one processor 101, at least one memory 102 comprising computer program code, and at least one interface 103 configured for communicating with at least another apparatus. The processor (i.e., the at least one processor 101 together with the at least one memory 102 and the computer program code) is configured to perform: receiving a first message from an application function entity, the first message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled traffic flow (the apparatus thus comprises corresponding means for receiving), and sending a second message to a congestion notification marking responsible entity, the second message comprising the parameter information (the apparatus thus comprises corresponding means for sending).

[0148] According to some example embodiments, an apparatus representing a network node or entity 40 comprises at least one processor 101, at least one memory 102 comprising computer program code, and at least one interface 103 configured for communicating with at least another apparatus. The processor (i.e., the at least one processor 101 together with the at least one memory 102 and the computer program code) is configured to perform: receiving a message from a network entity, the message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled traffic flow (the apparatus thus comprises corresponding means for receiving), detecting packet queue delay information related to the first congestion notification marking enabled traffic flow, the packet queue delay information indicating a congestion level (the apparatus thus comprises corresponding means for detecting), and determining the congestion notification marking rate to be applied to the first congestion notification marking enabled traffic flow based on the packet queue delay information, a general congestion notification marking rule and the parameter information (the apparatus thus comprises corresponding means for determining).

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

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

[0151] - 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;

[0152] - 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;

[0153] - 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;

[0154] - 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;

[0155] - 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;

[0156] - 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.

[0157] 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.

[0158] 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.

[0159] 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).

[0160] 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.

[0161] In view of the above, measures for flow-specific congestion handling are provided. By way of non-limiting and illustrative example, such measures may include: for a first congestion notification marking enabled service flow, determining parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking enabled service flow, and sending a message to a network entity, the message including the parameter information.

[0162] 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.

[0163] List of acronyms and abbreviations

[0164] 3GPP Third Generation Partnership Project

[0165] 5G Fifth Generation

[0166] 5GC 5G Core

[0167] 5GS 5G System

[0168] 5QI 5G QoS Identifier

[0169] AF Application Function

[0170] AL-FEC Application layer forward error correction

[0171] API Application Programming Interface

[0172] AQM Active Queue Management

[0173] AS Application Server

[0174] Congestion experienced by CE

[0175] DL Downlink

[0176] ECN Explicit Congestion Notification

[0177] ECT ECN-capable transport

[0178] GPRS General Packet Radio System

[0179] GTP-U GPRS Tunneling Protocol User Plane

[0180] IP Internet Protocol

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

[0182] NEF Network Exposure Function

[0183] NG-RAN Next Generation Radio Access Network

[0184] PCC Policy and Charging Control

[0185] PCF Policy Control Function

[0186] PDU Packet Data Unit

[0187] PER Packet Error Rate

[0188] PSA PDU Session Anchor

[0189] RTP Real Time Protocol

[0190] QoS Quality of Service

[0191] SMF session management functions

[0192] UE User Equipment

[0193] UL Uplink

[0194] UPF User Plane Function

[0195] XR

Claims

1. A method comprising: determining, for a first congestion notification marking enabled traffic flow, parameter information for modifying a congestion notification marking rate to be applied to the first congestion notification marking enabled traffic flow, and A message is sent to a network entity, where the message includes the parameter information.

2. The method according to claim 1, wherein: With respect to the determination, the method further comprises: The parameter information is determined based on at least one of the following: an application type of an application of the traffic flow causing the first congestion notification marking to be enabled, a characteristic of said application of the traffic flow causing said first congestion notification marking to be enabled, the number of concurrently existing congestion notification marking enabled traffic flows including the first congestion notification marking enabled traffic flow, The expected duration of the scenario in which the current congestion notification marking is enabled for the traffic flow, a user selection of said application with respect to a traffic flow resulting in said first congestion notification marking being enabled, or Information related to application layer forward error correction.

3. The method according to claim 1 or 2, wherein: The message includes validity time information associated with the parameter information, and the validity time information indicates a validity time of the parameter information.

4. A method comprising: receiving a first message from an application function entity, the first message comprising parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled traffic flow, and A second message is sent to a congestion notification mark responsible entity, where the second message includes the parameter information.

5. The method according to claim 4, wherein: The first message includes validity time information associated with the parameter information, the validity time information indicating the validity time of the parameter information, and The second message includes the validity time information associated with the parameter information.

6. The method according to claim 4 or 5, wherein: The parameter information includes multiplier information or percentage information, or The parameter information includes congestion level information.

7. A method comprising: receiving a message from a network entity, the message including parameter information for modifying a congestion notification marking rate to be applied to a first congestion notification marking enabled traffic flow, detecting packet queue delay information associated with a traffic flow enabled with the first congestion notification marking, the packet queue delay information indicating a congestion level; as well as The congestion notification marking rate to be applied to the first congestion notification marking enabled traffic flow is determined based on the packet queue delay information, a general congestion notification marking rule and the parameter information.

8. The method according to claim 7, further comprising: Packets of the first congestion notification marking enabled traffic flow are marked based on the congestion notification marking rate to be applied to the first congestion notification marking enabled traffic flow.

9. The method according to claim 7 or 8, wherein: The message includes validity time information associated with the parameter information, the validity time information indicating the validity time of the parameter information, and With respect to the determining, the method further comprises: enabling consideration of the parameter information if the parameter information is valid at the current time, and If the parameter information is not valid at the current time, consideration of the parameter information is disabled.

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 are configured to cause the apparatus to perform the method of any one of claims 1 to 9.

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

Images