Method and device for adjusting QoS of QoS flow based on auxiliary information

Abstract

The present application relates to an entity and a method for adjusting the quality of service. More specifically, the present application relates to an entity (100), in particular a radio access network (RAN) entity, for adjusting the QoS of at least one quality of service (QoS) flow in the RAN, wherein the entity (100) is used to: obtain auxiliary information (101), wherein the auxiliary information (101) is used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device (400), in particular at least one UE; provide a request (102) for adjustment from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information (103) to a second entity (110), in particular to a core network (CN) entity, wherein the request (102) or the QoS information (103) is based on the auxiliary information (101). In addition, the present application relates to a corresponding method.

Description

Technical Field

[0001] The present disclosure relates to an entity for a mobile network system, in particular for a fourth generation mobile or cellular communication system (4G system) or for a fifth generation mobile or cellular communication system (5G system). According to an embodiment of the present disclosure, the proposed entity and the corresponding method are used to support a communication session, i.e., multiple quality of service (QoS) levels of a QoS flow. The present disclosure particularly relates to a Radio Access Network (RAN) being able to decide whether to adjust a QoS profile of a QoS flow or request to adjust the QoS profile. Background Art

[0002] The concept of multiple QoS levels (multi-level QoS) has been introduced in TR 23.786 FS_eV2X as proposal #27, which allows the use of at least one alternative QoS profile in cases where the required QoS profile of a QoS flow cannot be met.

[0003] In contrast, in 5G systems, the Application Function (AF) can provide "alternative business requirements" in addition to the "requested business requirements" to the Policy Control Function (PCF). If notification control is enabled, the PCF can include "alternative QoS parameter sets" based on the alternative business requirements in the policy rule message sent to the Session Management Function (SMF). If notification control is enabled, the SMF can also derive "alternative QoS profiles" based on the alternative QoS parameter sets and send these profiles to the NG-RAN (i.e., RAN entity). When the RAN notifies the 5G Core (5GC) entity that the QoS characteristics cannot be met, the notification can include alternative QoS profiles that can be supported in the notification.

[0004] In solution #27 of TR 23.786, "Solution for supporting QoS for eV2X on the Uu interface" is concluded to be considered in the specification work. Solution #27 defines the following: The SMF sends multiple sets of QoS profiles to the NG-RAN (RAN entity), which are marked as "alternative" in addition to the target QoS profile. The NG-RAN receives an N2 PDU session request to establish a QoS flow from the SMF, and the N2 PDU session request includes the QoS profile in the N2 Session Management (SM) information. If the NG-RAN supports this function, the NG-RAN will also store the alternative QoS profile.

[0005] If the NG-RAN cannot meet the Guaranteed Flow Bit Rate (GFBR) requirement and / or the Packet Delay Budget (PDB) requirement and / or the Packet Error Rate (PER) requirement of the QoS profile, the NG-RAN notifies the 5GC using the procedure specified in Section 5.7.2.4 of TS 23.501, which then further notifies the AF (e.g., Vehicle-to-Everything (V2X) application). For example, the AF obtains this information from the PCF via the Network Exposure Function (NEF).

[0006] If, in addition to notifying the 5GC and V2X applications that the QoS targets cannot be met, an alternative QoS profile is received, the NG-RAN, when supporting this functionality, checks whether any of the alternative QoS profiles can be supported. If the NG-RAN can support one of the alternative QoS profiles, the NG-RAN may include its associated index in the notification so that the 5GC and V2X applications can take this information into account.

[0007] If none of the alternative QoS profiles are applicable, the NG-RAN may provide information on which QoS characteristics cannot be met, including the current “Guaranteed QoS Requirements” (e.g., GFBR, PDB and / or PER), using the procedures specified in section 5.7.2.4 of TS 23.501, and then further inform the AF if notification is required, so that the V2X application can consider this information and take appropriate action.

[0008] The NG-RAN still attempts to meet the original QoS targets after sending the notification.

[0009] When the radio conditions change and the requirements of the GFBR, PDB and PER of the QoS profile can be met again, the NG-RAN notifies the 5GC using the procedure specified in Section 5.7.2.4 of TS 23.501, which then further notifies the AF (e.g., V2X application). The V2X application then takes appropriate actions based on the information provided by the 3GPP system and other sources (if available). Summary of the invention

[0010] The embodiments of the present invention are based on the following more considerations. In particular, the above solution #27 is specified based on the following two situations.

[0011] Case 1 highlights a method for enhancing AF capabilities to monitor and influence QoS, and enables 5GS (including 5GC and RAN) to operate with multiple QoS profiles based on AF input. The method enables AF to indicate multiple (e.g., two or more) QoS profiles that are considered suitable to support related applications, and to notify in a timely manner when a QoS profile is changed, or when an appropriate QoS profile is no longer supported.

[0012] Case 2 highlights methods and techniques for a mobile device (e.g., vehicle) or an application server / AF / client that negotiates with a network entity to determine QoS. The QoS category list is sent during connection establishment or new bearer establishment. During a handover, the QoS category list is sent from a source base station to a target base station.

[0013] However, neither Case 1 nor Case 2 addresses how the RAN can evaluate whether a QoS profile can be met, cannot be met, or can be met again, especially considering QoS profiles from multiple QoS flows.

[0014] In view of the above, an object of an embodiment of the present invention is to improve methods and entities for adjusting QoS, for example, according to the method of solution #27. For example, the object is to enable the RAN to decide whether to adjust the QoS profile of a QoS flow, or whether to request adjustment of a QoS flow, for example, a QoS flow from a CN. In addition, it is desired that the RAN be able to evaluate the satisfaction or non-satisfaction of one or more QoS profiles for each QoS flow in one or more QoS flows, taking into account the complexity of supporting this functionality. In addition, the RAN should be able to dynamically adjust (i.e., upgrade and / or downgrade) the QoS of one or more flows, taking into account the available radio resources and service requirements.

[0015] This object is achieved by the embodiments of the invention described in the attached independent claims. Advantageous implementations of the embodiments of the invention are further defined in the dependent claims.

[0016] In particular, embodiments of the present disclosure propose a mechanism for performing QoS adjustment (e.g., upgrading and / or downgrading the QoS of a flow) in a RAN (NG-RAN) assuming that multi-level QoS is supported. In addition, embodiments of the present invention specify signaling that can be used between the RAN, 5GC, Operations, Administration and Maintenance (OAM), and User Equipment (UE).

[0017] A first aspect of the present disclosure provides an entity, in particular a RAN entity, for adjusting the QoS of at least one QoS flow in the RAN, wherein the entity is used to: obtain auxiliary information, the auxiliary information being used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device, in particular at least one UE; and provide a request for adjustment from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information to a second entity, in particular to a core network (CN) entity, wherein the request or the QoS information is based on the auxiliary information.

[0018] The entity of the first aspect, in particular the entity in the RAN, may decide whether to adjust the QoS profile of the first QoS flow on its own. This decision of the entity of the first aspect is supported by the auxiliary information, which the entity may receive from outside the RAN, for example from the CN. If the entity of the first aspect decides that it can adjust the QoS profile on its own, the entity may perform the QoS profile adjustment. Furthermore, in this case, the entity may send the QoS information to the second entity. The QoS information may be a report of the QoS profile adjustment performed by the entity of the first aspect. If the entity of the first aspect decides that it cannot or does not want to adjust the QoS profile on its own, the entity may send the request to the second entity. The second entity may be a network entity such as a CN entity, and may then further decide whether it adjusts the QoS profile on its own, or how to proceed with the QoS profile adjustment request.

[0019] It is worth noting that in the present disclosure, a QoS flow may be referred to as a communication session. In addition, the entity of the first aspect may be a RAN entity of a 4G or 5G system, for example, a base station in a RAN / NG-RAN of these systems.

[0020] In an implementation of the first aspect, the entity is further used to: provide the second entity with another request for adjustment from the first QoS profile of the second QoS flow to the second QoS profile or another QoS information of the adjustment, wherein the another request or the another QoS information is based on the auxiliary information.

[0021] Therefore, the entity of the first aspect may also decide to adjust the QoS profile of the second QoS flow, similar to the first QoS flow. Depending on the result of the decision of the entity whether to adjust the QoS profile of the second QoS flow by itself, the entity may send another request or another QoS information (another report).

[0022] In an implementation of the first aspect, the auxiliary information is provided for at least one packet data unit (PDU) session, at least one QoS profile, at least one QoS flow, at least one wireless communication device and / or at least one RAN entity.

[0023] Separate assistance information may also be provided for each PDU session, and / or each QoS profile, and / or each QoS flow, and / or each wireless communication device, and / or each RAN entity.

[0024] In an implementation of the first aspect, the auxiliary information includes at least one of the following: an identification (ID) of at least one PDU session; an ID of at least one QoS profile; an ID of at least one wireless communication device; and an ID of at least one QoS flow.

[0025] In an implementation of the first aspect, the auxiliary information includes at least one of the following: an indication of whether the entity performs the adjustment; an indication of the adjustment priority of the at least one QoS profile; timing information related to the time validity and / or periodicity of the evaluation of the adjustment of the at least one QoS profile; area information indicating the area to which the evaluation of the adjustment of the at least one QoS profile applies; event information indicating events at which the evaluation is started and / or ended and / or paused and / or resumed; and resource requirements of the at least one QoS profile.

[0026] With this auxiliary information, the entity supporting the first aspect decides whether to adjust the QoS profile of the at least one QoS flow itself.

[0027] In an implementation manner of the first aspect, the auxiliary information includes at least one of the following: cost information for enabling the entity to provide the request or the QoS information.

[0028] The entity of the first aspect may use the cost information to decide whether to adjust the QoS profile (whether to adjust it by itself, i.e., in the latter case, more precisely, to request a decision from the second entity). For example, if the cost information indicates that the cost for adjusting the QoS profile is below a certain cost threshold, the entity of the first aspect may decide to adjust the QoS profile. Then, either the QoS profile is adjusted by itself considering the cost, or the second entity is requested to make an adjustment based on the cost (the cost may be included in the request).

[0029] In an implementation of the first aspect, the adjustment from the first QoS profile to the second QoS profile includes at least one of: upgrading to a better or more desired QoS profile for the at least one QoS flow; downgrading to a worse or less desired QoS profile for the at least one QoS flow.

[0030] For example, the original QoS profile of a QoS flow can be changed / upgraded / downgraded to an alternative QoS profile specified for the QoS flow. This operation can be performed for each QoS flow.

[0031] In an implementation of the first aspect, the entity is further configured to perform the adjustment from the first QoS profile to the second QoS profile and provide the QoS information to the second entity.

[0032] In this case, the entity decides to make adjustments to the QoS profile on its own, the decision being based on the auxiliary information.

[0033] In an implementation manner of the first aspect, the QoS information includes a result of the adjustment.

[0034] For example, a new QoS profile may be indicated to the second entity. Furthermore, a cost of changing the QoS profile may be indicated.

[0035] In an implementation of the first aspect, the adjustment from the first QoS profile to the second QoS profile is based on the acquired auxiliary information and / or an evaluation of RAN capabilities supporting the adjustment of the at least one QoS flow.

[0036] In an implementation of the first aspect, the entity is further used to: perform the evaluation of the RAN capability to support the adjustment of the at least one QoS flow; and decide whether to perform the adjustment from the first QoS profile to the second QoS profile based on the result of the evaluation.

[0037] The entity of the first aspect may further decide whether to adjust the QoS profile itself based on evaluating whether one or more QoS profiles of each QoS flow are satisfied or not, while taking into account the complexity involved in adjusting the QoS profile.

[0038] In an implementation of the first aspect, the evaluation of whether the RAN is able to support the adjustment of the at least one QoS profile is based on non-periodic or periodic monitoring of the at least one QoS profile, in particular, the real-time actual or expected wireless resource quality, traffic load and / or resource availability of at least one alternative QoS profile and the current QoS profile according to the acquired auxiliary information.

[0039] In an implementation of the first aspect, the evaluation of whether the RAN is capable of supporting the adjustment of the at least one QoS profile is triggered by a handover and / or handover request message.

[0040] In this case, the wireless communication device, in particular the UE, may leave or join a cell associated with the entity of the first aspect, for example, if the entity of the first aspect is a base station, then the cell covered by the entity. The QoS profile may be different in another cell (i.e. the cell from which the wireless configuration device is switched), for example, such that the QoS profile is (also) not supported in the cell of the entity of the first aspect. In another case, the cell of the entity of the first aspect may support an expected QoS profile for at least one QoS flow of the wireless communication device, which expected QoS profile is not supported in another cell. In both cases, the QoS profile may be adjusted by the entity of the first aspect on its own or upon request.

[0041] In an implementation of the first aspect, the evaluation of whether the RAN can support the adjustment of the at least one QoS profile is a radio resource control (RRC) function and / or a radio resource management (RRM) function.

[0042] In an implementation manner of the first aspect, the entity is further configured to: not perform the adjustment from the first QoS profile to the second QoS profile by itself, and provide the request to the second entity.

[0043] The second entity, e.g. a CN entity, may then decide how to proceed and whether to adjust the QoS profile itself. The entity of the first aspect may also be instructed to perform the QoS profile adjustment.

[0044] In an implementation of the first aspect, the request includes a result of the evaluation.

[0045] Hence, the second entity is provided with more relevant information for deciding to adjust the QoS profile.

[0046] In an implementation manner of the first aspect, the auxiliary information is acquired from a network entity and / or a network management entity and / or an application entity.

[0047] In an implementation of the first aspect, the request or the QoS information includes at least one of: an indication of whether at least one QoS profile has been changed; a new or potential / expected QoS profile based on QoS flow adjustment; cost information; and an adjustment priority of at least one QoS profile.

[0048] A second aspect of the present disclosure provides an entity for supporting adjustment of the QoS of at least one QoS flow in a RAN, the entity being used to: provide auxiliary information, the auxiliary information being used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device, in particular at least one UE; and / or obtain a request for adjustment from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information, wherein the request or the QoS information is based on the auxiliary information.

[0049] Therefore, the entity of the second aspect can support other entities (e.g., the entity of the first aspect) to adjust the QoS. For example, the entity can provide the auxiliary information to the entity of the first aspect, and then the entity of the first aspect decides whether to adjust the QoS based on the auxiliary information. The entity of the second aspect can also receive the request or the QoS information from the entity of the first aspect, and can decide how to continue the QoS profile adjustment accordingly.

[0050] In an implementation manner of the first aspect, the entity is a network entity, a network management entity and / or an application entity.

[0051] A third aspect of the present disclosure provides a method for adjusting the QoS of at least one QoS flow in a RAN, the method comprising: obtaining auxiliary information, the auxiliary information being used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device, in particular at least one UE; providing a request for adjustment from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information, wherein the request or the QoS information is based on the auxiliary information.

[0052] In an implementation of the third aspect, the method further includes: providing to the second entity another request for adjustment from the first QoS profile of the second QoS flow to the second QoS profile or another QoS information of the adjustment, wherein the another request or the another QoS information is based on the auxiliary information.

[0053] In an implementation of the third aspect, the auxiliary information is provided for at least one packet data unit (PDU) session, at least one QoS profile, at least one QoS flow, at least one wireless communication device and / or at least one RAN entity.

[0054] In an implementation of the third aspect, the auxiliary information includes at least one of the following: an identifier (ID) of at least one PDU session; an ID of at least one QoS profile; an ID of at least one wireless communication device; and an ID of at least one QoS flow.

[0055] In an implementation of the third aspect, the auxiliary information includes at least one of the following: an indication of whether the entity performs the adjustment; an indication of the adjustment priority of the at least one QoS profile; timing information related to the time validity and / or periodicity of the evaluation of the adjustment of the at least one QoS profile; area information indicating the area to which the evaluation of the adjustment of the at least one QoS profile applies; event information indicating the event at which the evaluation is started and / or ended and / or paused and / or resumed; and resource requirements of the at least one QoS profile.

[0056] In an implementation manner of the third aspect, the auxiliary information includes at least one of the following: cost information for enabling the entity to provide the request or the QoS information.

[0057] In an implementation of the third aspect, the adjustment from the first QoS profile to the second QoS profile includes at least one of the following: upgrading to a better or more desired QoS profile for the at least one QoS flow; downgrading to a worse or less desired QoS profile for the at least one QoS flow.

[0058] In an implementation of the third aspect, the method further includes performing the adjustment from the first QoS profile to the second QoS profile and providing the QoS information to the second entity.

[0059] In an implementation manner of the third aspect, the QoS information includes a result of the adjustment.

[0060] In an implementation of the third aspect, the adjustment from the first QoS profile to the second QoS profile is based on the acquired auxiliary information and / or an evaluation of the RAN capabilities supporting the adjustment of the at least one QoS flow.

[0061] In an implementation of the third aspect, the method further includes: performing an evaluation of the RAN capability to support the adjustment of the at least one QoS flow; and deciding whether to perform the adjustment from the first QoS profile to the second QoS profile based on a result of the evaluation.

[0062] In one implementation of the third aspect, the evaluation of whether the RAN can support the adjustment of the at least one QoS profile is based on non-periodic or periodic monitoring of the at least one QoS profile, in particular, the real-time actual or expected wireless resource quality, traffic load and / or resource availability of at least one alternative QoS profile and the current QoS profile according to the acquired auxiliary information.

[0063] In an implementation manner of the third aspect, the evaluation of whether the RAN is capable of supporting the adjustment of the at least one QoS profile is triggered by a handover and / or handover request message.

[0064] In an implementation manner of the third aspect, the evaluation of whether the RAN can support the adjustment of the at least one QoS profile is an RRC function and / or an RRM function.

[0065] In an implementation manner of the third aspect, the entity is further configured to: not perform the adjustment from the first QoS profile to the second QoS profile by itself, and provide the request to the second entity.

[0066] In an implementation manner of the third aspect, the request includes a result of the evaluation.

[0067] In an implementation manner of the third aspect, the auxiliary information is acquired from a network entity and / or a network management entity and / or an application entity.

[0068] In one implementation of the third aspect, the request or the QoS information includes at least one of the following: an indication of whether at least one QoS profile has been changed; a new or potential or expected QoS profile based on QoS flow adjustment; cost information; and an adjustment priority of at least one QoS profile.

[0069] The method described in the third aspect and its implementation achieves the same advantages and effects as the entity described in the first aspect and its corresponding implementation.

[0070] A fourth aspect of the present disclosure provides a computer program. When the computer program runs on a computer, the computer executes the method according to the third aspect or any implementation manner thereof.

[0071] A fifth aspect of the present disclosure provides a non-transitory storage medium, which stores executable program code. When the executable program code is executed by a processor, the method according to the third aspect or any implementation manner thereof is executed.

[0072] A sixth aspect of the present disclosure provides an entity for adjusting the QoS of at least one communication session in a RAN, the entity being used to: obtain auxiliary information, the auxiliary information being used to adjust at least one QoS profile of the at least one communication session of at least one wireless communication device, in particular at least one UE; and provide a request / QoS information for adjustment from a first QoS profile of a first QoS flow to a second QoS profile to a second network entity, wherein the request / the QoS information is based on the auxiliary information.

[0073] In an implementation of the sixth aspect, the entity is further used to: provide a request / QoS information for adjustment from a first QoS profile of a second QoS flow to a second QoS profile to a second network entity, wherein the request / QoS information is based on the auxiliary information.

[0074] In an implementation of the sixth aspect, the auxiliary information may be provided for at least one PDU session, at least one QoS profile, at least one QoS flow, at least one UE, and at least one RAN entity.

[0075] In an implementation of the sixth aspect, the auxiliary information includes at least one of the following parameters: an identifier (ID) of the at least one communication session; an identifier (ID) of at least one QoS profile; an identifier (ID) of the at least one wireless communication device; an identifier (ID) of the at least one QoS flow; an indication of whether the RAN performs the adjustment; an indication of the adjustment priority of the QoS profile; timing information related to the time validity and / or periodicity of the evaluation of the adjustment of the QoS profile; area information indicating the area to which the evaluation of the adjustment applies; event information indicating the event at which the evaluation is started and / or ended and / or paused and / or resumed; and resource requirements of at least one QoS profile.

[0076] In an implementation of the sixth aspect, the adjustment from the first QoS profile to the second QoS profile includes at least one of the following: upgrading to a better QoS profile for at least one communication session; downgrading to a worse QoS profile for at least one communication session.

[0077] In an implementation of the sixth aspect, the adjustment of the QoS profile is based on the acquired configuration / auxiliary information and / or an evaluation of the RAN capability to support the adjustment of at least one communication session.

[0078] In an implementation of the sixth aspect, the evaluation of whether the RAN can support the QoS adjustment is based on non-periodic or periodic monitoring of the real-time actual or expected wireless resource quality, traffic load and / or resource availability of at least one QoS profile, especially at least one alternative QoS profile and the current QoS profile, based on the acquired auxiliary information.

[0079] In an implementation manner of the sixth aspect, the evaluation of whether the RAN can support the QoS adjustment is a radio resource control (RRC) function and / or a radio resource management (RRM) function.

[0080] In an implementation manner of the sixth aspect, the auxiliary information is obtained from a network entity and / or a network management entity and / or an application entity.

[0081] In an implementation of the sixth aspect, the request / the QoS information includes at least one of the following parameters: an indication of whether the QoS profile has been changed; a new or potential / expected QoS profile based on QoS flow adjustment; cost information; and an adjustment priority of the QoS profile.

[0082] The seventh aspect of the present disclosure provides a network entity, which is used to: provide auxiliary information, wherein the auxiliary information is used to adjust at least one QoS profile of at least one communication session of at least one wireless communication device, in particular at least one UE; obtain a request / QoS information for adjustment from a first QoS profile of a first QoS flow to a second QoS profile, wherein the request / the QoS information is based on the auxiliary information.

[0083] An eighth aspect of the present disclosure provides a network management entity, which is used to provide auxiliary information, wherein the auxiliary information is used to adjust at least one QoS profile of at least one communication session of at least one wireless communication device, especially at least one UE.

[0084] The ninth aspect of the present disclosure provides an application entity, which is used to: provide auxiliary information, wherein the auxiliary information is used to adjust at least one QoS profile of at least one communication session of at least one wireless communication device, in particular at least one UE; obtain a request / QoS information for adjustment from a first QoS profile of a first QoS flow to a second QoS profile, wherein the request / the QoS information is based on the auxiliary information.

[0085] The tenth aspect of the present disclosure provides a method for adjusting QoS, the method comprising: obtaining auxiliary information, the auxiliary information being used to adjust at least one quality of service (QoS) profile of at least one wireless communication device, in particular at least one UE, and providing a request / QoS information for adjustment from a first QoS profile of a first QoS flow to a second QoS profile to a second network entity, wherein the request / the QoS information is based on the auxiliary information.

[0086] 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. The steps performed by the various entities described in this application and the functions to be performed by the various entities described are intended to refer to the various entities being suitable for or used to perform the various steps and functions. Even if in the description of the following specific embodiments, the specific functions or steps to be performed by the external entity are not reflected in the description of the specific detailed elements of the entity performing the specific steps or functions, the technician should also be aware that these methods and functions can be implemented in the corresponding software or hardware elements or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] In conjunction with the accompanying drawings, the above aspects and their implementation methods will be described in the following description of specific embodiments, wherein:

[0088] Figure 1 The entity provided by the embodiment of the present invention is shown;

[0089] Figure 2 The entity provided by the embodiment of the present invention is shown;

[0090] Figure 3 The method provided by the embodiment of the present invention is shown;

[0091] Figure 4 A 5G system including an entity provided by an embodiment of the present invention is shown;

[0092] Figure 5 It shows a successful handover resource allocation operation involving entities provided by an embodiment of the present invention;

[0093] Figure 6It shows a successful handover preparation operation involving entities provided by an embodiment of the present invention;

[0094] Figure 7 The present invention shows a PDU session resource establishment request operation involving an entity provided by an embodiment of the present invention;

[0095] Figure 8 The embodiment of the present invention provides a PDU session resource modification request operation involving an entity;

[0096] Fig. 9 It shows a multi-QoS RAN configuration operation involving entities provided by an embodiment of the present invention;

[0097] Fig.10 An operation for obtaining auxiliary information involving an entity provided by an embodiment of the present invention is shown;

[0098] Fig.11 The PDU session resource notification operation involving an entity provided by an embodiment of the present invention is shown;

[0099] Fig.12 A successful PDU session resource modification indication operation involving an entity provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0100] Figure 1 The entity 100 provided by the embodiment of the present invention is shown. The entity 100 may be a RAN entity, for example, an entity in a RAN (4G system) or a NG-RAN (5G system). For example, the entity 100 may be a base station. In addition, Figure 2 A second entity 110 is also shown, which may be a network entity, specifically a CN entity in a 5G CN (5GC), etc. The entity 100 is used to support a process for adjusting the QoS of at least one QoS flow (e.g., a first QoS flow and / or a second QoS flow) in a RAN.

[0101] To this end, the entity 100 is used to obtain auxiliary information 101, wherein the auxiliary information 101 is used to adjust at least one wireless communication device 400 (for example, see Figure 4 ), in particular at least one QoS profile of at least one QoS flow of at least one UE. The entity 100 may obtain the auxiliary information 101 from another entity (possibly even from the second entity 110). The entity 100 may also be pre-configured with the auxiliary information 101, or the auxiliary information 101 may be generated by evaluating one or more network parameters.

[0102] Further, the entity 100 is used to provide a notification to the second entity 110. Specifically, the entity 100 is used to provide a request 102 for adjustment from a first QoS profile of a first QoS flow to a second QoS profile as a notification to the second entity 110, or to provide QoS information 103 for adjustment from a first QoS profile of a first QoS flow to a second QoS profile as a notification to the second entity 110. Therefore, the request 102 or the QoS information 103 is based on the auxiliary information 101.

[0103] In the case that the entity 100 adjusts the QoS profile itself, the QoS information 103 may be the result of the adjustment. The request 102 may be a request for the second entity 110 to adjust the QoS profile in the case that the entity 100 does not adjust the QoS profile itself. The entity 100 may use the auxiliary information 101 to decide whether to provide the request 102 as a notification to the second entity 110 or to provide the QoS information 103 as a notification to the second entity (therefore, the request 102 or the QoS information 103 is based on the auxiliary information 101). In particular, the entity may use the auxiliary information 101 to decide whether to adjust the QoS profile itself.

[0104] Figure 2 The entity 200 provided by the embodiment of the present invention is shown. The entity 200 may be the second entity 110, that is, it may be a CN entity. However, the entity 200 may also be a (CN) entity different from the entity 110. Generally, the entity 200 may be a network entity, for example, a network entity of a 5GC, or a network management entity or an application entity. The entity 200 is used to support adjustment of the QoS of at least one QoS flow in the RAN / NG-RAN. For example, the entity 200 may be used to support Figure 1 The entity 100 adjusts the QoS profile of at least one QoS flow.

[0105] To this end, the entity 200 may be configured to provide auxiliary information 101, wherein the auxiliary information 101 is used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device 400, in particular at least one UE. Figure 1 The entity 100 shown provides auxiliary information 101 .

[0106] Alternatively or additionally, the entity 200 may be configured to obtain a request 102 for adjusting a first QoS profile of a first QoS flow to a second QoS profile, or to obtain QoS information 103 for adjusting a first QoS profile of a first QoS flow to a second QoS profile. The request 102 or the QoS information 103 is based on the auxiliary information 101, for example, as described above in conjunction with Figure 1 described.

[0107] Figure 3 The method 300 for adjusting the QoS of at least one QoS flow in the RAN provided by an embodiment of the present invention is shown. The method 300 may be performed by Figure 1 The entity 100 shown is executed. The method 300 comprises: step 301, obtaining auxiliary information 101 for adjusting at least one QoS profile of at least one QoS flow of at least one wireless communication device 400, in particular at least one UE; step 302, providing a request 102 for adjusting from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information 103, wherein the request 102 or the QoS information 103 is based on the auxiliary information 101.

[0108] Embodiments of the present invention may be used in mobile communication network systems, in particular in fifth generation mobile or cellular communication (5G) systems (5GS). For example, 5GS may be used as Figure 4 However, the embodiment of the present invention can also be applied to another network system, which includes Figure 4 Specifically, Figure 4 The following entities are shown:

[0109] 5GC: 5G core network

[0110] AF: Application function (AF communicates with PCF through NEF)

[0111] AMF: Access and Mobility Management Function

[0112] RAN: Radio Access Network

[0113] SMF: Session Management Function

[0114] UE: User Equipment

[0115] PCF: Policy Control Function

[0116] NEF: Network Exposure Function

[0117] N1, N2, N11, N7, N15, N30, and N33 are interfaces between related entities.

[0118] OAM: Operation, Administration and Maintenance

[0119] For example, Figure 4 Shows that "RAN" may be or may include Figure 1 The entity 100 shown is a RAN entity. The SMF may also be Figure 1The second entity 110 shown. That is, the RAN entity 100 can notify the SMF 200 about the request 102 or the QoS information 103 through the AMF. However, any other 5GC entity can be the second entity 110. The UE can be the UE 400 mentioned above. The OAM can be Figure 2 Entity 200 shown. Alternatively or additionally, AF may also be Figure 2 That is, the OAM 200 or the AF 200 may provide the RAN entity 100 with the assistance information 101 and / or may obtain the request 102 or the QoS information 103 from the RAN entity 100 .

[0120] It should be understood that according to the embodiment of the present disclosure, the RAN may be a NG-RAN and may include one or more base stations (RAN entities). The one or more base stations may be Figure 1 Entity 100 shown. The base station is specifically a device deployed in the RAN for providing wireless communication functions for the terminal (for example, UE 400). The base station may include various forms of macro base stations, micro base stations (also called small cells), relay nodes, access points, etc. In systems using different wireless access technologies, devices with base station functions may have different names. For example, the device is called an evolved NodeB (evolved NodeB, eNB or eNodeB for short) in the LTE system, or a NodeB in the third generation (3rd generation, 3G for short) system, or a gNodeB (gNB) in the future new radio (New Radio, NR) network. For ease of description, in all embodiments of the present disclosure, the above-mentioned devices that provide wireless communication functions for the terminal are collectively referred to as base stations.

[0121] Next, before explaining the embodiments of the present invention in more detail, some terms used in 3GPP specification version 16 are explained, which are related to the terms used in the description of the embodiments of the present invention:

[0122] QoS flow mapping:

[0123] “The SMF provides the (R)AN with the following information, where applicable:

[0124] -QoS Flow Identifier (QFI);

[0125] - QoS profiles as described in Section 5.7.1.2;

[0126] - Optionally, the alternative QoS profiles described in Section 5.7.1.2a;"

[0127] Alternative QoS profiles:

[0128] “Optionally, an alternative QoS profile may be provided for a Notification Control-enabled GBR QoS flow. If the corresponding PCC rule includes the relevant information (as described in TS 23.503), the SMF shall provide the alternative QoS profile to the NG-RAN in addition to the QoS profile.

[0129] The alternative QoS profile represents a combination of QoS parameters and has the same format as the QoS profile of the QoS flow.

[0130] When the NG-RAN sends a notification to the SMF that a QoS profile cannot be guaranteed, the NG-RAN may include a reference to an alternative QoS profile (as described in clause 5.7.2.4) to indicate the QoS that the NG-RAN can guarantee.”

[0131] Notification Control:

[0132] “If the NG-RAN has received an alternative QoS profile for this QoS flow and supports the handling of the alternative QoS profile, the NG-RAN shall check whether the values ​​of the GFBR, PDB and PER parameters that the NG-RAN can guarantee match any of the alternative QoS profiles before sending a notification to the SMF that the GFBR can no longer be guaranteed. If so, the NG-RAN shall indicate a reference to the alternative QoS profile to the SMF and a notification to the SMF.”

[0133] In addition, the "QoS profile" in the present disclosure may generally refer to one or more parameters (of QoS) in a QoS parameter set. The one or more parameters in such a QoS parameter set may include: guaranteed flow bit rate (GFBR), packet delay budget (PDB) (including core network packet delay budget), and packet error rate (PER).

[0134] "Multi-level QoS" can be implemented by an entity or system, where each QoS level can correspond to a QoS profile. Multi-level QoS means that at least two QoS profiles for a QoS flow are supported. For example, in addition to the current QoS profile or the original QoS profile, at least one alternative QoS profile is supported.

[0135] According to 3GPP specification Release 16, 5GC can indicate a QoS profile and an alternative QoS profile to NG-RAN, but there is no provision for the manner in which NG-RAN (i.e., the responsible RAN entity, e.g., a base station) upgrades to an original QoS profile or an alternative QoS profile, the priority of the original QoS profile or the alternative QoS profile over the current QoS profile, and / or the manner in which the possibility of NG-RAN returning to the original QoS profile is evaluated, and / or the manner in which RAN selects a QoS profile for QoS adjustment.

[0136] To describe the embodiments of the present invention, the following definitions (from the perspective of RAN) are also used in this disclosure:

[0137] Original / Initial QoS Profile: Received from the SMF, mapped to the original requested QoS parameter set of the PCF and the original requested business requirements of the AF.

[0138] Alternative QoS profiles: Received from the SMF and mapped to the alternative QoS parameter sets of the PCF and the alternative service requirements of the AF; if the original QoS profile cannot be met, one or more alternative QoS profiles are considered.

[0139] Active QoS Profile: The QoS profile used by the RAN for the QoS flow. For example, the QoS profile currently in use.

[0140] According to 3GPP specification Release 16:

[0141] The active QoS profile can be the original QoS profile or one of the alternative QoS profiles.

[0142] The original QoS profile is a preferred QoS profile, for example, a QoS profile having the highest priority according to application requirements.

[0143] In order to enable the entity 100 (particularly when located in the NG-RAN or when being an NG-RAN entity) to evaluate whether one or more QoS profiles of each QoS flow are satisfied or not satisfied, and in order to enable the entity 100 to dynamically adjust the QoS profile of the QoS flow, an embodiment of the present invention proposes information transmission from the entity 200 (particularly located in the 5GC or as a CN entity) to the entity 100 according to the following format, etc.:

[0144]

[0145] In addition to this information already defined in 3GPP specification version 16, an embodiment of the present invention further proposes to provide additional information to the entity 100, i.e., in addition to the alternative QoS profiles. That is, an embodiment of the present invention further proposes to provide auxiliary information 101 to the entity 100 (e.g., configuration regarding NG-RAN multi-QoS profile handling options (e.g., ability to or inability to adjust the RAN's QoS, reporting before or after adjustment, reporting only the selected QoS profile or some additional information), 5GC priority / preference for QoS profile and / or QoS flow selection, allowed switching cost in the sense of allowed packet loss, allowed service interruption time, UE measurements, etc.). The entity 100 may use the auxiliary information 101 to select one or more candidate QoS flows, and / or evaluate one or more QoS profiles of the candidate QoS flows for possible QoS adjustment (i.e., downgrade / upgrade), possibly also taking into account NG-RAN conditions.

[0146] The embodiment of the present invention also provides a mechanism for evaluating and adjusting the QoS profile of at least one QoS flow by monitoring the RAN resource situation and service requirements and QoS characteristics by the entity 100. The embodiment of the present invention also includes providing relevant signaling between the entities 100, 110, 200 involved to notify the evaluation result and / or adjustment result of the QoS adjustment performed or determined by the entity 100.

[0147] Compared with the prior art, the embodiments of the present invention also support QoS profile adjustment, thereby realizing multiple implementation options for multi-QoS profile processing, and realizing QoS upgrade (not supported by 3GPP specification version 16) and related adjustments of QoS profiles of multiple QoS flows (for example, selecting some QoS flows from multiple candidate QoS flows for upgrading, and upgrading some QoS profiles while downgrading some other QoS profiles).

[0148] In some embodiments of the present invention, the entity 100 (e.g., a control unit or a control entity) is located in the RAN (or a network node, e.g., a management entity) and is configured to:

[0149] 1. Obtain auxiliary information 101 related to the adjustment of at least one QoS flow from one QoS profile (first) of the QoS flow of at least one UE 400 to another QoS profile (second). The auxiliary information 101 can be obtained by the entity 100 from the entity 200 (located in the 5GC), or obtained through the OAM system configuration (usually a network management entity), or obtained from the UE 400, or obtained from the application entity (e.g., AF). The auxiliary information 101 can be used for at least one PDU session, and / or at least one QoS profile, and / or at least one QoS flow, and / or at least one wireless communication device 400 and / or at least one RAN entity.

[0150] 2. Based on the obtained auxiliary information 101, and optionally based on the result of the evaluation, for example, also based on at least one of the RAN situation, business requirements, and QoS characteristics, perform an evaluation and decide on a potential / actual QoS adjustment of one or more QoS flows, which may be upgraded to a more desirable QoS profile or downgraded to a less desirable QoS profile. For example, the adjustment from a first QoS profile to a second QoS profile is based on the obtained auxiliary information 101 and the evaluation of the RAN capability to support the adjustment of at least one QoS flow.

[0151] 3. Performing adaptation of the QoS profile according to the auxiliary information 101 and according to the evaluation of the RAN (if configured in the auxiliary information 101). That is, the entity 100 can be used to perform the above-mentioned evaluation of the RAN capability and decide whether to perform the adjustment from the first QoS profile to the second QoS profile according to the evaluation result.

[0152] 4. Provide the evaluation and / or adaptation results to the second entity 110 and / or the OAM system in the 5GC. For example, the QoS information 103 may include the evaluation and / or adaptation results. In addition, the request 102 (if the entity 100 does not perform the adjustment itself based on the auxiliary information 101 and the evaluation decision) may also include the evaluation results.

[0153] The entities and methods proposed in the embodiments of the present invention are further described below. One or more steps described below may be optional.

[0154] First, the steps of the entity 100 (here located in the RAN, ie, the RAN entity) acquiring the auxiliary information 101 are described.

[0155] The auxiliary information 101 can be obtained from the entity 200 located in the 5GC, namely the CN entity, specifically the 5GC entity 200.

[0156] In this case, the auxiliary information 101 may include:

[0157] 1. Information for evaluating the possibility of NG-RAN QoS adjustment. For example, the auxiliary information 101 can be used to inform the entity 100 when, where and how to evaluate the possibility of QoS adjustment, that is, to perform an evaluation of the RAN capability to support the adjustment of at least one QoS flow. The evaluation result can be which QoS profiles meet the evaluation criteria. For example,

[0158] Triggering events evaluated: handover, PDU session establishment / modification, radio resource condition change.

[0159] • Relevant configurations for the evaluation, e.g., time (e.g., periodicity), location (e.g., entry into a cell / TA / region of interest), QoS adjustment priority in case of multiple candidate QoS profiles and QoS flows.

[0160] Whether to evaluate only the original QoS profile or all QoS profiles that have a preference / priority / rank higher than the active QoS profile.

[0161] RAN's evaluation criteria (e.g., allowed switching costs). For example, entity 100 can use this information and the evaluation results to determine whether to adjust the QoS profile itself and / or notify the second entity 110 (here in 5GC).

[0162] 2. Information for configuring QoS adjustments in entity 100 (RAN entity), for example,

[0163] Whether the entity 100 should only provide the evaluation results to the 5GC, or whether it should also perform QoS profile adjustment (i.e., whether the adjustment of the QoS profile is implemented at the RAN / NG-RAN).

[0164] • Under which circumstances the entity 100 should perform QoS profile adjustments (e.g., time, location, event, etc.).

[0165] 3. Information related to the notification, such as

[0166] • Indication of early notification (ie after evaluation of the situation by entity 100) and / or overdue notification (ie after QoS adjustment).

[0167] Whether additional parameters are required in the notification (e.g., handover cost from the NG-RAN perspective).

[0168] Notification timing (eg, delays in notifications allowed when conditions change).

[0169] · Target of the notification (e.g., to entity 110 (5GC) and / or to UE 400).

[0170] Figure 5 and Figure 6 The trigger event for evaluating a "handover" is shown above, which refers to the entity 100 (RAN entity) switching from the source RAN (eg, based on Xn; see Figure 5 ) or from AMF (e.g., N2-based handover; see Figure 6 ) receiving the handover request message 500. That is, the evaluation of whether the RAN can support the adjustment of at least one QoS profile may be triggered by the handover and / or the handover request message 500.

[0171] Figure 7 and Figure 8 The trigger event for evaluating "PDU session establishment / modification" is shown above, which refers to the entity 100 receiving a PDU session establishment message 700 for an alternative QoS profile or an original QoS profile from the AMF (see Figure 7 ) or PDU modification message 800 (see Figure 8 ).

[0172] The trigger event "radio resource condition change" (e.g., the available resources of the RAN node are greater than a determined threshold) can come from inside other RAN entities (e.g., directly from RRM, a data analysis function, such as part of Minimum drive test (MDT)), or from outside (e.g., from the OAM system, 5GC or UE). The 5GC or OAM system can also bridge the trigger event from the application server (e.g., as a third-party AF). UE 400 can bridge the trigger event from the application client at UE 400.

[0173] The auxiliary information 101 received from the entity 200 (5GC entity) may be carried by the PDU session establishment / modification message 700 / 800, for example, from the SMF to the entity 100 via the AMF, such as Figure 7 or Figure 8 shown.

[0174] In a possible implementation shown below (see Table 1 and Table 2), the auxiliary information 101 of each QoS flow may include Figure 7In the "PDU session resource establishment request transmission" message 700 shown in . Here, the auxiliary information 101 can be a QoS adjustment priority (for example, selection of a QoS profile and / or a QoS flow). The "alternative QoS flow level QoS parameter list" may include at least one "alternative QoS flow level QoS parameter item". It may also include an "alternative QoS flow level QoS parameter item" that is mapped to the original QoS profile before the 5GC requires downgrading to the alternative QoS profile. For example, the candidate QoS profile list or the alternative QoS profile list may include the original QoS profile.

[0175] Table 1 (PDU session resource establishment request transmission):

[0176]

[0177]

[0178] Table 2:

[0179] Range Limitation illustrate maxnoofQoSFlows The maximum number of QoS flows allowed in a PDU session. The value is 64. maxnoofQoSProfiles The maximum number of QoS profiles allowed in one QoS flow. The value is 8.

[0180] In another possible implementation illustrated below (see Table 3), the auxiliary information 101 (RAN adaptive control) may be configured according to the QoS profile. For example, the PCF may configure whether the entity 100 is allowed to perform QoS profile adjustment (RAN adaptive control) on the GBR QoS flow information. During the PDU session establishment / modification process, this information may be passed to the entity 100 as part of the PDU session context.

[0181] Table 3 (GBR QoS flow information):

[0182]

[0183]

[0184] The "Notification Control" IE and "RAN Adaptation Control" IE in Table 3 may also be implemented for each QoS flow, for example, as part of the "Assistance Information" given in Table 1. In this case, it does not need to be repeated for each "Alternative QoS Flow Level QoS Parameter Item".

[0185] In another implementation, the assistance information 101 may also be provided for each UE, for example, as a part of NG context establishment.

[0186] The auxiliary information 101 may also be obtained from an OAM system (e.g., from a management entity 200), which is or includes the entity 200. The OAM system may also provide NG-RAN configuration of the QoS evaluation / adjustment function for each service and / or each geographical area in a pre-operation / deployment phase or an operation phase. Such a configuration may include auxiliary information 101, such as QoS adjustment priority, periodicity, geographical areas to which the QoS evaluation / adjustment applies, and time validity. The auxiliary information 101 may support the entity 100 (NG-RAN) to perform QoS adjustment for a given geographical area or a given service type (e.g., according to a service ID) according to the policy of an operator or service provider. For example, the service may be a V2x service or a video service.

[0187] The configuration message may be sent from the OAM to the entity 100 with at least one of the following parameters:

[0188] Service ID,

[0189] UE ID (similar to non-open user group),

[0190] Optional Network Slice Selection Assistance Information (NSSAI),

[0191] Monitoring / evaluation configuration,

[0192] Geographic area (cell, tracking area level),

[0193] Time validity, periodicity,

[0194] QoS feature thresholds,

[0195] QoS adjustment priority of QoS flows (per service / UE),

[0196] UE / RAN measurement requirements,

[0197] • List of original QoS profiles and alternative QoS profiles (for each service).

[0198] The auxiliary information 101 may be or include one or more of the above parameters.

[0199] When the assistance information 101 is obtained from the OAM system, the assistance information 101 may be provided for each RAN node and / or each UE. For example, the assistance information 101 may be part of the RAN configuration sent through the interface between the OAM system and the entity 100, such as Fig. 9 shown.

[0200] The auxiliary information 101 may also be obtained by the entity 100 from the UE 400. In the case where some information comes from an application, the auxiliary information 101 may be provided by the UE 400 to the entity 100 (located in the NG-RAN), i.e., the UE 400 may bridge the auxiliary information 101 (from the application client) to the entity 100, instead of the 5GC bridging the auxiliary information 101 (e.g., from the application server) to the entity 100.

[0201] like Fig.10 As shown, in this case, the application client at UE 400, or the vertical application enablement client (e.g., as specified in TS23.434), can receive some assistance information 101 or policies from the application server or application enablement server through application layer signaling (e.g., V1, V1-AE, VAL-UU, SEAL-UU specified in TS23.434 / 23.286). This can be done during the configuration policy deployment phase or during service operation. Based on this information, the application at the UE can provide the assistance information 101 to the V2X or vertical layer and the AS layer. In this case, the assistance information 101 can be sent to the entity 100 (in the NG-RAN) through RRC signaling (UEAssistanceInformation).

[0202] Initially, after the interaction between 5GC and AF, the application server or enabling server (including AF function) can send the necessary configuration information to the application of UE 400 through application layer signaling. This can also include application ID or service ID or UEID, and configuration policy. The application client or application enabling client performs mapping for a single UE among multiple UEs (in the case of group communication) and sends it to the AS layer (in the case of V2X-UE, it will pass through the V2X layer). Mapped to QoS configuration policy, and then sent to NG-RAN through RRC to support the selection of QoS adjustment.

[0203] Fig.10 One or more of the above steps shown in may be optional. For example, Fig.10 Steps 0 to 3 in may be optional steps.

[0204] Next, the steps of evaluating QoS adjustments by entity 100 (in the RAN) using acquired assistance information 101 are described. First, some terms are explained:

[0205] CSI: Channel State Information

[0206] RRM: Radio Resource Management

[0207] RLM: Radio Link Monitoring

[0208] ICIC: Inter-cell Interference Coordination

[0209] eICIC: Enhanced ICIC

[0210] UL / DL: Uplink / Downlink

[0211] RRC: Radio Resource Control

[0212] PRB: Physical Resource Block

[0213] PDCP: Packet Data Convergence Protocol

[0214] Based on one or more measurements from the UE 400 (e.g., radio measurements, such as CSI / RRM / RLM measurements) and other RAN nodes (e.g., backhaul radio measurements, such as BH RRM / RLM / CSI or ICIC / eICIC information, load information from surrounding BSs, etc.), the entity 100 at the RAN can verify the QoS and evaluate possible QoS adjustments from the RAN perspective. The evaluation and adjustment (i.e., upgrade / downgrade) criteria for such decisions are implementation specific and are based on at least one of the following factors:

[0215] Downlink packet delay for each 5QI,

[0216] Downlink packet discard rate for each 5QI,

[0217] Uplink packet loss rate for each 5QI,

[0218] Uplink PDCP packet delay for each 5QI,

[0219] Each 5QI load,

[0220] Total uplink / downlink PRB utilization,

[0221] Uplink / downlink PRB total utilization distribution,

[0222] UL / DL PRB for data services,

[0223] Average uplink / downlink throughput of UE in gNB,

[0224] UE uplink / downlink throughput distribution in gNB,

[0225] Number of RRC connections,

[0226] QoS flow related measurements and statistics (e.g., QoS flow activity, QoS flow establishment).

[0227] Entity 100 (NG-RAN) may initially obtain the QoS profile for each PDU session from entity 200 in 5GC (in the initial context establishment or modification request, as part of the QoS requirements defined in TS38.413), and / or obtain the QoS policy (auxiliary information), including multiple QoS profiles for each PDU session, from OAM or 5GC / AF (application server) or UE (application client).

[0228] Upon receiving the initial context establishment request message, entity 100 may store the QoS profile of each received PDU session or QoS flow, which may include the requested QoS profile, alternative QoS profile and auxiliary information 101 to help entity 100 process the alternative QoS profile.

[0229] Upon receiving the UE context modification request message, the entity may store the received QoS profile for each PDU session or QoS flow, which may include the requested QoS profile, the alternative QoS profile and the auxiliary information 101.

[0230] In addition, entity 100 can determine the mapping of QoS flows to QoS profiles based on the configuration from entity 200 in 5GC (i.e., QoS profiles, alternative QoS profiles, and optionally, additional information used by 5GC to decide on QoS profile adjustments), evaluate the alternative QoS profiles, and notify the second entity 110 (which can be entity 200) in 5GC of the results.

[0231] Thirdly, the step of providing evaluation and / or adjustment results by the entity 100 (here in the RAN) is described.

[0232] Entity 100 may provide evaluation and / or adjustment results to entity 110 in 5GC. The evaluation results may be provided in request 102 or QoS information 103. The adjustment results may be provided in QoS information 103.

[0233] After evaluating the potential QoS adjustments, if the entity is not (yet) allowed to adjust the QoS, the entity 100 may provide a first notification (which may be or be included in the request 102) to the entity 110 about whether an upgrade is possible. The first notification may include at least one of the potential QoS profiles, and optionally auxiliary information, such as the cost / priority of switching to the potential QoS profile (from the RAN's perspective).

[0234] The complete list of information in the notification may include at least one of the following:

[0235] The reason for the notification (potential or anticipated upgrade / downgrade, adjustment outcome),

[0236] New or potential / anticipated QoS profiles based on QoS adjustments,

[0237] Optionally, a flag indicating that the notification is for upgrading or downgrading,

[0238] Optionally, the switching cost or priority from the RAN perspective,

[0239] an updated priority of the QoS profile of at least one QoS flow (communication session),

[0240] - Update of the switching cost for at least one QoS flow and / or geographical area (cell area).

[0241] The switching cost may include at least one of the following parameters: packet loss, service interruption time, impact on other GBRQoS flows. Each parameter may be expressed in digital (e.g., 10ms) form, logical (e.g., yes / no) form, or relative (e.g., high / medium / low) form.

[0242] The priority may be used to indicate a preference to adjust to that QoS profile from the RAN implementation perspective (eg, a QoS profile that consumes less radio resources may have a higher priority).

[0243] like Fig.11 As shown, the first notification that QoS can be achieved can be carried in a PDU session resource notification transmission message 1100. The purpose of the PDU session resource notification procedure is to notify that an already established QoS flow or PDU session of a given UE is released or is no longer satisfied or satisfied again by the NG-RAN node for which notification control is requested. The procedure can use UE-related signaling. The entity 100 can start the procedure by sending a PDU session resource notification message 1100. The PDU session resource notification message 1100 may include information on the PDU session resources or QoS flows released or no longer satisfied or satisfied again by the entity 100.

[0244] In addition, Table 4 and Table 5 show an implementation of the enhanced notification message described in the above TS38, 413. In the case of downgrade, the notification reason can be set to "unsatisfied", and in the case of upgrade, the notification reason can be set to "satisfied" (the current QoS profile can still be satisfied).

[0245] For a QoS flow with multiple QoS profiles, the PDU Session Resource Notification message shall include:

[0246] • A list of GBR QoS flows that are no longer satisfied, and an indication of which alternative QoS profile (if any) may be supported.

[0247] If a more desirable QoS profile than the current QoS profile can be satisfied, a list of GBR QoS flows and an indication of the corresponding QoS profile.

[0248] If NG-RAN is allowed to perform QoS profile adjustment, the adjusted GBR QoS flow list and an indication of the corresponding adjusted QoS profile.

[0249] Table 4 (PDU session resource notification transmission):

[0250]

[0251] Table 5

[0252] Range Limitation illustrate maxnoofQoSFlows The maximum number of QoS flows allowed in a PDU session. The value is 64.

[0253] The switching cost in the above example can also be expressed in the form of parameters such as timers and thresholds.

[0254] Instead of indicating the reason in the first notification, a new "upgrade or downgrade flag" IE may be introduced to indicate different scenarios, such as upgrade, downgrade.

[0255] In addition, the first notification can also be provided in a similar manner as a specific embodiment of the PDU session resource modification indication. Fig.12 As shown, the first notification that QoS can be implemented can be carried in the PDU session resource modification indication 1200. The purpose of the PDU session resource modification indication procedure is for the entity 100 to request modification of an established PDU session. This procedure can use UE-related signaling.

[0256] For a QoS flow with multiple QoS profiles, the PDU Session Resource Notification message shall include:

[0257] • A list of GBR QoS flows that are no longer satisfied, and an indication of which alternative QoS profile (if any) may be supported.

[0258] If a more desirable QoS profile than the current QoS profile can be satisfied, a list of GBR QoS flows and an indication of the corresponding QoS profile.

[0259] If NG-RAN is allowed to perform QoS profile adjustment, the adjusted GBR QoS flow list and an indication of the corresponding adjusted QoS profile.

[0260] In addition, Table 6 shows an implementation manner.

[0261] Table 6 (PDU session resource modification indication transmission):

[0262]

[0263] The "reason for modification" can also be implemented using flags such as "upgrade flag or downgrade flag".

[0264] Based on the first notification, which may be request 102, entity 100 may receive instructions for adjusting QoS, or QoS may be adjusted by another entity (eg, entity 110).

[0265] If entity 100 (NG-RAN) is allowed to adjust the QoS profile on its own, the same notification mechanism can be used to provide a second notification (which can be QoS information 103, or include QoS information 103) to indicate the intention to change the QoS profile to entity 110 in 5GC (advance notification). Entity 110 (5GC) can further provide this information to the application. Entity 110 and the application can prepare for the QoS profile change from the 5GC / application side, or stop the change at entity 100 if it is not needed (in the case of advance notification).

[0266] In addition to advance notification about, for example, expected changes, entity 100 may also provide a third notification (which may be, or include, QoS information 103) to entity 110 in 5GC after the adjustment is completed (expiration notification). The third notification to entity 110 in 5GC may include an indication of the current QoS profile. This additional notification may be implemented using the same PDU session resource notification transport message. The switching cost IE may be skipped. A new notification cause "adaptation" should be added to indicate to the 5GC that the QoS profile needs to be changed accordingly. This expiration notification may also be implemented using a PDU session resource modification request transport message, instead of as described above. Due to the adaptation of the QoS profile, entity 100 may update the priority / ranking / level / preference mapping of the QoS profile and provide it to the 5GC.

[0267] The entity 100 may provide the evaluation and / or adjustment results to the entity 110 in the OAM system. The evaluation and / or adaptation results may also be provided to the OAM system using a management interface between the entity 100 (NG-RAN) and the OAM. For example, the OAM may use information such as feedback to coordinate the configuration of related policies for multiple QoS processes across multiple NG-RAN nodes to achieve load balancing.

[0268] In the following, some examples from real use cases are described.

[0269] Example 1: Different operation options using auxiliary information 101.

[0270] Regarding the determination of QoS adjustments, there are different operational options regarding multi-QoS processing, performing QoS adjustments and notifying the 5GC of the results. Regarding the determination of QoS adjustments, there are 2 operational options:

[0271] Option 1: Entity 100 (NG-RAN) determines the QoS adjustment and notifies entity 110 (5GC).

[0272] Option 2: Entity 110 (5GC) determines QoS adjustment based on information provided by entity 100 (NG-RAN).

[0273] The assistance information 101 from the entity 200 (5GC) may indicate to the entity 100 which option should be used, and the information required for the entity 100 to operate in that option. For example, in option 1, the assistance information 101 may include information that helps the entity 100 determine QoS adjustments (e.g., allowed switching costs, 5GC switching preferences). For option 2, the assistance information 101 may include information about what the entity 100 should report to the entity 110 (e.g., switching costs, RAN switching preferences).

[0274] In the case of option 1, the entity 100 may also perform QoS adjustment on the RAN side and / or notify the entity 110 in the 5GC of the RAN QoS adjustment result when configured to operate according to the auxiliary information 110.

[0275] Example 2: Multi-QoS flow processing using auxiliary information

[0276] When entity 100 (NG-RAN) does not have the ability to upgrade all candidate QoS flows (for example, only 20 out of 100 QoS flows may be upgraded), entity 100 may select QoS flows to be upgraded based on auxiliary information 101 such as preference / priority provided by entity 200 (5GC / OAM).

[0277] The preferences / priorities can be derived from application requirements or service level agreements with users or network deployment considerations. For example, TSN / V2X services need to recover / upgrade QoS as soon as possible. While some services can tolerate working in degraded QoS (e.g., real-time streaming) for a little longer. In this case, the upgrade of TSN / V2X services of NG-RAN will be given higher priority and the live streaming services of NG-RAN will be given lower priority.

[0278] Based on the priority / preference information from 5GC, NG-RAN can decide the following:

[0279] 1. At a specific time, only some candidate QoS flows to be upgraded on one NG-RAN node (e.g., gNB) are selected for upgrading.

[0280] 2. Select to upgrade some QoS flows of a NG-RAN node at a specific time, while other QoS flows of the NG-RAN node are downgraded due to the upgrade.

[0281] The proposed embodiments are based on unique signaling in the radio interface, the NGAP interface and possibly the RAN-OAM interface involving the exchange of new messages; the already available messages are enhanced with new information elements.

[0282] According to another aspect of the present disclosure, a communication device is provided, comprising at least one of the following: a bus, a processor, a storage medium, a bus interface, a network adapter, a user interface and an antenna, wherein the bus is used to connect the processor, the storage medium, the bus interface and the user interface; the processor is used to execute the above method; the storage medium is used to store an operating system and data to be sent or received; the bus interface is connected to the network adapter; the network adapter is used to implement the signal processing function of the physical layer in the wireless communication network; the user interface is used to connect the user input device; and the antenna is used to send and receive signals.

[0283] Another aspect of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions. When the computer-readable storage medium runs on a computer, the computer executes the above method.

[0284] Another aspect of the present disclosure provides a computer program product comprising instructions, wherein when the computer program product is run on a computer, the computer performs the above method.

[0285] Another aspect of the present disclosure provides a computer program. When the computer program is executed on a computer, the computer executes the above method.

[0286] The method or algorithm steps described in conjunction with the content disclosed in this application can be implemented by hardware, or can be implemented by a processor executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, removable hard disks, CD-ROMs, or any other form of storage medium known in the art. For example, a storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. In addition, the ASIC may be located in a user device. Of course, the processor and the storage medium may be present in a user device as discrete components.

[0287] The above embodiments can be implemented in whole or in part by using software, hardware, firmware or any combination thereof. When the embodiments are implemented using software, the embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a server or a data center to another website, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber or digital subscriber line (DSL)) or wireless (e.g., infrared, radio or microwave). The computer-readable storage medium can be any available medium accessible to a computer, or it can be a data storage device integrating one or more available media, such as a server or a data center.

[0288] Available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), among others.

[0289] The term "and / or" in this specification only describes the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: only A exists, both A and B exist, and only B exists. In addition, the character " / " in this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0290] Those skilled in the art will appreciate that the units and algorithm steps in the examples described in conjunction with the embodiments disclosed in this specification may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether such functions are performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementations should not be considered to be beyond the scope of this application.

[0291] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, devices and units can refer to the corresponding processes in the aforementioned method embodiments, which will not be described in detail here.

[0292] The above description is only a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Within the technical scope disclosed in the present application, any changes or substitutions that can be thought of by those skilled in the art should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

[0293] The present application 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, other variations will be understood and implemented by those skilled in the art in practicing the claimed invention. In the claims and in the specification, the word "comprising" does not exclude other elements or steps, and "a" or "an" does not exclude the plural. A single element or other unit may fulfil the functions of several entities or items described in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not mean that a combination of these measures cannot be used in an advantageous implementation.

Claims

1. An entity (100), comprising a radio access network (RAN) entity, the entity (100) being used to adjust the QoS of at least one quality of service (QoS) flow in the RAN, characterized in that: The entity (100) comprises: Memory; A processor coupled to the memory, configured to: Acquiring auxiliary information (101), wherein the auxiliary information (101) is used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device (400), wherein the at least one wireless communication device (400) includes at least one user equipment UE; A request (102) for adjusting from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information (103) is provided to a second entity (110), wherein the processor decides whether to adjust the QoS profile of the first QoS flow by itself based on the auxiliary information (101), and if the processor decides to adjust the QoS profile by itself, the QoS information (103) is sent to the second entity (110), and if the processor decides not to adjust the QoS profile by itself, the request (102) is sent to the second entity (110), and the second entity (110) includes a core network CN entity.

2. The entity (100) according to claim 1, characterized in that The processor of the entity (100) is further configured to: Providing another request (102) for adjustment from the first QoS profile of the second QoS flow to the second QoS profile or another QoS information (103) of the adjustment to the second entity (110), wherein the another request (102) or the another QoS information (103) is based on the auxiliary information (101).

3. The entity (100) according to claim 1 or 2, characterized in that The assistance information (101) is provided for at least one packet data unit (PDU) session, at least one QoS profile, at least one QoS flow, at least one wireless communication device (400) and / or at least one RAN entity.

4. The entity (100) according to claim 1 or 2, characterized in that The auxiliary information (101) includes at least one of the following: An identification ID of at least one PDU session; an ID of the at least one QoS profile; an ID of the at least one wireless communication device (400); The ID of the at least one QoS flow.

5. The entity (100) according to claim 1 or 2, characterized in that The auxiliary information (101) includes at least one of the following: an indication as to whether said entity (100) performed said adjustment; an indication of an adjustment priority of the at least one QoS profile; timing information related to the time validity and / or periodicity of the evaluation of said adjustment of said at least one QoS profile; region information indicating a region to which said evaluation of said adjustment of said at least one QoS profile applies; event information indicating an event at which said evaluation was started and / or ended and / or paused and / or resumed; The resource requirements of the at least one QoS profile.

6. The entity (100) according to claim 1 or 2, characterized in that The auxiliary information (101) includes at least one of the following: Cost information for enabling the entity (100) to provide the request (102) or the QoS information (103).

7. The entity (100) according to claim 1 or 2, characterized in that The adjustment from the first QoS profile to the second QoS profile includes at least one of the following: upgrading to a better or more desired QoS profile for the at least one QoS flow; Downgrading to a worse or less desirable QoS profile for the at least one QoS flow.

8. The entity (100) according to claim 1 or 2, characterized in that The processor of the entity (100) is further configured to: The adjustment from the first QoS profile to the second QoS profile is performed and the QoS information (103) is provided to the second entity (110).

9. The entity (100) according to claim 8, characterized in that The QoS information (103) includes the result of the adjustment.

10. The entity (100) according to claim 1 or 2, characterized in that The adjustment from the first QoS profile to the second QoS profile is based on the acquired auxiliary information (101) and / or an evaluation of RAN capabilities to support the adjustment of the at least one QoS flow.

11. The entity (100) according to claim 10, characterized in that The processor of the entity (100) is further configured to: performing said evaluating of RAN capabilities to support said adjusting of said at least one QoS flow; Based on a result of the evaluation, it is decided whether to perform the adjustment from the first QoS profile to the second QoS profile.

12. The entity (100) according to claim 10, characterized in that The evaluation of whether the RAN is able to support the adjustment of the at least one QoS profile is based on non-periodic or periodic monitoring of real-time actual or expected radio resource quality, traffic load and / or resource availability of the at least one QoS profile according to the acquired auxiliary information (101), and the at least one QoS profile includes at least one alternative QoS profile and a current QoS profile.

13. The entity (100) according to claim 10, characterized in that The evaluation of whether the RAN is able to support the adjustment of the at least one QoS profile is triggered by a handover and / or handover request message (500).

14. The entity (100) according to claim 10, characterized in that The evaluation of whether the RAN is capable of supporting the adjustment of the at least one QoS profile is a Radio Resource Control, RRC, function and / or a Radio Resource Management, RRM, function.

15. The entity (100) according to claim 1 or 2, characterized in that The processor of the entity (100) is further configured to: The adjustment from the first QoS profile to the second QoS profile is not performed by itself, and the request (102) is provided to the second entity (110).

16. The entity (100) according to claim 10, characterized in that The request (102) includes a result of the evaluation.

17. The entity (100) according to claim 1 or 2, characterized in that The auxiliary information (101) is obtained from a network entity (200) and / or a network management entity and / or an application entity.

18. The entity (100) according to claim 1 or 2, characterized in that The request (102) or the QoS information (103) includes at least one of the following: an indication of whether the at least one QoS profile has been changed; New or potential or desired QoS profiles based on QoS flow adjustments; Cost information; An adjustment priority of the at least one QoS profile.

19. An entity (200) for supporting adjustment of QoS of at least one Quality of Service (QoS) flow in a RAN, characterized in that The entity (200) comprises: Memory; A processor coupled to the memory, configured to: Providing assistance information to a RAN entity, wherein the assistance information is used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device (400), the at least one wireless communication device (400) comprising at least one user equipment UE; and A request (102) for adjusting from a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information (103) is obtained from the RAN entity, wherein the auxiliary information (101) is used by the RAN entity to decide whether to adjust the QoS profile of the first QoS flow by itself, and if the RAN entity decides to adjust the QoS profile by itself, the QoS information (103) is sent to the entity (200); if the RAN entity decides not to adjust the QoS profile by itself, the request (102) is sent to the entity (200).

20. The entity (200) according to claim 19, characterized in that The entity (200) is a network entity, a network management entity or an application entity.

21. A method (300) for adjusting the QoS of at least one Quality of Service (QoS) flow in a RAN, characterized in that: The method (300) comprises: Acquiring (301) auxiliary information (101), the auxiliary information (101) being used to adjust at least one QoS profile of at least one QoS flow of at least one wireless communication device (400), the wireless communication device (400) comprising at least one user equipment UE; A request (102) for adjusting a first QoS profile of a first QoS flow to a second QoS profile or the adjusted QoS information (103) is provided (302), wherein a decision is made based on the auxiliary information (101) whether to adjust the QoS profile of the first QoS flow by itself, and if it is decided to adjust the QoS profile by itself, the QoS information (103) is sent, and if it is decided not to adjust the QoS profile by itself, the request (102) is sent.

22. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed on a computer, the computer performs the method (300) according to claim 21.

Images