Flexible policy decision and quality of service execution

Abstract

A wireless communication method for policy control functionality is disclosed herein. The method includes determining a flexible quality of service (QoS) profile for a QoS flow and transmitting the flexible QoS profile for the QoS flow to a session management function (SMF), where the flexible QoS profile includes a default set of QoS parameters for the QoS flow and slave QoS information for at least one slave set of QoS parameters for at least one internal flow in the QoS flow.

Description

Technical Field

[0001] This document primarily focuses on wireless communication, especially 5G wireless communication. Background Technology

[0002] In 5G networks, the QoS (Quality of Service) model is based on corresponding QoS flows. The 5G QoS model supports both QoS flows that require guaranteed flow bit rates (e.g., GBR QoS flows) and QoS flows that do not require guaranteed flow bit rates (e.g., non-GBR QoS flows). QoS flows represent the finest granularity of QoS differentiation within a Differentiated Transaction Unit (PDU) session. Furthermore, a QFI (QoS Flow ID (Identifier)) is used to identify a QoS flow in the 5G system.

[0003] To meet QoS requirements, 5G networks create a QoS profile for each QoS flow. The 5G network determines an explicit QoS profile based on the service requirements mapped to the corresponding QoS flow. Such QoS profiles are well-suited for QoS flows that contain only one type of service flow with uniform QoS requirements (e.g., only audio, video, or text data). However, if a QoS flow actually contains multiple types of service flows (e.g., audio, video, and haptic data belonging to XR (Augmented Reality) applications), it becomes difficult for the 5G network to determine an appropriate QoS profile for such a flow, because different types of service traffic require different QoS profiles. Summary of the Invention

[0004] This document relates to methods, systems, and apparatuses for implementing flexible QoS requirements, and in particular to methods, systems, and apparatuses for applying flexible QoS requirements to a single QoS flow.

[0005] This disclosure relates to a wireless communication method for policy control functions. The method includes: Determine the flexible Quality of Service (QoS) profile for QoS flows, and The flexible QoS profile of the QoS stream is transferred to the Session Management Function (SMF).

[0006] Various embodiments can preferably achieve the following features: Preferably, the flexible QoS profile includes a default QoS parameter set for the QoS flow and subordinate QoS information for at least one subordinate QoS parameter set of at least one internal flow in the QoS flow.

[0007] Preferably, the subordinate QoS information includes at least one of the following: at least one set of subordinate QoS parameters configured to be applied to at least one internal flow in the QoS flow, or at least one subordinate protocol description indicating the traffic characteristics of at least one internal flow in the QoS flow.

[0008] Preferably, the at least one subordinate protocol description is configured to indicate conditions for applying the at least one subordinate QoS parameter set to at least one internal flow in the QoS flow.

[0009] Preferably, each subordinate protocol description includes at least one of the following information for at least one corresponding internal flow in the QoS flow: transport protocol, at least one Internet Protocol address, at least one transport port, at least one QUIC (Fast User Datagram Protocol (UDP) Internet Connection (QUIC)) connection identifier, application protocol information, average size of datagrams in a burst data transmission, average number of datagrams in a burst data transmission, maximum total size of datagrams in a burst data transmission, or average interval between two consecutive burst data transmissions.

[0010] Preferably, each subordinate QoS parameter set includes at least one of the following: guaranteed stream bit rate, maximum stream bit rate, or maximum packet loss rate.

[0011] Preferably, the flexible QoS profile includes a flexible QoS requirement indication for applying at least one subordinate QoS parameter set to at least one internal flow within the QoS flow.

[0012] Preferably, the QoS stream is mapped to a service data stream or bound to a Fast User Datagram Protocol (UDP) Internet Connection (QUIC) connection.

[0013] Preferably, the QoS flow includes multiple internal flows with different QoS requirements and / or corresponding to different QoS parameters.

[0014] Preferably, the wireless communication method further includes: receiving flexible service information of service data streams from application functions, wherein the flexible QoS profile is determined based on the flexible service information.

[0015] Preferably, the flexible service information includes at least one of the following: the default QoS requirements of the service data stream, at least one subordinate QoS requirements of at least one internal stream in the service data stream, or at least one subordinate protocol description indicating the characteristics of at least one internal stream in the service data stream.

[0016] Preferably, the wireless communication method further includes: receiving QUIC traffic characteristic information of the QoS flow from the SMF, wherein the flexible QoS profile is determined based on the QUIC traffic characteristic information.

[0017] Preferably, the QUIC traffic characteristic information includes at least one of the following: source Internet Protocol address, destination Internet Protocol address, source User Datagram Protocol (UDP) port, destination UDP port, at least one QUIC connection identifier, or service public information of at least one internal flow in the QoS flow, wherein the service public information indicates at least one QoS requirement of at least one internal flow in the QoS flow.

[0018] This disclosure relates to a wireless communication method for a Session Management Function (SMF). The method includes: Receive flexible Quality of Service (QoS) profiles for QoS flows from the Policy Control Function (PCF). At least one updated Packet Forwarding Control Protocol (PFCP) rule is generated based on the flexible QoS profile, wherein the at least one updated PFCP rule includes flexible QoS information of the QoS flow; and The at least one updated PFCP rule, including the flexible QoS information, is transmitted to the User Plane Function (UPF).

[0019] Various embodiments preferably achieve the following features: Preferably, the flexible QoS profile includes a default QoS parameter set for the QoS flow and subordinate QoS information for at least one subordinate QoS parameter set of at least one internal flow in the QoS flow.

[0020] Preferably, the subordinate QoS information includes at least one of the following: at least one set of subordinate QoS parameters configured to be applied to at least one internal flow in the QoS flow, or at least one subordinate protocol description indicating the traffic characteristics of at least one internal flow in the QoS flow.

[0021] Preferably, at least one subordinate protocol description is configured to indicate conditions for applying the at least one subordinate QoS parameter set to at least one internal flow in the QoS flow.

[0022] Preferably, each subordinate protocol description includes at least one of the following information for at least one corresponding internal flow in the QoS flow: transport protocol, at least one Internet Protocol address, at least one transport port, at least one QUIC connection identifier, application protocol information, average size of datagrams in a burst data transmission, average number of datagrams in a burst data transmission, maximum total size of datagrams in a burst data transmission, or average interval between two consecutive burst data transmissions.

[0023] Preferably, each subordinate QoS parameter set includes at least one of the following: guaranteed stream bit rate, maximum stream bit rate, or maximum packet loss rate.

[0024] Preferably, the flexible QoS profile includes a flexible QoS requirement indication for applying at least one subordinate QoS parameter set to at least one internal flow within the QoS flow.

[0025] Preferably, the QoS stream is mapped to a service data stream or bound to a Fast User Datagram Protocol (UDP) Internet Connection (QUIC) connection.

[0026] Preferably, the QoS flow includes multiple internal flows with different QoS requirements and / or corresponding to different QoS parameters.

[0027] Preferably, the wireless communication method further includes: transmitting QUIC traffic characteristic information of the QoS flow to the PCF, wherein the flexible QoS profile is determined based on the traffic characteristic information.

[0028] Preferably, the QUIC traffic characteristic information includes at least one of the following: source Internet Protocol address, destination Internet Protocol address, source User Datagram Protocol (UDP) port, destination UDP port, at least one QUIC connection identifier, or service public information of at least one internal flow in the QoS flow, wherein the service public information indicates at least one QoS requirement of at least one internal flow in the QoS flow.

[0029] Preferably, the wireless communication method further includes: receiving QUIC traffic characteristic information of the QoS stream from the UPF.

[0030] Preferably, at least one PFCP rule including the flexible QoS information includes: at least one subordinate QoS enforcement rule associated with at least one subordinate QoS parameter set of at least one internal flow in the QoS flow, and at least one subordinate packet detection rule mapped from at least one subordinate protocol description, the subordinate protocol description indicating the traffic characteristics of at least one internal flow in the QoS flow.

[0031] Preferably, the at least one PFCP rule including flexible QoS information includes: at least one QoS enforcement rule associated with: at least one set of subordinate QoS parameters for at least one internal flow in the QoS flow, and at least one subordinate protocol description for indicating at least one traffic characteristic of at least one internal flow in the QoS flow.

[0032] This disclosure relates to a wireless communication method for user plane functions. The method includes: Receive at least one updated PFCP rule from the Session Management Function (SMF), the rule including Flexible Quality of Service (QoS) information for QoS flows, and At least one updated PFCP rule, including the flexible QoS information, is applied to the QoS flow.

[0033] Various embodiments preferably achieve the following features: Preferably, the at least one PFCP rule including the flexible QoS information includes: At least one subordinate QoS enforcement rule associated with at least one subordinate QoS parameter set of at least one internal flow in the QoS flow, and At least one subordinate packet detection rule mapped from at least one subordinate protocol description, the subordinate protocol description indicating at least one traffic characteristic of at least one internal flow in the QoS flow.

[0034] Preferably, applying at least one updated PFCP rule, including the flexible QoS information, to the QoS flow includes performing flexible QoS control on the traffic of the QoS flow based on at least one QoS enforcement rule and at least one subordinate packet detection rule.

[0035] Preferably, at least one PFCP rule including flexible QoS information includes: At least one QoS enforcement rule associated with the following: at least one set of subordinate QoS parameters for at least one internal flow in the QoS flow, and at least one subordinate protocol description for indicating at least one traffic characteristic of at least one internal flow in the QoS flow.

[0036] Preferably, applying updated PFCP rules, including flexible QoS information, to the QoS flow includes: Flexible QoS control is performed on the traffic of the QoS stream based on at least one subordinate protocol description and at least one subordinate QoS parameter set.

[0037] Preferably, each subordinate protocol description includes at least one of the following information for at least one corresponding internal flow: transport protocol, at least one Internet Protocol address, at least one transport port, at least one QUIC connection identifier, application protocol information, average size of datagrams in a burst data transmission, average number of datagrams in a burst data transmission, maximum total size of datagrams in a burst data transmission, or average interval between two consecutive burst data transmissions.

[0038] Preferably, each subordinate QoS parameter set includes at least one of the following: guaranteed stream bit rate, maximum stream bit rate, or maximum packet loss rate.

[0039] Preferably, the wireless communication method further includes: transmitting QUIC traffic characteristic information of the QoS stream to the SMF.

[0040] Preferably, the QUIC traffic characteristic information includes at least one of the following: source Internet Protocol address, destination Internet Protocol address, source User Datagram Protocol (UDP) port, destination UDP port, at least one QUIC connection identifier, or service public information of at least one internal flow in the QoS flow, wherein the service public information indicates at least one QoS requirement of at least one internal flow in the QoS flow.

[0041] This disclosure relates to a wireless device including policy control functionality. The wireless device includes: The processor, configured to determine a flexible Quality of Service (QoS) profile for QoS flows, and A communication unit configured to transmit a flexible QoS profile of the QoS stream to the Session Management Function (SMF).

[0042] This embodiment preferably achieves the following features: Preferably, the processor is also configured to perform any of the above-described wireless communication methods.

[0043] This disclosure relates to a wireless device including session management functionality. The wireless device includes: A communication unit configured to receive a flexible Quality of Service (QoS) profile of QoS flows from a Policy Control Function (PCF), and A processor configured to generate at least one updated Packet Forwarding Control Protocol (PFCP) rule based on the flexible QoS profile, wherein the at least one updated PFCP rule includes flexible QoS information of the QoS flow. The communication unit is further configured to transmit the at least one updated PFCP rule, including the flexible QoS information, to the User Plane Function (UPF).

[0044] Various embodiments preferably achieve the following features: Preferably, the processor is further configured to perform any of the above-described wireless communication methods.

[0045] This disclosure relates to a wireless device including user plane functionality. The wireless device includes: A communication unit configured to receive at least one updated PFCP rule from a Session Management Function (SMF), the rule including Flexible Quality of Service (QoS) information for QoS flows, and A processor configured to apply at least one updated PFCP rule, including the flexible QoS information, to the QoS flow.

[0046] Various embodiments preferably achieve the following features: Preferably, the processor is further configured to perform any of the above-described wireless communication methods.

[0047] This disclosure relates to a computer program product having stored computer-readable program medium code thereon, which, when executed by a processor, causes the processor to perform any of the aforementioned wireless communication methods. Attached Figure Description

[0048] The exemplary embodiments disclosed herein are intended to provide features that will become apparent when read in conjunction with the accompanying drawings in the following description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are merely examples and not limitations, and various modifications to the disclosed embodiments will be apparent to those skilled in the art upon reading this disclosure without departing from its scope.

[0049] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged without departing from the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in an exemplary order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0050] This invention is defined by the independent claims. Preferred embodiments are defined by the dependent claims. In the following description, although many features may be specified as optional, it should be acknowledged that all features included in the independent claims should not be considered optional.

[0051] The foregoing and other aspects, and their implementations, will be described in more detail in the accompanying drawings, description, and claims.

[0052] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0053] Figure 2 A schematic diagram of a QoS flow according to an embodiment of this disclosure is shown.

[0054] Figure 3 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0055] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0056] Figure 5 A schematic diagram of a QUIC packet header according to an embodiment of the present disclosure is shown.

[0057] Figure 6 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0058] Figure 7 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0059] Figure 8 A flowchart of a method according to an embodiment of this disclosure is shown.

[0060] Figure 9 A flowchart of a method according to an embodiment of this disclosure is shown.

[0061] Figure 10 A flowchart of a method according to an embodiment of this disclosure is shown. Detailed Implementation

[0062] Figure 1 A schematic diagram of a network (architecture) according to an embodiment of this disclosure is shown. Figure 1 In China, (5G) networks include the following network functions / entities: 1) UE: User Equipment In one embodiment, UE refers to a mobile terminal that accesses a 5G network.

[0063] 2) RAN: Radio Access Network In this disclosure, RAN can be equal to a RAN node or a next-generation RAN (NG-RAN) (node). For example, RAN can be a gNB.

[0064] 3) AMF: Access and Mobility Management Function AMF includes the following functions: registration management, connection management, reachability management, and mobility management. AMF terminates RANCP (Control Plane) interface N2 and NAS interface N1, and provides NAS (Non-Access Stratum) encryption and integrity protection. It also assigns SM (Session Management) NAS to the appropriate SMF (Session Management Function) via interface N11. AMF provides services to other consumer NFs (Network Functions) to subscribe to or receive notifications of mobility-related events and information.

[0065] 4) SMF: Session Management Function The SMF includes the following functions: session establishment, modification and release; UE IP (Internet Protocol) address allocation and management (including optional authorization functions); UP (User Plane) function selection and control; and downlink data notification. The SMF can subscribe to mobility-related events and information from the AMF.

[0066] 5) UPF: User-facing functionality UPF includes the following functions: acting as an anchor point for mobility within / between Radio Access Technologies (RATs) and an external session point for interconnection with data networks, packet routing and forwarding instructed by SMF, traffic usage reporting, QoS processing for UPs, downlink packet buffering, and downlink data notification triggering, etc.

[0067] 6: UDM: Unified Data Management The UDM manages the UE's subscription profile. Subscriptions include data for mobility management (e.g., restricted areas) and session management (e.g., QoS profiles per slice per DNN). Subscription data also includes slice selection parameters used by the AMF to select the appropriate SMF. The AMF and SMF obtain subscriptions from the UDM. Subscription data is stored in the UDR (Unified Data Repository). The UDM uses this data upon receiving a request from the AMF or SMF.

[0068] 7) PCF: Policy Control Function The PCF supports a unified policy framework for managing network behavior. The PCF provides access management policies to the AMF, session management policies to the SMF, and / or UE policies to the UE. The PCF can access the UDR to obtain subscription information related to policy decisions. The PCF can also generate policies for managing network behavior based on subscriptions and instructions from the AF (Application Function). The PCF can then provide policy rules to CP functions (e.g., AMF and / or SMF) to enforce these CP functions. For example, the PCF provides QoS policy rules to CP functions to enforce these rules.

[0069] 8) NEF: Network Exposure Function NEF supports exposing network capabilities and events to AFs. Third-party AFs can invoke services provided by the network through NEF, and NEF authenticates and authorizes third-party applications. NEF also provides translation of information exchanged with AFs and with internal NFs.

[0070] 9) AF: Application Function The Application Front-End (AF) interacts with the core network to provide services, such as supporting: application-driven traffic routing, access to the External Exposure Framework (NEF), and interaction with policy control frameworks. The AF can be considered trusted by the operator and may be allowed to interact directly with the relevant Functional Levels (NFs). When the operator does not allow the AF to directly access an NF, it should interact with the relevant NF via the NEF using the External Exposure Framework. The AF can store application information in the User Data Receipt (UDR) via the NEF. The AF can provide instructions to the Policy Control Framework (PCF) to influence QoS policy rules.

[0071] In this disclosure, the term "info" means "information".

[0072] In 5G networks, data traffic transmission is controlled by SMF and UPF. SMF is the CP function for data traffic control, handling the signaling aspects of data traffic transmission (e.g., PDU (Packet Data Unit) session establishment / modification / release, PFCP (Packet Forwarding Control Protocol) session establishment, modification / release, PFCP rule generation, etc.). UPF is the user plane function (UP function) for data traffic control, handling the user plane aspects of data traffic transmission based on instructions received from SMF (e.g., PFCP rules) (e.g., traffic detection, traffic filtering, traffic forwarding, usage reporting, etc.).

[0073] In one embodiment, if a QoS flow is selected for the UE to establish a QUIC (Fast User Datagram Protocol (UDP) Internet connection to a remote server (e.g., AF and / or AS (Application Server)), the network cannot know the binding relationship between the QoS flow and the QUIC connection. Note that in one embodiment, even if internal flows / movements within a QoS flow mapped to a QUIC connection may have different QoS requirements, the network may assign a single QoS profile to only a single QoS flow. In this case, it is difficult for the network to formulate accurate policies for the QoS flow and the QUIC connection, and it is also difficult to detect and protect QUIC traffic transmissions on that QoS flow.

[0074] Figure 2 A schematic diagram of QoS flows according to embodiments of this disclosure is shown. Figure 2In this embodiment, a QoS flow has multiple internal media streams / flows. The QUIC connection is mapped by the 5G network to a single QoS flow, and the QUIC connection itself has multiple internal streams / flows #x, #y, and #z. Although each internal stream / flow #x, #y, and #z within the QoS flow may have different QoS requirements, the 5G network assigns a single QoS profile to the QoS flow mapped to the QUIC connection.

[0075] In this disclosure, a method is proposed that allows a network to know the binding information of QoS flows and QUIC connections, so as to allow the network to formulate appropriate policies to detect and protect QUIC traffic transmission on the corresponding QoS flows.

[0076] PCF is based on flexible policy decisions using application-layer instructions. In one embodiment, once / after the UE obtains a PDU session from the network, the UE can initiate IP communication with a remote server (e.g., AF / AS). Because the remote server has full knowledge of the media components used in the application / service (e.g., audio, video, data, etc.), it can provide supplementary information to the network to facilitate policy decisions and QoS enforcement.

[0077] For example, if the QUIC protocol is used, the QUIC connection endpoints (such as the UE and a remote server) know exactly which media components are encapsulated in the QUIC connection. In this case, the remote server (such as the AF / AS) can facilitate / assist the network in making policy decisions and controlling QoS by providing flexible QoS requirements to the network.

[0078] Figure 3 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 3 The illustrated process can be a PDU session modification process with flexible QoS allocation, which can be triggered by the PCF or AF. During this process, the PCF allocates a flexible QoS profile for at least a portion of the QoS flows belonging to the PDU session. Specifically, Figure 3 The process shown includes the following steps: Step 301: The UE requests the network to establish a PDU session. The network executes the PDU session establishment process according to the request and allocates the corresponding resources (such as the UE IP address) for the requested PDU session.

[0079] During PDU session establishment, the PCF participates in generating appropriate PCC (Policy and Charging Control) policies (including QoS profiles) for the PDU session. The AF can also participate in setting or modifying AF session bindings to provide application layer information that the PCF can use to generate accurate PCC policies.

[0080] Step 302: The UE initiates uplink data transmission or receives downlink data transmission from the application layer (such as AF / AS).

[0081] Step 303: AF / AS can provide / revoke service information to PCF by invoking the service operation Npcf_PolicyAuthorization_Create request, Npcf_PolicyAuthorization_Update request, or Npcf_policy Authorization_Subscribe request (e.g., in response to AF session signaling). PCF accepts the service information and responds to AF.

[0082] In one embodiment, the AF can also provide flexible service information to the PCF. For example, the AF can provide flexible service information to the PCF when / if the service data stream (e.g., a QUIC connection) contains multiple (types) internal streams / flows (e.g., audio, video, and data streams).

[0083] In one embodiment, AF indicates at least one of the following service information for a service data stream: - Default QoS requirement, which applies if no special slave protocol description is indicated for the binding / corresponding dedicated slave QoS; - A list of subordinate QoS requirements, where each subordinate QoS requirement will be applied under specific conditions; - A list of subordinate protocol descriptions, where each subordinate protocol description is associated with a specific subordinate QoS requirement; or - The "Flexible QoS Required" indicator indicates that flexible QoS requirements are applied to the service data stream.

[0084] In one embodiment, if a flexible QoS requirement is determined / applied, the AF at least indicates a list of subordinate QoS requirements to the PCF, and may also carry a "Flexible QoS Required" indication. To further clarify the use of flexible QoS requirements, the AF may also carry a list of protocol descriptions, where each protocol description addresses the conditions for applying a corresponding subordinate QoS requirement.

[0085] In one embodiment, a subordinate protocol description is used to identify traffic characteristics of internal streams / flows within a service data stream, for example, when / if the service data stream contains multiple internal streams / flows. Each subordinate protocol description may contain a combination or at least one of the following information: transport protocol (e.g., UDP), transport IP address, transport port of the internal stream / flow, QUIC connection identifier, application protocol of the internal stream / flow (e.g., RTP (Real-Time Transport Protocol), RTSP (Real-Time Streaming Protocol), RTCP (Real-Time Transport Control Protocol), etc.), average datagram size, average number of datagrams in a burst data transmission, maximum overall size of datagrams in a burst data transmission, average interval between two (consecutive / adjacent) burst data transmissions, etc.

[0086] In this disclosure, a datagram may refer to a QUIC packet.

[0087] In one embodiment where the service data stream is for video transmission, if a 1080P resolution (1920x1080) video frame occupies 155kb (kilobytes) using some compression method, and a QUIC packet carries 1kb of data, then transmitting one frame of 1080P resolution video requires at least 155 consecutive QUIC packets. Furthermore, the interval between two consecutive frame transmissions is 20ms. In this embodiment, the slave protocol description may include or be set to: average datagram size = 1kb, average number of datagrams in a burst transmission = 155, and average time interval between two burst transmissions = 20ms.

[0088] Step 304: The PCF determines the policy information that the SMF needs to update and sends an SM policy update notification request (e.g., Npcf_SMPolicyControl_UpdateNotify) to the SMF. The SM policy update notification request includes updated policy information about the PDU session (e.g., PCC rules, QoS profiles, etc.).

[0089] In step 304, upon / after receiving flexible service information from the AF / AS, the PCF determines updated policy information, including flexible QoS profiles for some / some QoS flows.

[0090] In one embodiment, a flexible QoS profile for a QoS flow includes at least default QoS parameters, which include a combination of the following items: 5G QoS identifier (5QI), allocation and reservation priority (ARP), guaranteed flow bit rate (GFBR) (e.g., for uplink and / or downlink), maximum flow bit rate (MFBR) (e.g., for uplink and / or downlink), maximum packet loss rate (e.g., for uplink and / or downlink), etc.

[0091] In one embodiment, a flexible QoS profile for a QoS flow may also include flexible QoS parameters. For example, flexible QoS parameters may include the following items: - A list of subordinate protocol descriptions, where each subordinate protocol description is used to indicate the traffic characteristics of an internal flow / flow within a QoS flow; - A list of subordinate QoS parameter sets, each of which is applied to an internal flow / stream, which can be identified by a single subordinate protocol description; or - "Flexible QoS required" indicates that flexible QoS requirements are applied to media components or internal streaming / flows.

[0092] In one embodiment, the "requires flexible QoS" indication is optional.

[0093] In one embodiment, for each QoS flow, the PCF may indicate default QoS parameters (e.g., 5QI, ARP, priority, guaranteed flow bit rate, maximum flow bit rate, etc.).

[0094] In one embodiment, for QoS flows configured with flexible QoS requirements, PCF provides flexible QoS parameters (e.g., a list of dependent protocol descriptions, a list of dependent QoS parameter sets, etc.).

[0095] In one embodiment, the dependency protocol description is essentially the same as that described in step 303.

[0096] In one embodiment, the dependent QoS parameter set may include at least one of the following items: Guaranteed Stream Bit Rate (GFBR) (for uplink and / or downlink), Maximum Stream Bit Rate (MFBR) (for uplink and / or downlink), or Maximum Packet Loss Rate (for uplink and / or downlink).

[0097] Once a subordinate QoS requirement is applied to an internal flow / stream within a QoS flow (e.g., from / mapped to a service data flow), the QoS parameters indicated in the subordinate QoS parameter set will override those QoS parameters indicated by the default QoS parameters in the QoS profile.

[0098] Step 305: The SMF acknowledges the PCF request by transmitting an SM policy update notification (e.g., Npcf_SMPolicyControl_UpdateNotify) response.

[0099] Step 306: When / after the SMF receives an updated policy rule (such as a PCC rule) from the PCF, it determines to use the updated policy information received from the PCF to generate an updated PFCP rule.

[0100] In one embodiment, the SMF maps updated policy information (e.g., PCC rules and / or QoS profiles) to a set of QoS flows and generates corresponding PFCP rules for each QoS flow. PFCP rules include at least one of Packet Detection (PDR), Forward Action (FAR), QoS Enforcement (QER), Usage Reporting (URR), etc.

[0101] In step 306, the SMF generates PFCP rules with flexible QoS control information based on the flexible QoS profile provided by the PCF.

[0102] In one embodiment, the SMF generates not only PDRs and QERs for the QoS flow (i.e., all internal flows / mobiles within the QoS flow), but also generates PDRs for each internal flow / mobile within the QoS flow based on the flexible QoS profiles provided by the PCF (e.g., a list of subordinate QoS profiles, a list of subordinate protocol descriptions, etc.). In other words, the SMF maps subordinate protocol descriptions to subordinate PDRs and subordinate QoS parameter sets to subordinate QERs. For example, the SMF generates PDRs and QERs as follows: - Based on the default QoS parameters provided by PCF for this QoS flow, generate PDR (e.g., UL PDR and / or DLPDR) for the QoS flow, and generate corresponding QER (e.g., UL QER and / or DL ​​QER) for the associated PDR. - For each subordinate protocol description, generate a subordinate PDR whose protocol parameters are similar to (e.g., based on) the protocol parameters in the subordinate protocol description provided by the PCF to the SMF. - For each subordinate QoS parameter set, generate a subordinate QER, where the QoS parameters are the same as (e.g., based on) the QoS parameters in the subordinate QoS parameter set provided by the PCF to the SMF; and - For each internal flow / flow identified by the subordinate protocol description, the subordinate QER is associated with the corresponding subordinate PDR.

[0103] Instead, the SMF may not generate a subordinate PDR for the subordinate protocol description or a subordinate QER for the subordinate QoS parameter set. Instead, the SMF indicates information about the subordinate protocol description and subordinate QoS parameter set in the QER of the QoS flow. Specifically, the SMF indicates the following elements in the QER: - A list of subordinate protocol descriptions, such as the descriptions provided by PCF to SMF; - A list of subordinate QoS parameter sets, such as the parameter set provided by the PCF to the SMF; and - (Optional) "Requires flexible QoS" indication.

[0104] Step 307: The SMF sends an N4 session modification request to the UPF, requesting modification of the N4 session of the PDU session. The N4 session modification request carries a set of PFCP rules (e.g., PDR / FAR / QER / URR, etc.) for packet detection and QoS enforcement to be installed in the UPF.

[0105] Step 308: The UPF confirms by sending an N4 session modification response to the SMF.

[0106] Step 309: The UPF installs the updated PFCP rules received from the SMF, uses these PFCP rules to filter uplink / downlink traffic, and performs the necessary forwarding actions, QoS control, usage reporting, etc.

[0107] In one embodiment, if the UPF receives a PFCP rule with flexible QoS control information, the UPF implements / applies the corresponding flexible QoS control to the uplink / downlink traffic. In one embodiment, if a subordinate PDR / QER is assigned to a QoS flow along with a general / default PDR / QES for that QoS flow, the UPF detects internal flows / movements within the QoS flow according to the instructions of the subordinate PDR. If an internal flow / movement is detected, the UPF performs QoS control on the internal flow / movement according to the instructions of the associated subordinate QER. For example, the UPF performs QoS control on the guaranteed flow bit rate and maximum flow bit rate in the uplink / downlink direction.

[0108] As an alternative or supplement, if the QER rule associated with a QoS flow is configured with a subordinate protocol description and a subordinate QoS parameter set, the UPF detects internal flows / movements within the QoS flow according to the instructions in the subordinate protocol description. If an internal flow / movement is detected, the UPF performs QoS control on the internal flow / movement according to the instructions in the subordinate QoS parameter set.

[0109] In one embodiment, regardless of the method used by the UPF to detect internal flows, if only one internal flow is detected at a time or only one primary internal flow is detected, then the QoS control applied in this case implies on-demand flexible QoS requirements applied to that QoS flow.

[0110] Step 310 (AMF to RAN): The AMF transmits an N2 PDU session request (e.g., N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session modification command)) to the RAN. The AMF sends a NAS message to the RAN, which contains the PDU session ID and PDU session modification command for the UE, as well as the N2 SM message received from the SMF in the N2 PDU session request.

[0111] In step 310, if the flexible QoS profile is configured for a specific QoS flow, the RAN stores the flexible QoS profile and performs flexible QoS control on that QoS flow (typically mapped to a specific DRB (Data Radio Bearer)).

[0112] In one embodiment, if a QoS flow is configured with a list of subordinate protocol descriptions and a list of subordinate QoS parameter sets, the RAN detects internal flows / movements within the QoS flow according to the instructions in the subordinate protocol descriptions. If an internal flow / movement is detected, the RAN performs QoS control on the internal flow / movement according to the instructions in the subordinate QoS parameter sets.

[0113] Step 311 (RAN to UE): The RAN may exchange AN-specific signaling with the UE related to the information received from the SMF.

[0114] Step 312 (RAN to AMF): The RAN transmits the N2 PDU session response to the AMF (e.g., PDU session ID, reason, N2SM information (PDU session ID, AN channel information, list of accepted / rejected QFIs).

[0115] Step 313 (AMF to SMF): AMF transmits an Nsmf_PDUSession_UpdateSMContext request (e.g., N2 SM information) to SMF.

[0116] In step 313, the AMF forwards the N2 SM information received from the RAN to the SMF. If the list of rejected QFIs is included in the N2 SM information, the SMF releases the QoS profile associated with the rejected QFI.

[0117] Step 314: The SMF and UPF initiate the N4 session modification process. The SMF provides the UPF with RAN channel information and corresponding forwarding rules.

[0118] Step 315: SMF sends an Nsmf_PDUSession_UpdateSMContext response to AMF.

[0119] Flexible strategy decision-making for PCF based on SMF traffic detection reports In one embodiment, the PCF can make flexible policy decisions not only based on instructions received from the application layer (e.g., AF / AS) but also based on service information or traffic characteristics reported from the SMF. For example, if QUIC is used as the transport protocol, the UPF can detect certain service information, which may be presented as traffic characteristics in the QUIC packet header. This service information or traffic characteristics are reported from the UPF to the SMF and further forwarded to the PCF. Therefore, based on the forwarded service information or traffic characteristics, the PCF can make flexible policy decisions in an appropriate manner.

[0120] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Specifically, Figure 4 The process shown includes the following steps: Step 401: The UE requests the network to establish a PDU session.

[0121] Step 402: The UE initiates a QUIC connection establishment with a remote server (such as AF / AS).

[0122] Step 403: The UE initiates uplink data transmission or receives downlink data transmission from the application layer (such as AS).

[0123] Step 404: The UPF can be instructed to detect and report traffic characteristic information, for example, according to the instructions of the PFCP rules downloaded from the SMF in step 401.

[0124] In one embodiment, the SMF requests / demands the UPF to detect and report the traffic characteristics of QUIC traffic. The UPF performs QUIC traffic detection, collects the traffic characteristics of QUIC traffic, and reports the collected traffic characteristic information to the SMF.

[0125] Step 405: The UPF sends a PFCP session report request carrying traffic characteristic information to the SMF.

[0126] In step 405, the traffic characteristic information indicates QUIC traffic characteristics, which include a combination of at least one of the following: source IP address, destination IP address, source UDP port, destination UDP port, or QUIC connection ID.

[0127] In one embodiment, if the UPF detects that the QUIC packet header includes service disclosure information for an internal flow / current, this service disclosure information for the internal flow / current can also be included in the QUIC traffic information. For example, the service disclosure information for an internal flow / current carried in the QUIC packet header may affect the QoS requirements of the internal flow / current.

[0128] Step 406: SMF sends a PFCP session report response to UPF.

[0129] Step 407: The SMF sends an SM policy update (e.g., Npcf_SMPolicyControl_Update) request to the PCF, carrying traffic characteristic information. The SMF responds to the PCF request with an SM policy update notification (e.g., Npcf_SMPolicyControl_UpdateNotify) to acknowledge the PCF request.

[0130] Step 408: The PCF acknowledges the SMF request by sending an SM policy update (e.g., Npcf_SMPolicyControl_Update) response to the SMF, which contains updated policy information (e.g., PCC rules, QoS profiles, etc.).

[0131] In step 408, the PCF provides a flexible QoS profile in its response message to the SMF, such as... Figure 3 PCF in steps 304 and 305 shown.

[0132] Steps 409 to 418 are similar Figure 3 Steps 306 to 315 in the process. Specifically, the SMF generates updated PFCP rules to instruct the UPF to perform flexible QoS control, and updates the QoS flow profile to instruct the RAN to perform flexible QoS control.

[0133] QUIC packet headers expose internal / flowing service information. Figure 5 A schematic diagram of a QUIC packet header according to an embodiment of the present disclosure is shown. For example, Figure 5 The QUIC packet header shown can be a QUIC short header. The QUIC packet header can be configured to expose the internal flow / flow service information encapsulated in the QUIC packet of the QUIC connection.

[0134] like Figure 5 As shown, the QUIC packet header carries additional information including unencrypted Service Exposure Information (SEI). The SEI is used to expose service information for internal flows / currents within the QUIC traffic belonging to the corresponding QUIC connection. In one embodiment, the SEI may include at least one of the following: - The number of SELs (Service Exposure EL Elements), or - SEL list.

[0135] The number of SELs (e.g., Figure 5The SEL count shown is used / configured to indicate the total number of SELs in the following SEL list. Based on the SEL count, the network node can calculate the overall size of the SEI IE (Information Element). Following the SEL count IE, the SEL list consists of a list of SELs, each SEL used / configured to indicate information about a service flow within an internal flow / flow of a QUIC packet.

[0136] In one embodiment, SEL can be set to one of the following values: (a) The required QoS level, indicating the specific level of QoS requirements. The QoS level value may be defined in a standardized manner (e.g., using QFI or ARP values ​​defined by 3GPP) or in a manner determined by the operator; or (b) The type of service flow, such as low-capacity low-latency service, low-capacity high-latency service, high-capacity low-latency service, high-capacity high-latency service, etc.

[0137] In one embodiment, the SEI carried in the QUIC packet header exposes internal flow / flow (important) service information to any intermediate nodes in the transmission path, and these nodes can use it to determine appropriate policies to control QUIC traffic transmission (e.g., determine appropriate QoS policies for QUIC traffic transmission).

[0138] In one embodiment, the QUIC connection endpoint (e.g., the UE and / or remote AS / AF) naturally knows the content of the streams / flows encapsulated in its transmitted QUIC packets. Therefore, the QUIC connection endpoint can populate the QUIC packet header with an appropriate SEI (e.g., listing the SEL for each internal stream / flow). Since the encapsulation of different streams / flows within a QUIC packet dynamically changes according to current service requirements, the SEI carried in the QUIC packet header also dynamically changes based on the inclusion of internal streams / flows.

[0139] By using Figure 5 As shown in the QUIC packet header, the UPF can detect the SEI indicated / included in the QUIC packet header and report the detected SEI to the SMF accordingly. The SMF can forward the reported SEI to the PCF, allowing the PCF to set appropriate QoS policies for the corresponding QUIC traffic.

[0140] In some embodiments, a method for determining a flexible QoS profile is disclosed. This method can be used in PCF and includes: Determine a flexible QoS profile for a QoS flow applied to a PDU session; and Send the flexible QoS profiles included in the SM policy to the SMF.

[0141] In one embodiment, a flexible QoS profile applied to a QoS flow includes indications of the flexible QoS requirements.

[0142] In one embodiment, a flexible QoS profile applied to a QoS flow indicates a list of subordinate QoS parameter sets.

[0143] In one embodiment, a flexible QoS profile applied to a QoS flow is associated with a list of subordinate protocol descriptions.

[0144] In one embodiment, a subordinate protocol description indicates the conditions under which a subordinate QoS parameter set is applied.

[0145] In one embodiment, a subordinate QoS parameter set includes a combination or at least one of the following: guaranteed stream bit rate, maximum stream bit rate, and (maximum) packet loss rate.

[0146] In one embodiment, a subordinate protocol description includes a combination or at least one of the following information: transport protocol, IP address, port, QUIC connection identifier, internal stream / flow application protocol information, average size of a datagram, average number of packets in a burst data transmission, maximum overall size of datagrams in a burst data transmission, and average interval between two (consecutive / adjacent) burst data transmissions.

[0147] In one embodiment, the PCF determines a flexible QoS profile based on one of the following inputs: service information configured by the AF (e.g., see...). Figure 3 ) or traffic characteristic information reported by SMF (e.g. Figure 4 ).

[0148] In some embodiments, a flexible QoS enforcement method is disclosed. This method can be used in SMF and includes: Receive a flexible QoS profile from the PCF that is applied to a QoS flow; Generate updated PFCP rules that include flexible QoS control information; and Send the updated PFCP rules to UPF.

[0149] In one embodiment, a flexible QoS profile applied to a QoS flow includes a flexible QoS requirement indication.

[0150] In one embodiment, a flexible QoS profile applied to a QoS flow indicates a list of subordinate QoS parameter sets.

[0151] In one embodiment, a flexible QoS profile applied to a QoS flow is associated with a list of subordinate protocol descriptions.

[0152] In one embodiment, a subordinate protocol description indicates the conditions under which a subordinate QoS parameter set is applied.

[0153] In one embodiment, a subordinate QoS parameter set includes a combination or at least one of the following: guaranteed stream bit rate, maximum stream bit rate, and (maximum) packet loss rate.

[0154] In one embodiment, a subordinate protocol description includes a combination or at least one of the following information: transport protocol, IP address, port, QUIC connection identifier, internal stream / flow application protocol information, average size of a datagram, average number of datagrams in a burst data transmission, maximum overall size of datagrams in a burst data transmission, and average interval between two (consecutive / continuous) burst data transmissions.

[0155] In one embodiment, the PFCP rule with flexible QoS control information indicates a list of subordinate PDRs and a list of subordinate QERs.

[0156] In one embodiment, a subordinate PDR is mapped from a subordinate protocol description, and a subordinate QER is mapped from a subordinate QoS parameter set.

[0157] In one embodiment, a PFCP rule with flexible QoS control information indicates a QER with a list of subordinate protocol descriptions and a list of subordinate QoS parameter sets.

[0158] In some embodiments, a flexible QoS enforcement method is disclosed. This method can be used in UPF and includes: PFCP rules that receive flexible QoS control information from the SMF; and Flexible QoS control is applied based on instructions / instructions from flexible QoS control information.

[0159] In one embodiment, PFCP rules with flexible QoS control information indicate a list of subordinate PDRs and a list of subordinate QERs.

[0160] In one embodiment, a subordinate PDR is mapped from a subordinate protocol description, and a subordinate QER is mapped from a subordinate QoS parameter set.

[0161] In one embodiment, applying flexible QoS control based on instructions / instructions of flexible QoS control information further includes: enforcing / implementing / executing / applying corresponding flexible QoS control to uplink / downlink traffic based on subordinate PDRs and subordinate QERs.

[0162] In one embodiment, a PFCP rule with flexible QoS control information indicates a QER with a list of subordinate protocol descriptions and a list of subordinate QoS parameter sets.

[0163] In one embodiment, applying flexible QoS control according to the instructions / instructions of the flexible QoS control information further includes: enforcing / implementing / executing / applying corresponding flexible QoS control to uplink / downlink traffic according to the subordinate protocol description and subordinate QoS parameter set indicated in the QER.

[0164] In one embodiment, a subordinate protocol description indicates the conditions under which a subordinate QoS parameter set is applied.

[0165] In one embodiment, a subordinate QoS parameter set includes a combination or at least one of the following: guaranteed stream bit rate, maximum stream bit rate, and (maximum) packet loss rate.

[0166] In one embodiment, a subordinate protocol description includes a combination or at least one of the following information: transport protocol, IP address, port, QUIC connection identifier, internal stream / flow application protocol information, average size of a datagram, average number of datagrams in a burst data transmission, maximum overall size of datagrams in a burst data transmission, and average interval between two (consecutive / adjacent) burst data transmissions.

[0167] Figure 6 This is a schematic diagram relating to a wireless terminal 60 according to an embodiment of the present disclosure. The wireless terminal 60 may be a user equipment (UE), mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, and is not limited thereto. The wireless terminal 60 may include a processor 600 such as a microprocessor or application-specific integrated circuit (ASIC), a storage unit 610, and a communication unit 620. The storage unit 610 may be any data storage device storing program code 612 accessed and executed by the processor 600. Embodiments of the storage unit 610 include, but are not limited to, a user identification module (SIM), read-only memory (ROM), flash memory, random access memory (RAM), hard disk, and optical data storage devices. The communication unit 620 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of the processor 600. In one embodiment, the communication unit 620 is connected via... Figure 6 At least one antenna 622 shown transmits and receives signals.

[0168] In one embodiment, the storage unit 610 and the program code 612 may be omitted, and the processor 600 may include a storage unit containing the stored program code.

[0169] The processor 600 can implement any of the steps in the exemplary embodiments on the wireless terminal 60, for example, by executing program code 612.

[0170] The communication unit 620 may be a transceiver. Alternatively or as a supplement, the communication unit 620 may be combined with a transmission unit and a receiving unit configured to transmit signals to and receive signals from a wireless network node (e.g., a base station), respectively.

[0171] Figure 7 This diagram relates to a wireless network node 70 according to an embodiment of the present disclosure. The wireless network node 70 may be a satellite, base station (BS), network entity, mobility management entity (MME), serving gateway (S-GW), packet data network (PDN) gateway (P-GW), radio access network (RAN) node, next-generation RAN (NG-RAN) node, gNB, eNB, gNB central unit (gNBCU), gNB distributed unit (gNB-DU), data network, core network, or radio network controller (RNC), and is not limited thereto. Furthermore, the wireless network node 70 may include (execute) at least one network function, such as access and mobility management function (AMF), session management function (SMF), user location function (UPF), policy control function (PCF), application function (AF), etc. The wireless network node 70 may include a processor 700 such as a microprocessor or ASIC, a storage unit 710, and a communication unit 720. The storage unit 710 may be any data storage device storing program code 712 accessed and executed by the processor 700. Examples of storage units 710 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. The communication unit 720 can be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of the processor 700. In one example, the communication unit 720 is connected via... Figure 7 At least one antenna 722 shown transmits and receives signals.

[0172] In one embodiment, the storage unit 710 and the program code 712 may be omitted. The processor 700 may include a storage unit containing stored program code.

[0173] The processor 700 can implement any of the steps described in the exemplary embodiments on the wireless network node 70, for example, via executing program code 712.

[0174] The communication unit 720 may be a transceiver. Alternatively or as a supplement, the communication unit 720 may be combined with a transmitting unit and a receiving unit configured to transmit signals to and receive signals from a wireless terminal (e.g., a user equipment or another wireless network node).

[0175] Figure 8 A flowchart of a method according to an embodiment of this disclosure is shown. Figure 8The method shown can be used with PCF (e.g., wireless devices that include PCF) and includes the following steps: Step 801: Determine the flexible QoS profile for the QoS flow.

[0176] Step 802: Transmit the flexible QoS profile of the QoS stream to the SMF.

[0177] exist Figure 8 In this process, the PCF determines a flexible QoS profile for the QoS flow and transmits the determined flexible QoS profile to the SMF of the QoS flow. In one embodiment, the flexible QoS profile includes a default QoS parameter set for the QoS flow and / or subordinate QoS information of at least one subordinate QoS parameter set for at least one internal flow in the QoS flow. In this embodiment, different QoS parameters can be applied to the internal flows in the QoS flow to meet the different QoS requirements of different types of internal flows in the QoS flow.

[0178] In one embodiment, the dependent QoS information includes at least one set of dependent QoS parameters configured to be applied to at least one internal flow in the QoS flow, or at least one dependent protocol description indicating the traffic characteristics of at least one internal flow in the QoS flow. For example, at least one dependent protocol description is configured to indicate conditions for applying at least one set of dependent QoS parameters to at least one internal flow in the QoS flow identified by at least one dependent protocol description.

[0179] In one embodiment, each subordinate protocol description may include at least one of the following: The transport protocol of the corresponding internal stream in the QoS stream. At least one Internet Protocol address of the corresponding internal flow in the QoS flow. At least one transmission port of the corresponding internal flow in the QoS flow. At least one QUIC connection identifier for the corresponding internal flow in the QoS flow. Application protocol information of the corresponding internal flow in the QoS flow. The average size of datagrams during a single burst transmission of the corresponding internal flow within a QoS flow. The average number of datagrams transmitted in a single burst of data transmission within a corresponding internal flow in a QoS flow. The maximum total size of datagrams in a single burst transmission of the corresponding internal flow within a QoS flow, or The average interval between two adjacent / continuous burst data transmissions within a corresponding internal flow in a QoS flow.

[0180] In one embodiment, each subordinate QoS parameter set includes at least one of a guaranteed stream bit rate, a maximum stream bit rate, or a maximum packet loss rate.

[0181] In one embodiment, the flexible QoS profile includes a flexible QoS requirement indication for applying a set of subordinate QoS parameters to an internal flow within the QoS flow.

[0182] In one embodiment, the QoS stream is mapped to a service data stream or a QUIC connection.

[0183] In one embodiment, a QoS flow includes multiple internal flows with different QoS requirements and / or corresponding to different QoS parameters. For example, the internal flows in a QoS flow may carry different types of data (e.g., video, audio, haptic feedback, etc.).

[0184] In one embodiment, the PCF can receive flexible service information for service data streams from the AF. In this embodiment, the PCF determines a flexible QoS profile based on the received flexible service information. Further details of this embodiment can be found in [reference needed]. Figure 3 The illustrated embodiment. For example, flexible service information includes at least one of the following: a default QoS requirement for a service data flow, at least one subordinate QoS requirement for at least one internal flow in the service data flow, or at least one subordinate protocol description indicating the characteristics of at least one internal flow in the service data flow. The at least one subordinate protocol description can be configured to indicate the conditions for applying at least one subordinate QoS requirement to at least one internal flow in the QoS flow.

[0185] In one embodiment, the PCF receives QUIC traffic characteristic information of a QoS flow from the SMF. In this embodiment, the PCF determines a flexible QoS profile based on the received QUIC traffic characteristic information. For example, the QUIC traffic characteristic information includes at least one of the following: source IP address, destination IP address, source UDP port, destination UDP port, QUIC connection identifier, or service disclosure information for at least one internal flow within the QoS flow. In one embodiment, the service disclosure information indicates at least one QoS requirement for at least one internal flow within the QoS flow. Further details of this embodiment can be found in [reference needed]. Figure 4 Details.

[0186] Figure 9 A flowchart of a method according to an embodiment of this disclosure is shown. Figure 9 The method shown can be used in SMF or wireless devices that include SMF, and includes the following steps: Step 901: Receive the flexible QoS profile of the QoS stream from the PCF.

[0187] Step 902: Generate at least one updated PFCP rule based on the flexible QoS profile, wherein the at least one updated PFCP rule includes flexible QoS information for the QoS flow.

[0188] Step 903: Transmit at least one updated PFCP rule, including flexible QoS information, to the UPF.

[0189] exist Figure 9 In this process, the SMF receives flexible QoS profiles for QoS flows from the PCF. Based on the flexible QoS profiles, the SMF generates updated PFCP rules that include flexible QoS information for the QoS flows. The updated PFCP rules are then transmitted to the UPF to apply them to the QoS flows.

[0190] The contents of the flexible QoS configuration file can be referenced from the above embodiments.

[0191] In one embodiment, the SMF transmits QUIC traffic characteristic information of QoS flows to the PCF, where the QUIC traffic characteristic information serves as the basis for determining a flexible QoS profile. The QUIC traffic characteristic information of QoS flows can be obtained from the UPF. In one embodiment, the PFCP rules transmitted to the UPF include subordinate QERs and subordinate PDRs. In this embodiment, the SMF can generate subordinate QERs by mapping subordinate QoS parameter sets to subordinate QERs. Similarly, the SMF can generate subordinate PDRs by mapping subordinate protocol descriptions to subordinate PDRs. In one embodiment, the PFCP rules transmitted to the UPF may include a subordinate QER, which includes a subordinate QoS parameter set and a subordinate protocol description.

[0192] Figure 10 A flowchart of a method according to an embodiment of this disclosure is shown. Figure 10 The method shown can be used in a UPF or a wireless device that includes a UPF, and includes the following steps: Step 1001: Receive at least one updated PFCP rule from the SMF, which includes flexible QoS information for the QoS flow, and Step 1002: Apply at least one updated PFCP rule, including flexible QoS information, to the QoS flow.

[0193] exist Figure 10 In the process, the UPF receives updated PFCP rules that include flexible QoS information for QoS flows and applies the received PFCP rules to the QoS flows. Based on the flexible QoS information, the UPF can perform flexible QoS control based on the differentiated QoS requirements of internal flows within the QoS flows.

[0194] PFCP rules received from SMF can be used with Figure 9 The rules are the same in the embodiments.

[0195] In one embodiment of the PFCP rule with subordinate QERs and subordinate PDRs, the UPF performs flexible QoS control on the (uplink / downlink) traffic of the QoS flow based on the subordinate QERs and subordinate PDRs. Further details can be found in the embodiment of step 306.

[0196] In one embodiment of a PFCP rule with a QER, the QER includes a subordinate QoS parameter set and a subordinate protocol description. The UPF performs flexible QoS control on the (uplink / downlink) traffic of the QoS flow based on the subordinate QoS parameter set and the subordinate protocol description. Further details can be found in the embodiment of step 306.

[0197] In this disclosure, the subordinate QoS parameter set may refer to subordinate QoS parameters.

[0198] In this disclosure, a wireless device including an NF means a wireless device that performs at least some of the functions of an NF.

[0199] While various embodiments of this disclosure have been described above, it should be understood that they are by way of example only and not as limiting. Similarly, various accompanying drawings may depict exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0200] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names can be used as a convenient means of distinguishing two or more elements or instances of elements in this document. Therefore, mentioning the first and second elements does not imply that only two elements can be used, nor does it imply that the first element must precede the second element in some way.

[0201] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0202] Those skilled in the art will further understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software unit" for convenience), or any combination of these technologies.

[0203] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have been generally described above according to their functions. Whether this function is implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more functions described herein. The term "configured as" or "configured for" as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc., physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0204] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, cells, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, cells, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but may also be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0205] Computer-readable media include computer storage media and communication media, including any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various units are described as discrete units; however, as will be apparent to those skilled in the art, two or more units may be combined to form a single unit performing the relevant functions according to embodiments of this disclosure.

[0206] Furthermore, memory or other memory and communication components may be employed in the embodiments of this disclosure. It should be understood that, for clarity, the foregoing description has referenced various functional units and processors in the embodiments of this disclosure. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without diminishing the scope of this disclosure. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic unit or controller. Therefore, references to specific functional units are merely references to suitable means of providing said functionality and not indications of a strict logical or physical structure or organization.

[0207] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method for a policy control function, the method comprising: determining a flexible quality of service (QoS) profile of a QoS flow, and transmitting the flexible QoS profile of the QoS flow to a session management function (SMF), wherein the flexible QoS profile comprises a default QoS parameter set of the QoS flow and subordinate QoS information of at least one subordinate QoS parameter set of at least one inner flow of the QoS flow.

2. The wireless communication method according to claim 1, wherein, the subordinate QoS information comprises at least one of: at least one subordinate QoS parameter set configured to be applied to the at least one inner flow of the QoS flow, or at least one subordinate protocol description indicating traffic characteristics of the at least one inner flow of the QoS flow to indicate a condition for applying the at least one subordinate QoS parameter set to the at least one inner flow of the QoS flow.

3. The wireless communication method according to claim 2, wherein, each subordinate protocol description comprises at least one of the following information of at least one corresponding inner flow of the QoS flow: a transport protocol, at least one internet protocol address, at least one transport port, at least one QUIC connection identifier, application protocol information, an average size of datagrams in a burst data transmission, an average number of datagrams in a burst data transmission, a maximum aggregate size of datagrams in a burst data transmission, or an average interval between two consecutive burst data transmissions.

4. The wireless communication method according to any one of claims 1 to 3, wherein, each subordinate QoS parameter set comprises at least one of: a guaranteed flow bit rate, a maximum flow bit rate, or a maximum packet loss rate.

5. The wireless communication method according to any one of claims 1 to 4, wherein, the flexible QoS profile comprises an indication required for applying the at least one subordinate QoS parameter set to the at least one inner flow of the QoS flow.

6. The wireless communication method according to any one of claims 1 to 5, wherein, the QoS flow is mapped to a service data flow or bound to a QUIC connection.

7. The wireless communication method according to any one of claims 1 to 6, wherein, the QoS flow comprises a plurality of inner flows having different QoS requirements and / or corresponding to different QoS parameters. 8.The wireless communication method of any one of claims 1 to 7, further comprising: receiving flexible service information of a service data flow from an application function, wherein the flexible QoS profile is determined based on the flexible service information.

9. The wireless communication method according to claim 7, wherein, the flexible service information comprises at least one of: a default QoS requirement of the service data flow, at least one subordinate QoS requirement of at least one inner flow of the service data flow; or at least one subordinate protocol description indicating characteristics of the at least one inner flow of the service data flow to indicate a condition for applying the at least one subordinate QoS requirement to the at least one inner flow of the QoS flow. each subordinate protocol description comprises at least one of the following information of at least one corresponding inner flow of the QoS flow:

10. The wireless communication method according to claim 10, wherein, a transport protocol, at least one internet, at least one transport port, at least one QUIC connection identifier, application protocol information, an average size of datagrams in a burst data transmission, an average number of datagrams in a burst data transmission, a maximum aggregate size of datagrams in a burst data transmission, or an average interval between two consecutive burst data transmissions. ​ 11. The wireless communication method of any one of claims 1-7, further comprising: receiving, from a SMF, QUIC traffic characteristic information of the QoS flow, wherein the flexible QoS profile is determined based on the QUIC traffic characteristic information.

12. The wireless communication method according to claim 11, wherein, The QUIC traffic characteristic information comprises at least one of: a source internet protocol address, a target internet protocol address, a source user datagram protocol (UDP) port, a target UDP port, at least one QUIC connection identifier, or service exposure information of at least one inner flow of the QoS flow, wherein the service exposure information indicates at least one QoS requirement of the at least one inner flow of the QoS flow.

13. A wireless communication method for a session management function (SMF), the method comprising: receiving, from a policy control function (PCF), a flexible quality of service (QoS) profile of a QoS flow, generating at least one updated packet forwarding control protocol (PFCP) rule based on the flexible QoS profile, wherein the at least one updated PFCP rule comprises flexible QoS information of the QoS flow; and transmitting, to a user plane function (UPF), the at least one updated PFCP rule comprising the flexible QoS information, wherein the flexible QoS profile comprises a default QoS parameter set of the QoS flow and subordinate QoS information of at least one subordinate QoS parameter set of at least one inner flow of the QoS flow.

14. The wireless communication method of claim 13, wherein, The subordinate QoS information comprises at least one of: at least one subordinate QoS parameter set configured to be applied to the at least one inner flow of the QoS flow, or at least one subordinate protocol description indicating at least one traffic characteristic of the at least one inner flow of the QoS flow to indicate a condition for applying the at least one subordinate QoS parameter set to the at least one inner flow of the QoS flow.

15. The wireless communication method according to claim 14, wherein, Each subordinate protocol description comprises at least one of the following information of at least one corresponding inner flow: a transport protocol, at least one internet protocol address, at least one transport port, at least one QUIC connection identifier, application protocol information, an average size of datagrams in a one-time burst data transmission, an average number of datagrams in a one-time burst data transmission, a maximum aggregate size of datagrams in a one-time burst data transmission, or an average interval between two consecutive burst data transmissions.

16. The wireless communication method according to any one of claims 13 to 15, wherein, Each subordinate QoS parameter set comprises at least one of: a guaranteed flow bit rate, a maximum flow bit rate, or a maximum packet loss rate.

17. The wireless communication method according to any one of claims 13 to 16, wherein, The flexible QoS profile comprises an indication required for applying the at least one subordinate QoS parameter set to the at least one inner flow of the QoS flow.

18. The wireless communication method according to any one of claims 13 to 17, wherein, The QoS flow is mapped to a service data flow or bound to a quick user datagram protocol (UDP) internet connections (QUIC) connection.

19. The wireless communication method according to any one of claims 13 to 18, wherein, The QoS flow comprises a plurality of inner flows having different QoS requirements and / or corresponding to different QoS parameters.

20. The wireless communication method of any one of claims 13-19, further comprising: transmitting, to a PCF, QUIC traffic characteristic information of the QoS flow, wherein the flexible QoS profile is determined based on the traffic characteristic information.

21. The wireless communication method of claim 20, wherein, The QUIC traffic characteristic information comprises at least one of: a source Internet Protocol address, a destination Internet Protocol address, a source User Datagram Protocol (UDP) port, a destination UDP port, at least one QUIC connection identifier, or service exposure information of at least one inner flow in the QoS flow, wherein the service exposure information indicates at least one QoS requirement of the at least one inner flow in the QoS flow.

22. The wireless communication method of claim 20 or 21, further comprising: receiving, from a UPF, QUIC traffic characteristic information of the QoS flow.

23. The wireless communication method according to any one of claims 13 to 22, wherein, The at least one PFCP rule comprising the flexible QoS information comprises: at least one subordinate QoS enforcement rule associated with at least one subordinate QoS parameter set of at least one inner flow in the QoS flow, and at least one subordinate packet detection rule mapped from at least one subordinate protocol description indicating at least one traffic characteristic of the at least one inner flow in the QoS flow.

24. The wireless communication method according to any one of claims 13 to 22, wherein, The at least one PFCP rule comprising the flexible QoS information comprises: at least one QoS enforcement rule associated with: at least one subordinate QoS parameter set of at least one inner flow in the QoS flow, and at least one subordinate protocol description indicating at least one traffic characteristic of the at least one inner flow in the QoS flow.

25. A wireless communication method for a user plane function, the method comprising: receiving, from a session management function (SMF), at least one updated PFCP rule comprising flexible quality of service (QoS) information of a QoS flow, and applying, to the QoS flow, at least one updated PFCP rule comprising the flexible QoS information.

26. The wireless communication method of claim 25, wherein, The at least one PFCP rule comprising the flexible QoS information comprises: at least one subordinate QoS enforcement rule associated with at least one subordinate QoS parameter set of at least one inner flow in the QoS flow, and at least one subordinate packet detection rule mapped from at least one subordinate protocol description indicating at least one traffic characteristic of the at least one inner flow in the QoS flow.

27. The wireless communication method of claim 26, wherein, Applying, to the QoS flow, at least one updated PFCP rule comprising the flexible QoS information comprises: performing, based on the at least one QoS enforcement rule and the at least one subordinate packet detection rule, flexible QoS control on traffic of the QoS flow.

28. The wireless communication method of claim 25, wherein, The at least one PFCP rule comprising the flexible QoS information comprises: at least one QoS enforcement rule associated with: at least one subordinate QoS parameter set of at least one inner flow in the QoS flow, and at least one subordinate protocol description indicating at least one traffic characteristic of the at least one inner flow in the QoS flow.

29. The wireless communication method of claim 28, wherein, Applying, to the QoS flow, at least one updated PFCP rule comprising the flexible QoS information comprises: performing flexible QoS control on traffic of the QoS flow based on at least one dependent protocol description and at least one dependent QoS parameter set.

30. The wireless communication method of any one of claims 26 to 29, wherein, Each dependent protocol description comprises at least one of the following information for at least one corresponding inner flow: a transport protocol, at least one internet protocol address, at least one transport port, at least one QUIC connection identifier, application protocol information, an average size of datagrams in one burst of data transmission, an average number of datagrams in one burst of data transmission, a maximum aggregate size of datagrams in one burst of data transmission, or an average interval between two consecutive bursts of data transmission.

31. The wireless communication method of any one of claims 26 to 30, wherein, Each dependent QoS parameter set comprises at least one of: a guaranteed flow bit rate, a maximum flow bit rate, or a maximum packet loss rate.

32. The wireless communication method of any one of claims 25 to 31, further comprising: transmitting, to a SMF, QUIC traffic characteristic information of the QoS flow.

33. The wireless communication method of claim 32, wherein, The QUIC traffic characteristic information comprises at least one of: a source internet protocol address, a target internet protocol address, a source user datagram protocol (UDP) port, a target UDP port, at least one QUIC connection identifier, or service exposure information of at least one inner flow in the QoS flow, wherein the service exposure information indicates at least one QoS requirement of the at least one inner flow in the QoS flow.

34. A wireless device comprising a policy control function, the wireless device comprising: a processor configured to determine a flexible quality of service (QoS) profile of a QoS flow; and a communication unit configured to transmit the flexible QoS profile of the QoS flow to a session management function (SMF), wherein the flexible QoS profile comprises a default QoS parameter set of the QoS flow and dependent QoS information of at least one dependent QoS parameter set of at least one inner flow in the QoS flow. The processor is further configured to perform the wireless communication method of any one of claims 2 to 12.

35. The wireless device of claim 34, wherein, 36. A wireless device comprising a session management function, the wireless device comprising: a communication unit configured to receive, from a policy control function (PCF), a flexible quality of service (QoS) profile of a QoS flow; a processor configured to generate at least one updated packet forwarding control protocol (PFCP) rule based on the flexible QoS profile, wherein the at least one updated PFCP rule comprises flexible QoS information of the QoS flow, wherein the communication unit is further configured to transmit the at least one updated PFCP rule comprising the flexible QoS information to a user plane function (UPF), wherein the flexible QoS profile comprises a default QoS parameter set of the QoS flow and dependent QoS information of at least one dependent QoS parameter set of at least one inner flow in the QoS flow. The processor is further configured to perform the wireless communication method of any one of claims 14 to 24.

38. A wireless device comprising a user plane function, the wireless device comprising:

37. The wireless device of claim 36, wherein, ​ ​ a communication unit configured to receive at least one updated PFCP rule from a session management function (SMF), the rule including flexible quality of service (QoS) information for a QoS flow, and a processor configured to apply the at least one updated PFCP rule including the flexible QoS information to the QoS flow.

39. The wireless device of claim 38, wherein, the processor is further configured to perform the wireless communication method according to any one of claims 26-33.

40. A computer program product comprising a computer readable program medium code stored thereon, which when executed by a processor, causes the processor to implement the wireless communication method according to any one of claims 1-33.

Images