Policy enhancements for fast user datagram protocol international connection applications

Abstract

A wireless communication method for use in a session management function is disclosed. The method includes sending a Fast User Datagram Protocol Internet Connection (QUIC) data instruction to a user plane function, and receiving at least one QUIC report associated with QUIC data from the user plane function, where the QUIC data instruction includes at least one of a QUIC event reporting instruction or a QUIC statistical reporting instruction, and where the QUIC data instruction includes at least one of a QUIC event reporting instruction and a QUIC statistical reporting instruction. The QUIC event reporting instruction indicates one event associated with at least one QUIC report, and the QUIC statistics reporting instruction indicates at least one statistics included in each QUIC report.

Description

Technical Field

[0001] The present application is directed generally to wireless communications, and in particular to QUIC (Quick User Datagram Protocol (UDP) International Connections) communications. Background Art

[0002] In recent years, the QUIC protocol has been rapidly developing for establishing international connections between two endpoints. It is considered to be the next generation protocol for HTTP (Hypertext Transfer Protocol). In other words, the QUIC protocol can be used to replace the existing TCP (Transmission Control Protocol) + TLS (Transport Layer Security) + HTTP protocols.

[0003] A QUIC connection is a secure connection between two endpoints (e.g., a UE (User Equipment) and the UE's application server) that prohibits transmission nodes in the network from inspecting the content transmitted in the QUIC connection.

[0004] Currently, the 5G packet inspection and forwarding model can only detect QUIC data from other TCP / UDP services. It is difficult for the network to identify which service or application the QUIC data is related to. Therefore, it may not be possible to generate appropriate policies to be applied to the corresponding QUIC data.

[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, flexible QoS requirements may not be possible for QUIC data transmission because QUIC data transmission is encrypted and the internal payload within a QUIC packet may have significantly different QoS requirements. Summary of the invention

[0006] The present application relates to methods, systems and devices for QUIC communications, and in particular to methods, systems and devices associated with policies for QUIC applications.

[0007] The present disclosure relates to a wireless communication method used in a session management function. The method comprises:

[0008] sending Quick User Datagram Protocol Internet Connection (QUIC) data instructions to the user plane function, and

[0009] receiving at least one QUIC report associated with the QUIC data from a user plane function,

[0010] The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with the at least one QUIC report, and the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

[0011] Various embodiments may preferably implement the following features:

[0012] Preferably, the at least one event associated with the at least one QUIC report comprises at least one of the following events:

[0013] Events associated with QUIC data detection,

[0014] Events associated with QUIC connection establishment,

[0015] Events associated with QUIC connection release,

[0016] An event associated with the start of transmission of a QUIC data chunk, or

[0017] Event associated with the end of transmission of a QUIC data chunk.

[0018] Preferably, the at least one statistic included in each QUIC report comprises at least one of the following:

[0019] The average latency of QUIC data transmission,

[0020] The maximum latency of QUIC data transmission,

[0021] Minimum latency for QUIC data transmission,

[0022] The average size of a QUIC data block,

[0023] The maximum size of a QUIC data block,

[0024] The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or

[0025] Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

[0026] Preferably, each QUIC report includes at least one of the following:

[0027] at least one QUIC data parameter for the QUIC data,

[0028] at least one QUIC reporting event associated with a QUIC report, or

[0029] At least one statistic of QUIC data associated with a QUIC report.

[0030] Preferably, the at least one QUIC data parameter includes at least one of the following:

[0031] The QUIC protocol indication associated with the QUIC data,

[0032] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0033] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server,

[0034] at least one QUIC connection identifier for the QUIC data,

[0035] The QUIC version of the QUIC data, or

[0036] The packet number of the QUIC data.

[0037] The present disclosure relates to a wireless communication method used in a user plane function. The method comprises:

[0038] receiving a Quick User Datagram Protocol Internet Connection (QUIC) data instruction from a session management function, and

[0039] sending at least one QUIC report associated with the QUIC data to a session management function,

[0040] The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with at least one QUIC report, and the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

[0041] Various embodiments may preferably implement the following features:

[0042] Preferably, the at least one event associated with the at least one QUIC report comprises at least one of the following events:

[0043] Events associated with QUIC data detection,

[0044] Events associated with QUIC connection establishment,

[0045] Events associated with QUIC connection release,

[0046] An event associated with the start of transmission of a QUIC data chunk, or

[0047] Event associated with the end of transmission of a QUIC data chunk.

[0048] Preferably, the at least one statistic included in each QUIC report comprises at least one of the following:

[0049] The average latency of QUIC data transmission,

[0050] The maximum latency of QUIC data transmission,

[0051] Minimum latency for QUIC data transmission,

[0052] The average size of a QUIC data block,

[0053] The maximum size of a QUIC data block,

[0054] The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or

[0055] Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

[0056] Preferably, each QUIC report includes at least one of the following:

[0057] at least one QUIC data parameter for the QUIC data,

[0058] at least one QUIC reporting event associated with a QUIC report, or

[0059] At least one statistic of QUIC data associated with a QUIC report.

[0060] Preferably, the at least one QUIC data parameter includes at least one of the following:

[0061] The QUIC protocol indication associated with the QUIC data,

[0062] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0063] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server,

[0064] at least one QUIC connection identifier for the QUIC data,

[0065] The QUIC version of the QUIC data, or

[0066] The packet number of the QUIC data.

[0067] The present disclosure relates to a wireless communication method used in a session management function. The method comprises:

[0068] information to send Quick User Datagram Protocol Internet Connection (QUIC) data to a policy control function, and

[0069] receiving, from a policy control function, a policy and charging control (PCC) rule determined based on information of the QUIC data for the QUIC application,

[0070] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0071] Various embodiments may preferably implement the following features:

[0072] Preferably, the at least one event associated with the at least one QUIC report comprises at least one of the following events:

[0073] Events associated with QUIC data detection,

[0074] Events associated with QUIC connection establishment,

[0075] Events associated with QUIC connection release,

[0076] An event associated with the start of transmission of a QUIC data chunk, or

[0077] Event associated with the end of transmission of a QUIC data chunk.

[0078] Preferably, the at least one statistic included in each QUIC report comprises at least one of the following:

[0079] The average latency of QUIC data transmission,

[0080] The maximum latency of QUIC data transmission,

[0081] Minimum latency for QUIC data transmission,

[0082] The average size of a QUIC data block,

[0083] The maximum size of a QUIC data block,

[0084] The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or

[0085] Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

[0086] Preferably, the QUIC data information further includes at least one QUIC data parameter, and the QUIC data parameter includes at least one of the following:

[0087] The QUIC protocol indication associated with the QUIC data,

[0088] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0089] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server,

[0090] at least one QUIC connection identifier for the QUIC data,

[0091] The QUIC version of the QUIC data, or

[0092] The packet number of the QUIC data.

[0093] Preferably, the PCC rule includes at least one of the following:

[0094] QUIC application information,

[0095] QUIC connection information, or

[0096] At least one QUIC stream parameter.

[0097] Preferably, the QUIC application information includes at least one of the following:

[0098] The application identifier of the QUIC application,

[0099] The application service type of the QUIC application, or

[0100] An identifier of a wireless terminal associated with a QUIC application.

[0101] Preferably, the QUIC connection information includes at least one of the following:

[0102] at least one QUIC connection identifier for the QUIC application,

[0103] The Internet Protocol (IP) address of the wireless terminal associated with the QUIC application and the UDP port associated with the wireless terminal, or

[0104] The IP address of the remote server associated with the QUIC application and the UDP port associated with the remote server.

[0105] Preferably, the at least one QUIC stream parameter includes at least one of the following:

[0106] Quality of Service (QoS) flow identifier,

[0107] Assign and retain priorities,

[0108] Average Maximum Bit Rate (AMBR), or

[0109] Guaranteed Bit Rate (GBR).

[0110] Preferably, the at least one QUIC stream parameter includes at least one of the following:

[0111] Highest AMBR,

[0112] Minimum AMBR,

[0113] Highest GBR, or

[0114] Minimum GBR.

[0115] Preferably, the at least one QUIC stream parameter includes at least one of the following:

[0116] a list of QUIC packet number ranges and the AMBRs that correspond to those QUIC packet number ranges, or

[0117] A list of QUIC packet number ranges and the GBRs that correspond to those QUIC packet number ranges.

[0118] The present disclosure relates to a wireless communication method used in a policy control function. The method comprises:

[0119] receiving information about Quick User Datagram Protocol Internet Connections (QUIC) data from a session management function, and

[0120] sending, to a session management function, policy and charging control (PCC) rules determined based on information about the QUIC data for the QUIC application,

[0121] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0122] Various embodiments may preferably implement the following features:

[0123] Preferably, the at least one event associated with the at least one QUIC report comprises at least one of the following events:

[0124] Events associated with QUIC data detection,

[0125] Events associated with QUIC connection establishment,

[0126] Events associated with QUIC connection release,

[0127] An event associated with the start of transmission of a QUIC data chunk, or

[0128] Event associated with the end of transmission of a QUIC data chunk.

[0129] Preferably, the at least one statistic included in each QUIC report comprises at least one of the following:

[0130] The average latency of QUIC data transmission,

[0131] The maximum latency of QUIC data transmission,

[0132] Minimum latency for QUIC data transmission,

[0133] The average size of a QUIC data block,

[0134] The maximum size of a QUIC data block,

[0135] The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or

[0136] Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

[0137] Preferably, the QUIC data information further includes at least one QUIC data parameter, and the QUIC data parameter includes at least one of the following:

[0138] The QUIC protocol indication associated with the QUIC data,

[0139] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0140] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server,

[0141] at least one QUIC connection identifier for the QUIC data,

[0142] The QUIC version of the QUIC data, or

[0143] The packet number of the QUIC data.

[0144] Preferably, the PCC rule includes at least one of the following:

[0145] QUIC application information,

[0146] QUIC connection information, or

[0147] At least one QUIC stream parameter.

[0148] Preferably, the QUIC application information includes at least one of the following:

[0149] The application identifier of the QUIC application,

[0150] The application service type of the QUIC application, or

[0151] An identifier of a wireless terminal associated with a QUIC application.

[0152] Preferably, the QUIC connection information includes at least one of the following:

[0153] at least one QUIC connection identifier for the QUIC application,

[0154] The Internet Protocol (IP) address of the wireless terminal associated with the QUIC application and the UDP port associated with the wireless terminal, or

[0155] The IP address of the remote server associated with the QUIC application and the UDP port associated with the remote server.

[0156] Preferably, the at least one QUIC stream parameter includes at least one of the following:

[0157] Quality of Service (QoS) flow identifier,

[0158] Assign and retain priorities,

[0159] Average Maximum Bit Rate (AMBR), or

[0160] Guaranteed Bit Rate (GBR).

[0161] Preferably, the at least one QUIC stream parameter includes at least one of the following:

[0162] Highest AMBR,

[0163] Minimum AMBR,

[0164] Highest GBR, or

[0165] Minimum GBR.

[0166] Preferably, the at least one QUIC stream parameter includes at least one of the following:

[0167] a list of QUIC packet number ranges and the AMBRs that correspond to those QUIC packet number ranges, or

[0168] A list of QUIC packet number ranges and the GBRs that correspond to those QUIC packet number ranges.

[0169] Preferably, the wireless communication method further includes:

[0170] sending a QUIC assistance request including information about the QUIC data to the network data analysis function, and

[0171] receiving QUIC ancillary information associated with the QUIC data from the network data analysis function,

[0172] Among them, the PCC rules are determined based on QUIC auxiliary information.

[0173] Preferably, the QUIC assistance information includes at least one of the following:

[0174] The application service type associated with the QUIC data,

[0175] The application identifier associated with the QUIC data,

[0176] At least one QoS policy for QUIC data, or

[0177] At least one QUIC packet number range corresponding to at least one QoS policy.

[0178] Preferably, the wireless communication method further includes:

[0179] Sending a policy authorization notification including the QUIC data to the application function, and

[0180] Application service information associated with QUIC data is received from an application function, wherein PCC rules are determined based on the application service information.

[0181] Preferably, the application service information includes at least one of the following:

[0182] The application service type associated with the QUIC data,

[0183] The application identifier associated with the QUIC data,

[0184] an identifier of the wireless terminal associated with the QUIC data,

[0185] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0186] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server, or

[0187] At least one QoS policy for QUIC data.

[0188] The present disclosure relates to a wireless communication method used in a network data analysis function, the method comprising:

[0189] receiving, from a policy control function, a QUIC assistance request including information of Quick User Datagram Protocol Internet Connection (QUIC) data, and

[0190] Send QUIC ancillary information associated with the QUIC data to the policy control function,

[0191] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0192] Various embodiments may preferably implement the following features:

[0193] Preferably, the at least one event associated with the at least one QUIC report comprises at least one of the following events:

[0194] Events associated with QUIC data detection,

[0195] Events associated with QUIC connection establishment,

[0196] Events associated with QUIC connection release,

[0197] An event associated with the start of transmission of a QUIC data chunk, or

[0198] Event associated with the end of transmission of a QUIC data chunk.

[0199] Preferably, the at least one statistic included in each QUIC report comprises at least one of the following:

[0200] The average latency of QUIC data transmission,

[0201] The maximum latency of QUIC data transmission,

[0202] Minimum latency for QUIC data transmission,

[0203] The average size of a QUIC data block,

[0204] The maximum size of a QUIC data block,

[0205] The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or

[0206] Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

[0207] Preferably, the QUIC data information further includes at least one QUIC data parameter, and the QUIC data parameter includes at least one of the following:

[0208] The QUIC protocol indication associated with the QUIC data,

[0209] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0210] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server,

[0211] at least one QUIC connection identifier for the QUIC data,

[0212] The QUIC version of the QUIC data, or

[0213] The packet number of the QUIC data.

[0214] Preferably, the QUIC assistance information includes at least one of the following:

[0215] The application service type associated with the QUIC data,

[0216] The application identifier associated with the QUIC data,

[0217] At least one QoS policy for QUIC data, or

[0218] At least one QUIC packet number range corresponding to at least one QoS policy.

[0219] The present disclosure relates to a wireless communication method used in an application function. The method comprises:

[0220] receiving a policy authorization notification including Quick User Datagram Protocol Internet Connection (QUIC) data information from a policy control function, and

[0221] Send application service information associated with the QUIC data to the policy control function,

[0222] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0223] Various embodiments may preferably implement the following features:

[0224] Preferably, the at least one event associated with the at least one QUIC report comprises at least one of the following events:

[0225] Events associated with QUIC data detection,

[0226] Events associated with QUIC connection establishment,

[0227] Events associated with QUIC connection release,

[0228] An event associated with the start of transmission of a QUIC data chunk, or

[0229] Event associated with the end of transmission of a QUIC data chunk.

[0230] Preferably, the at least one statistic included in each QUIC report comprises at least one of the following:

[0231] The average latency of QUIC data transmission,

[0232] The maximum latency of QUIC data transmission,

[0233] Minimum latency for QUIC data transmission,

[0234] The average size of a QUIC data block,

[0235] The maximum size of a QUIC data block,

[0236] The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or

[0237] Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

[0238] Preferably, the QUIC data information further includes at least one QUIC data parameter, and the QUIC data parameter includes at least one of the following:

[0239] The QUIC protocol indication associated with the QUIC data,

[0240] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0241] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server,

[0242] at least one QUIC connection identifier for the QUIC data,

[0243] The QUIC version of the QUIC data, or

[0244] The packet number of the QUIC data.

[0245] Preferably, the application service information includes at least one of the following:

[0246] The application service type associated with the QUIC data,

[0247] The application identifier associated with the QUIC data,

[0248] an identifier of the wireless terminal associated with the QUIC data,

[0249] an Internet Protocol (IP) address of the wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal,

[0250] The IP address of the remote server associated with the QUIC data and the UDP port associated with the remote server, or

[0251] At least one QoS policy for QUIC data.

[0252] The present disclosure relates to a session management node. The session management node includes:

[0253] A communication unit, wherein the communication unit is configured to:

[0254] sending Quick User Datagram Protocol Internet Connection (QUIC) data instructions to the user plane function, and

[0255] receiving at least one QUIC report associated with the QUIC data from a user plane function,

[0256] The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with at least one QUIC report, or the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

[0257] Various embodiments may preferably implement the following features:

[0258] Preferably, the session management node further includes a processor, and the processor is configured to execute any one of the above wireless communication methods.

[0259] The present disclosure relates to a user plane node. The user plane node includes:

[0260] A communication unit, the communication unit being configured to:

[0261] receiving a Quick User Datagram Protocol Internet Connection (QUIC) data instruction from a session management function, and

[0262] sending at least one QUIC report associated with the QUIC data to a session management function,

[0263] The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with at least one QUIC report, and the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

[0264] Various embodiments may preferably implement the following features:

[0265] Preferably, the user plane node further comprises a processor, and the processor is configured to execute any one of the above wireless communication methods.

[0266] The present disclosure relates to a session management node. The session management node includes:

[0267] A communication unit, the communication unit being configured to:

[0268] sending Quick User Datagram Protocol Internet Connection (QUIC) data to a policy control function, and

[0269] receiving, from a policy control function, a policy and charging control (PCC) rule determined based on information of the QUIC data for the QUIC application,

[0270] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0271] Various embodiments may preferably implement the following features:

[0272] Preferably, the session management node further includes a processor, and the processor is configured to execute any one of the above wireless communication methods.

[0273] The present disclosure relates to a policy control node. The policy control node includes:

[0274] A communication unit, the communication unit being configured to:

[0275] receiving Quick User Datagram Protocol Internet Connections (QUIC) data from a session management function, and

[0276] sending, to a session management function, policy and charging control (PCC) rules determined based on information about the QUIC data for the QUIC application,

[0277] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0278] Various embodiments may preferably implement the following features:

[0279] Preferably, the policy control node further comprises a processor, and the processor is configured to execute any one of the above wireless communication methods.

[0280] The present disclosure relates to a network data analysis node. The network data analysis node includes:

[0281] A communication unit, the communication unit being configured to:

[0282] receiving, from a policy control function, a QUIC assistance request including information of Quick User Datagram Protocol Internet Connection (QUIC) data, and

[0283] Send QUIC ancillary information associated with the QUIC data to the policy control function,

[0284] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0285] Various embodiments may preferably implement the following features:

[0286] Preferably, the network data analysis node further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0287] The present disclosure relates to an application node. The application node includes:

[0288] A communication unit, the communication unit being configured to:

[0289] receiving a policy authorization notification including Quick User Datagram Protocol Internet Connection (QUIC) data information from a policy control function, and

[0290] Send application service information associated with the QUIC data to the policy control function,

[0291] The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

[0292] Various embodiments may preferably implement the following features:

[0293] Preferably, the application node further includes a processor, and the processor is configured to execute any one of the above wireless communication methods.

[0294] The present disclosure relates to a computer program product, which includes a computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the wireless communication method described in any one of the aforementioned methods.

[0295] The exemplary embodiments disclosed herein are intended to provide features that will become 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 should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0296] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of the steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of the steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Therefore, it should be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, the present disclosure is not limited to the specific order or hierarchy presented.

[0297] The above and other aspects and embodiments thereof will be described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0299] Figure 2 A schematic diagram of a PDU session establishment process according to an embodiment of the present disclosure is shown.

[0300] Figure 3 A schematic diagram of establishing a PFCP session according to an embodiment of the present disclosure is shown.

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

[0302] Figure 5 A schematic diagram of the QUIC data processing process according to an embodiment of the present disclosure is shown.

[0303] Figure 6A schematic diagram of the acquisition strategy and charging control rules of the QUIC application according to an embodiment of the present disclosure is shown.

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

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

[0306] Figures 9 to 14 A flow chart of a method according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0307] In order to enable the network to correctly formulate policy rules for QUIC applications, the present disclosure discloses a method of enhancing UPF to report QUIC data characteristics associated with QUIC data detection. Therefore, the network can be able to identify the services and / or applications related to the QUIC data and determine the accurate policy rules for processing the QUIC data accordingly.

[0308] Figure 1 A schematic diagram of a 5G network (architecture) according to an embodiment of the present disclosure is shown. Figure 1 The network shown includes the following network entities or network functions (NF):

[0309] 1. UE (User Equipment):

[0310] UE refers to a mobile terminal that accesses the 5G network.

[0311] 2. NG RAN (Next Generation Radio Access Network):

[0312] In a 5G network, NG RAN is a new radio (NR) base station and is also referred to as gNB. In addition, in the present disclosure, NG RAN may be equal to RAN (node).

[0313] 3. AMF (Access and Mobility Management Function):

[0314] AMF provides access management and mobility management for UE. For example, AMF can provide network registration, registration during UE mobility, etc.

[0315] 4. SMF (Session Management Function):

[0316] SMF provides PDU session management for UE, such as IP address allocation, QoS flow setting, etc.

[0317] 5. UPF (User Plane Function)

[0318] UPF provides IP service routing and forwarding management.

[0319] 6. PCF (Policy Control Function)

[0320] The PCF provides QoS policy rules to the control plane (network) functions to enforce these rules.

[0321] 7. AF (application function):

[0322] The AF provides instructions to the PCF to affect QoS policy rules.

[0323] 8. NWDAF (Network Data Analysis Function)

[0324] NWDAF collects network events from one or more other NFs (e.g., AMF, SMF, PCF, UPF, etc.) and analyzes network behavior and status, for example, by using artificial intelligence and / or machine learning.

[0325] In 5G networks, data service transmission is controlled by SMF and UPF. The SMF control plane function (CP function) for data service control handles the signaling aspects of data service transmission (e.g., PDU session establishment / modification / release, N4 session establishment / change / release, N4 rule generation, etc.). The UPF user plane function (UP function) for data service control handles the user plane aspects of data service transmission (e.g., service detection, service filtering, and service forwarding, usage reporting, etc.) based on one or more instructions (e.g., N4 rules) received from the SMF.

[0326] After the UE registers with the 5G network, if communication with the application server is required, the UE requests a PDU session establishment procedure toward the 5G network. During the PDU session establishment procedure, the 5G network allocates a default QoS flow to the UE, and may additionally allocate an indicated QoS flow to the UE based on the UE request or based on instructions from a policy configured for the UE.

[0327] Figure 2 FIG. 1 is a schematic diagram showing a PDU session establishment process according to an embodiment of the present disclosure. Figure 2 In the process, SMF allocates a set of QoS flows to ensure the communication between UE and application server.

[0328] Specifically, after the UE registers to the 5G network, the UE can request a PDU session establishment process, which includes the following steps:

[0329] Step 201: UE to AMF: NAS message (one or more S-NSSAI, DNN requested by UE, PDU session ID, request type, N1 SM container (PDU session establishment request)).

[0330] The PDU Session Establishment Request is included in a NAS message and is encapsulated in an N1 SM container. The NAS message sent by the UE is encapsulated by the RAN in an N2 message to the AMF.

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

[0332] Step 203: AMF to SMF: Nsmf_PDUSession_CreateSMContext request (SUPI, selected DNN, DNN requested by UE, one or more 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).

[0333] SUPI (Subscription Permanent Identifier) ​​uniquely identifies the UE subscription. AMF ID carries the GUAMI (Globally Unique AMF ID) that uniquely identifies the AMF serving the UE.

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

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

[0336] Step 206: SMF sends a Npcf_PolicyAssociation_Create request to PCF to perform the SM policy association establishment process and obtain the default PCC rules for the PDU session. The request should provide necessary parameters such as SUPI, PDU session ID, DNN, S-NSSAI. Other parameters such as GPSI, UE IP address, UE external ID, RAT type, access type, etc. can also be provided in the request message.

[0337] 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 allows the AF to dynamically influence the service model of the PDU session via the PCF, for example, to establish a new dedicated QoS flow, or to modify an existing QoS flow.

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

[0339] Step 209: The SMF selects the UPF that acts as the PDU Session Anchor (PSA).

[0340] Step 210: SMF sends an N4 session establishment request to UPF to request the establishment of an N4 session for the PDU session, and carries a set of N4 rules for packet detection and QoS enhancement to be installed in UPF. The N4 rules include packet detection rules (PDR), forwarding action rules (FAR), QoS enhancement rules (QER), usage report rules (URR), etc.

[0341] If 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) accordingly to reflect the determined QoS flows.

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

[0343] Step 211: UPF confirms by sending N4 Session Establishment Response.

[0344] Step 212: SMF to AMF: Namf_Communication_N1N2MessageTransfer Request (PDU Session ID, N2 SM Information (PDU Session ID, one or more QFIs, one or more QoS profiles, N3 CN Tunnel Information), N1SM Container (PDU Session Establishment Accept)).

[0345] The N2 SM message carries the information that the AMF should forward to the RAN, including the N3 CN tunnel information carrying the I-UPF UL F-TEID, the QFI and QoS profile used by the RAN to establish the QoS flow.

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

[0347] A typical QoS profile has the following parameters:

[0348] -QFI, which is used to uniquely identify a QoS flow in a PDU session;

[0349] - ARP, which indicates the allocation and retention priority of QoS flows;

[0350] -GBR QoS flow parameters, used by RAN to control QoS flows, such as 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, etc.

[0351] The N1 SM container contains the PDU session establishment acceptance that the AMF should provide to the UE. The PDU session establishment acceptance includes the following parameters: PDU session ID, PDU session type, UE IP address, one or more QoS rules, QoS flow level QoS parameters associated with these one or more QoS rules, DNN, s-NSSAI, etc.

[0352] Step 213: AMF to RAN: N2 PDU Session Request (N2 SM Information, NAS Message (PDU Session ID, N1 SM Container (PDU Session Establishment Accept))). The AMF sends a NAS message to the RAN within the N2 PDU Session Request, which contains the PDU Session ID and PDU Session Establishment Accept for the UE, as well as the N2 SM information received from the SMF.

[0353] Step 214: RAN to UE: The RAN may initiate specific signaling exchanges with the UE that are related to the information received from the SMF. For example, in the case of a 3GPP RAN, an RRC connection reconfiguration may occur as the UE establishes the necessary RAN resources associated with the QoS rules requested for the PDU session. The RAN forwards the NAS message (PDU Session ID, N1 SM Container (PDU Session Establishment Accept)) to the UE. The RAN also allocates AN N3 tunnel information for the PDU session.

[0354] Step 215: RAN to AMF: N2 PDU Session Response (PDU Session ID, cause, N2 SM information (PDU Session ID, AN Tunnel Information, list of one or more QFIs accepted / rejected)).

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

[0356] Step 216: AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (N2SM information).

[0357] The AMF forwards the N2 SM information received from the RAN to the SMF. If a list of rejected QFI(s) is included in the N2 SM information, the SMF shall release the QoS profile associated with the rejected QFI(s).

[0358] Step 217: SMF sends an N4 session modification request to UPF. SMF provides RAN tunnel information to UPF, possibly together with updated N4 rules.

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

[0360] Step 219: SMF sends a Nsmf_PDUSession_UpdateSMContext response to AMF.

[0361] Step 220: The UE initiates uplink traffic transmission, for example, toward its application server, or receives downlink traffic, for example, from its application server.

[0362] During the PDU session establishment process, the SMF may assign a default QoS flow to the UE for the PDU session. The SMF may also assign a dedicated QoS flow for this PDU session if the SMF is instructed by locally configured PCC rules (e.g., PCC rules associated with DNN and S-NSSAI) or by dynamic PCC rules from the PCF.

[0363] To elaborate on the process between SMF and UPF during PDU session establishment (i.e. Figure 2 Steps 210 to 211 in FIG. 1 , Figure 3 The PFCP session establishment process between the SMF and the UPF according to an embodiment of the present disclosure is shown to establish an N4 session.

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

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

[0366] SMF selects appropriate UP functions based on DNN, S-NSSAI and other necessary information.

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

[0368] PDR (Packet Detection Rules) defines packet filters for service data flows, for example, filtering out uplink / downlink traffic from / to a specific application (eg, HTTP messages to a specific website).

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

[0370] A QER (QoS Enforcement Rule) associated with at least one PDR defines how the QoS of the detected service flow is controlled.

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

[0372] The URR (Usage Reporting Rules) associated with at least one PDR defines how the detected volume / time usage of the service flow is reported and how the usage is reported to the CP function.

[0373] Step 303: After receiving the PFCP session establishment request from the SMF, the UPF will install the received rules (ie, PDR / QER / FAR / URR) for this PFCP session.

[0374] Step 304: UPF sends a PFCP session establishment response message back to SMF.

[0375] Step 305: SMF responds to the triggering entity (eg AMF) of PDU session establishment by sending a PDU session establishment response message.

[0376] Step 306: UPF starts detecting uplink / downlink traffic from / to UE and tries to match the received IP data packet with one or more PDRs. If the input IP data packet matches a PDR, the corresponding QER / URR / FAR should be executed.

[0377] Step 307: Later, the UE initiates an uplink service to the server. For example, the UE sends an HTTP request to a dedicated Web server.

[0378] Step 308: UPF checks 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 target to detect the HTTP request from the UE.

[0379] For some IP services (e.g., HTTP services), special operations may need to be performed before the UPF forwards the IP service. For example, the SMF may require HTTP header enrichment.

[0380] Step 309: According to the instruction of the FAR rule, the UPF sends the IP data packet forward. The IP data packet can be modified by the UPF based on the instruction from the SMF, for example, HTTP header enrichment can be performed on HTTP services.

[0381] In the subsequent process, according to the requirements of application service transmission, the UE or PCF can initiate the PDU session modification process to request the SMF to allocate a dedicated QoS flow. The SMF obtains the updated PCC rules from the PCF and allocates the dedicated QoS flow accordingly. Therefore, the SMF sends the N2 SM information to the RAN to update the QFI and QoS profile stored in the RAN, and sends the N1 SM container to the UE to update the QoS flow and QoS rules stored in the UE.

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

[0383] Step 401: The PDU session modification process may be triggered by the events described in steps 401a, 401b and 401c.

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

[0385] Step 401b: The PCF executes the SM policy association modification process initiated by the PCF to notify the SMF of the policy modification. This may be triggered by a policy decision or an AF request, for example, the impact of application functions on service routing.

[0386] Step 401c: The SMF may decide to modify the PDU session. This process may also be triggered based on a locally configured policy, or from the RAN. This process may also be triggered if the UP connection is activated and the SMF has marked one or more QoS flows as deleted in the 5GC but has not yet synchronized with the UE.

[0387] Step 402: If the PCF does not trigger the PDU session modification process, the SMF may initiate the SM policy association modification process toward the PCF. The SMF sends an Npcf_PolicyAssociation_Update request to the PCF to obtain updated QoS rules from the PCF.

[0388] Step 403: For a specific service, the PCF may interact with the AF to update the AF association. The AF may send a dynamic service authorization to the PDU session.

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

[0390] Step 405: SMF sends an N4 session modification request to UPF to request modification of the N4 session for this PDU session, carrying a set of rules for packet detection and QoS enhancement to be installed in UPF. These rules include packet detection rules (PDR), forwarding action rules (FAR), QoS enhancement rules (QER), usage report rules (URR), etc.

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

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

[0393] Step 406: UPF confirms by sending an N4 Session Modification Response.

[0394] Step 407: SMF to AMF: Namf_Communication_N1N2MessageTransfer request (PDU session ID, N2 SM information (one or more PDU session IDs, one or more QFIs, one or more QoS profiles, N3 CN tunnel information), N1 SM container (PDU session modification command)).

[0395] Step 408: 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 to the RAN within the N2 PDU Session Request, which contains the PDU Session ID and PDU Session Modification Command for the UE, as well as the N2 SM information received from the SMF.

[0396] Step 409: RAN to UE: The RAN may initiate a specific signaling exchange with the UE that is related to the information received from the SMF.

[0397] Step 410: RAN to AMF: N2 PDU Session Response (PDU Session ID, cause, N2 SM information (PDU Session ID, AN Tunnel Information, list of one or more QFIs accepted / rejected)).

[0398] Step 411: AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (N2SM information).

[0399] The AMF forwards the N2 SM information received from the RAN to the SMF. If a list of rejected QFI(s) is included in the N2 SM information, the SMF shall release the QoS profile associated with the rejected QFI(s).

[0400] Step 412: SMF and UPF initiate the N4 session modification process. SMF provides RAN tunnel information and corresponding forwarding rules to UPF.

[0401] Step 413: SMF sends a Nsmf_PDUSession_UpdateSMContext response to AMF.

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

[0403] Figure 5 FIG. 1 is a schematic diagram showing a PFCP session establishment process according to an embodiment of the present disclosure. Figure 5 In the PFCP session establishment process, SMF provides instructions to UPF for QUIC data detection. Specifically, the PFCP session establishment process includes the following steps:

[0404] Step 501: SMF sends a PFCP session establishment request to the selected UPF, wherein the PFCP session establishment request carries PDR, QER, FAR, and URR.

[0405] In this embodiment, the SMF carries QUIC data processing instructions to request the UPF to perform special processing on the QUIC data.

[0406] In one embodiment, the QUIC data processing instructions may include QUIC event reporting instructions, which are configured to instruct the UPF to detect and report certain QUIC events of interest. For example, it may be necessary to detect and report at least one of the following QUIC events:

[0407] – a QUIC data detected event, which requires the UPF to detect and report the first detection of a QUIC data transfer;

[0408] – QUIC connection establishment events, which require UPF to detect and report QUIC connection establishment events;

[0409] – QUIC connection release event, which requires UPF to detect and report the QUIC connection release event;

[0410] – a QUIC data chunk transfer started event, which requires the UPF to detect / report the start of a chunk of QUIC data packets transferred; or

[0411] – A QUIC data chunk transfer stopped event, which requires the UPF to detect and report the stop of a chunk of QUIC data packets transfer.

[0412] In one embodiment, the SMF may only request the UPF to detect general QUIC events (e.g., events of QUIC data detection). In this embodiment, the UPF detects QUIC data regardless of whether the QUIC data is related to any special QUIC event. As an alternative or supplementary solution, the SMF may request the UPF to detect one or more special QUIC events, such as at least one of the events of QUIC connection establishment / release and QUIC data block transmission start / stop.

[0413] In one embodiment, the QUIC data processing instructions may include QUIC statistics reporting instructions configured to instruct the UPF to analyze QUIC data transmissions, collect QUIC data statistics, and report results associated with the QUIC data statistics. For example, at least one of the following QUIC data statistics may be analyzed / collected / reported:

[0414] – Average latency of QUIC data transmission, maximum latency of QUIC data transmission, minimum latency of QUIC data transmission;

[0415] – average size of QUIC data blocks,

[0416] – Maximum size of QUIC data chunks,

[0417] – the minimum size of a QUIC data chunk; or

[0418] – The average transmission interval between (every two consecutive) QUIC data chunks;

[0419] Step 502: After receiving the PFCP session establishment request from the SMF, the UPF installs the received rules (ie, PDR / QER / FAR / URR) for the PFCP session.

[0420] In one embodiment where QUIC event reporting instructions are provided, the UPF stores the QUIC event reporting instructions and performs detection on the indicated QUIC events.

[0421] In one embodiment where QUIC statistics reporting instructions are provided, the UPF stores the QUIC statistics reporting instructions, performs QUIC data analysis, and collects QUIC data statistics.

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

[0423] Step 504a / 504b: Later, the uplink / downlink traffic arrives at the UPF.

[0424] Step 505: If QUIC data processing instructions are provided by SMF, UPF performs QUIC event detection and / or performs QUIC data analysis.

[0425] Note that both QUIC event detection and QUIC data feature analysis require UPF to be able to detect QUIC data and collect QUIC data parameters.

[0426] Typically, an HTTP server implementing the QUIC protocol listens for QUIC data on some special UDP ports (e.g., port 443 reserved for TLS, or port 80 / 8080 reserved for HTTP). Therefore, the UPF may be instructed by the SMF or through local rules of the UPF to detect QUIC data by inspecting and filtering QUIC data from uplink UDP traffic based on a preconfigured UDP port (e.g., port 443).

[0427] Once QUIC data is detected, the UPF collects QUIC data 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 data parameters:

[0428] - a transport protocol type indicating that the transport protocol is QUIC over UDP;

[0429] -UE IP address and UDP port used by the UE to send or receive QUIC data;

[0430] - The remote server IP address and UDP port used by the remote server to send or receive QUIC data;

[0431] - The QUIC version extracted from the QUIC header indicating the QUIC protocol version;

[0432] - a QUIC packet number extracted from the QUIC packet header indicating the packet number of the QUIC packet;

[0433] - One or more QUIC connection IDs extracted from the QUIC packet header that identify a QUIC connection between two endpoints (e.g., a UE and a remote server). The QUIC connection ID used by the UE to send uplink QUIC data is different from the QUIC connection ID used by the remote server to send downlink QUIC data. The UPF SHOULD be able to identify different QUIC connection IDs.

[0434] In addition, if certain QUIC events need to be reported, the UPF SHOULD also check whether the indicated QUIC event occurs.

[0435] Step 506: UPF sends a PFCP session report request carrying a QUIC data report to SMF.

[0436] In one embodiment, the QUIC data report shall include at least one of the following information items:

[0437] - QUIC Data Parameters IE, which carries a combination of the following QUIC data parameters: QUIC protocol indication, UE IP address and one or more ports, remote server IP address and one or more ports, one or more QUIC connection IDs, QUIC version, QUIC packet number;

[0438] - QUIC Event IE, which indicates at least one type of QUIC event;

[0439] - QUIC Data Characteristics IE, which carries a combination of the following QUIC data characteristics: average delay of QUIC data transmission, maximum delay of QUIC data transmission, minimum delay of QUIC data transmission, average size of QUIC data block, maximum size of QUIC data block, minimum size of QUIC data block, average interval of QUIC data transmission. In addition, the analysis duration can be presented to indicate the period of time when the QUIC data characteristics were collected.

[0440] Step 507: SMF sends a PFCP session report response to UPF. SMF can use the reported QUIC events and / or QUIC data features to request PCF to update PCC rules accordingly.

[0441] In some embodiments, the SMF may request the PCF to provide PCC rules for QUIC applications, for example when it receives a PFCP session report regarding QUIC data detection. Figure 6 FIG. 1 is a schematic diagram showing a PFCP session establishment process according to an embodiment of the present disclosure. Figure 6 In the FCP session establishment process, SMF provides instructions to UPF for QUIC data detection.

[0442] Step 601: SMF receives a PFCP session report carrying a QUIC data report from UPF. For example, SMF may receive Figure 5 The process is described in the PFCP Session Report.

[0443] Step 602: SMF determines the PCC rules needed for QUIC applications. If dynamic PCC is implemented, SMF needs to obtain the PCC rules for QUIC applications from PCF; otherwise, SMF can use locally configured rules to generate PCC rules for QUIC applications.

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

[0445] In one embodiment, the QUIC Data Information IE includes at least one of the following information items:

[0446] - QUIC Data Parameters IE, which carries a combination of the following QUIC data parameters: QUIC protocol indication, UE IP address and one or more ports, remote server IP address and one or more ports, one or more QUIC connection IDs, QUIC version, QUIC packet number;

[0447] - QUIC Event IE, which indicates at least one type of QUIC event;

[0448] - QUIC Data Characteristics IE, which carries a combination of the following QUIC data characteristics: average delay of QUIC data transmission, maximum delay of QUIC data transmission, minimum delay of QUIC data transmission, average size of QUIC data block, maximum size of QUIC data block, minimum size of QUIC data block, average interval of QUIC data transmission. In addition, the analysis duration can be presented to indicate the period of time when the QUIC data characteristics were collected.

[0449] Step 604: After receiving the SM policy association update from the SMF, the PCF determines that generation of PCC rules for QUIC applications needs to be based on the received QUIC data information.

[0450] In one embodiment, if the PCF is configured with local rules for QUIC applications (e.g., rules for identifying various QUIC applications, policy rules for these QUIC applications, etc.), or is able to obtain such rules from external storage (e.g., UDR), the PCF performs step 605A to generate policy rules.

[0451] 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.

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

[0453] Step 605A: PCF identifies the QUIC application based on the QUIC data information provided by SMF, and determines the policy rules of the QUIC application based on locally configured rules or rules obtained from external storage (e.g., UDR).

[0454] Step 605B: PCF sends a policy assistance request carrying QUIC data information to NWDAF. NWDAF sends a policy assistance response carrying policy assistance information to PCF.

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

[0456] In one embodiment, NWDAF can also associate QoS policies with specific QUIC packet number ranges. For example, for a packet number within QUIC packet number range #1, AMBR #1 and GBR #1 are applied, while for another packet number within QUIC packet number range #2, AMBR #2 and GBR #2 are applied.

[0457] After receiving the QUIC data information from the PCF, the NWDAF uses its knowledge to infer the service type, application identifier, and applicable QoS policy for the reported QUIC data. The NWDAF can collect various QUIC events and QUIC statistics from the network and can use AI methods to infer relevant information for QUIC services / applications.

[0458] Step 605C01: PCF sends a policy authorization notification carrying QUIC data information to AF. AF can verify the QUIC data information (e.g., QUIC data parameters) and determine to initiate an AF session binding to PCF.

[0459] Step 605C02: AF initiates the AF session binding process to PCF and provides application service information for QUIC to PCF.

[0460] In one embodiment, the application service information for QUIC may include / comprise a combination of at least one of the following application service information: 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 one or more ports, remote service IP address and port, one or more QUIC connection IDs, or applicable QoS policy (e.g., AMBR, GBR, maximum AMBR, minimum AMBR, maximum GBR, minimum GBR, etc.).

[0461] Step 606: The PCF generates PCC rules for the QUIC application by using the information obtained in steps 605A, 605B, or 605C01 and 605C02.

[0462] In an embodiment of step 605A being performed, the PCF generates PCC rules for the reported QUIC application using the QUIC application information it derived through local configuration rules or externally stored rules.

[0463] In an embodiment of step 5B being performed, the PCF uses the policy assistance information obtained from the NWDAF to generate PCC rules for the reported QUIC application.

[0464] In an embodiment of steps 605C01 and 605C02 being performed, the PCF uses the application service information obtained from the AF to generate PCC rules for the reported QUIC application.

[0465] In one embodiment, the generated PCC rule may contain / include at least one of the following information:

[0466] 1) QUIC application information, which also includes at least one of the following information: application identifier, application service type, UE identifier;

[0467] 2) QUIC connection information, which also includes at least one of the following information: one or more QUIC connection IDs, UE IP address and one or more UDP ports, remote server IP address and one or more UDP ports; or

[0468] 3) QoS flow parameters for QUIC data, which also include at least one of the following parameters: QoS flow identifier (QFI), allocation and reservation priority (ARP), average maximum bit rate (AMBR), guaranteed bit rate (GBR), etc. The QoS flow parameters may also include one of the following parameters: maximum AMBR, minimum AMBR, maximum GBR, and minimum GBR. Alternatively, the QoS flow parameters may also include a list of QUIC packet number ranges and the corresponding AMBR and GBR associated with each QUIC packet number range.

[0469] Step 607: PCF sends an SM policy association update response carrying PCC rules for QUIC applications to SMF.

[0470] Step 608: After 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. It is not that the PFCP rules are also called N4 rules on the N4 interface.

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

[0472] In one embodiment, at least one of the following information may be carried in an N4 rule (e.g., in a PDR) to instruct the UPF to detect specific QUIC data:

[0473] -QUIC Data Detection Indication instructs the UPF to detect QUIC data.

[0474] - The UE IP address and one or more UDP ports that instruct the UPF to detect QUIC data from / to this UE address;

[0475] - A remote server IP address and one or more ports that instruct the UPF to detect QUIC data from / to that remote server address;

[0476] - one or more QUIC connection IDs that instruct the UPF to detect QUIC data on the indicated QUIC connection;

[0477] Step 609: The UPF receives the PFCP session modification request and updates the received N4 rules (eg, PDR / QER / FAR / URR rules, etc.) into its memory.

[0478] Step 610: Based on the updated N4 rules, UPF starts detecting QUIC data for a specific QUIC application and performs required operations on the detected QUIC data (e.g., gating, QoS enforcement, forwarding, usage reporting, etc.).

[0479] Figure 7 A schematic diagram of a wireless terminal 70 according to an embodiment of the present disclosure is provided. 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 storage unit 710, and a communication unit 720. The storage unit 710 may be any data storage device that stores program code 712 accessed and executed by the processor 700. Embodiments of the storage 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 send and receive signals (e.g., messages or data packets) based on the processing results of the processor 700. In one embodiment, the communication unit 720 communicates with the user via a communication device. Figure 7 At least one antenna 722 is shown for transmitting and receiving signals.

[0480] In one embodiment, the storage unit 710 and the program code 712 may be omitted, and the processor 700 may include the storage unit with the stored program code.

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

[0482] The communication unit 720 may be a transceiver. As an alternative or in addition, the communication unit 720 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless network node (eg, a base station), respectively.

[0483] Figure 8 A schematic diagram of a radio network node 80 according to an embodiment of the present disclosure is provided. The radio 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 centralized 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 thereto. In addition, the radio network node 80 may include (execute) at least one network function such as an access and mobility management function (AMF), a session management function (SMF), a user location function (UPF), a policy control function (PCF), an application function (AF), etc. The radio network node 80 may include a processor 800 such as a microprocessor or an ASIC, a storage unit 810 and a communication unit 820. The storage unit 810 may be any data storage device storing a program code 812 accessed and executed by the processor 800. Examples of the storage 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 send and receive signals (e.g., messages or data packets) according to the processing results of the processor 800. In one example, the communication unit 820 communicates with the processor 800 via Figure 8 At least one antenna 822 is shown for transmitting and receiving signals.

[0484] In one embodiment, storage unit 810 and program code 812 may be omitted. Processor 800 may include a storage unit with stored program code.

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

[0486] The communication unit 820 may be a transceiver. Alternatively or additionally, the communication unit 820 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless terminal (eg, a user equipment or another wireless network node), respectively.

[0487] Fig. 9 A flow chart of a method according to an embodiment of the present disclosure is shown. Fig. 9 The method shown may be used in an SMF (e.g., a session management node, a wireless device including an SMF, or a wireless device including a device that performs at least part of the functionality of an SMF), and includes the following steps:

[0488] Step 901: Send QUIC data instructions to UPF.

[0489] Step 902: Receive at least one QUIC report related to QUIC data from the UPF.

[0490] exist Fig. 9 In the embodiment of the present invention, the SMF sends a QUIC data instruction to the UPF, for example, to instruct the UPF to detect and / or collect information about the QUIC data. In response to the QUIC data instruction, at least one QUIC report associated with the QUIC data is sent from the UPF to the SMF.

[0491] In one embodiment, the QUIC data instructions include at least one of a QUIC event reporting instruction indicating at least one event (generation / report) associated with at least one QUIC report or a QUIC statistics reporting instruction indicating at least one statistic included in each QUIC report.

[0492] In one embodiment, the at least one event associated with at least one QUIC report includes at least one of the following events: an event associated with QUIC data detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of transmission of a QUIC data chunk, or an event associated with the end of transmission of a QUIC data chunk. For more details on each event, refer to Figure 5 and Figure 6 The embodiment shown in .

[0493] In one embodiment, at least one statistic included in each QUIC report includes at least one of the following: an average delay in QUIC data transmission, a maximum delay in QUIC data transmission, a minimum delay in QUIC data 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 each two consecutive QUIC data transmissions, or an analysis duration indicating a period of time over which QUIC data characteristics for each QUIC report were collected.

[0494] In one embodiment, each QUIC report includes at least one of: at least one QUIC data parameter of the QUIC data, at least one QUIC reporting event associated with the QUIC report, or at least one statistic of the QUIC data associated with the QUIC report.

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

[0496] It should be noted that 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, where A / B / C refers to parameters, elements, statistics, etc.

[0497] Fig.10 A flow chart of a method according to an embodiment of the present disclosure is shown. Fig.10 The method shown may be used for a UPF (e.g., a user plane node, a wireless device including a UPF, or a wireless device including a device that performs at least part of the functionality of a UPF), and includes the following steps:

[0498] Step 1001: Receive QUIC data instructions from SMF.

[0499] Step 1002: Send at least one QUIC report associated with the QUIC data to the SMF.

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

[0501] In one embodiment, the QUIC data instructions include at least one of a QUIC event reporting instruction or a QUIC statistics reporting instruction, wherein the QUIC event reporting instruction indicates at least one event (generation / report) associated with at least one QUIC report and the QUIC statistics reporting instruction indicates at least one statistic included in each QUIC report.

[0502] In one embodiment, the at least one event associated with at least one QUIC report includes at least one of the following events: an event associated with QUIC data detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of transmission of a QUIC data chunk, or an event associated with the end of transmission of a QUIC data chunk. For more details on each event, refer to Figure 5 and Figure 6 The embodiment shown in .

[0503] In one embodiment, at least one statistic included in each QUIC report includes at least one of the following: an average delay in QUIC data transmission, a maximum delay in QUIC data transmission, a minimum delay in QUIC data 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 each two consecutive QUIC data transmissions, or an analysis duration indicating a period of time over which QUIC data characteristics for each QUIC report were collected.

[0504] In one embodiment, each QUIC report includes at least one of: at least one QUIC data parameter of the QUIC data, at least one QUIC reporting event associated with the QUIC report, or at least one statistic of the QUIC data associated with the QUIC report.

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

[0506] Fig.11 A flow chart of a method according to an embodiment of the present disclosure is shown. Fig.11 The method shown in may be used in an SMF (e.g., a session management node, a wireless device including an SMF, or a wireless device performing at least part of the functionality of an SMF), and includes the following steps:

[0507] Step 1101: Send QUIC data information to PCF.

[0508] Step 1102: Receive PCC rules determined based on information of QUIC data for a QUIC application from the PCF.

[0509] exist Fig.11 In the example, SMF sends information about the QUIC data to PCF. For example, SMF can execute Fig. 9The method in receives / requests information of QUIC data from UPF. Based on the information of QUIC data, PCF can determine / optimize / modify / adjust / add PCC rules for QUIC applications and send the PCC rules to SMF. Therefore, by adopting PCC rules, SMF can process QUIC data of QUIC applications more efficiently.

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

[0511] In one embodiment, the at least one event associated with at least one QUIC report includes at least one of the following events: an event associated with QUIC data detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of transmission of a QUIC data chunk, or an event associated with the end of transmission of a QUIC data chunk. For more details on each event, refer to Figure 5 and Figure 6 The embodiment shown in .

[0512] In one embodiment, at least one statistic included in each QUIC report includes at least one of the following: an average delay in QUIC data transmission, a maximum delay in QUIC data transmission, a minimum delay in QUIC data 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 each two consecutive QUIC data transmissions, or an analysis duration indicating a period of time over which QUIC data characteristics for each QUIC report were collected.

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

[0514] In one embodiment, the PCC rule includes at least one of the following: QUIC application information, QUIC connection information, or at least one QUIC stream parameter.

[0515] In one embodiment, the QUIC application information includes at least one of the following: 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.

[0516] In one embodiment, the QUIC connection information includes at least one of the following: at least one QUIC connection identifier of the QUIC application, the IP address of a 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 the QUIC application and the UDP port associated with the remote server.

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

[0518] In one embodiment, at least one QUIC stream parameter includes at least one of: maximum AMBR, minimum AMBR, maximum GBR, or minimum GBR.

[0519] In one embodiment, at least one QUIC stream parameter includes at least one of: a list of QUIC packet number ranges and the AMBRs corresponding to the QUIC packet number ranges, or a list of QUIC packet number ranges and the GBRs corresponding to the QUIC packet number ranges.

[0520] Fig.12 A flow chart of a method according to an embodiment of the present disclosure is shown. Fig.12 The method shown in may be used for a PCF (e.g., a policy control node, a wireless device including a PCF, or a wireless device performing at least part of the functionality of a PCF), and includes the following steps:

[0521] Step 1201: Receive information about QUIC data from SMF.

[0522] Step 1202: Send PCC rules determined based on information of QUIC data for QUIC application to SMF.

[0523] exist Fig.12 In the embodiment, PCF receives information of QUIC data from SMF. Based on the received information, PCF can determine / optimize / modify / adjust / add PCC rules for QUIC applications and send the PCC rules to SMF, for example, to allow SMF to effectively process QUIC data for QUIC applications.

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

[0525] In one embodiment, the at least one event associated with at least one QUIC report includes at least one of the following events: an event associated with QUIC data detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of transmission of a QUIC data chunk, or an event associated with the end of transmission of a QUIC data chunk. For more details on each event, refer to Figure 5 and Figure 6 The embodiment shown in .

[0526] In one embodiment, at least one statistic included in each QUIC report includes at least one of the following: an average delay in QUIC data transmission, a maximum delay in QUIC data transmission, a minimum delay in QUIC data 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 each two consecutive QUIC data transmissions, or an analysis duration indicating a period of time over which QUIC data characteristics for each QUIC report were collected.

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

[0528] In one embodiment, the PCC rule includes at least one of the following: QUIC application information, QUIC connection information, or at least one QUIC stream parameter.

[0529] In one embodiment, the QUIC application information includes at least one of the following: 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.

[0530] In one embodiment, the QUIC connection information includes at least one of the following: at least one QUIC connection identifier of the QUIC application, the IP address of a 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 the QUIC application and the UDP port associated with the remote server.

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

[0532] In one embodiment, at least one QUIC stream parameter includes at least one of: maximum AMBR, minimum AMBR, maximum GBR, or minimum GBR.

[0533] In one embodiment, at least one QUIC stream parameter includes at least one of: a list of QUIC packet number ranges and the AMBRs corresponding to the QUIC packet number ranges, or a list of QUIC packet number ranges and the GBRs corresponding to the QUIC packet number ranges.

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

[0535] In one embodiment, the QUIC auxiliary information includes at least one of the following: an application service type associated with the QUIC data, an application identifier associated with the QUIC data, at least one QoS policy for the QUIC data, or at least one QUIC packet number range corresponding to at least one QoS policy.

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

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

[0538] Fig.13 A flow chart of a method according to an embodiment of the present disclosure is shown. Fig.13 The method shown may be used in a NWDAF (e.g., a network data analysis node, a wireless device including a NWDAF, or a wireless device performing at least part of the functionality of a NWDAF), and includes the following steps:

[0539] Step 1301: Receive a QUIC assistance request from the PCF including information about QUIC data.

[0540] Step 1302: Send QUIC auxiliary information associated with the QUIC data to the PCF.

[0541] exist Fig.13 In the embodiment of the present invention, NWDAF receives a QUIC assistance request including information of QUIC data from PCF. NWDAF analyzes the information of QUIC data and generates QUIC assistance information accordingly, which can be used to determine PCC rules. The generated QUIC assistance information is sent from NWDAF to PCF.

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

[0543] In one embodiment, the at least one event associated with at least one QUIC report includes at least one of the following events: an event associated with QUIC data detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of transmission of a QUIC data chunk, or an event associated with the end of transmission of a QUIC data chunk. For more details on each event, refer to Figure 5 and Figure 6 The embodiment shown in .

[0544] In one embodiment, at least one statistic included in each QUIC report includes at least one of the following: an average delay in QUIC data transmission, a maximum delay in QUIC data transmission, a minimum delay in QUIC data 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 each two consecutive QUIC data transmissions, or an analysis duration indicating a period of time over which QUIC data characteristics for each QUIC report were collected.

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

[0546] In one embodiment, the QUIC auxiliary information includes at least one of the following: an application service type associated with the QUIC data, an application identifier associated with the QUIC data, at least one QoS policy for the QUIC data, or at least one QUIC packet number range corresponding to at least one QoS policy.

[0547] Fig.14 A flow chart of a method according to an embodiment of the present disclosure is shown. Fig.14 The method shown in may be used for an AF (e.g., an application node, a wireless device including an AF, or a wireless device performing at least part of the functions of an AF), and comprises the following steps:

[0548] Step 1401: Receive a policy authorization notification from the PCF including information about QUIC data.

[0549] Step 1402: Send application service information associated with QUIC data to PCF.

[0550] In this embodiment, the AF receives a policy authorization notification including information about the QUIC data from the PCF. Based on the information about the QUIC data, the AF generates and sends application service information associated with the QUIC data to the PCF, for example, to help the PCF determine the corresponding PCC rules.

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

[0552] In one embodiment, the at least one event associated with at least one QUIC report includes at least one of the following events: an event associated with QUIC data detection, an event associated with QUIC connection establishment, an event associated with QUIC connection release, an event associated with the start of transmission of a QUIC data chunk, or an event associated with the end of transmission of a QUIC data chunk. For more details on each event, refer to Figure 5 and Figure 6 The embodiment shown in .

[0553] In one embodiment, at least one statistic included in each QUIC report includes at least one of the following: an average delay in QUIC data transmission, a maximum delay in QUIC data transmission, a minimum delay in QUIC data 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 each two consecutive QUIC data transmissions, or an analysis duration indicating a period of time over which QUIC data characteristics for each QUIC report were collected.

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

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

[0556] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, these personnel should understand that the present disclosure is not limited to the example architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations. In addition, as those of ordinary skill in the art should understand, one or more features of an embodiment can be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0557] It should also be understood that any reference to an element using names such as "first," "second," etc., herein generally does not limit the number or order of these elements. Instead, these names may be used herein as a convenient means of distinguishing two or more elements or instances of an element. Thus, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some way.

[0558] In addition, it should be understood by those skilled in the art that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols that can be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0559] Those skilled in the art should also understand that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design codes containing instructions (for convenience, may be referred to herein as "software" or "software units"), or any combination of these technologies.

[0560] In order to clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits and steps have been generally described above with respect to their functionality. Whether such functions are implemented as hardware, firmware, or as software, or as a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not lead to deviations from the scope of the present disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. may be configured to perform one or more functions described herein. The terms "configured to" or "configured for" 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 a specified operation or function.

[0561] In addition, the technician should understand that the various illustrative logic blocks, units, devices, components and circuits described herein can be implemented in or performed by an integrated circuit (IC), which can include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor can be a microprocessor, but in an alternative, the processor can be any conventional processor, controller or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration for performing the functions described herein. If implemented in software, the function can be stored on a computer-readable medium as one or more instructions or codes. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.

[0562] Computer-readable media include computer storage media and communication media, which include any media that enable a computer program or code to be transferred from one place to another. Storage media can be any available media 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 media that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0563] In this application, the term "unit" used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for ease of discussion, various units are described as discrete units; however, it is obvious to those of ordinary skill in the art that two or more units can be combined to form a single unit of relevant functions according to embodiments of the present disclosure.

[0564] In addition, memory or other memory and communication components may be used in embodiments of the present disclosure. It should be understood that, for the sake of clarity, 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 appropriate functional distribution may be used between different functional units, processing logic elements or domains without departing from the present disclosure. For example, functions shown as being performed by different processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is only a reference to an appropriate means for providing the described functions, rather than an indication of a strict logical or physical structure or organization.

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

Claims

1. A wireless communication method for use in a session management function, the method comprising: Sending Fast User Datagram Protocol Internet Connection (QUIC) data instructions to the user plane function, and receiving at least one QUIC report associated with QUIC data from the user plane function, The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with the at least one QUIC report, and the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

2. The wireless communication method according to claim 1, wherein: The at least one event associated with the at least one QUIC report comprises at least one of the following events: Events associated with QUIC data detection, Events associated with QUIC connection establishment, Events associated with QUIC connection release, An event associated with the start of transmission of a QUIC data chunk, or Event associated with the end of transmission of a QUIC data chunk.

3. The wireless communication method according to claim 1 or 2, wherein: The at least one statistic included in each QUIC report includes at least one of the following: The average latency of QUIC data transmission, The maximum latency of QUIC data transmission, Minimum latency for QUIC data transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

4. The wireless communication method according to any one of claims 1 to 3, wherein: Each QUIC report includes at least one of the following: at least one QUIC data parameter of the QUIC data, at least one QUIC reporting event associated with said QUIC report, or At least one statistic of QUIC data associated with the QUIC report.

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

6. A wireless communication method used in a user plane function, the method comprising: receiving a Quick User Datagram Protocol Internet Connection (QUIC) data instruction from a session management function, and sending at least one QUIC report associated with the QUIC data to the session management function, The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with the at least one QUIC report, and the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

7. The wireless communication method according to claim 6, wherein: The at least one event associated with the at least one QUIC report comprises at least one of the following events: Events associated with QUIC data detection, Events associated with QUIC connection establishment, Events associated with QUIC connection release, An event associated with the start of transmission of a QUIC data chunk, or Event associated with the end of transmission of a QUIC data chunk.

8. The wireless communication method according to claim 6 or 7, wherein: The at least one statistic included in each QUIC report includes at least one of the following: The average latency of QUIC data transmission, The maximum latency of QUIC data transmission, Minimum latency for QUIC data transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or Indicates the analysis duration used to determine the period over which the QUIC data characteristics for each QUIC report are collected.

9. The wireless communication method according to any one of claims 6 to 8, wherein: Each QUIC report includes at least one of the following: at least one QUIC data parameter of the QUIC data, at least one QUIC reporting event associated with said QUIC report, or At least one statistic of QUIC data associated with the QUIC report.

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

11. A wireless communication method for use in a session management function, the method comprising: information to send Quick User Datagram Protocol Internet Connection (QUIC) data to a policy control function, and receiving, from the policy control function, a policy and charging control (PCC) rule determined based on information of the QUIC data for a QUIC application, The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

12. The wireless communication method according to claim 11, wherein: The at least one event associated with the information of the QUIC data includes at least one of the following events: Events associated with QUIC data detection, Events associated with QUIC connection establishment, Events associated with QUIC connection release, An event associated with the start of transmission of a QUIC data chunk, or Event associated with the end of transmission of a QUIC data chunk.

13. The wireless communication method according to claim 11 or 12, wherein: The statistics of the QUIC data include at least one of the following: The average latency of QUIC data transmission, The maximum latency of QUIC data transmission, Minimum latency for QUIC data transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or An analysis duration indicating a period over which QUIC data characteristics used to determine information about the QUIC data are collected.

14. The wireless communication method according to any one of claims 11 to 13, wherein: The QUIC data information further includes at least one QUIC data parameter, wherein the at least one QUIC data parameter includes at least one of the following: a QUIC protocol indication associated with the QUIC data, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC data and the UDP port associated with the remote server, at least one QUIC connection identifier for the QUIC data, the QUIC version of the QUIC data, or The packet number of the QUIC data.

15. The wireless communication method according to any one of claims 11 to 14, wherein: The PCC rules include at least one of the following: QUIC application information, QUIC connection information, or At least one QUIC stream parameter.

16. The wireless communication method according to claim 15, wherein: The QUIC application information includes at least one of the following: the application identifier of the QUIC application, The application service type of the QUIC application, or An identifier of a wireless terminal associated with the QUIC application.

17. The wireless communication method according to claim 15 or 16, wherein: The QUIC connection information includes at least one of the following: at least one QUIC connection identifier of the QUIC application, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC application and a 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.

18. The wireless communication method according to any one of claims 15 to 17, wherein: The at least one QUIC stream parameter comprises at least one of the following: Quality of Service (QoS) flow identifier, Assign and retain priorities, Average Maximum Bit Rate (AMBR), or Guaranteed Bit Rate (GBR).

19. The wireless communication method according to any one of claims 15 to 18, wherein: The at least one QUIC stream parameter comprises at least one of the following: Highest AMBR, Minimum AMBR, Maximum GBR, or Minimum GBR.

20. The wireless communication method according to any one of claims 15 to 19, wherein: The at least one QUIC stream parameter comprises at least one of the following: a list of QUIC packet number ranges and the AMBRs corresponding to said QUIC packet number ranges, or A list of QUIC packet number ranges and the GBRs corresponding to the QUIC packet number ranges.

21. A wireless communication method used in a policy control function, the method comprising: receiving information about Quick User Datagram Protocol Internet Connections (QUIC) data from a session management function, and sending, to the session management function, policy and charging control (PCC) rules determined based on the information of the QUIC data for the QUIC application, The QUIC information includes at least one event associated with the information of the QUIC data and / or statistics of the QUIC data.

22. The wireless communication method according to claim 21, wherein: The at least one event associated with the information of the QUIC data includes at least one of the following events: Events associated with QUIC data detection, Events associated with QUIC connection establishment, Events associated with QUIC connection release, An event associated with the start of transmission of a QUIC data chunk, or Event associated with the end of transmission of a QUIC data chunk.

23. The wireless communication method according to claim 21 or 22, wherein: The statistics of the QUIC data include at least one of the following: The average latency of QUIC data transmission, The maximum latency of QUIC data transmission, Minimum latency for QUIC data transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or An analysis duration indicating a period over which QUIC data characteristics used to determine information about the QUIC data are collected.

24. The wireless communication method according to any one of claims 21 to 23, wherein: The QUIC data information further includes at least one QUIC data parameter, wherein the at least one QUIC data parameter includes at least one of the following: a QUIC protocol indication associated with the QUIC data, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC data and the UDP port associated with the remote server, at least one QUIC connection identifier for the QUIC data, the QUIC version of the QUIC data, or The packet number of the QUIC data.

25. The wireless communication method according to any one of claims 21 to 24, wherein: The PCC rules include at least one of the following: QUIC application information, QUIC connection information, or At least one QUIC stream parameter.

26. The wireless communication method according to claim 25, wherein: The QUIC application information includes at least one of the following: the application identifier of the QUIC application, The application service type of the QUIC application, or An identifier of a wireless terminal associated with the QUIC application.

27. The wireless communication method according to claim 25 or 26, wherein: The QUIC connection information includes at least one of the following: at least one QUIC connection identifier of the QUIC application, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC application and a 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.

28. The wireless communication method according to any one of claims 25 to 27, wherein: The at least one QUIC stream parameter comprises at least one of the following: Quality of Service (QoS) flow identifier, Assign and retain priorities, Average Maximum Bit Rate (AMBR), or Guaranteed Bit Rate (GBR).

29. The wireless communication method according to any one of claims 25 to 28, wherein: The at least one QUIC stream parameter comprises at least one of the following: Highest AMBR, Minimum AMBR, Maximum GBR, or Minimum GBR.

30. The wireless communication method according to any one of claims 25 to 29, wherein: The at least one QUIC stream parameter comprises at least one of the following: a list of QUIC packet number ranges and the AMBRs corresponding to said QUIC packet number ranges, or A list of QUIC packet number ranges and the GBRs corresponding to the QUIC packet number ranges.

31. The wireless communication method according to any one of claims 21 to 30, further comprising: sending a QUIC assistance request including information about said QUIC data to the network data analysis function, and QUIC ancillary information associated with the QUIC data is received from the network data analysis function, wherein the PCC rules are determined based on the QUIC ancillary information.

32. The wireless communication method according to claim 31, wherein: The QUIC assistance information includes at least one of the following: the application service type associated with the QUIC data, an application identifier associated with the QUIC data, at least one QoS policy for the QUIC data, or At least one QUIC packet number range corresponding to the at least one QoS policy.

33. The wireless communication method according to any one of claims 21 to 32, further comprising: sending a policy authorization notification including information about the QUIC data to the application function, and Application service information associated with the QUIC data is received from the application function, wherein the PCC rule is determined based on the application service information.

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

35. A wireless communication method used in a network data analysis function, the method comprising: receiving, from a policy control function, a QUIC assistance request including information of Quick User Datagram Protocol Internet Connection (QUIC) data, and sending QUIC ancillary information associated with the QUIC data to the policy control function, The QUIC information includes at least one event associated with information about the QUIC data and / or statistics of the QUIC data.

36. The wireless communication method according to claim 35, wherein: The at least one event associated with the information of the QUIC data includes at least one of the following events: Events associated with QUIC data detection, Events associated with QUIC connection establishment, Events associated with QUIC connection release, An event associated with the start of transmission of a QUIC data chunk, or Event associated with the end of transmission of a QUIC data chunk.

37. The wireless communication method according to claim 35 or 36, wherein: The statistics of the QUIC data include at least one of the following: The average latency of QUIC data transmission, The maximum latency of QUIC data transmission, Minimum latency for QUIC data transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or An analysis duration indicating a period over which QUIC data characteristics used to determine information about the QUIC data are collected.

38. The wireless communication method according to any one of claims 35 to 37, wherein: The QUIC data information further includes at least one QUIC data parameter, wherein the at least one QUIC data parameter includes at least one of the following: a QUIC protocol indication associated with the QUIC data, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC data and the UDP port associated with the remote server, at least one QUIC connection identifier for the QUIC data, the QUIC version of the QUIC data, or The packet number of the QUIC data.

39. The wireless communication method according to any one of claims 35 to 38, wherein: The QUIC assistance information includes at least one of the following: the application service type associated with the QUIC data, an application identifier associated with the QUIC data, at least one QoS policy for the QUIC data, or At least one QUIC packet number range corresponding to the at least one QoS policy.

40. A wireless communication method used in an application function, the method comprising: receiving a policy authorization notification including Quick User Datagram Protocol Internet Connection (QUIC) data information from a policy control function, and sending application service information associated with the QUIC data to the policy control function, The QUIC information includes at least one event associated with the information of the QUIC data and / or statistics of the QUIC data.

41. The wireless communication method according to claim 40, wherein: The at least one event associated with the information of the QUIC data includes at least one of the following events: Events associated with QUIC data detection, Events associated with QUIC connection establishment, Events associated with QUIC connection release, An event associated with the start of transmission of a QUIC data chunk, or Event associated with the end of transmission of a QUIC data chunk.

42. The wireless communication method according to claim 40 or 41, wherein: The statistics of the QUIC data include at least one of the following: The average latency of QUIC data transmission, The maximum latency of QUIC data transmission, Minimum latency for QUIC data transmission, The average size of a QUIC data block, The maximum size of a QUIC data block, The minimum size of a QUIC data chunk, the average interval between two consecutive QUIC data transfers, or An analysis duration indicating a period over which QUIC data characteristics used to determine information about the QUIC data are collected.

43. The wireless communication method according to any one of claims 40 to 42, wherein: The QUIC data information further includes at least one QUIC data parameter, wherein the at least one QUIC data parameter includes at least one of the following: a QUIC protocol indication associated with the QUIC data, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC data and the UDP port associated with the remote server, at least one QUIC connection identifier for the QUIC data, the QUIC version of the QUIC data, or The packet number of the QUIC data.

44. The wireless communication method according to any one of claims 40 to 43, wherein: The application service information includes at least one of the following: the application service type associated with the QUIC data, an application identifier associated with the QUIC data, an identifier of a wireless terminal associated with the QUIC data, an Internet Protocol (IP) address of a wireless terminal associated with the QUIC data and a User Datagram Protocol (UDP) port associated with the wireless terminal, the IP address of a remote server associated with the QUIC data and the UDP port associated with the remote server, or At least one QoS policy for the QUIC data.

45. A session management node, the session management node comprising: A communication unit, wherein the communication unit is configured to: sending Quick User Datagram Protocol Internet Connection (QUIC) data instructions to the user plane function, and The slave user plane function receives at least one QUIC report associated with the QUIC data, wherein the QUIC data instruction includes at least one instruction of a QUIC event reporting instruction or a QUIC statistics reporting instruction, the QUIC event reporting instruction indicating at least one event associated with the at least one QUIC report, and the QUIC statistics reporting instruction indicating at least one statistic included in each QUIC report.

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

47. A user plane node, the user plane node comprising: A communication unit, wherein the communication unit is configured to: receiving a Quick User Datagram Protocol Internet Connection (QUIC) data instruction from a session management function, and sending at least one QUIC report associated with the QUIC data to the session management function, The QUIC data instruction includes at least one of a QUIC event report instruction or a QUIC statistics report instruction, wherein the QUIC event report instruction indicates at least one event associated with the at least one QUIC report, and the QUIC statistics report instruction indicates at least one statistic included in each QUIC report.

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

49. A session management node, the session management node comprising: A communication unit, wherein the communication unit is configured to: sending Quick User Datagram Protocol Internet Connection (QUIC) data to a policy control function, and receiving, from the policy control function, a policy and charging control (PCC) rule determined based on information of the QUIC data for a QUIC application, The QUIC information includes at least one event associated with the information of the QUIC data and / or statistics of the QUIC data.

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

51. A policy control node, the policy control node comprising: A communication unit, wherein the communication unit is configured to: receiving Quick User Datagram Protocol Internet Connections (QUIC) data from a session management function, and sending, to the session management function, policy and charging control (PCC) rules determined based on the information of the QUIC data for the QUIC application, The QUIC information includes at least one event associated with the information of the QUIC data and / or statistics of the QUIC data.

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

53. A network data analysis node, the network data analysis node comprising: A communication unit, wherein the communication unit is configured to: receiving, from a policy control function, a QUIC assistance request including information of Quick User Datagram Protocol Internet Connection (QUIC) data, and sending QUIC ancillary information associated with the QUIC data to the policy control function, The QUIC information includes at least one event associated with the information of the QUIC data and / or statistics of the QUIC data.

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

55. An application node, the application node comprising: A communication unit, wherein the communication unit is configured to: receiving a policy authorization notification including Quick User Datagram Protocol Internet Connection (QUIC) data information from a policy control function, and sending application service information associated with the QUIC data to the policy control function, The QUIC information includes at least one event associated with the information of the QUIC data and / or statistics of the QUIC data.

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

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

Images