Policy Extension for Quick User Datagram Protocol International Connection Application

Abstract

A wireless communication method for use in a session management function is disclosed. The method includes transmitting, to a user plane function, a Quick User Datagram Protocol Internet Connections (QUIC) traffic instruction, and receiving, from the user plane function, at least one QUIC report associated with the QUIC traffic, wherein the QUIC traffic instruction includes at least one of a QUIC event report instruction that instructs at least one event associated with the at least one QUIC report, or a QUIC statistical value report instruction that instructs at least one statistical value included in each QUIC report.

Description

Technical Field

[0001] This document generally relates to wireless communication, and in particular, to QUIC (Quick User Datagram Protocol (UDP) International Connection) communication.

Background Art

[0002] In recent years, the QUIC protocol for establishing international connections between two endpoints has been rapidly evolving. It is regarded as the next-generation protocol used for HTTP (Hypertext Transfer Protocol). That is, the existing TCP (Transmission Control Protocol) + TLS (Transport Layer Security) + HTTP protocol may be replaced using the QUIC protocol.

[0003] One QUIC connection is a secure connection between two endpoints (e.g., between a UE (User Equipment) and the UE's application server) that disables the inspection of the content transmitted in the QUIC connection by a transmitting node within the network.

[0004] Currently, the 5G packet detection and forwarding model can only detect QUIC traffic from other TCP / UDP traffic. It is difficult for the network to recognize which service or application the QUIC traffic is related to. Therefore, it may be impossible to generate an appropriate policy applied to the corresponding QUIC traffic.

[0005] Furthermore, since current QoS flow control typically provides fixed AMBR (Average Maximum Bit Rate) values and fixed GBR (Guaranteed Bit Rate) values for QoS (Quality-of-Service) flows, and since QUIC data transmission is encrypted and the internal payloads within QUIC packets can have significantly different QoS requirements, flexible QoS requirements for QUIC traffic transmission may not be possible.

[0006] This document relates to methods, systems, and devices for QUIC communication, and in particular, to methods, systems, and devices associated with policies for QUIC applications. SUMMARY OF THE INVENTION MEANS FOR SOLVING THE PROBLEM

[0007] The present disclosure relates to a wireless communication method used for a session management function. The method includes sending a Quick User Datagram Protocol Internet Connections (QUIC) traffic instruction to a user plane function, and receiving at least one QUIC report associated with the QUIC traffic from the user plane function and includes The QUIC traffic instruction includes at least one of a QUIC event report instruction that indicates at least one event associated with at least one QUIC report, or a QUIC statistic report instruction that indicates at least one statistic value included in each QUIC report.

[0008] Various embodiments may preferably implement the following features: Preferably, at least one event associated with at least one QUIC report is Events associated with QUIC traffic detection, Events associated with QUIC connection establishment, Events associated with QUIC connection termination, Events associated with the start of QUIC data block transmission, or Events associated with the end of QUIC data block transmission including at least one of them.

[0009] Preferably, at least one statistical value included in each QUIC report is The average delay of QUIC traffic transmission, The maximum delay of QUIC traffic transmission, The minimum delay of QUIC traffic transmission, The average size of QUIC data blocks, The maximum size of QUIC data blocks, The minimum size of QUIC data blocks, the average interval between every two consecutive QUIC traffic transmissions, or The analysis period indicating the period during which the QUIC traffic characteristics used to determine each QUIC report are collected including at least one of them.

[0010] Preferably, each QUIC report includes at least one QUIC traffic parameter of QUIC traffic, at least one QUIC report event associated with the QUIC report, or at least one statistical value of QUIC traffic associated with the QUIC report including at least one of them.

[0011] Preferably, at least one QUIC traffic parameter is The QUIC protocol indication associated with QUIC traffic, The Internet Protocol (IP) address of a wireless terminal associated with QUIC traffic and the User Datagram Protocol (UDP) port associated with that wireless terminal, The IP address of a remote server associated with QUIC traffic and the UDP port associated with that remote server, At least one QUIC connection identifier of the QUIC traffic, The QUIC version of the QUIC traffic, or The packet number of the QUIC traffic including at least one of.

[0012] This disclosure relates to a wireless communication method for use in user plane functions. This method includes receiving, from a session management function, a Quick User Datagram Protocol Internet Connection (QUIC) traffic instruction, and transmitting, to the session management function, at least one QUIC report associated with the QUIC traffic including The QUIC traffic instruction includes at least one of a QUIC event report instruction that instructs at least one event associated with at least one QUIC report, or a QUIC statistic report instruction that instructs at least one statistic value included in each QUIC report.

[0013] Various embodiments may preferably implement the following features: Preferably, at least one event associated with at least one QUIC report is an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or Events associated with the end of QUIC data block transmission including at least one of them.

[0014] Preferably, at least one statistical value included in each QUIC report is the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between every two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which the QUIC traffic characteristics used to determine each QUIC report are collected including at least one of them.

[0015] Preferably, each QUIC report includes at least one QUIC traffic parameter of QUIC traffic, at least one QUIC report event associated with the QUIC report, or at least one statistical value of QUIC traffic associated with the QUIC report including at least one of them.

[0016] Preferably, at least one QUIC traffic parameter is the QUIC protocol indication associated with the QUIC traffic, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with that wireless terminal, the IP address of the remote server associated with the QUIC traffic and the UDP port associated with that remote server, At least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic includes at least one of them.

[0017] The present disclosure relates to a wireless communication method used for a session management function. This method includes transmitting information of Quick User Datagram Protocol Internet connection (QUIC) traffic to a policy control function, and receiving, from the policy control function, a policy and charging control (PCC) rule determined for a QUIC application based on the information of the QUIC traffic and the QUIC information includes at least one event associated with the information of the QUIC traffic and / or the statistics of the QUIC traffic.

[0018] Various embodiments may preferably implement the following features: Preferably, at least one event associated with at least one QUIC report is an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission includes at least one of them.

[0019] Preferably, at least one statistic included in each QUIC report is the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, The average size of the QUIC data block, the maximum size of the QUIC data block, the minimum size of the QUIC data block, the average interval between every two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which the QUIC traffic characteristics used to determine each QUIC report are collected includes at least one of them.

[0020] Preferably, the information of the QUIC traffic is the QUIC protocol indication associated with the QUIC traffic, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with that wireless terminal, the IP address of the remote server associated with the QUIC traffic and the UDP port associated with that remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic further includes at least one QUIC traffic parameter including at least one of them.

[0021] Preferably, the PCC rule includes QUIC application information, QUIC connection information, or at least one QUIC flow parameter includes at least one of them.

[0022] Preferably, the QUIC application information is the application identifier of the QUIC application, the application service type of the QUIC application, or the identifier of the wireless terminal associated with the QUIC application include at least one of them.

[0023] Preferably, the QUIC connection information is at least one QUIC connection identifier of the QUIC application, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC application and the UDP port associated with the wireless terminal, or the IP address of the remote server associated with the QUIC application and the UDP port associated with the remote server include at least one of them.

[0024] Preferably, at least one QUIC flow parameter is a Quality of Service (QoS) flow identifier, allocation and retention priority, Average Maximum Bit Rate (AMBR) or Guaranteed Bit Rate (GBR) include at least one of them.

[0025] Preferably, at least one QUIC flow parameter is the highest AMBR, the lowest AMBR, the highest GBR, or the lowest GBR include at least one of them.

[0026] Preferably, at least one QUIC flow parameter is a list of a QUIC packet number range and the AMBR corresponding to the QUIC packet number range, or a list of a QUIC packet number range and the GBR corresponding to the QUIC packet number range include at least one of them.

[0027] The present disclosure relates to a wireless communication method for use in a policy control function. The method is Receiving information on Quick User Datagram Protocol Internet connection (QUIC) traffic from a session management function, and sending, to the session management function, a policy and charging control (PCC) rule determined for a QUIC application based on the information on QUIC traffic including The QUIC information includes information on QUIC traffic and / or at least one event associated with a statistic of QUIC traffic.

[0028] Various embodiments may preferably implement the following features: Preferably, at least one event associated with at least one QUIC report is an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission including at least one of them.

[0029] Preferably, at least one statistic included in each QUIC report is the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of a QUIC data block, the maximum size of a QUIC data block, the minimum size of a QUIC data block, the average interval between every two consecutive QUIC traffic transmissions, or an analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected including at least one of them.

[0030] Preferably, the information of the QUIC traffic includes the QUIC protocol indication associated with the QUIC traffic, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of the remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic and further includes at least one QUIC traffic parameter including at least one of them.

[0031] Preferably, the PCC rule includes QUIC application information, QUIC connection information, or at least one QUIC flow parameter including at least one of them.

[0032] Preferably, the QUIC application information includes the application identifier of the QUIC application, the application service type of the QUIC application, or the identifier of the wireless terminal associated with the QUIC application including at least one of them.

[0033] Preferably, the QUIC connection information includes at least one QUIC connection identifier of the QUIC application, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC application and the UDP port associated with the wireless terminal, or The IP address of a remote server associated with a QUIC application and the UDP port associated with that remote server includes at least one of them.

[0034] Preferably, at least one QUIC flow parameter is a Quality of Service (QoS) flow identifier, an allocation and retention priority, an average maximum bit rate (AMBR) or a guaranteed bit rate (GBR) includes at least one of them.

[0035] Preferably, at least one QUIC flow parameter is the highest AMBR, the lowest AMBR, the highest GBR, or the lowest GBR includes at least one of them.

[0036] Preferably, at least one QUIC flow parameter is a list of a QUIC packet number range and the AMBR corresponding to that QUIC packet number range, or a list of a QUIC packet number range and the GBR corresponding to that QUIC packet number range includes at least one of them.

[0037] Preferably, the wireless communication method includes transmitting a QUIC assistance request including information on QUIC traffic to a network data analysis function, receiving QUIC assistance information associated with the QUIC traffic from the network data analysis function, and further includes The PCC rule is determined based on the QUIC assistance information.

[0038] Preferably, the QUIC assistance information An application service type associated with QUIC traffic, An application identifier associated with QUIC traffic, At least one QoS policy for QUIC traffic, or At least one QUIC packet number range corresponding to at least one QoS policy including at least one of them.

[0039] Preferably, the wireless communication method is sending a policy approval notification including information on QUIC traffic to an application function, receiving, from the application function, application service information associated with QUIC traffic, wherein a PCC rule is determined based on the application service information, further including.

[0040] Preferably, the application service information is An application service type associated with QUIC traffic, An application identifier associated with QUIC traffic, An identifier of a wireless terminal associated with QUIC traffic, An Internet Protocol (IP) address of a wireless terminal associated with QUIC traffic and a User Datagram Protocol (UDP) port associated with the wireless terminal, An IP address of a remote server associated with QUIC traffic and a UDP port associated with the remote server, or At least one QoS policy for QUIC traffic including at least one of them.

[0041] The present disclosure is a wireless communication method for use in a network data analysis function, Receiving, from a policy control function, a QUIC assistance request including information on QUIC (Quick User Datagram Protocol Internet Connectivity) traffic; sending, to the policy control function, QUIC assistance information associated with the QUIC traffic; and including wherein the QUIC information includes at least one event associated with information on the QUIC traffic and / or statistical values of the QUIC traffic, relating to a wireless communication method.

[0042] Various embodiments may preferably implement the following features: Preferably, at least one event associated with at least one QUIC report is an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission including at least one of them.

[0043] Preferably, at least one statistical value included in each QUIC report is the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between every two consecutive QUIC traffic transmissions, or an analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected including at least one of them.

[0044] Preferably, the QUIC traffic information includes a QUIC protocol indication associated with the QUIC traffic, the Internet Protocol (IP) address of a wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic and further includes at least one QUIC traffic parameter including at least one of the foregoing.

[0045] Preferably, the QUIC support information includes an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, at least one QoS policy for the QUIC traffic, or at least one QUIC packet number range corresponding to at least one QoS policy and includes at least one of the foregoing.

[0046] The present disclosure relates to a wireless communication method for use in an application function. The method includes receiving, from a policy control function, a policy approval notification including information on Quick User Datagram Protocol Internet Connection (QUIC) traffic, transmitting, to the policy control function, application service information associated with the QUIC traffic and the QUIC information includes at least one event associated with information on the QUIC traffic and / or statistics of the QUIC traffic.

[0047] Various embodiments may preferably implement the following features: Preferably, at least one event associated with at least one QUIC report is an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection termination, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission and includes at least one of them.

[0048] Preferably, at least one statistical value included in each QUIC report is the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between every two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which the QUIC traffic characteristics used to determine each QUIC report are collected and includes at least one of them.

[0049] Preferably, the information of QUIC traffic is the QUIC protocol indication associated with the QUIC traffic, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of the remote server associated with the QUIC traffic and the UDP port associated with the remote server, At least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic and further includes at least one QUIC traffic parameter including at least one of them.

[0050] Preferably, the application service information is the application service type associated with the QUIC traffic, the application identifier associated with the QUIC traffic, the identifier of the wireless terminal associated with the QUIC traffic, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with that wireless terminal, the IP address of the remote server associated with the QUIC traffic and the UDP port associated with that remote server, or at least one QoS policy for the QUIC traffic and includes at least one of them.

[0051] This disclosure relates to a session management node. The session management node is configured to send a Quick User Datagram Protocol Internet connection (QUIC) traffic command to the user plane function and receive at least one QUIC report associated with the QUIC traffic from the user plane function and comprises a communication unit so configured, wherein the QUIC traffic command includes at least one of a QUIC event report command for instructing at least one event associated with at least one QUIC report, or a QUIC statistic report command for instructing at least one statistic value included in each QUIC report.

[0052] Various embodiments may preferably implement the following features.

[0053] Preferably, the session management node further comprises a processor configured to implement any of the aforementioned wireless communication methods.

[0054] The present disclosure relates to a user plane node. The user plane node is configured to receive, from a session management function, a Quick User Datagram Protocol Internet Connection (QUIC) traffic instruction, and is configured to transmit, to the session management function, at least one QUIC report associated with the QUIC traffic, and comprises a communication unit configured as such, wherein the QUIC traffic instruction includes at least one of a QUIC event report instruction for instructing at least one event associated with at least one QUIC report, or a QUIC statistic report instruction for instructing at least one statistic value included in each QUIC report.

[0055] Various embodiments may preferably implement the following features.

[0056] Preferably, the user plane node further comprises a processor configured to implement any of the aforementioned wireless communication methods.

[0057] The present disclosure relates to a session management node. The session management node is configured to transmit, to a policy control function, information on Quick User Datagram Protocol Internet Connection (QUIC) traffic, and is configured to receive, from the policy control function, a policy and charging control (PCC) rule determined for a QUIC application based on the QUIC traffic information, and comprises a communication unit configured as such, QUIC information includes information on QUIC traffic and / or at least one event associated with statistics of QUIC traffic.

[0058] Various embodiments may preferably implement the following features.

[0059] Preferably, the session management node further comprises a processor configured to implement any of the aforementioned wireless communication methods.

[0060] The present disclosure relates to a policy control node. The policy control node is configured to receive information on Quick User Datagram Protocol Internet Connection (QUIC) traffic from a session management function and to send a policy and charging control (PCC) rule determined for a QUIC application based on the QUIC traffic information to the session management function and comprises a communication unit configured as such. QUIC information includes information on QUIC traffic and / or at least one event associated with statistics of QUIC traffic.

[0061] Various embodiments may preferably implement the following features.

[0062] Preferably, the policy control node further comprises a processor configured to implement any of the aforementioned wireless communication methods.

[0063] The present disclosure relates to a network data analysis node. The network data analysis node is configured to receive a QUIC assistance request including information on Quick User Datagram Protocol Internet Connection (QUIC) traffic from a policy control function and to send QUIC assistance information associated with the QUIC traffic to the policy control function and comprises a communication unit configured as such. QUIC information includes information on QUIC traffic and / or at least one event associated with statistical values of QUIC traffic.

[0064] Various embodiments may preferably implement the following features.

[0065] Preferably, the network data analysis node further comprises a processor configured to implement any of the aforementioned wireless communication methods.

[0066] This disclosure relates to an application node. The application node is configured to receive, from a policy control function, a policy approval notification including information on Quick User Datagram Protocol Internet connection (QUIC) traffic, and to transmit, to the policy control function, application service information associated with the QUIC traffic and comprises a communication unit configured as such, wherein the QUIC information includes information on QUIC traffic and / or at least one event associated with statistical values of QUIC traffic.

[0067] Various embodiments may preferably implement the following features.

[0068] Preferably, the application node further comprises a processor configured to implement any of the aforementioned wireless communication methods.

[0069] This disclosure relates to a computer program product comprising computer-readable program media code stored therein, the code causing a processor to implement, when executed by the processor, the wireless communication method described in any one of the aforementioned methods.

[0070] The exemplary embodiments disclosed herein are directed to providing features that will be readily apparent by reference to the following description when taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it is to be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those skilled in the art upon reading this disclosure that various modifications to the disclosed embodiments can be made within the scope of this disclosure.

[0071] Accordingly, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Further, the particular order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the particular order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this disclosure. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the particular order or hierarchy presented, unless otherwise specified.

[0072] The above and other aspects and their implementations are described in more detail in the drawings, description, and claims.

Brief Description of the Drawings

[0073]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

DETAILED DESCRIPTION OF THE INVENTION

[0074] To enable the network to correctly create policy rules for QUIC applications, the present disclosure discloses a method of extending the UPF to report QUIC traffic characteristics associated with QUIC traffic detection. As a result, the network may be able to recognize the services and / or applications to which the QUIC traffic pertains, and thus may be able to determine accurate policy rules for processing the QUIC traffic.

[0075] FIG. 1 shows a schematic diagram of a 5G network (architecture) according to an embodiment of the present disclosure. The network shown in FIG. 1 includes the following network entities or network functions (NFs).

[0076] 1. UE (User Equipment): UE refers to a mobile terminal that accesses the 5G network.

[0077] 2. NG RAN (Next Generation Radio Access Network): In the 5G network, NG RAN is a new radio (NR) base station, also called a gNB. Further, NG RAN may be equal to RAN (node) in this disclosure.

[0078] 3. AMF (Access and Mobility Management function): AMF provides access management and mobility management to the UE. For example, AMF may provide registration to the network, registration during UE mobility, etc.

[0079] 4. SMF (Session Management Function): SMF provides PDU session management to the UE, such as IP address allocation, QoS flow setup, etc.

[0080] 5. UPF (User plane function): UPF provides IP traffic routing and transfer management.

[0081] 6. PCF (Policy Control Function): PCF provides QoS policy rules to the control plane (network) function to enforce the rules.

[0082] 7. AF (Application Function): AF provides instructions that affect QoS policy rules to the PCF.

[0083] 8. NWDAF (Network Data Analytics Function): NWDAF collects network events from other NFs (such as AMF, SMF, PCF, UPF, etc.) and analyzes the behavior and state of the network by using, for example, artificial intelligence and / or machine learning.

[0084] In a 5G network, data traffic transmission is controlled by the SMF and the UPF. The SMF is a control plane function (CP Function) for data traffic control and processes the signaling mode of data traffic transmission (such as PDU session establishment / modification / release, N4 session establishment / modification / release, N4 rule generation, etc.). The UPF is a user plane function (UP Function) for data traffic control and processes the user plane mode of data traffic transmission (such as traffic detection, traffic filtering, and traffic forwarding, usage reporting, etc.) based on the instructions (such as N4 rules) received from the SMF.

[0085] After the UE registers with the 5G network, if communication with the application server is required, the UE requests the PDU session establishment procedure towards the 5G network. During the PDU session establishment procedure, the 5G network assigns a default QoS flow to the UE and may further assign the QoS flows indicated for the UE according to the UE request or the instructions from the policies configured for the UE.

[0086] Figure 2 shows a schematic diagram of the PDU session establishment procedure according to an embodiment of the present disclosure. In Figure 2, the SMF assigns a set of QoS flows to ensure communication between the UE and the application server.

[0087] Specifically, after the UE registers with the 5G network, the UE can request a PDU session establishment procedure including the following steps: Step 201: From the UE to the AMF: NAS message (S-NSSAI, UE requested DNN, PDU session ID, request type, N1 SM container (PDU session establishment request)).

[0088] The PDU session establishment request is included in the NAS message and encapsulated in the N1 SM container. The NAS message sent by the UE is encapsulated by the RAN into an N2 message towards the AMF.

[0089] Step 202: The AMF selects an appropriate SMF (i.e., the anchor SMF) that provides services for the PDU session based on the requested DNN, S-NSSAI, and the current UE location information.

[0090] Step 203: From the AMF to the SMF: Nsmf_PDUSession_CreateSMContext request (SUPI, selected DNN, UE requested DNN, S-NSSAI, PDU session ID, AMF ID, request type, N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI, GPSI).

[0091] The SUPI (Subscription Permanent Identifier) uniquely identifies the UE subscription. The AMF ID carries a GUAMI (Globally Unique AMF ID) that uniquely identifies the AMF providing services to the UE.

[0092] Step 204: From the SMF to the AMF: Nsmf_PDUSession_CreateSMContext response (cause, SM context ID). The SM context ID identifies the SM context created in the SMF for the UE.

[0093] Step 205: If dynamic PCC (Policy and Charging Control) is to be used for the PDU session, the SMF selects an appropriate PCF to serve the PDU session.

[0094] Step 206: The SMF sends an Npcf_PolicyAssociation_Create request to the PCF to perform the SM policy association establishment procedure and obtain the default PCC rules for the PDU session. It is assumed that necessary parameters such as SUPI, PDU session ID, DNN, S-NSSAI are provided in the request. Other parameters such as GPSI, UE IP address, UE external ID, RAT type, access type may also be provided in the request message.

[0095] Step 207: For a specific service, the PCF may interact with the AF to establish an AF association for the specific service. The AF association establishment enables the AF to dynamically influence the traffic model of the PDU session via the PCF, for example, setting up a new dedicated QoS flow or modifying an existing QoS flow.

[0096] Step 208: The PCF sends an Npcf_PolicyAssociation_Create response to the SMF to return the default PCC rules for the PDU session.

[0097] Step 209: The SMF selects a UPF that functions as the PDU Session Anchor (PSA).

[0098] Step 210: The SMF sends an N4 session establishment request carrying a set of N4 rules for packet detection and QoS extension installed in the UPF to the UPF, requesting to establish an N4 session for this PDU session. The N4 rules include a Packet Detection Rule (PDR), a Forward Action Rule (FAR), a QoS Enhancement Rule (QER), a Usage Reporting Rule (URR), etc.

[0099] When the SMF receives PCC rules from the PCF, the SMF maps the PCC rules to a set of QoS flows and generates a set of N4 rules (e.g., PDR / FAR / QER / URR rules) to reflect the determined QoS flows.

[0100] The UPF installs these N4 rules for this PDU session, uses these rules to filter uplink / downlink traffic, and performs corresponding QoS extensions on the filtered uplink / downlink traffic.

[0101] Step 211: The UPF sends a positive response by sending an N4 session establishment response.

[0102] Step 212: From the SMF to the AMF: Namf_Communication_N1N2MessageTransfer request (PDU session ID, N2 SM information (PDU session ID, QFI, QoS profile, N3 CN tunnel information), N1 SM container (PDU session establishment acceptance)).

[0103] The N2 SM information carries information that the AMF transfers to the RAN, including N3 CN tunnel information carrying the I-UPF UL F-TEID, the QFI, and the QoS profile used by the RAN to set up the QoS flows.

[0104] One or more QoS profiles and corresponding QFIs are provided to the RAN to enable the RAN to control QoS flows and perform traffic detection and admission control at the QoS flow level.

[0105] A typical QoS profile has the following parameters: - QFI used to uniquely identify one QoS flow within a PDU session, - ARP of the QoS flow (indicating Allocation and Retention Priority), - GBR QoS flow parameters used by the RAN to control the QoS flow, such as the maximum flow bit rate downlink, maximum flow bit rate uplink, guaranteed flow bit rate downlink, guaranteed flow bit rate uplink, maximum packet loss rate downlink, maximum packet loss rate uplink.

[0106] The N1 SM container accommodates the PDU session establishment acceptance provided by the AMF to the UE. The PDU session establishment acceptance contains the following parameters: PDU session ID, PDU session type, UE IP address, one or more QoS rules, QoS parameters at the QoS flow level associated with those QoS rules, DNN, S-NSSAI, etc.

[0107] Step 213: From the AMF to the RAN: N2 PDU session request (N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance))). The AMF sends a NAS message to the RAN that contains the PDU session ID and PDU session establishment acceptance targeted at the UE, and the N2 SM information received from the SMF within the N2 PDU session request.

[0108] Step 214: From RAN to UE: RAN may initiate AN - specific signaling exchange with the UE related to the information received from SMF. For example, in the case of 3GPP (registered trademark) RAN, RRC connection re - configuration may be performed with the UE to establish the necessary RAN resources related to the QoS rules for the PDU session request. RAN transfers NAS messages (PDU session ID, N1 SM container (PDU session establishment acceptance)) to the UE. RAN also allocates AN N3 tunnel information for the PDU session.

[0109] Step 215: From RAN to AMF: N2 PDU session response (PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs)).

[0110] The AN tunnel information corresponds to the access network address of the N3 tunnel corresponding to the PDU session.

[0111] Step 216: From AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (N2 SM information).

[0112] AMF transfers the N2 SM information received from RAN to SMF. If the list of rejected QFIs is included in the N2 SM information, SMF shall release the QoS profiles associated with the rejected QFIs.

[0113] Step 217: SMF sends an N4 session modification request to UPF. SMF provides the RAN tunnel information to UPF, optionally along with updated N4 rules.

[0114] Step 218: UPF updates the RAN tunnel information and installs the N4 rules. UPF sends an N4 session modification response to SMF.

[0115] Step 219: The SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF.

[0116] Step 220: The UE starts transmitting uplink traffic, for example, towards its application server, or receives downlink traffic, for example, from its application server.

[0117] During the PDU session establishment procedure, the SMF may allocate a default QoS flow to the UE for the PDU session. If the SMF is instructed by a locally configured PCC rule (e.g., one associated with a DNN and S-NSSAI) or by a dynamic PCC rule from the PCF, the SMF may also allocate a dedicated QoS flow to this PDU session.

[0118] To detail the procedure between the SMF and the UPF during PDU session establishment (i.e., steps 210 - 211 in Figure 2), Figure 3 shows the PFCP session establishment procedure between the SMF and the UPF for setting up an N4 session according to an embodiment of the present disclosure.

[0119] More specifically, during the PFCP session establishment / modification procedure, the SMF provides the necessary information to the UPF to instruct the UPF to perform packet detection and forwarding.

[0120] Step 301: The SMF is triggered to establish a PFCP session with the UP function. The trigger is a PDU session establishment request message from the AMF.

[0121] The SMF selects an appropriate UP function based on the DNN, S-NSSAI, and other necessary information.

[0122] Step 302: The SMF sends a PFCP session establishment request carrying PDR, QER, FAR, and URR to the selected UP function.

[0123] The PDR (Packet Detection Rule) defines a packet filter for a service data flow, for example, to filter uplink / downlink traffic between a specific application (e.g., an HTTP message to a specific website).

[0124] In the PDR, there may be one or more SDF (Service Data Flow) filters to represent the packet filter for a specific service data flow.

[0125] The QER (QoS Enforcement Rule) associated with at least one PDR defines how to control the QoS of the detected service flow.

[0126] The FAR (Forwarding Action Rule) associated with at least one PDR defines how to route and forward the detected service flow. For example, MEC traffic may be required to be routed to a local server.

[0127] The URR (Usage Reporting Rule) associated with at least one PDR defines how to report the amount / time usage of the detected service flow and how to report the usage to the CP function.

[0128] Step 303: When the UPF receives a PFCP session establishment request from the SMF, the UPF installs the received rules (i.e., PDR / QER / FAR / URR) for this PFCP session.

[0129] Step 304: The UPF returns a PFCP session establishment response message to the SMF.

[0130] Step 305: The SMF responds to the PDU session establishment trigger entity (e.g., the AMF) by sending a PDU session establishment response message.

[0131] Step 306: The UPF starts to detect uplink / downlink traffic with the UE and tries to match the received IP packet with the PDR. If the incoming IP packet matches one PDR, the corresponding QER / URR / FAR should be implemented.

[0132] Step 307: Then, the UE starts uplink traffic towards the server. For example, the UE sends an HTTP request to a dedicated web server.

[0133] Step 308: The UPF inspects the uplink traffic from the UE and detects whether it matches one of the installed PDRs. For example, the uplink traffic (HTTP request from the UE) matches the PDR targeted at detecting HTTP requests from the UE.

[0134] For certain IP traffic (e.g., HTTP traffic), special actions may be required before the UPF forwards the IP traffic. For example, HTTP header extensions may be required by the SMF.

[0135] Step 309: According to the instructions of the FAR rule, the UPF forwards the IP packet. The IP packet may be modified by the UPF based on instructions from the SMF. For example, HTTP header extensions may be implemented for HTTP traffic.

[0136] In subsequent procedures, in order to request the SMF to allocate a dedicated QoS flow in response to a request for application traffic transmission, the PDU session modification procedure can be initiated by the UE or the PCF. The SMF obtains the updated PCC rules from the PCF and allocates a dedicated QoS flow accordingly. As a result, the SMF sends N2 SM information to the RAN to update the QFI and QoS profile stored in the RAN, and sends an N1 SM container to the UE to update the QoS flow and QoS rules stored in the UE.

[0137] Figure 4 shows a schematic diagram of the PDU session modification procedure according to an embodiment of the present disclosure. The PDU session modification procedure can be triggered by the UE, the PCF, or the SMF. In certain scenarios, other network functions (e.g., UDM, RAN, or AMF) may also trigger the PDU session modification procedure. The PDU session modification procedure shown in Figure 4 includes the following steps.

[0138] Step 401: The PDU session modification procedure can be triggered by the events described in steps 401a, 401b, and 401c.

[0139] Step 401a: The UE initiates the PDU session modification procedure by transmitting a NAS message (N1 SM container (PDU session modification request), PDU session ID). The NAS message is transferred by the RAN to the AMF. The AMF calls Nsmf_PDUSession_UpdateSMContext (SM context ID, N1 SM container (PDU session modification request)).

[0140] Step 401b: The PCF performs the PCF-initiated SM policy association modification procedure to notify the SMF about policy modification. This can be triggered by policy decision or by an AF request, e.g., the impact of an application function on traffic routing.

[0141] Step 401c: The SMF may determine to modify the PDU session. This procedure may also be triggered based on a locally configured policy or by the RAN. It may also be triggered when the UP connection is activated and the SMF marks that the status of one or more QoS flows has been deleted in the 5GC but is not yet synchronized with the UE.

[0142] Step 402: If the PDU session modification procedure is not triggered by the PCF, the SMF may initiate an SM policy association modification procedure towards the PCF. The SMF sends an Npcf_PolicyAssociation_Update request to the PCF to obtain updated QoS rules from the PCF.

[0143] Step 403: For a specific service, the PCF may interact with the AF to update the AF association. The AF may send a decision on dynamic traffic authorization for this PDU modification.

[0144] Step 404: The PCF sends an Npcf_PolicyAssociation_Update request to the SMF to return the updated PCC rules for the PDU session.

[0145] Step 405: The SMF sends an N4 session modification request carrying a set of rules for packet detection and QoS extension to be installed in the UPF to request the modification of the N4 session for this PDU session. The rules include packet detection rules (PDRs), forwarding action rules (FARs), QoS extension rules (QERs), usage reporting rules (URRs), etc.

[0146] The SMF maps the updated PCC rules received from the PCF to a set of QoS flows and, accordingly, generates a set of updated PDR / FAR / QER / URR rules to reflect the updated QoS flows.

[0147] The UPF installs these updated rules for this PDU session, uses these rules to filter uplink / downlink traffic, and performs corresponding QoS enhancements on the filtered uplink / downlink traffic.

[0148] Step 406: The UPF responds affirmatively by sending an N4 session modification response.

[0149] Step 407: From SMF to AMF: Namf_Communication_N1N2MessageTransfer request (PDU session ID, N2 SM information (PDU session ID, QFI, QoS profile, N3 CN tunnel information), N1 SM container (PDU session modification command)).

[0150] Step 408: From AMF to RAN: N2 PDU session request (N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session modification command))). The AMF sends a NAS message containing the PDU session ID targeted at the UE and the PDU session modification command, and the N2 SM information received from the SMF within the N2 PDU session request, to the RAN.

[0151] Step 409: From RAN to UE: The RAN may initiate AN-specific signaling exchange with the UE related to the information received from the SMF.

[0152] Step 410: From RAN to AMF: N2 PDU session response (PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs)).

[0153] Step 411: From AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (N2 SM information).

[0154] The AMF transfers 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 shall release the QoS profiles associated with the rejected QFIs.

[0155] Step 412: The SMF initiates an N4 session modification procedure by the UPF. The SMF provides the RAN tunnel information to the UPF and the corresponding forwarding rules.

[0156] Step 413: The SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF.

[0157] In one embodiment, the UPF is instructed to detect QUIC traffic and report information associated with the QUIC traffic detection. For example, during the PFCP session establishment procedure, the SMF may detect QUIC traffic and instruct the UPF to report the QUIC traffic detection.

[0158] FIG. 5 shows a schematic diagram of a PFCP session establishment procedure according to an embodiment of the present disclosure. In FIG. 5, the SMF provides instructions for QUIC traffic detection to the UPF. Specifically, the PFCP session establishment procedure includes the following steps: Step 501: The SMF sends a PFCP session establishment request to the selected UPF, and the PFCP session establishment request carries PDR, QER, FAR, and URR.

[0159] In this embodiment, the SMF carries a QUIC traffic processing instruction to request the UPF to perform special processing for QUIC traffic.

[0160] In one embodiment, the QUIC traffic processing instruction may include a QUIC event report instruction configured to instruct the UPF to detect and report specific QUIC events of interest. For example, there may be cases where at least one of the following QUIC events needs to be detected and reported: - An event of QUIC traffic detection that requests the UPF to detect and report the first detection of QUIC traffic transmission, - An event of QUIC connection establishment that requires the UPF to detect and report the event of QUIC connection establishment, - An event of QUIC connection release that requires the UPF to detect and report the event of QUIC connection release, - An event of QUIC data block transmission start that requests the UPF to detect / report the start of a block of QUIC packet transmission, or - An event of QUIC data block transmission stop that requests the UPF to detect and report the stop of a block of QUIC packet transmission.

[0161] In one embodiment, the SMF may only request the UPF to detect general QUIC events (e.g., an event of QUIC traffic detection). In this embodiment, the UPF detects QUIC traffic regardless of whether the QUIC traffic is associated with any special QUIC event. Alternatively, or in addition, the SMF may request the UPF to detect at least one of one or more special QUIC events, such as an event of QUIC connection establishment / release and an event of QUIC data block transmission start / stop.

[0162] In one embodiment, the QUIC traffic processing instruction may include a QUIC statistic report instruction configured to instruct the UPF to analyze QUIC traffic transmission, collect QUIC traffic statistics, and report the results associated with the QUIC traffic statistics. For example, at least one of the following QUIC traffic statistics may be analyzed / collected / reported: -Average delay of QUIC data transmission, maximum delay of QUIC traffic transmission, minimum delay of QUIC data transmission, -Average size of QUIC data blocks, -Maximum size of QUIC data blocks, -Minimum size of QUIC data blocks, or -Average transmission interval between (every two consecutive) QUIC data blocks.

[0163] Step 502: When receiving a PFCP session establishment request from the SMF, the UPF installs the received rules (i.e., PDR / QER / FAR / URR) for this PFCP session.

[0164] In one embodiment of the provided QUIC event report instruction, the UPF stores the QUIC event report instruction and performs detection for the indicated QUIC event.

[0165] In one embodiment of the provided QUIC statistic report instruction, the UPF stores the QUIC statistic report instruction, performs QUIC traffic analysis, and collects QUIC traffic statistics.

[0166] Step 503: The UPF sends a PFCP session establishment response message to the SMF.

[0167] Steps 504a / 504b: Subsequently, uplink / downlink traffic arrives at the UPF.

[0168] Step 505: When a QUIC traffic processing instruction is provided by the SMF, the UPF performs QUIC event detection and / or QUIC traffic analysis.

[0169] Note that either QUIC event detection or QUIC traffic characteristic analysis requires the UPF to be able to detect QUIC traffic and collect QUIC traffic parameters.

[0170] Generally, an HTTP server implementing the QUIC protocol listens for QUIC traffic on a specific special UDP port (e.g., port 443 reserved for TLS, or port 80 / 8080 reserved for HTTP). Therefore, the UPF may be instructed by the SMF or via the UPF's local rules to detect QUIC traffic by checking and filtering QUIC traffic from uplink UDP traffic based on a preconfigured UDP port (e.g., port 443).

[0171] When QUIC traffic is detected, the UPF collects QUIC traffic parameters from the UDP packet header and / or the QUIC packet header. For example, the UPF may detect at least one of the following QUIC traffic parameters: - The transport protocol type indicating that the transport protocol is QUIC over UDP, - The UE IP address and UDP port used by the UE to send or receive QUIC traffic, - The remote server IP address and UDP port used by the remote server to send or receive QUIC traffic, - The QUIC version indicating the QUIC protocol version extracted from the QUIC packet header, - The QUIC packet number indicating the packet number of the QUIC packet extracted from the QUIC packet header, - A QUIC connection ID that identifies one QUIC connection between two endpoints (e.g., a UE and a remote server) extracted from the QUIC packet header. The QUIC connection ID used by the UE to send uplink QUIC traffic is different from the QUIC connection ID used by the remote server to send downlink QUIC traffic. The UPF must be able to recognize different QUIC connection IDs.

[0172] Furthermore, if a specific QUIC event needs to be reported, the UPF shall further check whether the indicated QUIC event occurs.

[0173] Step 506: The UPF sends a PFCP session report request carrying the QUIC traffic report to the SMF.

[0174] In one embodiment, at least one of the following information items shall be included in the QUIC traffic report: - A QUIC traffic parameter IE that carries the following combination of QUIC traffic parameters: QUIC protocol indication, UE IP address and port, remote server IP address and port, QUIC connection ID, QUIC version, QUIC packet number, - A QUIC event IE that indicates at least one type of QUIC event, - A QUIC traffic characteristic IE that carries the following combination of QUIC traffic characteristics: average delay of QUIC traffic transmission, maximum delay of QUIC traffic transmission, minimum delay of QUIC traffic transmission, average size of QUIC data blocks, maximum size of QUIC data blocks, minimum size of QUIC data blocks, average interval of QUIC traffic transmission. Furthermore, there may be an analysis period that indicates the period during which the QUIC traffic characteristics are collected.

[0175] Step 507: The SMF sends a PFCP session report response to the UPF. The SMF may request the PCF to update the PCC rules accordingly using the reported QUIC event and / or QUIC traffic characteristics.

[0176] In some embodiments, the SMF may request the PCF to provide a PCC rule for the QUIC application, for example, when receiving a PFCP session report with QUIC traffic detection. FIG. 6 shows a schematic diagram of a PFCP session establishment procedure according to an embodiment of the present disclosure. In FIG. 6, the SMF provides instructions for QUIC traffic detection to the UPF during the FCP session establishment procedure.

[0177] Step 601: The SMF receives a PFCP session report carrying a QUIC traffic report from the UPF. For example, the SMF may receive the PFCP session report as described in the procedure of FIG. 5.

[0178] Step 602: The SMF determines that a PCC rule for the QUIC application is required. If dynamic PCC is implemented, the SMF needs to obtain the PCC rule for the QUIC application from the PCF. Otherwise, the SMF may generate the PCC rule for the QUIC application using local configuration rules.

[0179] Step 603: If dynamic PCC is implemented, the SMF sends an SM policy association update request carrying QUIC traffic information to the PCF.

[0180] In one embodiment, the QUIC traffic information IE includes at least one of the following information items: - A QUIC traffic parameter IE that carries the following combination of QUIC traffic parameters: QUIC protocol indication, UE IP address and port, remote server IP address and port, QUIC connection ID, QUIC version, QUIC packet number, - A QUIC event IE that indicates at least one type of QUIC event, - A QUIC traffic characteristic IE that carries the following combination of QUIC traffic characteristics: average delay of QUIC traffic transmission, maximum delay of QUIC traffic transmission, minimum delay of QUIC traffic transmission, average size of QUIC data blocks, maximum size of QUIC data blocks, minimum size of QUIC data blocks, average interval of QUIC traffic transmission. Further, there may be an analysis period that indicates the period during which the QUIC traffic characteristics are collected.

[0181] Step 604: When the PCF receives an SM policy association update from the SMF, the PCF determines that it is necessary to generate a PCC rule for the QUIC application based on the received QUIC traffic information.

[0182] In one embodiment, if the PCF is configured by local rules for the QUIC application (e.g., rules for recognizing various QUIC applications, policy rules for those QUIC applications, etc.), or if such rules (e.g., UDR) can be obtained from storage, the PCF performs step 605A to generate policy rules.

[0183] In one embodiment, if the PCF is configured to obtain policy assistance information from the NWDAF, the PCF performs step 605B to obtain the policy assistance information.

[0184] In one embodiment, when the PCF is configured to contact the corresponding AF implemented to process the QUIC application, the PCF performs steps 605C01 and 605C02 to obtain policy information from the AF.

[0185] Step 605A: The PCF recognizes the QUIC application based on the QUIC traffic information provided by the SMF, and determines the policy rules for the QUIC application based on the locally configured rules or the rules (e.g., UDR) obtained from the storage.

[0186] Step 605B: The PCF sends a policy assistance request for carrying the QUIC traffic information to the NWDAF. The NWDAF sends a policy assistance response for carrying the policy assistance information to the PCF.

[0187] In one embodiment, the policy assistance information returned by the NWDAF may accommodate / include at least one of the following information: application service type, application identifier, applicable QoS policies (e.g., AMBR, GBR, highest AMBR, lowest AMBR, highest GBR, lowest GBR, etc.). Such information helps the PCF to correctly generate the policy rules for the QUIC traffic.

[0188] In one embodiment, the NWDAF may further associate the QoS policy with a specific QUIC packet number range. For example, AMBR#1 and GBR#1 are applied to the packet numbers within the QUIC packet number range #1, and AMBR#2 and GBR#2 are applied to another packet number within the QUIC packet number range #2.

[0189] When the NWDAF receives the QUIC traffic information from the PCF, it uses that knowledge to estimate the service type, application identifier, and applicable QoS policy of the reported QUIC traffic. The NWDAF may collect various QUIC events and QUIC statistical values from the network and may also use AI methods to estimate relevant information about QUIC services / applications.

[0190] Step 605C01: The PCF sends a policy approval notification carrying the QUIC traffic information to the AF. The AF may verify the QUIC traffic information (e.g., QUIC traffic parameters) and decide to initiate an AF session binding to the PCF.

[0191] Step 605C02. The AF initiates the AF session binding procedure to the PCF and provides the QUIC application service information to the PCF.

[0192] In one embodiment, the QUIC application service information may accommodate / contain at least one combination of the following items: application service type (identifying the service of the QUIC application), application identifier (identifying the QUIC application), UE identifier (e.g., SUPI or GPSI), UE IP address and port, remote service IP address and port, QUIC connection ID, or applicable QoS policy (e.g., AMBR, GBR, highest AMBR, lowest AMBR, highest GBR, lowest GBR, etc.).

[0193] Step 606: The PCF uses the information obtained in steps 605A, 605B, or 605C01 and 605C02 to generate a PCC rule for the QUIC application.

[0194] In one embodiment in which step 605A is performed, the PCF generates PCC rules for the reported QUIC application using QUIC application information derived by itself via locally configured rules or rules outside the storage.

[0195] In one embodiment of step 5B performed, the PCF generates PCC rules for the reported QUIC application using the policy assistance information obtained from the NWDAF.

[0196] In one embodiment in which steps 605C01 and 605C02 are performed, the PCF generates PCC rules for the reported QUIC application using the application service information obtained from the AF.

[0197] In one embodiment, the generated PCC rules may accommodate / include at least one of the following information: 1) QUIC application information, which further includes at least one of an application identifier, an application service type, and a UE identifier, 2) QUIC connection information, which further includes at least one of a QUIC connection ID, a UE IP address and UDP port, a remote server IP address and UDP port, or 3) QoS flow parameters of QUIC traffic, which further includes at least one of a QoS flow identifier (QFI), an allocation and retention priority (ARP), an average maximum bit rate (AMBR), and a guaranteed bit rate (GBR). The QoS flow parameters may further include one of the highest AMBR, the lowest AMBR, the highest GBR, and the lowest GBR. Alternatively, the QoS flow parameters may further include a list of QUIC packet number ranges and the corresponding AMBR and GBR associated with each QUIC packet number range.

[0198] Step 607: The PCF sends a SM policy association update response carrying the PCC rules for the QUIC application to the SMF.

[0199] Step 608: Upon receiving the PCC rules for the QUIC application, the SMF generates the corresponding PFCP rules (i.e., PDR / QER / FAR / URR rules, etc.) for the QUIC application and sends a PFCP session modification request carrying the updated PFCP rules to the UPF. Note that the PFCP rules are also referred to as N4 rules on the N4 interface.

[0200] In one embodiment, at least one PDR rule for QUIC traffic detection is created. One or more QER / FAR / URR rules for the QUIC traffic are created and linked to the PDR rule for the QUIC traffic detection described above.

[0201] In one embodiment, to instruct the UPF to detect specific QUIC traffic, at least one of the following information may be carried in the N4 rule (e.g., PDR): - A QUIC traffic detection instruction to instruct the UPF to detect QUIC traffic, - The UE IP address and UDP port to instruct the UPF to detect QUIC traffic between it and the UE address, - The IP address and port of the remote server to instruct the UPF to detect QUIC traffic between it and the remote server address, - The QUIC connection ID to instruct the UPF to detect QUIC traffic via the indicated QUIC connection.

[0202] Step 609: The UPF receives the PFCP session modification request and updates the received N4 rules (e.g., PDR / QER / FAR / URR rules, etc.) in its storage.

[0203] Step 610: The UPF starts detecting QUIC traffic for a specific QUIC application based on the updated N4 rules and performs necessary actions (such as gate control, QoS enforcement, forwarding, usage reporting, etc.) on the detected QUIC traffic.

[0204] FIG. 7 relates to a schematic diagram of a wireless terminal 70 according to an embodiment of the present disclosure. The wireless terminal 70 may be a user equipment (UE), a mobile phone, a laptop, a tablet computer, an e - book, or a portable computer system, and is not limited herein. The wireless terminal 70 may include a processor 700 such as a microprocessor or an application specific integrated circuit (ASIC), a memory unit 710, and a communication unit 720. The memory unit 710 may be any data storage device that stores program code 712 accessed and executed by the processor 700. Embodiments of the memory unit 710 include, but are not limited to, a subscriber identity module (SIM), a read - only memory (ROM), a flash memory, a random - access memory (RAM), a hard disk, and an optical data storage device. The communication unit 720 may be a transceiver and is used to transmit and receive signals (such as messages or packets) according to the processing results of the processor 700. In one embodiment, the communication unit 720 transmits and receives signals via at least one antenna 722 shown in FIG. 7.

[0205] In one embodiment, the memory unit 710 and the program code 712 may be omitted, and the processor 700 may include a memory unit having the stored program code.

[0206] The processor 700 may implement any one of the steps in the illustrated embodiments on the wireless terminal 70, for example, by executing the program code 712.

[0207] The communication unit 720 may be a transceiver. Alternatively or in addition, the communication unit 720 may combine a transmission unit and a reception unit configured to respectively transmit and receive signals to and from a wireless network node (e.g., a base station).

[0208] FIG. 8 relates to a schematic diagram of a wireless network node 80 according to an embodiment of the present disclosure. The wireless network node 80 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a radio network controller (RNC), and is not limited herein. Further, the wireless network node 80 may include (or may implement) at least one network function such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), and an application function (AF). The wireless network node 80 may include a processor 800 such as a microprocessor or an ASIC, a memory unit 810, and a communication unit 820. The memory unit 810 may be any data storage device that stores program code 812 accessed and executed by the processor 800. Examples of the memory unit 810 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 820 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 800. In one example, the communication unit 820 transmits and receives signals via at least one antenna 822 shown in FIG. 8.

[0209] In one embodiment, the memory unit 810 and the program code 812 may be omitted. The processor 800 may include a memory unit having the stored program code.

[0210] The processor 800 may implement any of the steps described in the illustrated embodiments on the wireless network node 80, for example, by executing the program code 812.

[0211] The communication unit 820 may be a transceiver. The communication unit 820 may alternatively or additionally combine a transmission unit and a reception unit configured to transmit and receive signals, respectively, with a wireless terminal (e.g., a user device or another wireless network node).

[0212] FIG. 9 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 9 may be used in an SMF (e.g., a session management node, a wireless device including an SMF, or a wireless device implementing at least a part of the functions of an SMF) and includes the following steps: Step 901: Transmit a QUIC traffic instruction to the UPF.

[0213] Step 902: Receive at least one QUIC report associated with the QUIC traffic from the UPF.

[0214] In FIG. 9, the SMF transmits a QUIC traffic instruction to the UPF, for example, to instruct the UPF to detect and / or collect information on the QUIC traffic. In response to the QUIC traffic instruction, at least one QUIC report associated with the QUIC traffic is transmitted from the UPF to the SMF.

[0215] In one embodiment, the QUIC traffic instruction includes at least one of a QUIC event report instruction that indicates at least one event associated with (generating / reporting) at least one QUIC report, or a QUIC statistic report instruction that indicates at least one statistic value included in each QUIC report.

[0216] In one embodiment, at least one event associated with at least one QUIC report includes at least one of an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission. Further details of each event may refer to the embodiments shown in FIGS. 5 and 6.

[0217] In one embodiment, at least one statistic value included in each QUIC report includes at least one of the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected.

[0218] In one embodiment, each QUIC report includes at least one of at least one QUIC traffic parameter of QUIC traffic, at least one QUIC report event associated with the QUIC report, or at least one statistic value of QUIC traffic associated with the QUIC report.

[0219] In one embodiment, at least one QUIC traffic parameter includes at least one of a QUIC protocol instruction associated with the QUIC traffic, an IP address of a wireless terminal (e.g., UE) associated with the QUIC traffic and a UDP port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, a QUIC version of the QUIC traffic, or a packet number of the QUIC traffic.

[0220] In the present disclosure, at least one of A, B, and / or C may refer to at least one A and / or at least one B and / or at least one C. It should be noted that A / B / C refers to parameters, elements, statistics, etc.

[0221] FIG. 10 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 10 may be used in a UPF (e.g., a user plane node, a wireless device including a UPF, or a wireless device implementing at least a part of the functions of a UPF) and includes the following steps: Step 1001: Receive a QUIC traffic instruction from the SMF.

[0222] Step 1002: Transmit at least one QUIC report associated with the QUIC traffic to the SMF.

[0223] In this embodiment, the UPF receives a QUIC traffic instruction from the SMF. Based on the QUIC traffic instruction, the UPF starts detecting the QUIC traffic and collecting information associated with the detected QUIC traffic. The UPF transmits at least one QUIC report associated with the QUIC traffic.

[0224] In one embodiment, the QUIC traffic instruction includes at least one of a QUIC event report instruction that indicates at least one event (generating / reporting it) associated with at least one QUIC report, or a QUIC statistical value report instruction that indicates at least one statistical value included in each QUIC report.

[0225] In one embodiment, at least one event associated with at least one QUIC report includes at least one of an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection termination, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission. Further details of each event may refer to the embodiments shown in FIGS. 5 and 6.

[0226] In one embodiment, at least one statistical value included in each QUIC report includes at least one of the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected.

[0227] In one embodiment, each QUIC report includes at least one of at least one QUIC traffic parameter of QUIC traffic, at least one QUIC report event associated with the QUIC report, or at least one statistical value of QUIC traffic associated with the QUIC report.

[0228] In one embodiment, at least one QUIC traffic parameter includes at least one of a QUIC protocol indication associated with the QUIC traffic, an IP address of a wireless terminal (e.g., UE) associated with the QUIC traffic and a UDP port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, a QUIC version of the QUIC traffic, or a packet number of the QUIC traffic.

[0229] FIG. 11 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 11 may be used in an SMF (e.g., a session management node, a wireless device including the SMF, or a wireless device implementing at least a part of the functions of the SMF) and includes the following steps: Step 1101: Transmit information on QUIC traffic to the PCF.

[0230] Step 1102: Receive, from the PCF, a PCC rule determined for the QUIC application based on the information on the QUIC traffic.

[0231] In FIG. 11, the SMF transmits information on the QUIC traffic to the PCF. For example, the SMF may receive / request information on the QUIC traffic from the UPF by implementing the method of FIG. 9. Based on the information on the QUIC traffic, the PCF may determine / optimize / modify / adjust / add a PCC rule for the QUIC application and transmit the PCC rule to the SMF. Thus, by adopting the PCC rule, the SMF can process the QUIC traffic of the QUIC application more efficiently.

[0232] In one embodiment, the QUIC information includes at least one event associated with the information on the QUIC traffic and / or the statistics of the QUIC traffic.

[0233] In one embodiment, at least one event associated with at least one QUIC report includes at least one of an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission. Further details of each event may be referred to the embodiments shown in FIGS. 5 and 6.

[0234] In one embodiment, at least one statistical value included in each QUIC report includes at least one of the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected.

[0235] In one embodiment, the information of QUIC traffic further includes at least one QUIC traffic parameter including at least one of a QUIC protocol indication associated with the QUIC traffic, the IP address of a wireless terminal (e.g., UE) associated with the QUIC traffic and the UDP port associated with the wireless terminal, the IP address of a remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic.

[0236] In one embodiment, the PCC rule includes at least one of QUIC application information, QUIC connection information, or at least one QUIC flow parameter.

[0237] In one embodiment, the QUIC application information includes at least one of an application identifier of the QUIC application, an application service type of the QUIC application, or an identifier of a wireless terminal associated with the QUIC application.

[0238] In one embodiment, the QUIC connection information includes at least one of at least one QUIC connection identifier of the QUIC application, an IP address of a wireless terminal associated with the QUIC application and a UDP port associated with the wireless terminal, or an IP address of a remote server associated with the QUIC application and a UDP port associated with the remote server.

[0239] In one embodiment, the at least one QUIC flow parameter includes at least one of a QoS flow identifier, an allocation and retention priority, an AMBR, or a GBR.

[0240] In one embodiment, the at least one QUIC flow parameter includes at least one of a highest AMBR, a lowest AMBR, a highest GBR, or a lowest GBR.

[0241] In one embodiment, the at least one QUIC flow parameter includes at least one of a list of a QUIC packet number range and an AMBR corresponding to the QUIC packet number range, or a list of a QUIC packet number range and a GBR corresponding to the QUIC packet number range.

[0242] FIG. 12 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 12 may be used in a PCF (for example, a policy control node, a wireless device including a PCF, or a wireless device implementing at least a part of the functions of a PCF) and includes the following steps: Step 1201: Receive information on QUIC traffic from the SMF.

[0243] Step 1202: The SMF sends the PCC rules determined for the QUIC application based on the information of the QUIC traffic.

[0244] In FIG. 12, the PCF receives the information of the QUIC traffic from the SMF. Based on the received information, the PCF may determine / optimize / modify / adjust / add the PCC rules for the QUIC application, for example, to enable the SMF to efficiently process the QUIC traffic of the QUIC application, and send the PCC rules to the SMF.

[0245] In one embodiment, the QUIC information includes at least one event associated with the information of the QUIC traffic and / or the statistics of the QUIC traffic.

[0246] In one embodiment, at least one event associated with at least one QUIC report includes at least one of an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission. Further details of each event may refer to the embodiments shown in FIGS. 5 and 6.

[0247] In one embodiment, at least one statistic included in each QUIC report includes at least one of the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of the QUIC data block, the maximum size of the QUIC data block, the minimum size of the QUIC data block, the average interval between two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which the QUIC traffic characteristics used to determine each QUIC report are collected.

[0248] In one embodiment, the information of the QUIC traffic further includes at least one QUIC traffic parameter including at least one of a QUIC protocol indication associated with the QUIC traffic, an IP address of a wireless terminal (e.g., UE) associated with the QUIC traffic and a UDP port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, a QUIC version of the QUIC traffic, or a packet number of the QUIC traffic.

[0249] In one embodiment, the PCC rule includes at least one of QUIC application information, QUIC connection information, or at least one QUIC flow parameter.

[0250] In one embodiment, the QUIC application information includes at least one of an application identifier of the QUIC application, an application service type of the QUIC application, or an identifier of a wireless terminal associated with the QUIC application.

[0251] In one embodiment, the QUIC connection information includes at least one of at least one QUIC connection identifier of the QUIC application, an IP address of a wireless terminal associated with the QUIC application and a UDP port associated with the wireless terminal, or an IP address of a remote server associated with the QUIC application and a UDP port associated with the remote server.

[0252] In one embodiment, the at least one QUIC flow parameter includes at least one of a QoS flow identifier, an allocation and retention priority, an AMBR, or a GBR.

[0253] In one embodiment, at least one QUIC flow parameter includes at least one of the highest AMBR, the lowest AMBR, the highest GBR, or the lowest GBR.

[0254] In one embodiment, at least one QUIC flow parameter includes at least one of a list of QUIC packet number ranges and the AMBR corresponding to the QUIC packet number ranges, or a list of QUIC packet number ranges and the GBR corresponding to the QUIC packet number ranges.

[0255] In one embodiment, the PCF further sends a QUIC assistance request including information on QUIC traffic to the NWDAF. In response to the QUIC assistance request, the NWDAF sends QUIC assistance information to the PCF. The PCF determines PCC rules further based on the QUIC assistance information.

[0256] In one embodiment, the QUIC assistance information includes at least one of an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, at least one QoS policy for the QUIC traffic, or at least one QUIC packet number range corresponding to the at least one QoS policy.

[0257] In one embodiment, the PCF may send a policy approval notification including information on QUIC traffic to the AF and receive application service information associated with the QUIC traffic from the AF. Based on the application service information, the PCF determines PCC rules.

[0258] In one embodiment, the application service information includes at least one of an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, an identifier of a wireless terminal associated with the QUIC traffic, an IP address of the wireless terminal associated with the QUIC traffic and a UDP port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, or at least one of at least one QoS policy for the QUIC traffic.

[0259] FIG. 13 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 13 may be used in an NWDAF (e.g., a network data analysis node, a wireless device including the NWDAF, or a wireless device implementing at least a part of the functions of the NWDAF) and includes the following steps: Step 1301: Receive, from the PCF, a QUIC support request including information on the QUIC traffic.

[0260] Step 1302: Transmit, to the PCF, QUIC support information associated with the QUIC traffic.

[0261] In FIG. 13, the NWDAF receives, from the PCF, a QUIC support request including information on the QUIC traffic. The NWDAF analyzes the information on the QUIC traffic and, accordingly, generates QUIC support information that can be used to determine a PCC rule. The generated QUIC support information is transmitted from the NWDAF to the PCF.

[0262] In one embodiment, the QUIC information includes at least one event associated with information on the QUIC traffic and / or statistical values of the QUIC traffic.

[0263] In one embodiment, at least one event associated with at least one QUIC report includes at least one of an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission. Further details of each event may refer to the embodiments shown in FIGS. 5 and 6.

[0264] In one embodiment, at least one statistical value included in each QUIC report includes at least one of the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected.

[0265] In one embodiment, the information of QUIC traffic further includes at least one QUIC traffic parameter including at least one of a QUIC protocol indication associated with the QUIC traffic, the IP address of a wireless terminal (e.g., UE) associated with the QUIC traffic and the UDP port associated with the wireless terminal, the IP address of a remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic.

[0266] In one embodiment, the QUIC support information includes at least one of an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, at least one QoS policy for the QUIC traffic, or at least one QUIC packet number range corresponding to the at least one QoS policy.

[0267] FIG. 14 shows a flowchart of a method according to an embodiment of the present disclosure. The method shown in FIG. 14 may be used in an AF (e.g., an application node, a wireless device including an AF, or a wireless device implementing at least a part of the functions of an AF) and includes the following steps: Step 1401: Receive a policy approval notification including information on QUIC traffic from the PCF.

[0268] Step 1402: Transmit application service information associated with the QUIC traffic to the PCF.

[0269] In this embodiment, the AF receives a policy approval notification including information on QUIC traffic from the PCF. Based on the information on the QUIC traffic, the AF generates and transmits application service information associated with the QUIC traffic to the PCF to help, for example, the PCF determine the corresponding PCC rule.

[0270] In one embodiment, the QUIC information includes at least one event associated with information on the QUIC traffic and / or statistics of the QUIC traffic.

[0271] In one embodiment, at least one event associated with at least one QUIC report includes at least one of an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission. Further details of each event may refer to the embodiments shown in FIGS. 5 and 6.

[0272] In one embodiment, at least one statistical value included in each QUIC report includes at least one of the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between two consecutive QUIC traffic transmissions, or the analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected.

[0273] In one embodiment, the information of QUIC traffic further includes at least one QUIC traffic parameter including at least one of a QUIC protocol indication associated with the QUIC traffic, the IP address of a wireless terminal (e.g., UE) associated with the QUIC traffic and the UDP port associated with the wireless terminal, the IP address of a remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic.

[0274] In one embodiment, the application service information includes at least one of an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, an identifier of a wireless terminal associated with the QUIC traffic, an IP address of the wireless terminal associated with the QUIC traffic and a UDP port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, or at least one of at least one QoS policy for the QUIC traffic.

[0275] As described above, various embodiments of the present disclosure have been described, but it should be understood that they are not limiting and are presented only as examples. Similarly, the various figures may depict an exemplary architecture or configuration provided to enable those skilled in the art to understand the exemplary features and functions of the present disclosure. However, such a person will understand that the present disclosure is not limited to the illustrated exemplary architecture or configuration and can be implemented using various alternative architectures and configurations. Further, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the width and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

[0276] It should also be understood that any reference in this specification to elements using terms such as "first", "second", etc. generally does not limit the quantity or order of those elements. Rather, these terms can be used in this specification as a convenient means to distinguish two or more elements or instances of elements. Therefore, references to the first and second elements do not mean that only two elements can be employed, nor that the first element must in some way precede the second element.

[0277] Furthermore, those skilled in the art will understand that information and signals can be represented using any one of a variety of different scientific and technical disciplines. For example, data, instructions, commands, information, signals, bits, and symbols, which may be referred to in the above description, can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0278] Those skilled in the art will further recognize that any one of the various exemplary logical blocks, units, processors, means, 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 programs or design code incorporating instructions (which may be referred to herein, for convenience, as "software" or "software units"), or any combination of these technologies.

[0279] To clearly illustrate this interchangeability of hardware, firmware, and software, various exemplary components, blocks, units, circuits, and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these technologies depends on the particular application and design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in various ways for each particular application, but such implementations do not depart from the scope of the present disclosure. According to various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein. The terms "configured to" or "configured for" as used herein with respect to a specified operation or function refer to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0280] Furthermore, those skilled in the art will understand that the various exemplary logical blocks, units, devices, components, and circuits described herein can be implemented within or by an integrated circuit (IC) including 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 device, or any combination thereof. The logical blocks, units, and circuits can further include antennas and / or transceivers for communicating with various components within a network or device. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other suitable configuration for performing the functions described herein. When implemented in software, the functions can be stored on a computer-readable medium as one or more instructions or code. Accordingly, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0281] A computer-readable medium includes both a computer storage medium and a communication medium including any medium that can be used to enable a computer program or code to be transmitted from one location to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0282] As used herein, the term "unit" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Further, for purposes of discussion, although various units are described as separate units, as will be apparent to those skilled in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.

[0283] Furthermore, in embodiments of the present disclosure, a memory or other storage device, as well as communication components, may be employed. For clarity, it will be understood that the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functions between different functional units, processing logic elements or domains may be used without detracting from the present disclosure. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units are not intended to indicate a strict logical or physical structure or organization, but rather are merely references to suitable means for providing the described functions.

[0284] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of the claims. Accordingly, this disclosure is not intended to be limited to the implementations shown herein, but rather should be accorded 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 use in a session management function, comprising: sending, to a user plane function, a Quick User Datagram Protocol Internet Connections (QUIC) traffic instruction; receiving, from the user plane function, at least one QUIC report associated with the QUIC traffic; wherein the QUIC traffic instruction includes at least one of a QUIC event report instruction for instructing at least one event associated with the at least one QUIC report or a QUIC statistical value report instruction for instructing at least one statistical value included in each QUIC report. A wireless communication method.

2. The at least one event associated with the at least one QUIC report includes at least one of: an event associated with QUIC traffic detection; an event associated with QUIC connection establishment; an event associated with QUIC connection release; an event associated with the start of QUIC data block transmission; or an event associated with the end of QUIC data block transmission. The wireless communication method according to claim 1.

3. The at least one statistical value included in each QUIC report includes at least one of: an average delay of QUIC traffic transmission; a maximum delay of QUIC traffic transmission; a minimum delay of QUIC traffic transmission; an average size of a QUIC data block; a maximum size of a QUIC data block; a minimum size of a QUIC data block; an average interval between every two consecutive QUIC traffic transmissions; or an analysis period indicating a period during which QUIC traffic characteristics used to determine each QUIC report are collected. The wireless communication method according to claim 1 or 2.

4. Each QUIC report includes at least one of: at least one QUIC traffic parameter of the QUIC traffic; the at least one QUIC report event associated with the QUIC report; or the at least one statistical value of the QUIC traffic associated with the QUIC report. The wireless communication method according to any one of claims 1 to 3.

5. The at least one QUIC traffic parameter includes a QUIC protocol instruction associated with the QUIC traffic, an Internet protocol (IP) address of a wireless terminal associated with the QUIC traffic and a User Datagram Protocol (UDP) port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, a QUIC version of the QUIC traffic, or a packet number of the QUIC traffic The wireless communication method according to claim 4, including at least one of the above.

6. A wireless communication method for use in a user plane function, comprising: receiving, from a session management function, a Quick User Datagram Protocol Internet Connections (QUIC) traffic instruction; and transmitting, to the session management function, at least one QUIC report associated with the QUIC traffic The wireless communication method, wherein the QUIC traffic instruction includes at least one of a QUIC event report instruction for instructing at least one event associated with the at least one QUIC report or a QUIC statistical value report instruction for instructing at least one statistical value included in each QUIC report.

7. The at least one event associated with the at least one QUIC report includes an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission The wireless communication method according to claim 6, including at least one of the above.

8. The at least one statistical value included in each QUIC report includes an average delay of QUIC traffic transmission, a maximum delay of QUIC traffic transmission, a minimum delay of QUIC traffic transmission, ​ The average size of a QUIC data block, the maximum size of a QUIC data block, the minimum size of a QUIC data block, the average interval between every two consecutive QUIC traffic transmissions, or an analysis period indicating the period during which QUIC traffic characteristics used to determine each QUIC report are collected The wireless communication method according to claim 6 or 7, including at least one of the above.

9. Each QUIC report includes at least one QUIC traffic parameter of the QUIC traffic, at least one QUIC report event associated with the QUIC report, or at least one statistical value of the QUIC traffic associated with the QUIC report The wireless communication method according to any one of claims 6 to 8, including at least one of the above.

10. The at least one QUIC traffic parameter includes a QUIC protocol indication associated with the QUIC traffic, the Internet protocol (IP) address of a wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic The wireless communication method according to claim 9, including at least one of the above.

11. A wireless communication method for use in a session management function, comprising: sending information on Quick User Datagram Protocol Internet Connections (QUIC) traffic to a policy control function; and receiving, from the policy control function, a policy and charging control (PCC) rule determined for a QUIC application based on the information on the QUIC traffic and including A wireless communication method, wherein the QUIC information includes at least one event associated with the information of the QUIC traffic and / or statistical values of the QUIC traffic. **Claim 12** The at least one event associated with the information of the QUIC traffic is an event associated with QUIC traffic detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of QUIC data block transmission, or an event associated with the end of QUIC data block transmission The wireless communication method according to claim 11, including at least one of the above. **Claim 13** The statistical values of the QUIC traffic are the average delay of QUIC traffic transmission, the maximum delay of QUIC traffic transmission, the minimum delay of QUIC traffic transmission, the average size of QUIC data blocks, the maximum size of QUIC data blocks, the minimum size of QUIC data blocks, the average interval between every two consecutive QUIC traffic transmissions, or an analysis period indicating the period during which QUIC traffic characteristics used to determine the information of the QUIC traffic are collected The wireless communication method according to claim 11 or 12, including at least one of the above. **Claim 14** The information of the QUIC traffic is a QUIC protocol indication associated with the QUIC traffic, the Internet protocol (IP) address of a wireless terminal associated with the QUIC traffic and the user datagram protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC traffic and the UDP port associated with the remote server, at least one QUIC connection identifier of the QUIC traffic, the QUIC version of the QUIC traffic, or the packet number of the QUIC traffic The wireless communication method according to any one of claims 11 to 13, further including at least one QUIC traffic parameter including at least one of the above. **Claim 15** The PCC rules are QUIC application information, QUIC connection information, or at least one QUIC flow parameter The wireless communication method according to any one of claims 11 to 14, including at least one of them.

16. The QUIC application information includes the application identifier of the QUIC application, the application service type of the QUIC application, or the identifier of the wireless terminal associated with the QUIC application The wireless communication method according to claim 15, including at least one of them.

17. The QUIC connection information includes at least one QUIC connection identifier of the QUIC application, the Internet Protocol (IP) address of the wireless terminal associated with the QUIC application and the UDP port associated with the wireless terminal, or the IP address of the remote server associated with the QUIC application and the UDP port associated with the remote server The wireless communication method according to claim 15 or 16, including at least one of them.

18. The at least one QUIC flow parameter includes a Quality of Service (QoS) flow identifier, an allocation and retention priority, an Average Maximum Bit Rate (AMBR), or a Guaranteed Bit Rate (GBR) The wireless communication method according to any one of claims 15 to 17, including at least one of them.

19. The at least one QUIC flow parameter includes the highest AMBR, the lowest AMBR, the highest GBR, or the lowest GBR The wireless communication method according to any one of claims 15 to 18, including at least one of them.

20. The at least one QUIC flow parameter includes a list of a QUIC packet number range and the AMBR corresponding to the QUIC packet number range, or a list of a QUIC packet number range and the GBR corresponding to the QUIC packet number range The wireless communication method according to any one of claims 15 to 19, including at least one of them.

21. A wireless communication method for use in a policy control function, Receiving information on Quick User Datagram Protocol Internet Connections (QUIC) traffic from a session management function; Sending, to the session management function, a policy and charging control (PCC) rule determined for a QUIC application based on the information on the QUIC traffic; and The QUIC information includes at least one event associated with the information on the QUIC traffic and / or statistics of the QUIC traffic. A wireless communication method.

22. The at least one event associated with the information on the QUIC traffic is An event associated with QUIC traffic detection, An event associated with QUIC connection establishment, An event associated with QUIC connection release, An event associated with the start of QUIC data block transmission, or An event associated with the end of QUIC data block transmission The wireless communication method according to claim 21, including at least one of them.

23. The statistics of the QUIC traffic are The average delay of QUIC traffic transmission, The maximum delay of QUIC traffic transmission, The minimum delay of QUIC traffic transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data block, the average interval between every two consecutive QUIC traffic transmissions, or An analysis period indicating a period during which QUIC traffic characteristics used to determine the information on the QUIC traffic are collected The wireless communication method according to claim 21 or 22, including at least one of them.

24. The information on the QUIC traffic is A QUIC protocol indication associated with the QUIC traffic, The Internet protocol (IP) address of a wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with the wireless terminal The IP address of the remote server associated with the QUIC traffic and the UDP port associated with the remote server, At least one QUIC connection identifier of the QUIC traffic, The QUIC version of the QUIC traffic, or The packet number of the QUIC traffic The wireless communication method according to any one of claims 21 to 23, further comprising at least one QUIC traffic parameter including at least one of the above.

25. The PCC rule is QUIC application information, QUIC connection information, or At least one QUIC flow parameter The wireless communication method according to any one of claims 21 to 24, including at least one of the above.

26. The QUIC application information is The application identifier of the QUIC application, The application service type of the QUIC application, or The identifier of the wireless terminal associated with the QUIC application The wireless communication method according to claim 25, including at least one of the above.

27. The QUIC connection information is At least one QUIC connection identifier of the QUIC application, The Internet Protocol (IP) address of the wireless terminal associated with the QUIC application and the UDP port associated with the wireless terminal, or The IP address of the remote server associated with the QUIC application and the UDP port associated with the remote server The wireless communication method according to claim 25 or 26, including at least one of the above.

28. The at least one QUIC flow parameter is Quality of Service (QoS) flow identifier, Allocation and retention priority, Average Maximum Bit Rate (AMBR) or Guaranteed Bit Rate (GBR) The wireless communication method according to any one of claims 25 to 27, including at least one of the above.

29. The at least one QUIC flow parameter is The highest AMBR, The lowest AMBR, The highest GBR, or The lowest GBR The wireless communication method according to any one of claims 25 to 28, including at least one of the above.

30. The at least one QUIC flow parameter is a list of a QUIC packet number range and an AMBR corresponding to the QUIC packet number range, or a list of a QUIC packet number range and a GBR corresponding to the QUIC packet number range The wireless communication method according to any one of claims 25 to 29, including at least one of the above.

31. Transmitting a QUIC support request including the information of the QUIC traffic to a network data analysis function; Receiving QUIC support information associated with the QUIC traffic from the network data analysis function further including The wireless communication method according to any one of claims 21 to 30, wherein the PCC rule is determined based on the QUIC support information.

32. The QUIC support information is an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, at least one QoS policy for the QUIC traffic, or at least one QUIC packet number range corresponding to the at least one QoS policy The wireless communication method according to claim 31, including at least one of the above.

33. Transmitting a policy approval notice including the information of the QUIC traffic to an application function; Receiving application service information associated with the QUIC traffic from the application function, wherein the PCC rule is determined based on the application service information further including The wireless communication method according to any one of claims 21 to 32.

34. The application service information is an application service type associated with the QUIC traffic, an application identifier associated with the QUIC traffic, an identifier of a wireless terminal associated with the QUIC traffic, an Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and a User Datagram Protocol (UDP) port associated with the wireless terminal, an IP address of a remote server associated with the QUIC traffic and a UDP port associated with the remote server, or At least one QoS policy for the QUIC traffic The wireless communication method according to claim 33, including at least one of them.

35. A wireless communication method for use in a network data analysis function, comprising: Receiving, from a policy control function, a QUIC support request including information on Quick User Datagram Protocol Internet Connections (QUIC) traffic; Transmitting, to the policy control function, QUIC support information associated with the QUIC traffic; Including The wireless communication method, wherein the QUIC information includes at least one event associated with the information of the QUIC traffic and / or statistical values of the QUIC traffic.

36. The at least one event associated with the information of the QUIC traffic is An event associated with QUIC traffic detection, An event associated with QUIC connection establishment, An event associated with QUIC connection release, An event associated with the start of QUIC data block transmission, or An event associated with the end of QUIC data block transmission The wireless communication method according to claim 35, including at least one of them.

37. The statistical values of the QUIC traffic are The average delay of QUIC traffic transmission, The maximum delay of QUIC traffic transmission, The minimum delay of QUIC traffic transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data block, the average interval between every two consecutive QUIC traffic transmissions, or An analysis period indicating a period during which QUIC traffic characteristics used to determine the information of the QUIC traffic are collected The wireless communication method according to claim 35 or 36, including at least one of them.

38. The information of the QUIC traffic is A QUIC protocol instruction associated with the QUIC traffic The Internet Protocol (IP) address of the wireless terminal associated with the QUIC traffic and the User Datagram Protocol (UDP) port associated with the wireless terminal, The IP address of the remote server associated with the QUIC traffic and the UDP port associated with the remote server, At least one QUIC connection identifier of the QUIC traffic, The QUIC version of the QUIC traffic, or The packet number of the QUIC traffic The wireless communication method according to any one of claims 35 to 37, further comprising at least one QUIC traffic parameter including at least one of the above.

39. The QUIC support information includes The application service type associated with the QUIC traffic, The application identifier associated with the QUIC traffic, At least one QoS policy for the QUIC traffic, or At least one QUIC packet number range corresponding to the at least one QoS policy The wireless communication method according to any one of claims 35 to 38, including at least one of the above.

40. A wireless communication method for use in an application function, comprising: Receiving, from a policy control function, a policy approval notification including information on Quick User Datagram Protocol Internet Connections (QUIC) traffic; and Transmitting, to the policy control function, application service information associated with the QUIC traffic including The wireless communication method, wherein the QUIC information includes at least one event associated with the information of the QUIC traffic and / or the statistical value of the QUIC traffic.

41. The at least one event associated with the information of the QUIC traffic includes An event associated with QUIC traffic detection, An event associated with QUIC connection establishment, An event associated with QUIC connection release, An event associated with the start of QUIC data block transmission, or Events associated with the end of QUIC data block transmission The wireless communication method according to claim 40, comprising at least one of them.

42. The statistical value of the QUIC traffic is The average delay of QUIC traffic transmission The maximum delay of QUIC traffic transmission The minimum delay of QUIC traffic transmission The average size of a QUIC data block The maximum size of a QUIC data block The minimum size of a QUIC data block, the average interval between every two consecutive QUIC traffic transmissions, or The analysis period indicating the period during which the QUIC traffic characteristics used to determine the information of the QUIC traffic are collected The wireless communication method according to claim 40 or 41, comprising at least one of them.

43. The information of the QUIC traffic is The QUIC protocol instruction associated with the QUIC traffic The Internet protocol (IP) address of the wireless terminal associated with the QUIC traffic and the user datagram protocol (UDP) port associated with the wireless terminal The IP address of the remote server associated with the QUIC traffic and the UDP port associated with the remote server At least one QUIC connection identifier of the QUIC traffic The QUIC version of the QUIC traffic, or The packet number of the QUIC traffic The wireless communication method according to any one of claims 40 to 42, further comprising at least one QUIC traffic parameter including at least one of them.

44. The application service information is The application service type associated with the QUIC traffic The application identifier associated with the QUIC traffic The identifier of the wireless terminal associated with the QUIC traffic The Internet protocol (IP) address of the wireless terminal associated with the QUIC traffic and the user datagram protocol (UDP) port associated with the wireless terminal The IP address of the remote server associated with the QUIC traffic and the UDP port associated with the remote server, or At least one QoS policy for the QUIC traffic The wireless communication method according to any one of claims 40 to 43, including at least one of them.

45. To the user plane function, so as to send a Quick User Datagram Protocol Internet Connections (QUIC) traffic command, and From the user plane function, so as to receive at least one QUIC report associated with the QUIC traffic A communication unit configured to include The QUIC traffic command includes at least one of a QUIC event report command for instructing at least one event associated with the at least one QUIC report, or a QUIC statistical value report command for instructing at least one statistical value included in each QUIC report, a session management node.

46. The session management node according to claim 45, further comprising a processor configured to implement the wireless communication method according to any one of claims 2 to 5.

47. From the session management function, so as to receive a Quick User Datagram Protocol Internet Connections (QUIC) traffic command, and To the session management function, so as to send at least one QUIC report associated with the QUIC traffic A communication unit configured to include The QUIC traffic command includes at least one of a QUIC event report command for instructing at least one event associated with the at least one QUIC report, or a QUIC statistical value report command for instructing at least one statistical value included in each QUIC report, a user plane node.

48. The user plane node according to claim 47, further comprising a processor configured to implement the wireless communication method according to any one of claims 7 to 10.

49. configured to cause a policy control function to transmit information on Quick User Datagram Protocol Internet Connections (QUIC) traffic, and configured to cause the policy control function to receive, from the policy control function, a policy and charging control (PCC) rule determined for a QUIC application based on the information on the QUIC traffic, a communication unit, a session management node, wherein the QUIC information includes at least one event associated with the information on the QUIC traffic and / or a statistic of the QUIC traffic.

50. The session management node according to claim 49, further comprising a processor configured to implement the wireless communication method according to any one of claims 12 to 20.

51. configured to cause a session management function to receive information on Quick User Datagram Protocol Internet Connections (QUIC) traffic, and configured to cause the session management function to transmit, to the session management function, a policy and charging control (PCC) rule determined for a QUIC application based on the information on the QUIC traffic, a communication unit, a policy control node, wherein the QUIC information includes at least one event associated with the information on the QUIC traffic and / or a statistic of the QUIC traffic.

52. The policy control node according to claim 51, further comprising a processor configured to implement the wireless communication method according to any one of claims 22 to 34.

53. configured to cause a policy control function to receive a QUIC assistance request including information on Quick User Datagram Protocol Internet Connections (QUIC) traffic, and configured to cause the policy control function to transmit QUIC assistance information associated with the QUIC traffic, a communication unit, A network data analysis node, wherein the QUIC information includes at least one event associated with the information of the QUIC traffic and / or the statistical value of the QUIC traffic.

54. The network data analysis node according to claim 53, further comprising a processor configured to implement the wireless communication method according to any one of claims 36 to 39.

55. Receiving, from a policy control function, a policy approval notification including information on Quick User Datagram Protocol Internet Connections (QUIC) traffic, and Transmitting, to the policy control function, application service information associated with the QUIC traffic A communication unit configured as such, An application node, wherein the QUIC information includes at least one event associated with the information of the QUIC traffic and / or the statistical value of the QUIC traffic.

56. The application node according to claim 55, further comprising a processor configured to implement the wireless communication method according to any one of claims 41 to 44.

57. A computer program product, including computer-readable program media code stored therein, wherein when the code is executed by a processor, the processor is caused to implement the wireless communication method according to any one of claims 1 to 44.

Images