Method for performing quality of service operations in a mobile communication network and user equipment

Abstract

A method and a user equipment for performing quality of service operation in a mobile communication network are proposed. The UE checks whether there is a QoS operation error in the QoS configuration received from the network. When the UE receives a QoS rule associated with a specific QFI but there is no QoS flow description for the QFI, the UE further determines whether the QoS rule belongs to a GBR QoS flow. If yes, the UE detects a QoS operation error. If the QoS rule is a default QoS rule, the UE releases the PDU session. If the QoS rule is not a default QoS rule, the UE rejects a PDU session modification command message carrying the QoS rule or deletes a PDU rule carried by a PDU session establishment accept message with a 5GSM cause value indicating a QoS operation error. According to the method and the user equipment provided by the present application, the QoS rule associated with a specific QFI but without a QoS flow description for the specific QFI can be processed and relevant operation can be performed.

Description

[0001] This application is a divisional application of patent application No. 201980003943.0, with an international filing date of August 9, 2019, international application No. PCT / CN2019 / 099905, entitled "Enhanced Processing of Service Quality Flow Description".

[0002] Cross-references to related applications

[0003] This application claims priority to U.S. Provisional Application 62 / 717,352, filed August 10, 2018, entitled “5G System Performance Enhancement,” and U.S. Application 16 / 530,152, filed August 2, 2019, the subject of which is incorporated herein by reference. Technical Field

[0004] The disclosed embodiments generally relate to wireless communication, and more specifically, to a method for enhancing the quality of service (QoS) stream description in a 5G new radio (NR) system. Background Technology

[0005] Over the years, wireless communication networks have grown exponentially. Long-Term Evolution (LTE) systems offer higher peak data rates, lower latency, improved system capacity, and lower operating costs due to their simplified network architecture. LTE systems (also known as 4G systems) also provide seamless integration with older wireless networks such as GSM, CDMA, and the Universal Mobile Telecommunication System (UMTS). In LTE systems, the evolved universal terrestrial radio access network (E-UTRAN) comprises multiple evolved Node-Bs (eNodeB / eNBs) that communicate with multiple mobile stations called user equipment (UEs). The 3rd Generation Partner Project (3GPP) network typically includes a hybrid of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) committee has decided to focus future NGMN activities on defining the end-to-end requirements for 5G NR systems.

[0006] In 5G, Protocol Data Unit (PDU) session establishment is a parallel process to the Packet Data Network (PDN) connection process in 4G. A PDU session defines the association between the UE and the data network providing PDU connection services. Each PDU session is identified by a PDU session ID and can include multiple QoS flows and QoS rules. In 5G networks, QoS flows represent the optimal granularity for QoS management, enabling more flexible QoS control. The concept of QoS flows in 5G is similar to EPS bearers in 4G. Each QoS flow is identified by a unique QoS flow ID (QFI) within the PDU session. Each QoS rule is identified by a QoS rule ID (QRI). More than one QoS rule may be associated with the same QoS flow. For each PDU session establishment, a default QoS rule needs to be sent to the UE and associated with a QoS flow. There should be one and only one default QoS rule within a PDU session.

[0007] QoS indicates performance from the network user's perspective. All types of services mapped to the same LTE EPS bearer or the same 5G QoS stream will receive the same level of packet forwarding processing (e.g., scheduling policies, queue management policies, rate shaping policies, RLC configuration, etc.). Providing different QoS forwarding processing requires separate 5G QoS streams. Each QoS stream can include multiple QoS rules consisting of a QoS profile, packet filters, and a priority order. The QoS profile includes QoS parameters and QoS tags. Packet filters are used to bind QoS streams to specific QoS tags. The priority order indicates the priority for adapting QoS rules to QoS streams. The UE performs uplink (UL) user plane service classification and tagging, i.e., associating UL services with QoS streams based on QoS rules.

[0008] The QoS flow parameters provided by the network through the QoS flow description information element (IE) are separate from the QoS rule IE. When the network configures QoS rules for QFI, it may not provide the corresponding QoS flow description. A solution is needed to enable the UE to handle QoS rule configurations that do not provide corresponding QoS flow descriptions. Summary of the Invention

[0009] A QoS rule management method with enhanced processing of QoS flow descriptions is proposed. The UE checks the QoS configuration received from the network for QoS operation errors. When the UE receives a QoS rule associated with a specific QFI but without a QoS flow description for that QFI, the UE further determines whether the QoS rule belongs to a guaranteed bit rate (GBR) QoS flow. If so, the UE detects a QoS operation error. If the QoS rule is the default QoS rule, the UE releases the PDU session. If the QoS rule is not the default QoS rule, the UE rejects the PDU session modification command message carrying the QoS rule, or deletes the PDU rule carried by the PDU session establishment accept message with a 5GSM cause value indicating a QoS operation error.

[0010] In one embodiment, in a mobile communication network, a UE receives a PDU session modification command message for performing a QoS operation associated with a PDU session based at least on one of a QoS rule IE and a QoS flow description IE. The UE determines that a QoS rule associated with a QoS flow having a specific QFI does not have a corresponding QoS flow description, where the specific QFI indicates a GBR QoS flow. If the QoS rule IE contains another valid QoS rule, the UE deletes the QoS rule associated with the QoS flow having the specific QFI after completing the QoS operation; or if the QoS rule IE does not contain another valid QoS rule, the UE rejects the PDU session modification command message, where the QoS rule associated with the QoS flow having the specific QFI is not the default QoS rule.

[0011] In another embodiment, in a mobile communication network, the UE receives a PDU session establishment accept message for performing QoS operations associated with the PDU session based at least on one of the QoS rule IE and the QoS flow description IE. After the QoS operation, the UE determines that the QoS rule associated with a QoS flow having a specific QFI does not have a corresponding QoS flow description. The UE determines that the QoS flow with the specific QFI has a GBR QoS flow resource type. If the QoS rule is not the default QoS rule, the UE deletes the QoS rule; if the QoS rule is the default QoS rule, the UE releases the PDU session.

[0012] According to the method and user equipment for performing quality of service operations in a mobile communication network provided by the present invention, QoS rules associated with a specific QFI but without a QoS flow description for that specific QFI can be processed and related operations can be performed.

[0013] Other embodiments and advantages are described in the detailed description below. This overview is not intended to define the invention. The invention is defined by the claims. Attached Figure Description

[0014] In the accompanying drawings, the same numbers represent the same components, illustrating embodiments of the present invention.

[0015] Figure 1 An exemplary 5G network supporting QoS rule management according to a novel aspect is shown;

[0016] Figure 2 A simplified block diagram of a UE according to an embodiment of the present invention is shown;

[0017] Figure 3 The illustration shows an example of a QoS rule that includes QRI and QFI;

[0018] Figure 4 An example of a QoS flow description identified by QFI is shown;

[0019] Figure 5 An embodiment of a PDU session modification process with enhanced QoS flow description processing based on a novel aspect is shown;

[0020] Figure 6 An embodiment of a PDU session establishment process with enhanced QoS flow description processing based on a novel aspect is shown;

[0021] Figure 7 This is a flowchart of a method for QoS flow description processing of a PDU session modification procedure according to a novel aspect of the present invention;

[0022] Figure 8 This is a flowchart of a method for QoS flow description processing in a PDU session establishment process according to a novel aspect of the present invention. Detailed Implementation

[0023] Reference will now be made in detail to some embodiments of the invention, examples of which are shown in the accompanying drawings.

[0024] Figure 1 An exemplary 5G network 100 is illustrated, which supports QoS rule management according to a novelty aspect. The 5G NR network 100 includes a user equipment (UE) 101, a base station (gNB) 102, an access and mobility management function (AMF) 103, and a 5G core network 5GC 104. Figure 1In the example, UE 101 and its serving base station gNB 102 are part of the radio access network RAN ​​120. At the Access Stratum (AS) layer, RAN 120 provides radio access to UE 101 via radio access technology (RAT). At the Non-Access Stratum (NAS) layer, AMF 103 communicates with gNB 102 and 5GC 104 to manage access and mobility for radio access devices in the 5G network 100. UE 101 can be equipped with one or more radio frequency (RF) transceivers to provide different application services through different RATs / CNs. UE 101 can be a smartphone, wearable device, Internet of Things (IoT) device, tablet, etc.

[0025] 5GS networks are packet-switched (PS) Internet Protocol (IP) networks. This means the network transmits all data services in the form of IP packets and provides users with always-on IP connectivity. When a UE joins a 5GS network, a PDN address (i.e., an address that can be used on the PDN) is assigned to the UE for its connection to the PDN. In 4G, EPS defines the default EPS bearer to provide always-on IP connectivity. In 5G, the PDU session establishment process is a parallel process to the PDN connection process in 4G. A PDU session defines the association between the UE and the data network providing PDU connection services. Each PDU session is identified by a PDU session ID and can include multiple QoS flows and QoS rules. In 5G networks, QoS flows represent the optimal granularity for QoS management, enabling more flexible QoS control. The concept of a QoS flow in 5G is similar to that of an EPS bearer in 4G. Each QoS flow is identified by a unique QFI within the PDU session. Each QoS rule is identified by a QRI. There may be more than one QoS rule associated with the same QoS flow. For each PDU session established, a default QoS rule needs to be sent to the UE and associated with the QoS flow.

[0026] exist Figure 1In the example, UE 101 establishes PDU session 110, which includes multiple QoS flows and QoS rules in the NAS layer. Each QoS flow needs to be supported by a Mapped Data Radio Bearer (DRB) in the AS layer. Multiple QoS flows can be mapped to the same DRB. For example, QoS flows #1 and #2 are mapped to DRB #1, and QoS flow #3 is mapped to DRB #2. If the PDU session has a default DRB, all QoS flows that do not have a mapped DRB will be sent through the default DRB. In the current 5G NAS specification, based on the QoS operation codes defined in the QoS rule IE and QoS flow description IE, different QoS operations are allowed, including creating, modifying, and deleting QoS rules and QoS flow descriptions through the PDU session establishment and modification process. However, the QoS flow parameters provided by the network through the QoS flow description IE are separate from the QoS rule IE. As a result, when the network configures QoS rules with QFI, the network may not provide the corresponding QoS flow description for the QFI. In addition, QoS rules can belong to GBRQoS flows, which require QoS flow parameters for data transmission and reception. It is unclear how the UE should handle this situation.

[0027] According to a novel aspect, UE behavior and error handling are defined for QoS rule operations through the PDU session establishment and modification process. The default QoS rule indication (DQR) and QFI of QoS rules established based on signaling exchange should not be changed. The UE should check the QoS configuration (130) provided in the PDU session modification command message and the PDU session establishment accept message to check for QoS operation errors. In one example, when UE 101 receives a QoS rule associated with a specific QFI but without a QoS flow description for that QFI, and UE 101 also determines that the QoS rule belongs to a GBRQoS flow, UE 101 detects a QoS operation error. If the QoS rule is the default QoS rule, UE 101 releases the PDU session. If the QoS rule is not the default QoS rule, UE 101 either rejects the PDU session modification command carrying the QoS rule or deletes the QoS rule carried by the PDU session modification request with a 5GSM cause value indicating a QoS operation error.

[0028] Figure 2A simplified block diagram of a wireless device (e.g., UE 201 and network entity 211) according to an embodiment of the present invention is shown. Network entity 211 may be a base station combined with an MME or AMF. Network entity 211 has an antenna 215 for transmitting and receiving radio signals. An RF transceiver module 214 coupled to the antenna receives RF signals from antenna 215, converts them into baseband signals, and then sends the baseband signals to processor 213. RF transceiver 214 also converts the baseband signals received from processor 213 into RF signals and sends them to antenna 215. Processor 213 processes the received baseband signals and invokes different functional modules to perform functions in network entity 211. Memory 212 includes a non-volatile computer-readable storage medium and a volatile readable storage medium, and stores program instructions and data 220 to control the operation of network entity 211. Figure 2 In the example, network entity 211 also includes a protocol stack 280 and a set of control function modules and circuits 290. PDU session processing circuit 231 handles the PDU session establishment and modification process. QoS flow and rule management circuit 232 creates, modifies, and deletes QoS flows and QoS rules for the UE. Configuration and control circuit 233 provides various parameters to configure and control relevant UE functions, including mobility management and session management.

[0029] Similarly, UE 201 has memory 202, processor 203, and RF transceiver module 204. RF transceiver 204 is coupled to antenna 205, receives RF signals from antenna 205, converts them into baseband signals, and then sends the baseband signals to processor 203. RF transceiver 204 also converts baseband signals received from processor 203 into RF signals and sends them to antenna 205. Processor 203 processes the received baseband signals and invokes different functional modules and circuits to perform functions in UE 201. Memory 202 stores data and program instructions 210 that will be executed by the processor to control the operation of UE 201. Suitable processors include, for example, dedicated processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and other types of integrated circuits (ICs) and / or state machines. The processor associated with the software can be used to implement and configure the features of UE 201.

[0030] UE 201 also includes a set of functional modules and control circuitry to perform the functional tasks of UE 201. Protocol stack 260 includes a NAS layer for communicating with MME or AMF entities connected to the core network, a Radio Resource Control (RRC) layer for higher-level configuration and control, a Packet Data Convergence Protocol / Radio Link Control (PDCP / RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer. System modules and circuitry 270 can be implemented and configured through software, firmware, hardware, and / or a combination thereof. When executed by a processor via program instructions contained in memory, the functional modules and circuitry interact with each other to allow UE 201 to perform embodiments, functional tasks, and features within the network. In one example, system module and circuit 270 includes: PDU session processing circuit 221 that performs the process of establishing and modifying PDU sessions with the network; QoS flow and rule management circuit 222 that manages, creates, modifies and deletes QoS flows and QoS rules; and configuration and control circuit 223 that processes configuration and control parameters for mobility management and session management.

[0031] Figure 3 An example of QoS rules including QRI and QFI is shown. The network can provide the UE with a QoS rule IE, which includes a list of QoS rules. Figure 3 As shown, each QoS rule includes a QRI, the length of the QoS rule, the rule operation code, the DQR bit, multiple packet filters, a list of packet filters, the QoS rule priority, and a QFI. Since the QFI identifies the corresponding QoS flow, a QoS rule with a specific QFI is associated with the QoS flow through the same specific QFI.

[0032] Figure 4 An example of a QoS flow description identified by QFI is shown. The network can provide the UE with a QoS flow description IE, which includes a list of QoS flow descriptions. Figure 4As shown, each QoS flow description includes a QFI, a QoS flow operation code, multiple QoS flow parameters, and a list of QoS flow parameters. As defined in the 3GPP specification, the parameter identifier field identifies each parameter included in the parameter list, and the parameter identifier field contains the hexadecimal encoding of the parameter identifier. For example, the following parameter identifiers are specified: 01H (5QI), 02H (GFBR uplink), 03H (GFBR downlink), 04H (MFBR uplink), 05H (MFBR downlink), 06H (average window), and 07H (EPS bearer identifier). The 3GPP specification also defines a standardized mapping from 5QI to QoS characteristics, such as which 5QI is mapped to a GBR resource type and which 5QI is mapped to a non-GBR resource type.

[0033] Figure 5 An embodiment of a PDU session modification process with enhanced QoS flow description processing according to a novel aspect is illustrated. In step 511, UE 501 and network 502 establish a PDU session through a PDU session establishment procedure. A PDU session can be established to include one or more QoS rules, which include a default QoS rule. Each QoS rule is associated with a QoS flow identified by a QFI. In step 521, network 502 sends a PDU session modification command message to UE 501. This session modification command message is used by the UE to perform certain QoS operations on the PDU session, such as creating a new QoS rule or a new QoS flow description, and / or modifying an existing QoS rule or an existing QoS flow description. The command message carries the QoS rule IE and / or QoS flow description IE for such QoS operation. In step 531, UE 501 determines whether the QoS operation will result in an empty QoS flow description for the existing, created, or modified QoS rule.

[0034] QoS rules with empty QoS flow descriptions can occur under different QoS operations. First, if the QoS operation creates a new QoS rule with a specific QFI, but the network does not provide a corresponding QoS flow description for that specific QFI, UE 501 will not receive any QoS flow description provided for the specific QFI of the new QoS rule, and the QoS rule to be created will have an empty QoS flow description. Second, if the QoS operation deletes an existing QoS flow description for a QFI, this deletion may result in the QoS rule associated with that QFI having an empty QoS flow description. Third, if the QoS operation modifies an existing QoS rule by changing to a new QFI, the QoS rule associated with the new QFI will have no QoS flow description.

[0035] In step 532, UE 501 checks whether an existing QoS rule to be created or modified belongs to a GBR QoS flow. If so, a QoS operation error occurs because the QoS rule should not have an empty QoS flow description for a GBR QoS flow. For the UE to properly control service flows under a GBR QoS flow, the UE needs to know the detailed QoS flow parameters used for the uplink and downlink, such as GFBR and MFBR. As a result, it is an error to not configure a QoS flow description for a GBR QoS flow. The UE can determine this in different scenarios. In the first example, either a GBR QoS flow or a non-GBR QoS flow can use 5QI as the QFI in the description section of the QoS flow. Because the 5QI value is mapped to QoS characteristics that include GBR or non-GBR resource types, the UE can determine whether a QoS rule belongs to a GBR QoS flow or a non-GBR QoS flow. When a corresponding QoS operation is used to create a new QoS rule, the UE 501 will not receive any QoS flow description for the specific QFI of the new QoS rule; or, when a corresponding QoS operation is used to delete an existing QoS flow description, the QoS flow description associated with the specific QFI of the existing QoS rule is deleted after the QoS operation; or, when a corresponding QoS operation is used to modify an existing QoS operation, the modified QoS rule is associated with a specific QFI that does not have a QoS flow description after the QoS operation. In another example, the QoS rule is provided along with a QoS flow description indicating that it is a GBR QoS flow. However, the QoS flow description will be deleted, and the UE can therefore determine that the QoS rule belongs to a GBR QoS flow without the QoS flow description.

[0036] In step 533, UE 501 also checks whether the existing QoS rule to be created or modified is the default QoS rule. If the detection result of step 533 is positive, it means that the QoS rule is the default QoS rule, and this syntax error causes a problem with the default QoS rule of the PDU session. As a result, the PDU session should be released. In step 541, UE 501 initiates the PDU session release procedure by sending a PDU session release request message to network 502. This request message carries a 5GSM cause value #84 indicating "syntax error in QoS operation". If the detection result in step 533 is negative, it means that the QoS rule is not the default QoS rule. Then, in step 551, if the QoS rule IE does not contain other QoS rules, UE 501 rejects the PDU session modification command message with a 5GSM cause value #84 indicating "syntax error in QoS operation". On the other hand, if the QoS rule IE contains other QoS rules, then in step 552, UE 501 should, after the current PDU session modification process is completed, delete the corresponding QoS rule that does not have the corresponding QoS flow description by initiating the PDU session modification process.

[0037] Figure 6 An embodiment of a PDU session establishment process with enhanced QoS flow description processing according to a novel aspect is illustrated. In step 611, UE 601 sends a PDU session establishment request message to network 602. In step 621, network 602 sends a PDU session establishment accept message to UE 601. This accept message carries a QoS rule IE and / or QoS flow description IE for the UE to create new QoS rules and QoS flow descriptions. In step 631, UE 601 determines whether a QoS operation will result in the QoS rule to be created having an empty QoS flow description. In step 632, UE 601 checks whether the QoS rule to be created belongs to the GBR QoS flow resource type. If so, a QoS operation error occurs because the QoS rule should not provide an empty QoS flow description for a GBR QoS flow.

[0038] In step 633, UE 601 also checks whether the QoS rule to be created is the default QoS rule. If the detection result in step 633 is positive, it means that the QoS rule is the default QoS rule, and this syntax error will cause a problem with the default QoS rule of the PDU session. As a result, the PDU session should be released. In step 641, UE 601 initiates the PDU session release process by sending a PDU session release request message to network 602. This request message carries a 5GSM cause value #84 indicating "syntax error in QoS operation". If the detection result in step 633 is negative, it means that the QoS rule is not the default QoS rule. Then in step 651, UE 601 deletes the QoS rule by sending a PDU session modification request message to network 602, which has a 5GSM cause value #84 indicating "syntax error in QoS operation".

[0039] Figure 7 This is a flowchart of a method for processing a QoS flow description during a PDU session modification process according to a novel aspect of the present invention. In step 701, in a mobile communication network, the UE receives a PDU session modification command message for performing a QoS operation associated with the PDU session based at least on one of a QoS rule IE and a QoS flow description IE. In step 702, the UE determines that the QoS rule associated with a QoS flow having a specific QFI does not have a corresponding QoS flow description, wherein the specific QFI indicates a GBR QoS flow. In step 703, if the QoS rule IE contains another valid QoS rule, the UE deletes the QoS rule associated with the QoS flow having the specific QFI after completing the QoS operation; or if the QoS rule IE does not contain another valid QoS rule, the UE rejects the PDU session modification command message, wherein the QoS rule associated with the QoS flow having the specific QFI is not a default QoS rule.

[0040] Figure 8 This is a flowchart of a method for processing a QoS flow description during a PDU session establishment process according to a novel aspect of the present invention. In step 801, in the mobile communication network, the UE receives a PDU session establishment acceptance message for performing QoS operations associated with the PDU session based at least on one of a QoS rule IE and a QoS flow description IE. In step 802, after the QoS operation, the UE determines that the QoS rule associated with a QoS flow having a specific QFI does not have a corresponding QoS flow description. In step 803, the UE determines that the QoS flow having the specific QFI has a GBR QoS flow resource type. In step 804, if the QoS rule is not the default QoS rule, the UE deletes the QoS rule; or if the QoS rule is the default QoS rule, the PDU session is released.

[0041] Although the invention has been described in conjunction with certain specific embodiments for illustrative purposes, the invention is not limited thereto. Therefore, various modifications, adaptations, and combinations of the features of the described embodiments can be made without departing from the scope of the invention as set forth in the claims.

Claims

1. A method for performing Quality of Service (QoS) operations in a mobile communication network, comprising: In the mobile communication network, a user equipment receives a Protocol Data Unit Session Modification Command Message, which is used to perform the Quality of Service (QoS) operation associated with the Protocol Data Unit Session based at least on one of the QoS Rule Information Element and the QoS Flow Description Information Element. It is determined that there is no corresponding service quality flow description for the service quality rule associated with the service quality flow having a specific service quality flow ID, wherein the specific service quality flow ID indicates a guaranteed bit rate service quality flow; as well as If the Quality of Service (QoS) rule information element contains another valid QoS rule, then the QoS rule associated with the QoS flow having a specific QoS flow ID is deleted after the QoS operation is completed; or if the QoS rule information element does not contain another valid QoS rule, then the Protocol Data Unit (PDU) session modification command message is rejected, wherein the QoS rule associated with the QoS flow having a specific QoS flow ID is not the default QoS rule.

2. The method according to claim 1, characterized in that, When the quality of service rule associated with the quality of service flow having a specific quality of service flow ID is the default quality of service rule, the user equipment releases the protocol data unit session.

3. The method according to claim 1, characterized in that, In the mobile communication network, a mapping between 5QI values ​​and quality of service flow resource types with guaranteed bit rate or non-guaranteed bit rate is predefined, wherein the 5QI value is used as the specific quality of service flow ID of the quality of service flow.

4. The method according to claim 3, characterized in that, The quality of service operation is used to create a new quality of service rule, wherein the user equipment does not receive any quality of service flow description for the specific quality of service flow ID of the quality of service rule.

5. The method according to claim 1, characterized in that, Prior to the quality of service operation, the specific quality of service flow ID has a quality of service flow description, wherein the quality of service flow description indicates that the quality of service flow is a guaranteed bit rate quality of service flow.

6. The method according to claim 5, characterized in that, The quality of service (QoS) operation is used to delete an existing QoS flow description, wherein the QoS flow description associated with the specific QoS flow ID of the QoS rule will be deleted after the QoS operation.

7. The method according to claim 1, characterized in that, The quality of service operation is used to modify an existing quality of service rule, wherein the quality of service rule is associated with a specific quality of service flow ID that does not have a corresponding quality of service flow description after the quality of service operation.

8. The method according to claim 1, characterized in that, The user equipment rejects the Protocol Data Unit Session Modification Command message which has a 5GSM reason value indicating a service quality operation error.

9. A user equipment for performing Quality of Service (QoS) operations in a mobile communication network, comprising: The receiver receives a Protocol Data Unit Session Modification Command Message for performing the Quality of Service (QoS) operation associated with the Protocol Data Unit Session, based at least on one of the QoS Rule Information Element and the QoS Flow Description Information Element. A Quality of Service (QoS) flow and rule management circuit is used to determine that a QoS rule associated with a QoS flow having a specific QoS flow ID does not have a corresponding QoS flow description, wherein the specific QoS flow ID indicates a guaranteed bit rate QoS flow; and The Protocol Data Unit (PDU) session processing circuit is configured to delete the QoS rule associated with the QoS flow having a specific QoS flow ID after completing the QoS operation if the QoS rule information element contains another valid QoS rule; or reject the PDU session modification command message if the QoS rule information element does not contain another valid QoS rule, wherein the QoS rule associated with the QoS flow having a specific QoS flow ID is not the default QoS rule.

10. The user equipment according to claim 9, characterized in that, When the quality of service rule associated with the quality of service flow having a specific quality of service flow ID is the default quality of service rule, the user equipment releases the protocol data unit session.

11. The user equipment according to claim 9, characterized in that, In the mobile communication network, a mapping between 5QI values ​​and quality of service flow resource types with guaranteed bit rate or non-guaranteed bit rate is predefined, wherein the 5QI value is used as a specific quality of service flow ID for the quality of service flow.

12. The user equipment according to claim 11, characterized in that, The quality of service operation is used to create a new quality of service rule, wherein the user equipment does not receive any quality of service flow description for the specific quality of service flow ID of the quality of service rule.

13. The user equipment according to claim 9, characterized in that, Prior to the quality of service operation, the specific quality of service flow ID has a corresponding quality of service flow description, wherein the quality of service flow description indicates that the quality of service flow is a guaranteed bit rate quality of service flow.

14. The user equipment according to claim 13, characterized in that, The quality of service (QoS) operation is used to delete an existing QoS flow description, wherein the QoS flow description associated with the specific QoS flow ID of the QoS rule will be deleted after the QoS operation.

15. The user equipment according to claim 9, characterized in that, The quality of service operation is used to modify an existing quality of service rule, wherein the quality of service rule is associated with a specific quality of service flow ID that does not have a corresponding quality of service flow description after the quality of service operation.

16. The user equipment according to claim 9, characterized in that, The user equipment rejects the Protocol Data Unit Session Modification Command message which has a 5GSM reason value indicating a service quality operation error.

17. A method for performing Quality of Service (QoS) operations in a mobile communication network, comprising: In the mobile communication network, a user equipment receives a Protocol Data Unit Session Establishment Acceptance Message for performing the Quality of Service (QoS) operation associated with the Protocol Data Unit Session, based at least on one of the QoS Rule Information Elements and QoS Flow Description Information Elements. After the service quality operation, it is determined that there is no corresponding service quality flow description for the service quality rule associated with the service quality flow having a specific service quality flow ID; The specific quality of service flow ID is determined to indicate the guaranteed bit rate quality of service flow; as well as If the quality of service rule is not the default quality of service rule, then the quality of service rule is deleted; if the quality of service rule is the default quality of service rule, then the protocol data unit session is released.

18. The method according to claim 17, characterized in that, In the mobile communication network, a mapping between 5QI values ​​and quality of service flow resource types with guaranteed bit rate or non-guaranteed bit rate is predefined, wherein the 5QI value is used as the specific quality of service flow ID of the quality of service flow.

19. The method according to claim 17, characterized in that, The quality of service operation is used to create a new quality of service rule, wherein the user equipment does not receive any quality of service flow description for the specific quality of service flow ID of the quality of service rule.

20. The method according to claim 17, characterized in that, The user equipment deletes the quality of service rule by sending a Protocol Data Unit Session Modification Request message with a 5GSM cause value indicating a quality of service operation error to the mobile communication network.

21. A user equipment for performing Quality of Service (QoS) operations in a mobile communication network, comprising: A processor, coupled to a memory storing program instructions and data, which, when executed by the processor, cause the user equipment to perform the method of any one of claims 1-8 above.

22. A user equipment for performing Quality of Service (QoS) operations in a mobile communication network, comprising: A processor, coupled to a memory storing program instructions and data, which, when executed by the processor, cause the user equipment to perform the method of any one of claims 17-20.

23. A non-volatile computer-readable storage medium storing program instructions and data, which, when executed by a processor of a user equipment performing quality of service operations in a mobile communication network, cause the user equipment to perform the method of any one of claims 1-8, 17-20.

Images