Devices used to support and influence QoS levels

Abstract

The present invention provides a device (100) for improving a mobile network system, in particular a 4G or 5G system. The device (100) is used to support multiple QoS levels (101) of a session (102) associated with an application (103) or a service. In particular, the device (100) may include an AF 200 and a PCF (201), wherein the AF (200) is used to request (202) the PCF (201) to configure multiple QoS levels (101) of the session (102). Advantageously, in the event that the session (102) is modified, in particular in the event that one or more parameters of the session (102) are modified, the device (100) may switch from the current QoS level (101) of the session (102) to another QoS level (101) of the session (102).

Description

Technical Field

[0001] The present invention relates to an apparatus for a mobile network system, in particular for a 4G system or a 5G system. The apparatus is used to support multiple quality of service (QoS) levels for sessions associated with an application or service, and to influence and monitor the QoS level of the session. The present invention also relates to a method for a mobile network system, in particular a method for configuring multiple QoS levels for sessions of an application or service. Background Art

[0002] For many applications or services provided in mobile network systems, it is critical to provide a certain QoS level. For example, since most vehicle-to-everything (V2X) applications and services involve driving safety functions (such as assisted driving) or assisted driving functions (such as remote driving), safety concerns are critical in both cases. Therefore, strict monitoring and control of QoS needs to be provided from the V2X application function (AF) to ensure that the QoS expected by the V2X application or service is actually provided. In the event that the expected QoS cannot be provided, at least the V2X application or service should be notified in a timely manner of the actually provided QoS.

[0003] 3GPP systems prior to Release 15 provide some mechanisms to exchange QoS information with the AF. However, the QoS information available to the AF and the ability of the AF to influence QoS are very limited. In particular, the 5G system (5GS) according to the 3GPP Release 15 specification and previous generations of communication systems (e.g., 4G, LTE / EPC, UMTS) do not allow the AF to monitor and / or influence end-to-end QoS on a per-session basis when the negotiated per-session QoS cannot be provided.

[0004] In addition, in Release 15, the QoS model of 3GPP 5GS is based on QoS flows. A QoS flow is the smallest granularity of QoS differentiation in a session (e.g., a protocol data unit (PDU) session). A QoS flow ID (QFI) is used to identify a QoS flow in 5GS. User plane (UP) services with the same QFI in a PDU session will receive the same service forwarding treatment. A QoS flow is typically characterized by a single QoS profile provided to an access network (AN), one or more QoS rules provided by a terminal equipment (UE), and one or more service data flow (SDF) templates provided to a user plane function (UPF). However, if the 5GS cannot meet the QoS profile of a QoS flow for some reason, a PDU session modification may be triggered and the QoS flow may be released. AF cannot affect the outcome of the PDU session modification (e.g., through QoS fallback).

[0005] While the 5GS Release 15 specification includes some mechanisms for the AF to influence the PCC framework, this capability is very limited. In particular, the AF can only subscribe to the PCF to be notified during the lifecycle of the QoS flow of the session corresponding to the application or service when the QoS targets of the corresponding application or service cannot be met. This allows the AF to make decisions related to the corresponding application or service (e.g., terminate the QoS flow or continue with other characteristics). However, the AF cannot influence the provided QoS or control the monitoring of the provided QoS. Summary of the invention

[0006] In view of the above shortcomings and challenges, the present invention aims to improve the current implementation. The purpose of the present invention is to enhance the capabilities of 5GS in order to support, influence, and monitor the QoS of sessions associated with applications or services. In particular, the present invention is directed to an apparatus for a mobile network system that allows the AF to monitor and / or influence the end-to-end QoS on a per-session basis. In addition, the apparatus should also allow the AF to influence the results of session modifications in the event that the mobile network system cannot meet the required QoS profile.

[0007] The objects of the invention are achieved by the solutions provided in the attached independent claims. Advantageous embodiments of the invention are further defined in the dependent claims.

[0008] In particular, the present invention proposes a device that can use multiple QoS levels for each session. The present invention also proposes to enhance the ability of the AF in the device to monitor and / or influence the QoS level. Therefore, the present invention enables the 5GS to operate with multiple QoS levels based on the AF input.

[0009] A first aspect of the present invention provides a device for a mobile network system (particularly a 4G or 5G system), the device being used to support multiple QoS levels for sessions associated with an application or service. The device may be a UE, a RAN, or a core network device.

[0010] By supporting multiple QoS levels, a suitable QoS level can be selected for an application or service. In addition, in the case where a session is modified because it is no longer possible to achieve the target QoS level, at least one determined fallback QoS level can be advantageously provided, rather than terminating the session or downgrading it without controlling the QoS level of the session.

[0011] In the sense of this document, the term "session" includes an association between a UE and a data network (DN) through a mobile network system that provides connectivity, ie, the ability to exchange data between the UE and the DN. A session may be a PDU session.

[0012] In the sense of this document, the term "application" comprises a software entity and / or a computer program installed and executed on an application server of a UE and / or a DN for providing services to end users.

[0013] In the sense of this document, the term "service" includes actions and / or tasks performed jointly by the UE and / or DN and / or mobile network system and / or a combination of applications for providing utility or for assisting end users, such as remote driving, vehicle platooning, and assisted driving, etc. A service may be an Application Function (AF) session.

[0014] In an implementation form of the first aspect, sessions, applications, and / or services are associated with a single or multiple slices.

[0015] Such network slices are logical end-to-end subnetworks corresponding to, for example, different vertical industries. Assuming a shared network infrastructure, network slices can meet various requirements of, for example, multiple vertical industries. By providing network slices, network applications or services can be customized based on the requirements of different use cases, thereby improving the operational efficiency of the mobile network system.

[0016] In another implementation form of the first aspect, the device is used to switch from a current QoS level of the session to another QoS level of the session when the session is modified, in particular when one or more parameters of the session are modified.

[0017] "Parameters" in particular include QoS parameters. For this embodiment, in the case of a session modification, a determined QoS level upgrade or downgrade can be performed. Thus, the device can influence the result of the session modification and can advantageously avoid terminating the session or downgrading it without controlling the QoS level of the session. The parameter can be a parameter of the access node.

[0018] In another implementation form of the first aspect, the apparatus comprises an AF and a PCF, wherein the AF is used to request the PCF to configure a plurality of QoS levels for a session. Additionally or alternatively, the AF may be used to request the PCF to configure the SMF, in particular to adjust one or more parameters for controlling and / or monitoring the QoS of an application. Additionally or alternatively, the AF may be used to request the SMF to configure an access node, in particular to adjust one or more parameters for controlling and / or monitoring the QoS of an application.

[0019] For example, the AF may indicate to the PCF multiple (e.g., two or more) QoS levels that are considered suitable for supporting relevant applications or services, and the AF may also request to be notified in a timely manner when the QoS levels change or when all suitable QoS levels cannot (are no longer) supported.

[0020] The AF may specifically request the PCF to configure rules for supporting different QoS levels for a session. The term "configure" in the above phrase "request the PCF to configure multiple QoS levels for a session" includes the PCF authorizing multiple QoS levels for a session (or rules for supporting different QoS levels). The policy of supporting multiple QoS levels for a session may be applicable to sessions associated with a subset of UEs and / or a subset of network slices and / or an application or service.

[0021] In another implementation form of the first aspect, for configuring multiple QoS levels, when a QoS flow for a session is established, the QoS flow is associated with multiple QoS profiles for implementing the above-mentioned multiple QoS levels, in particular, wherein the above-mentioned association is performed by the PCF and requested by the AF.

[0022] In other words, a single QoS flow can support multiple QoS levels. The QoS profile of a QoS flow can be switched to change the QoS level.

[0023] In another implementation form of the first aspect, for configuring multiple QoS levels, when a group of QoS flows for a session is established, each QoS flow in the group of QoS flows is associated with a QoS profile for achieving a determined QoS level, in particular, wherein the above association is performed by the PCF and requested by the AF.

[0024] In other words, a single QoS flow supports a single QoS level. QoS flows associated with different QoS profiles may be switched to change the QoS level. In particular, for configuring multiple QoS levels, the set of QoS flows for the session may be established and the QoS flows may be bound together. Furthermore, at least one QoS flow in the set of QoS flows may be activated for transmitting data according to its QoS profile.

[0025] In another implementation form of the first aspect, the device is used to switch from a current QoS profile of at least one QoS flow of a session to another QoS profile of at least one QoS flow of the session when the session is modified, in particular, wherein the above-mentioned switching is triggered by one or more of the following: AN; SMF; UDM; PCF; UE; User Plane Function (UPF).

[0026] Thus, even in cases where session modification makes the target QoS level impossible, the session for the application or service may continue using the new QoS level associated with the other QoS profile.

[0027] In another implementation form of the first aspect, the device is used to switch from a currently activated QoS flow associated with a first QoS profile for a session to a currently inactivated QoS flow associated with a second QoS profile for the session, in particular when the session is modified; and / or switch from a currently activated QoS profile to a currently inactivated QoS profile.

[0028] After the above switching, the activated QoS flow becomes inactive and the inactive QoS flow becomes active. The above switching may be triggered by one or more of the following: AN; SMF; UDM; PCF; UE. Thus, even if the session modification makes the target QoS level impossible, the session of the application or service can be continued using the new QoS level associated with the new activated QoS flow. The above switching may be because the parameter reaches a predetermined value, in particular because one or more predetermined QoS flows become inactive.

[0029] In the sense of this document, an "activated QoS flow" includes a QoS flow that is being used to transfer data from a UE to a DN and / or from a DN to a UE. In the sense of this document, an "inactive QoS flow" includes a QoS flow that is not being used to transfer data from a UE to a DN and / or from a DN to a UE. In the sense of this document, an "activated QoS profile" of a multi-QoS profile flow includes a QoS profile in which QoS parameters are used to regulate data transmission for that flow. In the sense of this document, an "inactive QoS profile" of a multi-QoS profile flow includes a QoS profile in which QoS parameters are not used to regulate data transmission for that flow.

[0030] In another implementation form of the first aspect, the PCF (particularly the PCC rules in the PCF) is configured to support different QoS levels, in particular, configure the PCC rules in the PCF that implement the association of different QoS profiles of the service and QoS flow, and in particular configure the preferred QoS level downgrade when the target QoS level of the session cannot be met. This configuration can be pre-configured and / or configured by the AF.

[0031] In the sense of the present application, the configuration may also be a request from the AF to the PCF. That is, the PCF may configure multiple QoS levels based on the request of the AF, including configuring a preferred QoS level downgrade, so that the preferred QoS level downgrade is performed when the target QoS level of the service cannot (no longer) be met during the life cycle of the corresponding QoS flow. Therefore, the session of the application or service can be downgraded, and there is no need to terminate after the session modification, nor to continue with an uncontrolled low QoS level.

[0032] In the sense of this document, a "target QoS level" for a multi-QoS level session may be the QoS level that the mobile network system should attempt to support upon session establishment.

[0033] In another implementation form of the first aspect, the preferred QoS level downgrade comprises a set of QoS downgrade rules, in particular one QoS downgrade rule for each QoS flow of the session.

[0034] This allows the AF to instruct the PCF how to handle each QoS flow specifically in case of session modifications that affect this QoS flow.

[0035] In another implementation form of the first aspect, the preferred QoS level downgrade comprises a QoS downgrade mode, which determines whether the QoS downgrade rules in the set of QoS downgrade rules are applied to the QoS flows of the session independently or collectively.

[0036] This allows the AF to instruct the PFC on how to specifically handle QoS level degradation if a session modification affects at least one flow, and can be flexibly adjusted based on the type of application or service.

[0037] In another implementation form of the first aspect, the PCF is used to provide QoS level service operations, and the AF is used to invoke the QoS level service operations so as to subsequently configure the PCF with multiple QoS levels.

[0038] In the sense of this article, "service operations" include primitives of NF services provided by a network function (ie, one-way signaling messages sent by a NF to another NF). Service operations allow NFs (especially AFs) to invoke QoS-influencing capabilities as needed.

[0039] In another implementation form of the first aspect, the AF is configured to configure the PCF to provide multiple QoS levels through a point-to-point interface.

[0040] In another implementation form of the first aspect, the AF is used to provide a network identifier (ID) and / or a network slice ID and / or an AF service ID and / or a terminal equipment (UE) ID to the PCF to indicate the network and / or network slice and / or AF service and / or UE to which the multi-QoS level session should be applied.

[0041] Thus, the AF can configure multiple QoS levels in a flexible manner as needed.

[0042] In another implementation form of the first aspect, the device (in particular the PCF and / or any other NF and / or AN of the device) is used to notify the AF of the expected modification and / or completed modification of the session, in particular, wherein the notification includes information related to the change of QoS level.

[0043] This notification can be sent at any time, in particular, before the session modification is completed. Therefore, the device has QoS monitoring capabilities. Whenever a session modification occurs, for example, the NF that detects this situation can immediately notify the AF of the start of the session modification directly, or indirectly notify the AF of the start of the session modification via the PCF.

[0044] In another implementation form of the first aspect, the AF is used to configure the PCF and / or other NF and / or AN using at least one QoS monitoring parameter, and the PCF and / or other NF and / or AN is used to notify the AF of expected modifications and / or completed modifications of the session based on the above-mentioned at least one QoS monitoring parameter.

[0045] Therefore, AF can freely configure QoS monitoring capabilities as needed.

[0046] In another implementation form of the first aspect, the at least one QoS monitoring parameter includes a QoS monitoring timing, which determines whether the PCF and / or other NFs and / or ANs notify the AF of expected modifications to the session and / or completed modifications to the session.

[0047] In another implementation form of the first aspect, the at least one QoS monitoring parameter includes a QoS monitoring mode, which determines whether the PCF or other NFs and / or ANs directly notify the AF of expected modifications and / or completed modifications of the session, or whether other NFs and / or ANs indirectly notify the AF of expected modifications and / or completed modifications of the session via the PCF.

[0048] A second aspect of the present invention provides a method for a mobile network system (particularly a 4G or 5G system), the method comprising an AF in the mobile network system configuring a PCF in the mobile network system using multiple QoS levels for sessions associated with an application or service.

[0049] In an implementation form of the second aspect, sessions, applications, and / or services are associated with a single or multiple slices.

[0050] In another implementation form of the second aspect, the method comprises: in case the session is modified, in particular in case one or more parameters of the session are modified, switching from a current QoS level of the session to another QoS level of the session.

[0051] In another implementation form of the second aspect, for configuring multiple QoS levels, when a QoS flow for a session is established, the QoS flow is associated with multiple QoS profiles for implementing multiple QoS levels, particularly, wherein the above association is performed by the PCF and required by the AF.

[0052] In another implementation form of the second aspect, for configuring multiple QoS levels, when a set of QoS flows for a session is established, each QoS flow in the set of QoS flows is associated with a QoS profile for achieving a determined QoS level, particularly, wherein the above association is performed by the PCF and requested by the AF.

[0053] In another implementation form of the second aspect, the method includes, when the session is modified, switching from a current QoS profile of at least one QoS flow of a session to another QoS profile of the above-mentioned at least one QoS flow of the session, in particular, wherein the above-mentioned switching is triggered by one or more of the following: AN; SMF; UDM; PCF; UE.

[0054] In another implementation form of the second aspect, the method includes, when the session is modified, switching from a currently activated QoS flow of the session associated with a first QoS profile to a currently inactivated QoS flow of the session associated with a second QoS profile; and / or switching from a currently activated QoS profile to a currently inactivated QoS profile.

[0055] In particular, the above switching is triggered by one or more of the following: AN; SMF; UDM; PCF; UE.

[0056] In another implementation form of the second aspect, the method includes the AF downgrading the PCF using the preferred QoS level if the target QoS level for the session cannot be met.

[0057] In another implementation form of the second aspect, the preferred QoS level downgrade comprises a set of QoS downgrade rules, in particular one QoS downgrade rule for each QoS flow of the session.

[0058] In another implementation form of the second aspect, the preferred QoS level downgrade comprises a QoS downgrade mode, which determines whether the QoS downgrade rules in the set of QoS downgrade rules are applied independently or jointly to the QoS flows of the session.

[0059] In another implementation form of the second aspect, the PCF provides QoS level service operations, and the AF invokes the QoS level service operations to subsequently configure the PCF with multiple QoS levels.

[0060] In another implementation form of the second aspect, the AF configures the PCF via a point-to-point interface to provide multiple QoS levels.

[0061] In another implementation form of the second aspect, the AF provides a network identifier (ID) and / or a network slice ID and / or an AF service ID and / or a terminal equipment (UE) ID to the PCF to indicate the network and / or network slice and / or AF service and / or UE to which the multi-QoS level session should be applied.

[0062] In another implementation form of the second aspect, the method (in particular a method implemented by the PCF and / or any other NF and / or AN) comprises notifying the AF of an intended modification and / or a completed modification of the session, in particular wherein the notification comprises information relating to the change in QoS level.

[0063] In another implementation form of the second aspect, the AF configures the PCF and / or other NF and / or AN using at least one QoS monitoring parameter, and the PCF and / or other NF and / or AN notifies the AF of expected modifications and / or completed modifications of the session based on the at least one QoS monitoring parameter.

[0064] In another implementation form of the second aspect, the at least one QoS monitoring parameter includes a QoS monitoring timing, which determines whether the PCF and / or other NFs and / or ANs notify the AF of expected modifications to the session and / or completed modifications to the session.

[0065] In another embodiment of the second aspect, the at least one QoS monitoring parameter includes a QoS monitoring mode, which determines whether the PCF or other NF and / or AN directly notifies the AF of the expected modifications and / or completed modifications of the session, or whether other NF and / or AN indirectly notifies the AF of the expected modifications and / or completed modifications of the session via the PCF.

[0066] The method of the second aspect and its implementation form achieve the same advantages and effects as described above for the device of the first aspect and its corresponding implementation form.

[0067] In general, as described below, the apparatus and method of the present invention significantly improve 5GS. Compared to previous generations of mobile network systems, 5GS is expected to extend its applications to vertical industries through network slicing, with notable examples being V2X communications, industrial automation, and smart cities. In order to facilitate the integration of vertical industry requirements and to simplify the customization of 5GS behavior accordingly, extension capabilities for third-party AFs are introduced in the 3GPP Release 15 specification. This can be achieved using the 5GC service based interface (SBI) functionality. The apparatus according to the first aspect of the present invention and the method according to the second aspect of the present invention enhance the QoS impact and QoS monitoring capabilities of third-party AFs. The apparatus and method are very beneficial for V2X use cases, where a close interaction between AF and 5GS is considered to be very beneficial.

[0068] It should be noted that all devices, elements, units, and devices described in this application can be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in this application and the functions described as performed by the various entities are intended to indicate that the corresponding entities are suitable for or used to perform the corresponding steps and functions. Although in the following description of specific embodiments, the specific functions or steps performed by the external entities are not reflected in the description of the specific specific elements of the entity performing the specific steps or functions, it should be clear to the technician that these methods and functions can be implemented in the corresponding software or hardware elements or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] The above aspects and implementation forms of the present invention will be explained in the following description of specific embodiments in relation to the accompanying drawings, in which:

[0070] Figure 1 An apparatus according to an embodiment of the invention is shown.

[0071] Figure 2 An apparatus according to an embodiment of the invention is shown.

[0072] Figure 3 A method according to an embodiment of the present invention is shown.

[0073] Figure 4 (A) and (B) show a session of an application or service in a device according to an embodiment of the present invention.

[0074] Figure 5 The AF request / response process for activating QoS monitoring and QoS influencing capabilities is shown.

[0075] Figure 6 The effect of QoS impact capability on PDU session modification is shown. DETAILED DESCRIPTION

[0076] Figure 1 A device 100 for a mobile network system (particularly for a 4G system or a 5G system) according to an embodiment of the present invention is shown. The device 100 is used to support multiple QoS levels 101 for sessions 102 associated with applications 103 or services. Here, different QoS levels 101 are exemplarily marked with a, b, c, and d, respectively. The fact that the device 100 supports these multiple QoS levels 101 preferably means that, in particular in the case of modifying the session 102, the device 100 is able to switch from one (current) QoS level 101 of the session 102 to another QoS level 101 of the session 102. This advantageously allows the device 100 to continue the application 103 and / or service at a different QoS level 101 than before the modification of the session, and the termination of the session 102 and the application 103 or service can be avoided.

[0077] Figure 2 The apparatus 100 according to an embodiment of the present invention (established in Figure 1 Based on the device 100 shown in FIG. 1 ). Accordingly, Figure 2 The illustrated apparatus 100 also supports multiple QoS levels 101 for sessions 102 . Figure 1 and Figure 2 The same elements are correspondingly marked with the same reference numerals and have the same function.

[0078] Figure 2 The illustrated apparatus 100 comprises in particular an AF 200 and a PCF 201. The AF 200 is used to request the PCF 201 to configure a plurality of QoS levels 101 of a session 102 (e.g. via a request message 202). This advantageously provides the AF 200 with QoS influencing capabilities. The AF 200 may also be provided with QoS monitoring capabilities. To this end, the PCF 201 and / or any other NF and / or AN of the apparatus 100 is preferably configured to inform the AF 200 of intended modifications and / or completed modifications of the session 102 (e.g. via a request of the AF 200).

[0079] Figure 3 The method 300 for a mobile network system (particularly for a 4G system or a 5G system) according to an embodiment of the present invention is shown. The method 300 may be Figure 2 or Figure 2The device 100 shown in the figure performs. In particular, the method 300 comprises step 301: the AF 200 in the mobile network system or in the device 100 configures the PCF 201 in the mobile network system or in the device 100 with a plurality of QoS levels 101 of sessions 102 associated with applications 103 or services.

[0080] It may be necessary to activate the QoS influencing capability and QoS monitoring capability of AF 200. For example, Figure 2 The PCF 201 of the illustrated apparatus 100 may be configured to provide a QoS level service operation, and the AF 200 may be configured to invoke the QoS level service operation in order to subsequently request 202 the PCF 201 to configure the above-mentioned multiple QoS levels 101. Similarly, the AF 200 may also invoke the QoS level service operation in order to request to be subsequently notified of any expected modification and / or completed modification of the session 102.

[0081] The activation of these new QoS capabilities is now described in detail. The AF 200 can specifically activate the QoS influence capability by calling the "Npcf_QoS_Influence_Request / Response" service operation provided by the PCF 201. This service operation allows the AF 200 to configure the PCF 201 by preferably indicating one or more of the following:

[0082] • DNN and / or network slice identifier (S-NSSAI) and / or AF service identifier to which QoS affecting capabilities (i.e., multiple QoS classes 101) should be applied.

[0083] • UE identifiers for which QoS affecting capabilities (ie multiple QoS classes 101) should be applied.

[0084] ·Multiple QoS level operation modes. Figure 4 Two different QoS level operation modes are shown. In particular, Figure 4 (A) and (B) show different sessions 102 of an application 103 or service supporting multiple QoS levels 101 .

[0085] refer to Figure 4 The first QoS level operation mode shown in (A) is “multi-QoS profile flow mode.” In this operation mode, the session 102 supports multiple QoS levels 101 through the multi-QoS profile flow 400 . Figure 4The QoS flow 400 of the session 102 shown in (A) is associated with multiple QoS profiles for implementing multiple QoS levels 101 (respectively represented as a, b, c, d). In particular, each of the multiple QoS flows 400 of the session 102 can be associated with multiple QoS profiles, and the QoS profiles of the QoS flows 400 can be changed according to network conditions (e.g., network load, wireless link capacity, etc.) and / or when the session is modified.

[0086] refer to Figure 4 The second QoS operation mode shown in (B) is "multi-stream session mode". In this operation mode, the session 102 supports multiple QoS levels 101 through multiple single QoS profile flows 400. A set of QoS flows 400 is established for the session 102, and each QoS flow 400 in the set of QoS flows 400 is associated with a (different) QoS profile for achieving a determined QoS level 101 (the different QoS levels 101 are also represented as a, b, c, d, respectively).

[0087] In case of “multi-QoS profile flow mode”, a set of QoS profiles associated with a QoS flow 400, or in case of “multi-stream session mode”, the set of QoS flows 400 and a corresponding QoS profile for each QoS flow 400.

[0088] In addition, the AF 200 may specifically activate the QoS monitoring capability by invoking the "Nxxx_QoS_Monitoring_Request / Response" service operation provided by the AN, AMF, SMF, UDM, and / or PCF (where "xxx" may be AN, AMF, SMF, UDM, PCF). The QoS monitoring capability may be activated on each NF (i.e., AN, AMF, SMF, UDM, and / or PCF). The service operation allows the AF 200 to configure the AN, AMF, SMF, UDM, and / or PCF 201 by indicating one or more of the following:

[0089] The DNN and / or network slice identifier (S-NSSAI) and / or AF service identifier to which the QoS monitoring capability should be applied (i.e., the AF 200 is notified of the expected modification and / or completed modification of the session 102, in particular, the notification includes information related to the change of QoS level 101).

[0090] • UE identifiers for which the QoS monitoring capability should be applied (ie the AF 200 is notified of the intended modification and / or completed modification of the session 102, in particular the notification includes information related to the QoS class 101 change).

[0091] • QoS monitoring timing (eg, early and / or late, as described below with respect to the operation of the QoS monitoring capability). QoS monitoring timing is a QoS monitoring parameter.

[0092] • QoS Monitoring Mode (eg, direct or indirect, as described below with respect to the operation of the QoS Monitoring capability). The QoS Monitoring Mode is a QoS monitoring parameter.

[0093] The operation of the new QoS capability is now described in detail. After activating the QoS influence capability, the PCF 201 is used to support multi-QoS level sessions 102 as indicated by Npcf_QoS_Influence_Request.

[0094] The DNN and / or network slice identifier (S-NSSAI) indicated by the Nxxx_QoS_Influence_Request and

[0095] and / or AF service identifier and / or UE-related sessions 102 shall support multiple QoS levels 101 indicated by Nxxx_QoS_Influence_Request.

[0096] In "Multiple QoS Profiles Flow Mode" (see Figure 4 In the case of (A)), whenever a session modification occurs, at least one QoS flow 400 of the session 102 may switch its QoS profile according to the multiple QoS levels 101 indicated in the Nxxx_QoS_Influence_Request. In other words, when the session 102 is modified, the device 100 may switch from the current QoS profile of at least one QoS flow 400 of the session 102 to another QoS profile of the at least one QoS flow 400 of the session 102.

[0097] In "Multi-stream session mode" (see Figure 4 In the case of (B)), for each requested QoS flow 400 indicated in Nxxx_QoS_Influence_Request, a set of QoS flows 400 is established at session establishment. Preferably, radio resource reservation is applied only to the requested QoS flows 400. In the case where the session is modified, if the modification is related to an activated QoS flow 400, radio resource reservation is not maintained for the activated QoS flow 400, and resource reservation is applied to another inactivated QoS flow 400 of the set of QoS flows 400. In other words, in the case where the session 102 is modified, the device 100 can switch from a currently activated QoS flow 400 of the session 102 associated with a first QoS profile to a currently inactivated QoS flow 400 of the session 102 associated with a second QoS profile, and / or switch from a currently activated QoS profile to a currently inactivated QoS profile.

[0098] After the QoS monitoring capability has been activated on any NF supporting the QoS monitoring capability (AN, AMF, SMF, UDM, PCF 201), the NF shall notify the AF 200 of the QoS changes associated with the session 102 as indicated by the Nxxx_QoS_Monitoring_Request.

[0099] The NF shall notify any QoS changes of the PDU Session 102 related to the DNN and / or Network Slice Identifier (S-NSSAI) and / or AF Service Identifier and / or UE indicated by the Nxxx_QoS_Monitoring_Request.

[0100] If the QoS monitoring timing in Nxxx_QoS_Monitoring_Request is set to "early", the NF shall notify the AF 200 when a session modification occurs.

[0101] If the QoS monitoring timing in Nxxx_QoS_Monitoring_Request is set to "late", the NF shall notify the AF 200 when the session modification is completed after a session modification situation occurs.

[0102] If the QoS monitoring timing in Nxxx_QoS_Monitoring_Request is set to "Early and Late", the NF shall notify the AF 200 when a session modification situation occurs and when the session modification is completed after the session modification situation occurs.

[0103] For AN, AMF, SMF, UDF, PCF 201, if the QoS monitoring mode in Nxxx_QoS_Monitoring_Request is set to "Direct", the NF shall notify the AF 200 of the QoS change directly via the Nxxx_EventExposure_Notify service operation.

[0104] For AN, AMF, SMF, UDF, if the QoS monitoring mode in Nxxx_QoS_Monitoring_Request is set to "indirect", the NF shall notify the PCF 201 of the QoS change via the Nxxx_EventExposure_Notify service operation, and the PCF 201 shall notify the AF of the QoS change directly via the Npcf_EventExposure_Notify service operation indirectly.

[0105] An exemplary and simplified implementation of the solution of the present invention is now shown below. In particular, this implementation is considered as a gradual enhancement of 5GS. This implementation allows the device 100 according to an embodiment of the present invention (e.g. Figure 1 or Figure 2 The AF 200 shown in FIG. 1 performs the following operations:

[0106] Configure the PCF 201's preferred QoS level downgrade (preferably per QoS flow 400) via Npcf_QoS_Influence_Request to perform the preferred QoS level downgrade when the target QoS of the application 103 or service cannot be met during the life cycle of the corresponding QoS flow 400. The Npcf_QoS_Influence_Request message includes the preferred QoS level downgrade for QoS attributes and values ​​such as 5QI (per flow), ARP (per flow), RQA (per flow), GFBR (UL and DL) (per flow), MFBR (UL / DL) (per flow), Session AMBR (per PDU session 102)

[0107] Whenever a session (herein, the PDU session 102) is modified, the NF that detects this situation (the NF can be the AMF or UDM of the SMF) should directly notify the PDU session modification start via the Nxxx_EventExposure_Notify message (xxx can be AN, AMF, UDM, SMF), or indirectly notify the PDU session modification start via the PCFNpcf_EventExposure_Notify message after the PCF 201 has participated in the PDU session modification.

[0108] Figure 5 This exemplary embodiment is shown along with the AF request / response procedures for activating the QoS monitoring capability and the QoS influencing capability, respectively.

[0109] Step 1.a: AF 200 calls the Npcf_QoS_Influence_Request service operation. The request contains:

[0110] DNN and possibly slice information (S-NSSAI) or AF service identifier;

[0111] Information about UEs with QoS that needs to be affected;

[0112] • Preferred QoS level downgrade configuration message (detailed information of the message will be shown later).

[0113] Step 2.a.: AF 200 sends its request to PCF 201 directly or via network exposure function (NEF) 504 .

[0114] Step 3.a: PCF 201 stores the preferred QoS level degradation rules for DNN, S-NSSAI, AF service identifier, and UE.

[0115] Step 4.a: PCF 201 invokes the Npcf_QoS_Influence_Response service operation.

[0116] Step 1.b: AF 200 invokes the Npcf_QoS_Monitoring_Request service operation. The request contains:

[0117] DNN and possibly slice information (S-NSSAI) or AF service identifier;

[0118] Information of UEs with QoS that needs to be monitored;

[0119] · List of triggers for PDU session modification to be monitored early.

[0120] PDU session modification trigger notification mode (QoS monitoring mode), i.e., direct notification or indirect notification.

[0121] Step 2.b: The AF 200 sends its request 202 to at least one of the following NFs: AN 500, AMF 501, SMF 502, UDM 503, PCF 201 (depending on the list of triggers for PDU session modification to be monitored earlier) directly or via NEF 504.

[0122] Step 3.b: At least one of the following NFs invokes the Nxxx_QoS_Monitoring_Response service operation: AN 500, AMF 501, SMF 502, UDM 503, PCF 201 (depending on the list of triggers for PDU sessions to be monitored early).

[0123] Figure 6The PDU Session Modification procedure according to TS 23.502 is shown, with the activation of the QoS Impact Capability highlighted in step 0, whereby the AF 200 can request 202 the PCF 201 to configure a different QoS level 101 and (preferably) a preferred QoS level downgrade. The PDU Session Modification procedure will be affected according to a Preferred QoS Downgrade Configuration message received by the PCF 201. This Preferred QoS Downgrade Configuration message preferably includes:

[0124] · “QoS degradation mode parameters”.

[0125] · “QoS degradation rule table”.

[0126] The QoS degradation mode parameter indicates how the QoS degradation rules should be applied in case of a multi-flow PDU session 102. The QoS degradation mode can be set to one of the following:

[0127] "Each stream is independent"

[0128] "Interweaving Flow"

[0129] If the QoS downgrade mode parameter is set to "per flow independent", the QoS downgrade rules are applied independently to each QoS flow 400 according to the QoS downgrade rule table. In other words, the preferred QoS level downgrade is attempted independently by the QoS flow 400 according to the QoS downgrade rule table.

[0130] If the QoS degradation mode parameter is set to "interleaved flows", the QoS level degradation rules are applied together to all QoS flows 400 according to the QoS degradation rule table. In other words, all QoS flows 400 of the PDU session 102 are considered together to attempt a preferred QoS level degradation according to the QoS degradation rule table and the relative values ​​of other QoS parameters (including, for example, priority, packet delay budget, packet error rate, default averaging window, ARP).

[0131] An exemplary QoS downgrade rule table is shown below, which indicates the preferred QoS downgrade rules for each QoS flow 400. In particular, for each 5QI value, the table indicates the preferred fallback 5QI. For each GBR 5QI value, the table also indicates the preferred GBR scaling factor (i.e., the preferred GBR value reduction after the PDU session modification is completed).

[0132]

[0133] The invention has been described in conjunction with various embodiments and implementations as examples. However, from a study of the drawings, the present disclosure, and the independent claims, a person skilled in the art may understand and implement other variations and practice the claimed invention. In the claims and in the specification, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. A single element or other unit may perform the functions of multiple entities or items recited in the claims. The fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous embodiment.

Claims

1. A communication method, characterized in that: include: Application function AF sends a request, The request is used to request a policy control function PCF to configure multiple quality of service QoS levels for a session, the session being associated with an application or a service; When the QoS flow of the session corresponding to the application or service is established, the QoS flow is associated with a plurality of QoS profiles for implementing the plurality of QoS levels; In response to the modification of one or more parameters of the session, a current QoS level of the application is switched to another QoS level of the application.

2. The method according to claim 1, characterized in that The application function AF sends a request, including: The AF sends a request to the PCF via a network opening function NEF.

3. The method according to claim 1, characterized in that Also includes: The AF requests the PCF to configure a session management function SMF; and The AF requests the SMF to configure the access node AN.

4. The method according to claim 1, characterized in that: At least one of the sessions, applications or services is associated with one or more slices.

5. The method according to any one of claims 1 to 4, characterized in that: Also includes: Switch the current QoS profile to another QoS profile.

6. The method according to claim 5, characterized in that The switching is triggered by one or more of the following: Access node AN and / or parameter changes of AN; Session management function SMF; Unified Data Management UDM; the PCF; Terminal equipment UE; User plane UP function.

7. The method according to any one of claims 1 to 4, characterized in that: When the target QoS level of the session cannot be met, the AF configures the PCF to downgrade the QoS level.

8. The method according to claim 7, characterized in that The QoS level downgrade includes a set of QoS downgrade rules.

9. The method according to claim 7, characterized in that: The QoS level downgrade includes: a QoS downgrade rule for each QoS flow of the session.

10. The method according to any one of claims 1 to 4, characterized in that: Also includes: The AF receives a notification, where the notification is used to indicate change information of the QoS level of the session.

11. The method according to any one of claims 1 to 4, characterized in that: The AF invokes the QoS level service operation provided by the PCF.

12. The method according to any one of claims 1 to 4, characterized in that Also includes: The AF provides one or more of the following information to the PCF: a network identifier ID, a network slice ID, an AF service ID, or a user equipment UE ID.

13. A communication method, characterized in that: include: A policy control function PCF receives a request for requesting the PCF to configure a plurality of quality of service QoS levels for a session, the session being associated with an application or a service; The PCF configures the QoS level of the session according to the request; When a QoS flow for the application or service is established, the QoS flow is associated with multiple QoS profiles for implementing the multiple QoS levels; in response to a modification of one or more parameters of the session, the current QoS level of the application is switched to another QoS level of the application.

14. The method according to claim 13, characterized in that The policy control function PCF receives the request, including: The PCF receives the transmission request from the application function AF via the network opening function NEF.

15. The method according to claim 13, characterized in that At least one of the sessions, applications or services is associated with one or more slices.

16. The method according to any one of claims 13 to 15, characterized in that Also includes: The PCF associates the multiple QoS levels with multiple QoS profiles.

17. The method according to claim 16, characterized in that Also includes: Switch the current QoS profile to another QoS profile.

18. The method according to claim 17, characterized in that The switching is triggered by one or more of the following: Access node AN and / or parameter changes of AN; Session management function SMF; Unified Data Management UDM; the PCF; Terminal equipment UE; User plane UP function.

19. The method according to claim 18, characterized in that Also includes: The PCF configures the session management function SMF.

20. The method according to any one of claims 13 to 15, characterized in that The PCF configures the QoS level of the session according to the request, including: The PCF enables the multiple QoS profiles for the multiple QoS flows associated with the service through a policy and charging control (PCC) rule.

21. The method according to any one of claims 13 to 15, characterized in that When the target QoS level of the session cannot be met, the PCF downgrades the QoS level.

22. The method according to claim 21, characterized in that The PCF performs QoS level downgrading including: The PCF performs QoS level downgrading based on a set of QoS downgrading rules.

23. The method according to claim 22, characterized in that The set of QoS degradation rules includes: one QoS degradation rule for each QoS flow of the session.

24. The method according to any one of claims 13 to 15, characterized in that Also includes: The PCF sends a notification, where the notification is used to indicate change information of the QoS level of the session.

25. The method according to any one of claims 13 to 15, characterized in that The PCF provides QoS level service operations.

26. The method according to any one of claims 13 to 15, characterized in that Also includes: The PCF receives one or more of the following information: a network identifier ID, a network slice ID, an AF service ID or a user equipment UE ID.

27. A communication device, comprising a hardware element, wherein the hardware element is used to implement the method according to any one of claims 1 to 12.

28. A communication device, comprising a hardware element, wherein the hardware element is used to implement the method according to any one of claims 13 to 26.

29. A computer program product, which, when executed on a computer, enables the method according to any one of claims 1 to 12 to be executed; or enables the method according to any one of claims 13 to 26 to be executed.

Images