Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/12—Setup of transport tunnels

Definitions

• This document is directed generally to wireless communications, in particular to fifth generation (5G) wireless communication.
• 5G fifth generation
• the QUIC (Quick UDP International Connection) protocol is a rapidly developing for setting up an international connection between two end points.
• the QUIC is regarded as the next generation protocol used for HTTP, i.e., to be used to replace existing TCP+TLS+HTTP protocol.
• the QUIC connection is a secured connection between two endpoints, e.g., between a UE and an Application Server of the UE, which disables a transmission node in the network to inspect contents transmitted on the QUIC connection.
• the 5G packet detection and forwarding model can only detect possible QUIC traffic from other TCP/UDP traffic. It is hard for the network to detect QUIC connection parameters (e.g., QUIC Connection ID) and to recognize services or applications to which the QUIC traffic is related.
• QUIC connection parameters e.g., QUIC Connection ID
• This document relates to methods, systems, and devices for the QUIC connection and in particular to methods, systems, and devices for reporting information of the QUIC connection.
• the present disclosure relates to a wireless communication method for use in a wireless terminal.
• the method comprises:
• QUIC quick user datagram protocol international connection
• QoS quality of service
• the binding information comprises information of the QoS flow and the QUIC connection.
• the information of the QoS flow comprises a QoS flow identifier (QFI) of the QoS flow.
• QFI QoS flow identifier
• the information of the QUIC connection comprises at least one of a QUIC Connection identifier (ID) of the QUIC connection, a Server ID part of the QUIC Connection ID or a range of the QUIC Connection ID.
• ID QUIC Connection identifier
• the binding information is transmitted in a session management (SM) message.
• SM session management
• the wireless network node comprises a user plane function (UPF) .
• UPF user plane function
• the wireless communication method further comprises receiving, from an SMF, a QUIC information reporting indication, wherein wireless terminal transmits the binding information in response to the QUIC information reporting indication.
• the QUIC information reporting indication is included in a PCO information element or an extended PCO information element within the SM message or in a user equipment route selection policy (URSP) rule.
• URSP user equipment route selection policy
• the wireless communication method further comprises receiving, from the SMF, a method indication associated with transmitting the binding information, the wireless terminal transmits the binding information based on the method indication.
• the present disclosure relates to a wireless communication method for use in a session management function (SMF) .
• the method comprises:
• QoS quality of service
• QUIC quick user datagram protocol international connection
• PFCP packet forwarding control protocol
• the binding information comprises information of the QoS flow and the QUIC connection.
• the information of the QoS flow comprises a QoS flow identifier (QFI) of the QoS flow.
• QFI QoS flow identifier
• the at least one PFCP rule comprises a first Packet Detection Rule associated with a QFI of the QoS flow and information of the QUIC connection.
• the information of the QUIC connection comprises at least one of a QUIC Connection identifier (ID) of the QUIC connection, a Server ID part of the QUIC Connection ID or a range of the QUIC Connection ID.
• ID QUIC Connection identifier
• the binding information is received in a session management (SM) message.
• SM session management
• the wireless communication method further comprises transmitting, to the wireless terminal, a QUIC information reporting indication associated with a transmission of the binding information.
• the QUIC information reporting indication is transmitting in an SM message.
• FIG. 6 shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.
• FIG. 8 shows a flowchart of a method according to an embodiment of the present disclosure.
• FIG. 9 shows a flowchart of a method according to an embodiment of the present disclosure.
• FIG. 1 shows a schematic diagram of a network (architecture) according to an embodiment of the present disclosure.
• the network comprises the following network functions/entities:
• NG-RAN Next Generation Radio Access Network
• the SMF provides PDU session management for the UE.
• the functionalities of the SMF comprises, e.g., IP address allocation, QoS flow setup, etc.
• the UPF provides IP traffic routing and forwarding management.
• the UDM manages the subscription profile for the UEs.
• the subscription includes the data used for mobility management (e.g., restricted area) , session management (e.g., QoS profile per slice per DNN) .
• the subscription data also includes the slice selection parameters which is used for AMF to select a proper SMF.
• the AMF and SMF get the subscription from UDM.
• the subscription data is stored in the Unified Data Repository (UDR) .
• UDM uses such data upon reception of request from AMF or SMF.
• PCF Policy Control Function
• the 5G network cannot know the binding relationship between the QoS flow and the QUIC connection. Thus, it is impossible for the network to make accurate policy for the QoS flow and the QUIC connection and to detect and guard the QUIC traffic transmission over the selected QoS flow.
• the present disclosure provides a method to let the network to acknowledge the binding information of the QoS flow and the QUIC connection, so as to allow the network to make accurate policy for detecting and guarding the QUIC traffic transmission over the corresponding QoS flow.
• the UE reports the binding information of the QoS flow and the QUIC connection to the SMF. For example, the UE may select an appropriate QoS flow to set up a QUIC connection towards the remote server (e.g., Application Server of the UE) . Once/After the QUIC connection is established, the UE reports the binding information of the selected QoS flow and the QUIC connection to the SMF, e.g., via the PCO/ePCO (protocol configuration option or extended protocol configuration option) in an SM (session management) message.
• PCO/ePCO program configuration option or extended protocol configuration option
• a PDU session is established upon request (s) from the UE.
• the UE sets up a QUIC connection with the remote server (i.e., AS (application server) of the UE in this embodiment) over an appropriate QoS flow selected by the UE.
• the UE may first select an appropriate QoS flow that fulfils the QoS requirements of the application.
• a pair of QUIC Connection IDs is allocated by the UE and the remote server.
• the QUIC Connection ID at the UE side (i.e., allocated by the UE) and the QUIC Connection ID at the remote side are exchanged with the peer terminal during the QUIC connection establishment.
• the QUIC Connection ID allocated by the UE is used by the remote server in downlink QUIC traffic (i.e., filled in a destination QUIC Connection ID field) , to indicate the target QUIC connection at the UE side.
• the QUIC Connection ID allocated by the remote server is used by the UE in uplink QUIC traffic (i.e., filled in the destination QUIC Connection ID field) , to indicate the target QUIC connection at the remote server side.
• the UE initiates an SM message (e.g., PDU Session Modification Request) towards the SMF, wherein the SM message carries the binding information of QoS flow and QUIC connection.
• the said binding information can be encapsulated directly in the SM message or in a PCO/ePCO IE inside the SM message.
• the binding information of QoS flow and QUIC connection comprise:
• QoS flow information may be a QFI (QoS flow identifier) corresponds to the QoS flow that is used to sets up the QUIC connection; and
• the QUIC connection information comprises at least one of: a QUIC Connection identifier (ID) of the QUIC connection, a Server ID part of the QUIC Connection ID or a range of the QUIC Connection ID.
• ID QUIC Connection identifier
• the QUIC Connection ID in) the QUIC connection information comprises at least one of the QUIC Connection ID at the UE side, the QUIC Connection ID at the remote server side, or both of the QUIC Connection ID at the UE side and the QUIC Connection ID at the remote server side.
• the SMF may determine to update the PFCP rules based on the received binding information when/after receiving the binding information of the QoS flow and the QUIC connection.
• the SMF can use the binding information to update the Packet Detection Rule (PDR) , as per following:
• the QUIC Connection ID allocated by the UE in the DL PDR associated with the indicated QFI to instruct the UPF to detect and filter the downlink traffic of that QUIC connection.
• the QUIC Connection ID allocated by the remote server may also be included in the DL PDR; and/or
• the QUIC Connection ID allocated by the UE may also be presented/comprised in the UL PDR.
• step 206 the UPF sends a PFCP Session Modification Response message to the SMF.
• step 207 the UPF installs the updated PFCP rules received from the SMF. After/Once the updated PFCP rules are installed, the UPF can use the QFI and the QUIC Connection ID (s) present in the UL/DL PDR to detect and guard the QUIC traffic transmitted over the indicated QoS flow.
• the UPF can use the QFI and the QUIC Connection ID (s) present in the UL/DL PDR to detect and guard the QUIC traffic transmitted over the indicated QoS flow.
• the UE reports the binding information of the QoS flow and the QUIC connection to the UPF. For example, the UE may select an appropriate QoS flow to set up a QUIC connection towards the remote server (e.g., the Application Server) . After/Once the QUIC connection is established, the UE can report the binding information of the QoS flow and the QUIC connection to the UPF, e.g., via a direct user plane message to the UPF.
• the remote server e.g., the Application Server
• FIG. 3 shows a schematic diagram of a procedure according to an embodiment of the present disclosure.
• the UE reports the binding information of the QoS flow and the corresponding QoS connection to the UPF.
• a PDU session is established upon request (s) from the UE.
• the UE sets up a QUIC connection with the remote server over an appropriate QoS flow selected by the UE.
• the UE may first select an appropriate QoS flow that fulfils the QoS requirement of the application.
• a pair of QUIC Connection IDs is allocated by the UE and the remote server and these QUIC Connection IDs are exchanged between the peer sides.
• step 305 the SMF sends a PFCP Session Report Response to the UPF.
• the SMF may determine to update the PFCP rules based on the received binding information.
• the way of the SMF updating the PFCP rules based on the received information is similar to that of step 204.
• Steps 307 to 309 are similar to steps 205 to 207. Thus, the detail of the steps 307 to 309 can be referred to steps 205 to 207.
• the UE may be locally configured or preconfigured to report the binding information of the QoS flow and the QUIC connection to the network.
• the SMF sends an instruction to the UE for indicating a need of reporting the binding information of the QoS flow and the QUIC connection.
• the UE may be instructed by the network to report the binding information of the QoS flow and the QUIC connection.
• the SMF may send the indication to the UE to trigger the reporting of the said binding information.
• FIG. 4 shows a schematic diagram of a procedure according to an embodiment of the present disclosure.
• the SMF sends indication to the UE to instruct/trigger the reporting of the binding information of the QoS flow and the QUIC connection.
• step 401 the PDU session is established upon requests from the UE.
• the SMF initiates an SM message (e.g., PDU Session Modification Request) towards the UE, wherein the SM message carries the QUIC information reporting indication.
• an SM message e.g., PDU Session Modification Request
• the QUIC information reporting indication is used to instruct the UE to report the binding information of the QoS flow and the QUIC connection and can be encapsulated by one of the following ways:
• URSP UE Route Selection Policy
• additional indication may be presented/transmitted together with the QUIC information reporting indication (i.e., by the method of inclusion) : QUIC information reporting method.
• the QUIC information reporting indication may further indicate a method used by the UE for reporting the binding information of the QoS flow and the QUIC connection.
• the QUIC information reporting indication may comprise a value indicating that the binding information is reported by one of: PCO/ePCO IE, the direct user plane message, or by the PMFP message.
• the UE sets up a QUIC connection with the remote server (e.g., its application server) over an appropriate QoS flow selected by the UE.
• the remote server e.g., its application server
• the SMF/UPF receives the binding information of the QoS flow and the QUIC connection and can use the received binding information to update the PFCP rules of handling the QUIC traffic.
• the UPF therefore can use the updated PFCP rules to detect the QUIC traffic transmission over the corresponding QoS flow.
• the UPF may further guard whether QUIC traffic belonging to one QUIC connection is correctly transmitted over an indicated QoS flow. If not, the UPF may report such mis-behavior to the SMF, e.g., by sending a PFCP session report which indicates the wrong binding information of the QoS flow and the QUIC connection.
• FIG. 5 relates to a schematic diagram of a wireless terminal 50 according to an embodiment of the present disclosure.
• the wireless terminal 50 may be a user equipment (UE) , a mobile phone, a laptop, a tablet computer, an electronic book or a portable computer system and is not limited herein.
• the wireless terminal 50 may include a processor 500 such as a microprocessor or Application Specific Integrated Circuit (ASIC) , a storage unit 510 and a communication unit 520.
• the storage unit 510 may be any data storage device that stores a program code 512, which is accessed and executed by the processor 500.
• Embodiments of the storage unit 510 include but are not limited to a subscriber identity module (SIM) , read-only memory (ROM) , flash memory, random-access memory (RAM) , hard-disk, and optical data storage device.
• SIM subscriber identity module
• ROM read-only memory
• RAM random-access memory
• the communication unit 520 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 500. In an embodiment, the communication unit 520 transmits and receives the signals via at least one antenna 522 shown in FIG. 5.
• the storage unit 510 and the program code 512 may be omitted and the processor 500 may include a storage unit with stored program code.
• the processor 500 may implement any one of the steps in exemplified embodiments on the wireless terminal 50, e.g., by executing the program code 512.
• the communication unit 520 may be a transceiver.
• the communication unit 520 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless network node (e.g., a base station) .
• a wireless network node e.g., a base station
• FIG. 6 relates to a schematic diagram of a wireless network node 60 according to an embodiment of the present disclosure.
• the wireless network node 60 may be a satellite, a base station (BS) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU) , a gNB distributed unit (gNB-DU) a data network, a core network or a Radio Network Controller (RNC) , and is not limited herein.
• BS base station
• MME Mobility Management Entity
• S-GW Serving Gateway
• PDN Packet Data Network Gateway
• RAN radio access network
• NG-RAN next generation RAN
• gNB next generation RAN
• gNB next generation RAN
• the wireless network node 60 may comprise (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
• the wireless network node 60 may include a processor 600 such as a microprocessor or ASIC, a storage unit 610 and a communication unit 620.
• the storage unit 610 may be any data storage device that stores a program code 612, which is accessed and executed by the processor 600. Examples of the storage unit 610 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
• the communication unit 620 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 600.
• the communication unit 620 transmits and receives the signals via at least one antenna 622 shown in FIG. 6.
• the storage unit 610 and the program code 612 may be omitted.
• the processor 600 may include a storage unit with stored program code.
• the binding information comprises QoS flow information QUIC connection information.
• the QoS flow information comprises a QFI of the QoS flow.
• the wireless terminal may receive a QUIC information indication from the SMF.
• the wireless terminal transmits the binding information.
• the QUIC information reporting indication may be received in an SM message (e.g., in a PCO IE or an ePCO IE of the SM message.
• the wireless terminal receives a method indication associated with transmitting/reporting the binding information. Based on the method indication, the wireless terminal determines the method of transmitting the binding information. For example, the method indication may be transmitted together with or carried/comprised in the QUIC information reporting indication.
• Step 801 Receive binding information of a QoS flow and a QUIC connection between a wireless terminal and a remote terminal.
• Step 802 Update at least one PFCP rule associated with QUIC traffic based on the binding information.
• Step 803 Transmit, to a UPF, the at least one PFCP rule.
• the SMF receives binding information of a QoS flow and a QUIC connection between a wireless terminal (e.g., UE) and a remote terminal (e.g., application server) . That is, QUIC traffic of the QUIC connection may be transmitted on the QoS flow indicated in the binding information.
• the SMF updates PFCP rule (s) associated with the QUIC traffic of the QUIC connection and transmits the updated PFCP rule (s) to the UPF, to allow the UPF to detect and guard the QUIC traffic of the QUIC connection on the QoS flow.
• the binding information comprises QoS flow information QUIC connection information.
• the QoS flow information comprises a QFI of the QoS flow.
• the QoS connection information comprises at least one of a QUIC Connection ID of the QUIC connection, a Server ID part of the QUIC Connection ID or a range of the QUIC Connection ID.
• the QoS Connection ID in the QoS connection information may comprises a QoS Connection ID at the wireless terminal side and/or another QoS Connection ID at the remote terminal side.
• the QoS Connection ID at the wireless terminal side may be used to update the PFCP rule for downlink QUIC traffic and/or the QoS Connection ID at the remote terminal side may be used to update the PDCP rule for uplink QUIC traffic.
• the at least one PFCP rule comprises a first Packet Detection Rule associated with the QFI of the QoS flow and the information of the QUIC connection (e.g., the QUIC Connection ID (s) and/or Server ID part of the QUIC Connection ID (s) and/or a range of the QUIC Connection ID (s) ) .
• a first Packet Detection Rule associated with the QFI of the QoS flow and the information of the QUIC connection (e.g., the QUIC Connection ID (s) and/or Server ID part of the QUIC Connection ID (s) and/or a range of the QUIC Connection ID (s) ) .
• the binding information is received from the wireless terminal.
• the binding information may be received/carried in an SM message (e.g., in a PCO IE or an ePCO IE of the SM message) .
• the binding information is received from the UPF.
• the binding information may be received in a PMFP Session Report message.
• the SMF further transmits a QUIC information reporting indication associated with a transmission of the binding information to the wireless terminal.
• the QUIC information reporting indication may be received/carried in an SM message (e.g., in a PCO IE or an ePCO IE of the SM message) or in a user equipment route selection policy (URSP) rule.
• SM message e.g., in a PCO IE or an ePCO IE of the SM message
• URSP user equipment route selection policy
• the SMF further transmits a method indication associated with transmitting the binding information to the wireless terminal.
• the method indication may be transmitted together with or in the QUIC information reporting indication.
• FIG. 9 shows a flowchart of a method according to an embodiment of the present disclosure.
• the method shown in FIG. 9 may be used in a UPF (e.g., wireless network node/device comprising the UPF or wireless network node/device performing/having at least part of functionalities of the UPF) and comprises the following steps:
• a UPF e.g., wireless network node/device comprising the UPF or wireless network node/device performing/having at least part of functionalities of the UPF
• Step 901 Receive, from an SMF, at least one PFCP rule associated with QUIC traffic of a QUIC connection between a wireless terminal and a remote terminal.
• Step 902 Apply the at least one PFCP rule to the QUIC traffic.
• the UPF receives PFCP rule (s) associated with QUIC traffic of a QUIC connection between a wireless terminal (e.g., UE) and a remote terminal (e.g., remote server or application server) .
• the UPF applies the received PFCP rule (s) on/for the QUIC traffic of the QUIC connection.
• the at least one PFCP rule comprises a first Packet Detection Rule associated with the QFI of the QoS flow and the information of the QUIC connection (e.g., the QUIC Connection ID (s) and/or Server ID part of the QUIC Connection ID (s) and/or a range of the QUIC Connection ID (s) ) .
• a first Packet Detection Rule associated with the QFI of the QoS flow and the information of the QUIC connection (e.g., the QUIC Connection ID (s) and/or Server ID part of the QUIC Connection ID (s) and/or a range of the QUIC Connection ID (s) ) .
• the UPF applies the PFCP rule on/for the QUIC traffic by using a QFI and a QUIC Connection ID indicated in the at least one PFCP rule to detect and guard the QUIC traffic of the QUIC Connection.
• the UPF receives binding information associated with a QoS flow and the QUIC connection and transmits the received binding information to the SMF.
• the details of the binding information can be referred to the above embodiments.
• the UPF receives the binding information in a direct user plane message from the wireless terminal (e.g., PMFP message) .
• the UPF transmits the binding information in a PMFP Session Report message.
• any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
• any one of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a “software unit” ) , or any combination of these techniques.
• IC integrated circuit
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
• a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
• a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
• Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
• a storage media can be any available media that can be accessed by a computer.
• such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
• unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.
• memory or other storage may be employed in embodiments of the present disclosure.
• memory or other storage may be employed in embodiments of the present disclosure.
• any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
• functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
• references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (1)

Publications (1)

Family

ID=91955111

Family Applications (1)

Country Status (3)

Family Cites Families (4)

• 2023
  • 2023-01-20 EP EP23916815.6A patent/EP4623596A1/de active Pending
  • 2023-01-20 WO PCT/CN2023/073309 patent/WO2024152336A1/en not_active Ceased
  • 2023-01-20 CN CN202380088332.7A patent/CN120530660A/zh active Pending

Also Published As

Similar Documents

Legal Events