WO2024209366A1 - Procédé et appareil associés à des flux de service d'application comprenant des unités de données de protocole appartenant à des ensembles d'unités de données de protocole et des unités de données de protocole n'appartenant pas à des ensembles d'unités de données de protocole - Google Patents

Procédé et appareil associés à des flux de service d'application comprenant des unités de données de protocole appartenant à des ensembles d'unités de données de protocole et des unités de données de protocole n'appartenant pas à des ensembles d'unités de données de protocole Download PDF

Info

Publication number
WO2024209366A1
WO2024209366A1 PCT/IB2024/053245 IB2024053245W WO2024209366A1 WO 2024209366 A1 WO2024209366 A1 WO 2024209366A1 IB 2024053245 W IB2024053245 W IB 2024053245W WO 2024209366 A1 WO2024209366 A1 WO 2024209366A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol data
data unit
quality
rule
information identifying
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IB2024/053245
Other languages
English (en)
Inventor
Colin Kahn
Devaki Chandramouli
Markus Sakari ISOMÄKI
Matti Einari Laitila
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to CN202480023705.7A priority Critical patent/CN121002940A/zh
Publication of WO2024209366A1 publication Critical patent/WO2024209366A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0268Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/20Traffic policing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/31Flow control; Congestion control by tagging of packets, e.g. using discard eligibility [DE] bits

Definitions

  • Example embodiments of the subject matter described herein relate to apparatus, a method, and a computer program, for wireless communication networks and in particular, but not exclusively to apparatus, methods and computer programs for processing application service flows comprising protocol data units belonging to protocol data unit sets and protocol data units not belonging to protocol data unit sets.
  • the protocol data units of an application service flow may include a combination of protocol data units that belong to a protocol data unit set and protocol data units that do not belong to a protocol data unit set.
  • a method comprising: receiving by a user plane function of a core network of a wireless communication network information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined by the user plane function to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined by the user plane function to not belong to a protocol data unit set; and processing by the user plane function a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined by the user plane function to belong to a protocol data unit set.
  • the method may further comprise receiving from a session management function a first packet detection rule comprising information identifying the at least one first protocol data unit processing rule, and receiving from the session management function a second packet detection rule comprising information identifying the at least one second protocol data unit processing rule.
  • the first packet detection rule may comprise one or more of: information identifying a forwarding action rule specifying the addition of protocol data unit set information to a message header for sending a protocol data unit by the user plane function to a radio access network node of the communications system; information identifying a quality of service enforcement rule specifying a quality of service flow identifier; information identifying a usage reporting rule.
  • Application of the first packet detection rule and application of the second packet detection rule to a protocol data unit may both be dependent on user plane function determining that the protocol data unit belongs to the application service flow; wherein application of the first packet detection rule to a protocol data unit is additionally dependent on the user plane function determining that the protocol data unit belongs to a protocol data unit set; and application of the second packet detection rule to a protocol data unit is not additionally dependent on the user plane function determining that the protocol data unit belongs to a protocol data unit set; and wherein processing the protocol data unit may comprise checking whether the first packet detection rule is applicable to the protocol data unit, and only checking whether the second packet detection rule is applicable to the protocol data unit in the event that the first packet detection rule is not applicable to the protocol data unit.
  • the determination of whether a protocol data unit belongs to a protocol data unit set may be based on protocol description information received from the session management function as part of the first packet detection rule.
  • the method may further comprise receiving from a session management function a single packet detection rule comprising information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule
  • the method may comprise, based on determining by the user plane function that the single packet detection rule is applicable to a protocol data unit, determining, by the user plane function, whether the protocol data unit belongs to a protocol data unit set; and based on determining by the user plane function that the protocol data unit belongs to a protocol data unit set, using the at least one first protocol data unit processing rule for processing the protocol data unit.
  • the at least one first protocol data unit processing rule may comprise at least one of: information identifying a forwarding action rule specifying the addition of protocol data unit set information to a message header for sending a protocol data unit by the user plane function to a radio access network of the communications system; information identifying a quality of service enforcement rule specifying a quality of service flow identifier; information identifying a usage report rule.
  • the method may comprise: based on determining by the user plane function that the single packet detection rule is applicable to a protocol data unit, determining whether the protocol data unit belongs to a protocol data unit set; and based on determining by the user plane function that the protocol data unit does not belong to a protocol data unit set, using the at least one second protocol data unit processing rule for processing the protocol data unit.
  • the determination of whether a protocol data unit belongs to a protocol data unit set may be based on protocol description information received from the session management function as part of the single packet detection rule.
  • a method comprising: receiving by a session management function information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; generating by the session management function at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generating by the session management function at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and sending by the session management function information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • the method may further comprise receiving by the session management function a first policy and charging control rule comprising information identifying at least one first quality of service parameter; and receiving by the session management function a second policy and charging control rule comprising information identifying the at least one second quality of service parameter; and wherein the first and second policy and charging control rules share a service flow template.
  • the method may further comprise receiving by the session management function a single policy and charging control rule comprising information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter.
  • the method may comprise sending to the user plane function a first packet detection rule comprising information identifying the at least one first protocol data unit processing rule; and sending to the user plane function information identifying the at least one second protocol data unit processing rule.
  • the method may comprise sending to the user plane function a single packet detection rule comprising information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule.
  • the method may comprise: setting up a first quality of service flow based on the at least one first quality of service parameter, and a second quality of service flow based on the at least one second quality of service parameter; sending information identifying at least one first quality of service rule for the first quality of service flow to a user equipment associated with the application service flow, and sending information identifying at least one second quality of service rule for the second quality of service flow to the user equipment associated with the application service flow; and sending information identifying at least one first quality of service profile for the first quality of service flow to a radio access network serving the user equipment, and sending information identifying at least one second quality of service profile for the second quality of service flow to the radio access network serving the user equipment.
  • a method comprising: generating by a policy control function of a wireless communication network at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending by the policy control function information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function of the wireless communications network.
  • the method may comprise receiving from an application function of the communications system by the policy control function quality of service requirement information for the application service flow; wherein the quality of service requirement information identifies the at least one first quality of service requirement and the least one second quality of service requirement.
  • a method comprising: generating by an application function quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending by the application function the quality of service requirement information to a session management function of a wireless communication network.
  • the header information may indicate that the protocol data unit belongs to a protocol data unit set having a size of one protocol data unit.
  • Apparatus comprising: means for receiving information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined to not belong to a protocol data unit set; and means for processing a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined to belong to a protocol data unit set.
  • the apparatus may further comprise: means for receiving from a session management function a first packet detection rule comprising information identifying the at least one first protocol data unit processing rule, and receiving from the session management function a second packet detection rule comprising information identifying the at least one second protocol data unit processing rule.
  • the first packet detection rule may comprise one or more of: information identifying a forwarding action rule specifying the addition of protocol data unit set information to a message header for sending a protocol data unit to a radio access network node of the communications system; information identifying a quality of service enforcement rule specifying a quality of service flow identifier; information identifying a usage reporting rule.
  • Application of the first packet detection rule and application of the second packet detection rule to a protocol data unit may both be dependent on determining that the protocol data unit belongs to the application service flow; wherein application of the first packet detection rule to a protocol data unit is additionally dependent on determining that the protocol data unit belongs to a protocol data unit set; and application of the second packet detection rule to a protocol data unit is not additionally dependent on determining that the protocol data unit belongs to a protocol data unit set; and wherein the means for processing the protocol data unit comprises means for checking whether the first packet detection rule is applicable to the protocol data unit, and only checking whether the second packet detection rule is applicable to the protocol data unit in the event that the first packet detection rule is not applicable to the protocol data unit.
  • the determination of whether a protocol data unit belongs to a protocol data unit set may be based on protocol description information received from the session management function as part of the first packet detection rule.
  • the apparatus may further comprise: means for receiving from a session management function a single packet detection rule comprising information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule
  • the apparatus may further comprise: means for, based on determining that the single packet detection rule is applicable to a protocol data unit, determining whether the protocol data unit belongs to a protocol data unit set; and means for, based on determining that the protocol data unit belongs to a protocol data unit set, using the at least one first protocol data unit processing rule for processing the protocol data unit.
  • the at least one first protocol data unit processing rule may comprise at least one of: information identifying a forwarding action rule specifying the addition of protocol data unit set information to a message header for sending a protocol data unit by the user plane function to a radio access network of the communications system; information identifying a quality of service enforcement rule specifying a quality of service flow identifier; information identifying a usage report rule.
  • the apparatus may comprise: means for, based on determining that the single packet detection rule is applicable to a protocol data unit, determining whether the protocol data unit belongs to a protocol data unit set; and means for, based on determining that the protocol data unit does not belong to a protocol data unit set, using the at least one second protocol data unit processing rule for processing the protocol data unit.
  • the determination of whether a protocol data unit belongs to a protocol data unit set may be based on protocol description information received from the session management function as part of the single packet detection rule.
  • Apparatus comprising: means for receiving information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; means for generating at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generating at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and means for sending information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • the apparatus may comprise: means for receiving a single policy and charging control rule comprising information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter.
  • the apparatus may comprise: means for setting up a first quality of service flow based on the at least one first quality of service parameter, and a second quality of service flow based on the at least one second quality of service parameter; means for sending information identifying at least one first quality of service rule for the first quality of service flow to a user equipment associated with the application service flow, and sending information identifying at least one second quality of service rule for the second quality of service flow to the user equipment associated with the application service flow; and means for sending information identifying at least one first quality of service profile for the first quality of service flow to a radio access network serving the user equipment, and sending information identifying at least one second quality of service profile for the second quality of service flow to the radio access network serving the user equipment.
  • Apparatus comprising: means for generating at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and means for sending information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function.
  • the apparatus may comprise: means for receiving from an application function quality of service requirement information for the application service flow; wherein the quality of service requirement information identifies the at least one first quality of service requirement and the least one second quality of service requirement.
  • Apparatus comprising: means for generating quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and means for sending the quality of service requirement information to a session management function.
  • Apparatus comprising: means for receiving a protocol data unit belonging to an application service flow; means for determining whether the protocol data unit belongs to a protocol data unit set; and means for, based on determining that the protocol data unit is not identifiable as belonging to a protocol data unit set, sending the protocol data unit to a radio access network node of the wireless communication network with header information linking the protocol data unit to a quality of service flow also comprising a protocol data unit determined as belonging to a protocol data unit set.
  • the header information may indicate that the protocol data unit belongs to a protocol data unit set having a size of one protocol data unit.
  • Apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus to perform: receiving information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined to not belong to a protocol data unit set; and processing a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined to belong to a protocol data unit set.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: receive from a session management function a first packet detection rule comprising information identifying the at least one first protocol data unit processing rule, and receive from the session management function a second packet detection rule comprising information identifying the at least one second protocol data unit processing rule.
  • the first packet detection rule may comprise one or more of: information identifying a forwarding action rule specifying the addition of protocol data unit set information to a message header for sending a protocol data unit to a radio access network node of the communications system; information identifying a quality of service enforcement rule specifying a quality of service flow identifier; information identifying a usage reporting rule.
  • Application of the first packet detection rule and application of the second packet detection rule to a protocol data unit may both be dependent on determining that the protocol data unit belongs to the application service flow; wherein application of the first packet detection rule to a protocol data unit is additionally dependent on determining that the protocol data unit belongs to a protocol data unit set; and application of the second packet detection rule to a protocol data unit is not additionally dependent on determining that the protocol data unit belongs to a protocol data unit set; and wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to: check whether the first packet detection rule is applicable to the protocol data unit, and only check whether the second packet detection rule is applicable to the protocol data unit in the event that the first packet detection rule is not applicable to the protocol data unit.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: determine whether a protocol data unit belongs to a protocol data unit set based on protocol description information received from the session management function as part of the first packet detection rule.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: receive from a session management function a single packet detection rule comprising information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: based on determining that the single packet detection rule is applicable to a protocol data unit, determine whether the protocol data unit belongs to a protocol data unit set; and based on determining that the protocol data unit belongs to a protocol data unit set, use the at least one first protocol data unit processing rule for processing the protocol data unit.
  • the at least one first protocol data unit processing rule may comprise at least one of: information identifying a forwarding action rule specifying the addition of protocol data unit set information to a message header for sending a protocol data unit to a radio access network; information identifying a quality of service enforcement rule specifying a quality of service flow identifier; information identifying a usage report rule.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: based on determining that the single packet detection rule is applicable to a protocol data unit, determine whether the protocol data unit belongs to a protocol data unit set; and based on determining that the protocol data unit does not belong to a protocol data unit set, use the at least one second protocol data unit processing rule for processing the protocol data unit.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: determine whether a protocol data unit belongs to a protocol data unit set based on protocol description information received from the session management function as part of the single packet detection rule.
  • Apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus to perform: receiving information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; generating at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generating at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and sending information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: receive a first policy and charging control rule comprising information identifying at least one first quality of service parameter, and receive a second policy and charging control rule comprising information identifying the at least one second quality of service parameter; and wherein the first and second policy and charging control rules share a service flow template.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: receive a single policy and charging control rule comprising information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: send to the user plane function a first packet detection rule comprising information identifying the at least one first protocol data unit processing rule; and send to the user plane function a second packet detection rule comprising information identifying the at least one second protocol data unit processing rule.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: send to the user plane function a single packet detection rule comprising information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: set up a first quality of service flow based on the at least one first quality of service parameter, and a second quality of service flow based on the at least one second quality of service parameter; send information identifying at least one first quality of service rule for the first quality of service flow to a user equipment associated with the application service flow, and send information identifying at least one second quality of service rule for the second quality of service flow to the user equipment associated with the application service flow; and send information identifying at least one first quality of service profile for the first quality of service flow to a radio access network serving the user equipment, and send information identifying at least one second quality of service profile for the second quality of service flow to the radio access network serving the user equipment.
  • Apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus to perform: generating at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function.
  • the at least one memory and computer program code may be configured to, with the at least one processor, cause the apparatus to: receive from an application function quality of service requirement information for the application service flow; wherein the quality of service requirement information identifies the at least one first quality of service requirement and the least one second quality of service requirement.
  • Apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus to perform: generating quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending the quality of service requirement information to a session management function.
  • Apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus to perform: receiving a protocol data unit belonging to an application service flow; determining whether the protocol data unit belongs to a protocol data unit set; and based on determining that the protocol data unit is not identifiable as belonging to a protocol data unit set, sending the protocol data unit to a radio access network node of the wireless communication network with header information linking the protocol data unit to a quality of service flow also comprising a protocol data unit determined as belonging to a protocol data unit set.
  • the header information may indicate that the protocol data unit belongs to a protocol data unit set having a size of one protocol data unit.
  • Apparatus comprising: receiving circuitry for receiving information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined to not belong to a protocol data unit set; and processing circuitry for processing a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined to belong to a protocol data unit set.
  • Apparatus comprising: receiving circuitry for receiving information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; generating circuitry for generating at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generating at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and sending circuitry for sending information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • Apparatus comprising: generating circuitry for generating at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending circuitry for sending information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function.
  • Apparatus comprising: generating circuitry for generating quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending circuitry for sending the quality of service requirement information to a session management function.
  • Apparatus comprising: receiving circuitry for receiving a protocol data unit belonging to an application service flow; determining circuitry for determining whether the protocol data unit belongs to a protocol data unit set; and sending circuitry for, based on determining that the protocol data unit is not identifiable as belonging to a protocol data unit set, sending the protocol data unit to a radio access network node with header information linking the protocol data unit to a quality of service flow also comprising a protocol data unit determined as belonging to a protocol data unit set.
  • a non-transitory computer readable medium comprising instructions stored thereon which, when executed by at least one processor cause the at least one processor to perform the operations comprising: receiving information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined to not belong to a protocol data unit set; and processing a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined to belong to a protocol data unit set.
  • a non-transitory computer readable medium comprising instructions stored thereon which, when executed by at least one processor cause the at least one processor to perform the operations comprising: receiving information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; generating at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generating at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and sending information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • a non-transitory computer readable medium comprising instructions stored which, when executed by at least one processor cause the at least one processor to perform the operations comprising: generating at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function.
  • a non-transitory computer readable medium comprising instructions stored which, when executed by at least one processor cause the at least one processor to perform the operations comprising: generating quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending the quality of service requirement information to a session management function.
  • a computer readable medium comprising instructions stored thereon which, when executed by at least one processor cause the at least one processor to perform the operations comprising: receiving a protocol data unit belonging to an application service flow; determining whether the protocol data unit belongs to a protocol data unit set; and based on determining that the protocol data unit is not identifiable as belonging to a protocol data unit set, sending the protocol data unit to a radio access network node of the wireless communication network with header information linking the protocol data unit to a quality of service flow also comprising a protocol data unit determined as belonging to a protocol data unit set.
  • a non-transitory computer readable medium comprising instructions stored thereon which, when executed by at least one processor cause the at least one processor to perform the operations comprising: receiving information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined to not belong to a protocol data unit set; and processing a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined to belong to a protocol data unit set.
  • a non-transitory computer readable medium comprising instructions stored thereon which, when executed by at least one processor cause the at least one processor to perform the operations comprising: receiving information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; generating at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generating at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and sending information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • a non-transitory computer readable medium comprising program instructions stored thereon for performing: generating at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function.
  • a non-transitory computer readable medium comprising program instructions stored thereon for performing: generating quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and sending the quality of service requirement information to a session management function.
  • a non-transitory computer readable medium comprising program instructions stored thereon for performing: receiving a protocol data unit belonging to an application service flow; determining whether the protocol data unit belongs to a protocol data unit set; and based on determining that the protocol data unit is not identifiable as belonging to a protocol data unit set, sending the protocol data unit to a radio access network node of the wireless communication network with header information linking the protocol data unit to a quality of service flow also comprising a protocol data unit determined as belonging to a protocol data unit set.
  • a computer program comprising computer executable code which when run on at least one processor is configured to cause an apparatus to: receive information identifying at least one first protocol data unit processing rule and at least one second protocol data unit processing rule for protocol data units belonging to an application service flow, wherein the at least one first protocol data unit processing rule is for protocol data units determined to belong to a protocol data unit set; and the at least one second protocol data unit processing rule is for protocol data units determined to not belong to a protocol data unit set; and process a protocol data unit belonging to the application service flow according to the at least one first protocol data unit processing rule or according to the at least one second protocol data unit processing rule depending on whether or not the protocol data unit is determined to belong to a protocol data unit set.
  • a computer program comprising computer executable code which when run on at least one processor is configured to cause an apparatus to: receive information identifying at least one first quality of service parameter for protocol data units belonging to an application service flow and belonging to a protocol data unit set, and information identifying at least one second quality of service parameter for protocol data units belonging to the application service flow and not belonging to a protocol data unit set; generate at least one first protocol data unit processing rule for a user plane function based on the at least one first quality of service parameter, and generate at least one second protocol data unit processing rule for the user plane function based on the at least one second quality of service parameter; and send information identifying the at least one first protocol data unit processing rule and information identifying the at least one second protocol data unit processing rule to the user plane function.
  • a computer program comprising computer executable code which when run on at least one processor is configured to cause an apparatus to: generate at least one first quality of service parameter for an application service flow based on at least one first quality of service requirement for protocol data units belonging to a protocol data unit set, and at least one second quality of service parameter for the application service flow based on at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and send information identifying the at least one first quality of service parameter and information identifying the at least one second quality of service parameter to a session management function.
  • a computer program comprising computer executable code which when run on at least one processor is configured to cause an apparatus to: generate quality of service requirement information for an application service flow; wherein the quality of service requirement information identifies at least one first quality of service requirement for protocol data units belonging to a protocol data unit set; and at least one second quality of service requirement for protocol data units not belonging to a protocol data unit set; and send the quality of service requirement information to a session management function.
  • a computer program comprising computer executable code which when run on at least one processor is configured to cause an apparatus to: receive a protocol data unit belonging to an application service flow; determine whether the protocol data unit belongs to a protocol data unit set; and based on determining that the protocol data unit is not identifiable as belonging to a protocol data unit set, send the protocol data unit to a radio access network node with header information linking the protocol data unit to a quality of service flow also comprising a protocol data unit determined as belonging to a protocol data unit set.
  • FIG. 2 shows a representation of an example of control plane signalling (control plane messages) between the application function (AF), 5G core (5GC) network, Next Generation Radio Access Network (NG-RAN) and user equipment (UE) of Figure 1 according to some example embodiments;
  • AF application function
  • 5GC 5G core
  • NG-RAN Next Generation Radio Access Network
  • UE user equipment
  • Figure 3 shows a representation of operations performed by the user plane function of Figure 1 according to an example embodiment
  • Figure 5 shows a representation of operations performed by the user plane function of Figure 1 according to some other example embodiments
  • Figure 6 shows a representation of operations performed by the user plane function of Figure 1 according to some other example embodiments.
  • Figure 9 shows a representation of an example of non-volatile memory media.
  • the following description focusses on the example of a wireless communications network operating according to a radio access technology, such as 5G or NR, but the underlying methods disclosed herein may also be applicable to wireless communication networks operating according to other radio access technologies, such as 6G or the like.
  • Fig. 1 shows a simple representation of one example of a wireless communication network comprising a 5G system.
  • the 5G system includes a user equipment (UE), a next generation radio access network (NG-RAN), and a 5G core network (5GC).
  • UE user equipment
  • NG-RAN next generation radio access network
  • GC 5G core network
  • All the units shown in Figure 1 are logical units.
  • the connections shown in Figure 1 are logical connections; the actual physical connections may be different.
  • a 5G core network may comprise additional instances of the network functions shown in Figure 1.
  • the core network provides connections between the user equipment (UE)) and one or more data networks (DN) via a Next Generation Radio Access Network (NG-RAN) comprising radio access network nodes, such as a gNB (gNodeB) or eNB.
  • NG-RAN Next Generation Radio Access Network
  • gNB gNodeB
  • eNB gNodeB
  • a radio access network node e.g., gNB
  • UPF user plane function
  • the one or more data networks may include a packet data network.
  • UE user equipment
  • UE may refer to any type of wireless communication device.
  • the UE may be a mobile or static device (e.g. a portable or non-portable computing device) including, but not limited to, the following types of devices: mobile phone, smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, Virtual Reality device, Augmented Reality device, Mixed Reality device, other Extended Reality device and multimedia device. It should be appreciated that a UE may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • PDA personal digital assistant
  • laptop and/or touch screen computer tablet, game console, notebook, Virtual Reality device, Augmented Reality device, Mixed Reality device, other Extended Reality device and multimedia device.
  • a UE may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a UE may also be a wireless communication device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction, e.g., to be used in smart power grids and connected vehicles.
  • the UE may also utilise cloud.
  • a UE may comprise a user portable device with radio parts (such as a watch, earphones, extended reality headset or eyeglasses) and the computation is carried out in the cloud.
  • the NG-RAN may include one or more radio access nodes (e.g., gNB).
  • a radio access node e.g., gNB
  • MIMO multiple input - multiple output
  • the NG-RAN may include large numbers of RAN nodes (e.g., gNBs) including macro RAN nodes operating in co-operation with smaller RAN nodes and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available.
  • a 5GS may be used for communications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control).
  • mMTC massive machine-type communications
  • a 5GS may employ multiple frequency bands, e.g., below 6GHz or above 24 GHz, cmWave and mmWave, and may also be integrable with existing legacy radio access technologies, such as LTE. Integration with LTE may be implemented, as a system, where macro coverage is provided by LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, a 5GS may support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, 6 or above 24 GHz - cmWave and mmWave).
  • 5G networks may employ network slicing, in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.
  • the 5GC has a service-based architecture (SB A) for the control plane as shown and described in Figure 4.2.3-1 of 3GPP TS 23.501and communication between network functions in the control plane is performed using Service Based Interfaces (SBIs). Application Programming Interfaces (APIs) are used for the SBIs.
  • SBIs Service Based Interfaces
  • APIs Application Programming Interfaces
  • Some protocol data units of an application service flow may belong to a PDU set comprising one or more PDUs.
  • a PDU Set for an application service flow may comprise one or more PDUs carrying the payload of one unit of information generated at the application level (e.g., a video frame or video slice for extended Reality (XR) services).
  • the same application service flow may also contain PDUs for which classification (i.e.
  • RTCP real-time transport control protocol
  • RTP real-time transport protocol
  • PDUs to control real-time transport protocol (RTP) flow(s)
  • PDUs that represent additional media components such as an audio stream where a unit of information generated at the application level may always fit into a single PDU.
  • the application service flow may contain a variety of PDUs that do not conform to a template, algorithm or other methodology used by the UPF to determine that a PDU belongs to a PDU Set.
  • PDU-set PDUs and non-PDU- set PDUs may be multiplexed into one single application service flow, for instance using the various Internet Engineering Task Force (IETF) protocol multiplexing options that cover, e.g., RTP with multiple media streams; RTCP; Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) (STUN); Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP) (DTLS-SRTP); and Web Real-Time Communication (WebRTC) data channel.
  • IETF Internet Engineering Task Force
  • Figure 2 shows a representation of an example of control plane signalling (control plane messages) sent between the AF, 5GC, NG-RAN, UE of Figure 1 according to some example embodiments; and
  • Figure 3 shows a representation of an example of operations performed by UPF of Figure 1 according to some example embodiments.
  • a policy control function generates (or is configured to generate) at least first and second policy and charging control rules (PCC rules) for an application service flow between a data network (DN) and a user equipment (UE) via at least one UPF instance of the 5G core and a radio access network (RAN) node.
  • the first PCC rule denoted PCC-1
  • the second PCC rule denoted PCC-2
  • the first and second PCC rules contain or include the same Service Flow Template.
  • the first and second PCC rules may be generated based on information, received from an application function (AF) (optionally via a network exposure function NEF), indicative of one or more quality of service (QoS) requirements (such as e.g. PDU Set delay budget, PDU Set error rate etc.) for PDUs of the application service flow that belong to PDU sets, and information indicative of one or more QoS requirements (such as e.g. packet delay budget, packet error rate etc.) for PDUs of the application service flow that do not belong to a PDU Set.
  • the AF sends (or is configured to send), at 100, a QoS request that includes information indicative of one or more quality of service (QoS) requirements (such as e.g.
  • the QoS requirements are determined by the PCF based on a local configuration of the PCF, where local configuration is performed by a network operator, for example via a management interface to the PCF.
  • the configuration may be associated with Network Slice Selection Assistance Information (NSSAI), Data Network Name (DNN), UE or Subscriber ID, UE or Subscriber Group in which case it can be applied without explicit input from an Application Function.
  • NSSAI Network Slice Selection Assistance Information
  • DNN Data Network Name
  • UE or Subscriber ID UE or Subscriber Group in which case it can be applied without explicit input from an Application Function.
  • the PCF sends at 200 the two PCC rules (e.g., the first PCC rule, PCC-1 and the second PCC rule, PCC-2) to the SMF instance associated with the application service flow.
  • the SMF receives the two PCC rules (e.g., the first PCC rule PCC-1 and the second PCC rule) PCC-2 and maps the two PCC rules to respective QoS flows (e.g., maps the first PCC rule PCC-1 to QoS flow 1 and maps the second PCC rule PCC-2 to QoS flow 2.
  • Each QoS flow is characterized by a QoS Profile, UPF instructions for the UPF instance involved in the application service flow, and QoS Rules.
  • SMF sends at 300 UPF instructions to UPF, sends at 400 QoS profiles for the QoS flows to the NG-RAN node (MESSAGING 400 of Figure 2); and sends at 500 the QoS rules for the QoS flows to the UE via the NG- RAN node.
  • the UPF instructions, QoS profile for the QoS flows, and the QoS rules for the QoS flows sent by the SMF at 300, 400, 500 may be sent by the SMF in any order.
  • QoS flow 1 is used for PDUs belonging to PDU Sets; and RAN applies the PDU Set QoS Parameters (e.g., PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB) and PDU-Set Integrated Handing Indication (PSIHI) specified in the QoS profile 1 to PDUs classified by UPF as belonging to PDU sets.
  • PSER PDU Set Error Rate
  • PSDB PDU Set Delay Budget
  • PSIHI PDU-Set Integrated Handing Indication
  • QoS Flow 2 is used for PDUs not belonging to a PDU Set; and the RAN applies QoS Parameters specified in the QoS Profile 2 (PDU Error Rate (PER) and PDU PDB) to PDUs classified by UPF as not belonging to a PDU Set.
  • PSER PDU Set Error Rate
  • PSDB PDU Set Delay Budget
  • PSIHI PDU-Set Integrated Handing Indication
  • SMF sends at 300 the UPF instructions to the UPF instance for the application service flow over the N4 interface.
  • the UPF instructions comprise first and second packet detection rules PDR-1 and PDR-2 for the application service flow.
  • PDR packet detection rule
  • a packet detection rule (PDR) has a format as set out at 3GPP 23.501 clause 5.8.2.11.3.
  • the “Source interface”, UE IP address”, “Network instance”, “CN tunnel info”, “Packet Filter Set”, “Application identifier”, “QoS Flow ID”, “Ethernet PDU Session Information” and “Framed Route Information” parts of the “Packet Detection Information” attribute have the same content for both PDR-1 and PDR-2.
  • the PDR-1 for PDUs that belong to a set of PDUs additionally includes an indicator that PDR-1 applies to PDUs that are classified by the UPF as belonging to a PDU set.
  • the indicator may e.g., take the form of a flag indicating that PDU Set information is to be sent to the NG-RAN node, or the indicator may be the presence of (or inclusion of) information in PDR-1 used by the UPF to enable PDU Set processing, such as a “Protocol Description” providing information about protocol headers and payload formats containing the information based on which the UPF can identify and form the PDU Sets. Depending on the specificity of this information the UPF may treat it either as a mere hint or as a rule.
  • this indicator is that the applicability of this PDR-1 to a PDU is dependent on the UPF classifying the PDU as belonging to a PDU set (i.e., the UPF identifying that the PDU belongs to a PDU set).
  • the applicability of PDR-2 to a PDU is dependent on the UPF not classifying the PDU as belonging to a PDU set (i.e., the UPF not identifying that PDU belongs to a PDU set).
  • PDR-1 is above PDR-2 in the precedence order in which the PDRs are to be checked against downlink PDUs by UPF. This precedence order may be implemented by SMF assigning to PDR-1 a higher PDR precedence value than SMF assigns to PDR-2.
  • UPF may be configured with a rule according to which any PDR that is indicated to be applicable to PDU-set PDUs is treated by UPF as having a higher precedence than any PDR that is not indicated to be applicable to PDU-set PDUs.
  • an explicit precedence value is not required to be provided by the SMF.
  • PDR-1 and PDR-2 each include information about at least one PDU processing rule.
  • the PDU processing rules comprise information identifying: a forwarding action rule, a usage reporting rule, and a QoS enforcement rule.
  • one or more of the “Forwarding Action Rule ID”, “List of Usage Reporting Rule ID(s)” and “List of QoS Enforcement Rule ID(s)” may have different values between PDR-1 and PDR- 2.
  • UPF receives PDR-1 and PDR-2 from SMF.
  • UPF determines whether PDR-1 is applicable to a downlink PDU (OPERATION 600 of Figure 3). If the UPF determines that PDR-1 applies to the PDU (i.e., PDU meets all the conditions specified by the packet detection information attribute of PDR-1, and the PDU is classified by UPF (i.e., identified by the UPF) as belonging to a PDU set), UPF applies to the PDU the PDU processing rules identified in PDR-1. Determining by UPF whether a PDU belongs to a PDU set may be done by UPF by inspecting the content and pattern of the application traffic flow in an implementation specific manner. For this the UPF may or may not utilize the “Protocol Description” or any other information provided by the SMF.
  • UPF determines whether PDR-2 (next in the PDR precedence order after PDR-1) is applicable to the PDU (OPERATION 610 of Figure 3). If the PDU meets all the conditions specified by the packet detection information attribute of PDR-2, UPF applies to the PDU the PDU processing rules identified in PDR-2. On the other hand, if UPF determines that the PDU does not meet all the conditions specified by the packet detection information attribute of PDR-2, UPF moves onto the next PDR in the PDR precedence order. In this example, there are only two PDRs for this application service flow, and a determination that PDR-2 is not applicable to the PDU indicates that the PDU does not belong to this application service flow (and may belong to a different application service flow).
  • PCF instead of generating two PCC rules for the application service flow, PCF generates for the application service flow a single PCC rule that comprises information identifying (e.g., references via a 5G QoS Identifier (5QI)) both PDU Set QoS Parameters (e.g. PSER, PSDB) for PDUs belonging to a PDU set, and PDU QoS parameters (PDB, PER) for PDUs not belonging to any PDU set.
  • PSER PDU Set QoS Parameters
  • PDU QoS parameters e.g. PSER, PSDB
  • PDU QoS parameters e.g. PDU QoS parameters
  • Figure 4 shows a representation of another example of control plane signalling (e.g., control plane messages) between the AF, 5GC, NG-RAN, UE of Figure 1 according to some example embodiments; and
  • Figure 5 shows a representation of another example of operations by UPF of Figure 1 according to some example embodiments.
  • a policy control function generates at least first and second policy and charging control rules (PCC rules) for an application service flow (traffic flow) between a data network (DN) and a user equipment (UE) via at least one UPF instance of the 5G core, and a radio access network (RAN).
  • the first PCC rule PCC-1 is for PDUs of the application service flow that belong to PDU sets; and the second PCC rule is for PDUs of the application service flow that do not belong to a PDU set.
  • the two PCC rules contain the same Service Flow Template.
  • the two PCC rules may be generated based on information received from an application function (AF) (via network exposure function NEF) about one or more quality of service (QoS) requirements (such as e.g. (PDU Set delay budget, PDU Set error rate etc.) for PDUs of the application service flow that belong to PDU sets, and about one or more QoS requirements (such as e.g. packet delay budget, packet error rate etc.) for PDUs of the application service flow that do not belong to a PDU Set.
  • the AF sends (or is configured to send), at 1000, a QoS request that includes information indicative of one or more quality of service (QoS) requirements (such as e.g.
  • the QoS requirements are determined by the PCF based on a local configuration of the PCF.
  • the PCF sends at 2000 the two PCC rules to the SMF instance associated with the application service flow.
  • the SMF receives the two PCC rules PCC-1 and PCC-2 and maps them to respective QoS flows: QoS flow 1 and QoS flow 2.
  • QoS flow is characterized by a QoS Profile, UPF instructions for the UPF instance involved in the application service flow, and QoS Rules.
  • SMF sends at 3100 the UPF instructions to UPF; sends at 4000 the QoS profiles for the QoS flows to a NG-RAN node; and sends at 5000 the QoS rules for the QoS flows to the UE via the NG-RAN node
  • the UPF instructions, QoS profile for the QoS flows, and the QoS rules for the QoS flows 3100, 4000 and 5000 may be sent by SMF in any order.
  • QoS flow 1 is used for PDUs classified (i.e., identified) by the UPF instance involved in the application service flow as belonging to PDU Sets; and the NG-RAN applies the PDU Set QoS Parameters (e.g., PSER, PSDB and PSIHI) specified in the QoS profile 1 to PDUs classified (i.e., identified) by UPF involved in the application service flow as belonging to PDU sets.
  • PDU Set QoS Parameters e.g., PSER, PSDB and PSIHI
  • QoS Flow 2 is used for PDUs classified (i.e., identified) by the UPF involved in the application service flow as not belonging to a PDU Set; and the NG-RAN node applies QoS Parameters specified in the QoS Profile 2 (PER and PDB) to PDUs classified (i.e., identified) by the UPF involved in the application service flow as not belonging to a PDU Set. Additional QoS parameters and characteristics may be different between the two QoS flows.
  • SMF sends the UPF instructions to the UPF instance for the application service flow over the N4 interface (OPERATION 300 of Figure 4).
  • the UPF instructions comprise a single PDR for the application service flow.
  • the packet detection rule (PDR) comprises a format as set out at 3GPP TS 23.501 V17.6.0 clause 5.8.2.11.3.
  • the single PDR for an application service flow includes an identifier of a Forwarding Action Rule (referred to as the “Forwarding Action Rule ID”), identifiers of Usage Reporting Rules (referred to as a “List of Usage Reporting Rule ID(s)”) and identifiers of QoS Enforcement Rules (referred to as “List of QoS Enforcement Rule ID(s)”) of the structure set out at 3GPP TS 23.501 clause 5.8.2.11.3.
  • the single PDR additionally includes (i) “Protocol Description” indicating the service protocol used in the application service flow e.g.
  • FAR Rule ID for PDU Set PDUs indicating an identifier of a forwarding action rule (referred to as forwarding action rule ID) that identifies a forwarding action;
  • forwarding action rule ID identifier(s) of URR(s) for PDU Set PDUs (referred to as “URR ID(s) for PDU Set PDUs”) that identify a measurement action;
  • QER Rule ID(s) identifiers of QER rules
  • the FAR (forwarding action rule), URR (usage reporting rule) and QER (QoS enforcement rule) of the PDU Set Processing attribute are PDU processing rules that are used (instead of the FAR, URR and QER identified elsewhere in the PDR) for processing PDUs that the UPF instance involved in the application service flow determines belong to a PDU Set.
  • One or more of the PDU processing rules for PDUs belonging to a PDU set may be different to one or more of the PDU processing rules for PDUs not belonging to a PDU set (indicated by the ’’FAR Rule ID for PDU Set PDUs”, “URR ID(s) for PDU Set PDUs” and “QER Rule ID(s) for PDU Set” parts of the “PDU Set Processing” attribute).
  • each PDR e.g., PDR-1 and PDR-2) comprises one or more PDU processing rules. Examples of such PDU processing rules are a FAR, a QER, and a URR.
  • the structure of a single PDR for an application service flow includes attributes and a description of each respective attribute, including an additional clustered attribute comprised of the PDU processing rules for PDUs not belonging to a PDU set.
  • the UPF instance for the application service flow receives this PDR from SMF.
  • the UPF instance for the application service flow determines whether this PDR is applicable to a downlink PDU (OPERATION 620 of Figure 5). If the UPF instance for the application service flow determines that the PDU does not meet all the conditions specified by the packet detection information included in the PDR, the UPF instance for the application service flow moves onto the next PDR in the PDR precedence order. In this example, there is only one PDR for this application service flow; and a determination that the PDR does not apply to a PDU indicates that the PDU does not belong to this application service flow (and may belong to a different application service flow).
  • the UPF instance for the application service flow determines if the PDU is classifiable (i.e., identifiable) as belonging to a PDU set (OPERATION 630 of Figure 5). Determining by the UPF instance for the application service flow whether a PDU belongs to a PDU set may be done, for example by detecting RTP/SRTP header or payload.
  • the UPF instance for the for the application service flow determines that the PDU is classifiable (i.e., identifiable) as not belonging to a PDU set comprising one or more PDUs
  • the UPF instance for the for the application service flow processes the PDU according to at least one processing rule included in the single PDR.
  • processing rules that may be included in the single PDR are the rules identified by the “Forwarding Action Rule ID”, “List of Usage Reporting Rule ID(s)” and “List of QoS Enforcement Rule ID(s)”,.
  • the UPF instance for the for the application service flow determines that the PDU is classifiable (i.e., identifiable) as belonging to a PDU set comprising one or more PDUs
  • the UPF instance for the application service flow processes the PDU according to at least one processing rule included in the single PDR.
  • processing rules that may be included in the single PDR are the rules identified by the "FAR Rule ID for PDU Set PDUs”, “URR ID(s) for PDU Set PDUs” and “QER Rule ID(s) for PDU Set”.
  • the PCF instead of generating two PCC rules for the application service flow, the PCF generates for the application service flow a single PCC rule that comprises information identifying (e.g., references via 5QI) both PDU Set QoS Parameters (e.g., PSER, PSDB) for PDUs belonging to a PDU set, and PDU QoS parameters (PDB, PER) for PDUs not belonging to any PDU set.
  • SMF maps the single PCC Rule to two QoS Flows for the same application service flow, and sends the single PDR rule to the UPF instance for the application service flow.
  • the PCF generates for the application service flow a single PCC rule that comprises a 5QI which references or is associated with information identifying both PDU Set QoS Parameters (e.g., PSER, PSDB) for PDUs belonging to a PDU set, and PDU QoS parameters (PDB, PER) for PDUs not belonging to any PDU set.
  • PDU Set QoS Parameters e.g., PSER, PSDB
  • PDU QoS parameters e.g., PER
  • Figure 6 shows operations performed by UPF according to further example embodiments.
  • the SMF sets up only one QoS flow when a (one) PCC rule is received from the PCF indicating that PDU Set processing is enabled.
  • the UPF instance for the application service flow receives from SMF a PDR that activates PDU Set processing.
  • the PDR contains, comprises, or includes packet detection information that allows the UPF instance for the application service flow to determine whether a PDU belongs to the application service flow for which the PDR is created.
  • the PDR may contain, comprise, or includes “Protocol Description” information that informs the UPF of the service protocol (e.g., RTP header or payload) used by the application of the application service data flow.
  • the PDR also identifies a rule (e.g., a parameter in a FAR, which is contained, comprised, or included in the PDR), according to which the UPF instance for the application service flow sends a PDU-set PDU (PDU classified (i.e., identified) by UPF as belonging to a PDU set) to NG-RAN with PDU Set Information in the GTP-U header of the packet by which UPF sends the PDU to NG-RAN node.
  • the PDU Set Information has the format described at 3GPP TS 23.501 clause 5.37. Determining by UPF whether a PDU belongs to a PDU set may, for example, be done by the UPF by inspecting the content and pattern of the application service flow.
  • the UPF instance for the application service flow may or may not utilize the “Protocol Description” or any other information provided by the SMF.
  • the PDU Set information sent to the NG-RAN node in the GTP-U header comprises the following: PDU Set Sequence Number; Indication of End PDU of the PDU Set; PDU Sequence Number within a PDU Set; PDU Set Size in bytes; PDU Set Importance, which identifies the importance of a PDU Set within a QoS Flow.
  • PDU Set Importance is the only one of these that differentiates PDU Sets according to the type of application/media layer attributes represented (e.g., a different importance value can be given to a PDU carrying an I-Frame versus a P-Frame).
  • the NG-RAN node may use the PDU Set Importance for PDU Set level packet discarding in presence of congestion.
  • UPF Based on the Packet Detection Information of the PDR, UPF determines that a PDR (received from SMF) is applicable to a downlink PDU (OPERATION 700). For example, the Packet Detection Information contains a packet filter set that is matched against the packet header of a received PDU.
  • UPF determines whether the PDU belongs to a PDU set (OPERATION 710). [0138] If the UPF determines that the PDU belongs to a PDU set (i.e. the PDU matches both the Packet Detection Information of the PDR and the UPF determines that the PDU belongs to a PDU Set based on the Protocol Description provided in the PDR and/or implementation specific means used by the UPF to classify (i.e., identify) a PDU as belonging to a PDU set), UPF sends the PDU to NG-RAN node in a GTP-U packet with GTP-U header including PDU set information (OPERATION 720). In some implementations, a classifier may be used to classify a PDU as belonging to a PDU set.
  • the UPF determines that the PDU matches the Packet Detection Information attribute of the PDR and does not belong to a PDU set (i.e. the PDU matches both the Packet Detection Information of the PDR and the UPF determines that the PDU belongs to a PDU Set based on the Protocol Description provided in the PDR and/or implementation specific means used by the UPF to classify a PDU as belonging to a PDU set)
  • the UPF sends the PDU (having unknown application-level attributes) to NG-RAN node in a GTP-U packet with a GTP-U header including default PDU set information determined by the UPF; and the NG_RAN node processes the PDU as a PDU-set PDU based on the PDU default set information (OPERATION 730).
  • PDU set information included in the GTP-U header may include the size of the PDU set; and in the case of the default set, the PDU set information indicates that the size of the PDU set (referred to herein as PDU set size) is one PDU.
  • PDUs of the default PDU Set are mapped to the same QoS flow as PDUs that are determined to belong to a PDU Set (i.e. PDUs that match both the Packet Detection Information of the PDR from SMF and for which the UPF determines that the PDU belongs to a PDU Set based on the Protocol Description provided in the PDR from SMF and/or implementation specific means used by the UPF to classify a PDU as belonging to a PDU set).
  • PDU Set QoS using PDU Set attributes (e.g., PSDB and PSER) to all the PDUs of the application service flow (including PDUs that UPF does not classify as belonging to a PDU set).
  • PDU Set attributes e.g., PSDB and PSER
  • Figure 7 illustrates an example of an apparatus 1200 comprising or implementing a network function of the 5GC as illustrated on Figure 1.
  • the apparatus 1200 may comprise at least one random access memory (RAM) 1211a, at least on read only memory (ROM) 1211b, at least one processor 1212, 1213 and an input/output interface 1214.
  • the at least one processor 1212, 1213 may be coupled to the RAM 1211a and the ROM 1211b.
  • the at least one processor 1212, 1213 may be configured to execute an appropriate instructions of software code 1215.
  • the software code 1215 may for example software code of a network function of the 5GC, for example, software code of the PCF, SMF, UPF described herein.
  • the software code 1215 of a network function comprises executable instructions, which when executed by the at least one processor 1212, 1213, causes the apparatus to perform one or more operations of the network function, for example, one or more of the operations of the PCF, SMF, or UPF described herein.
  • the software code 1215 may for example be software code of the application function described herein, and the software of the application function comprises executable instructions, which when executed by the at least one processor 1212, 1213, causes the apparatus to perform the one or more operations of the application function described herein.
  • the software code 1215 may be stored in the ROM 121 lb.
  • the apparatus 200 may be interconnected with another control apparatus 1200 controlling another function of the 5GC or an apparatus of the NG-RAN.
  • each network function of the 5GC is comprised or implemented in an apparatus 1200.
  • two or more network functions of the 5GC may be comprised or implemented in an apparatus 1200.
  • FIG. 8 illustrates an example of the UE illustrated in Figure 1.
  • the UE may receive signals over an air or radio interface 1307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals.
  • transceiver apparatus is designated schematically by block 1306.
  • the transceiver apparatus 1306 may be provided for example by means of a radio part and associated antenna arrangement.
  • the antenna arrangement may be arranged internally or externally to the mobile device.
  • the UE may be provided with at least one processor 1301, at least one memory ROM 1302a, at least one RAM 1302b and other possible components 1303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices.
  • the at least one processor 1301 is coupled to the RAM 1302b and the ROM 1302a.
  • the at least one processor 1301 may be configured to execute instructions of software code 1308.
  • the execution of the instructions of the software code 1308 may for example allow the UE to perform one or more operations, including operations of the UE described herein.
  • the software code 1308 may be stored in the ROM 1302a.
  • the processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 1304.
  • the device may optionally have a user interface such as key pad 1305, touch sensitive screen or pad, combinations thereof or the like.
  • a display, a speaker and a microphone may be provided depending on the type of the device.
  • Figure 9 shows a schematic representation of non-volatile memory media 1100a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 1100b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters 1102 which when executed by a processor allows the processor to perform one or more of the steps of the methods described previously.
  • non-volatile memory media 1100a e.g. computer disc (CD) or digital versatile disc (DVD)
  • 1100b e.g. universal serial bus (USB) memory stick
  • example embodiments may be implemented as circuitry, in software, hardware, application logic or a combination of software, hardware and application logic.
  • the application logic, software or an instruction set is maintained on any computer-readable media.
  • a "computer- readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as the base stations or user equipment of the above-described example embodiments.
  • circuitry refers to all of the following: (a) hardware- only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the user equipment or base stations of the above-described embodiments, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un procédé mis en œuvre par une fonction de commande de politique qui consiste à : générer, par une fonction de commande de politique d'un réseau de communication sans fil, au moins un premier paramètre de qualité de service pour un flux de service d'application sur la base d'au moins une première exigence de qualité de service pour des unités de données de protocole appartenant à un ensemble d'unités de données de protocole; générer au moins un second paramètre de qualité de service pour le flux de service d'application sur la base d'au moins une seconde exigence de qualité de service pour des unités de données de protocole n'appartenant pas à un ensemble d'unités de données de protocole; et envoyer des informations identifiant le ou les premiers paramètres de qualité de service et des informations identifiant le ou les seconds paramètres de qualité de service à une fonction de gestion de session du réseau de communication sans fil.
PCT/IB2024/053245 2023-04-06 2024-04-03 Procédé et appareil associés à des flux de service d'application comprenant des unités de données de protocole appartenant à des ensembles d'unités de données de protocole et des unités de données de protocole n'appartenant pas à des ensembles d'unités de données de protocole Ceased WO2024209366A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202480023705.7A CN121002940A (zh) 2023-04-06 2024-04-03 与包括属于协议数据单元集的协议数据单元和不属于协议数据单元集的协议数据单元的应用服务流相关的方法和装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363494699P 2023-04-06 2023-04-06
US63/494,699 2023-04-06

Publications (1)

Publication Number Publication Date
WO2024209366A1 true WO2024209366A1 (fr) 2024-10-10

Family

ID=90720012

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2024/053245 Ceased WO2024209366A1 (fr) 2023-04-06 2024-04-03 Procédé et appareil associés à des flux de service d'application comprenant des unités de données de protocole appartenant à des ensembles d'unités de données de protocole et des unités de données de protocole n'appartenant pas à des ensembles d'unités de données de protocole

Country Status (2)

Country Link
CN (1) CN121002940A (fr)
WO (1) WO2024209366A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026091886A1 (fr) * 2024-10-29 2026-05-07 华为技术有限公司 Procédé et appareil de communication

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200145876A1 (en) * 2018-11-02 2020-05-07 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200145876A1 (en) * 2018-11-02 2020-05-07 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SHABNAM SULTANA ET AL: "Introduction of support for PDU Set handling", vol. 3GPP SA 2, no. Online; 20230116 - 20230120, 9 January 2023 (2023-01-09), XP052231812, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/Docs/S2-2300336.zip S2-2300336 23.501_XRM_KI4-5v2.docx> [retrieved on 20230109] *
YOUNGKYO BAEK ET AL: "(KI #4&5) modification on QoS description for PDU set based mechanism", vol. 3GPP SA 2, no. Online; 20230116 - 20230120, 9 January 2023 (2023-01-09), XP052232226, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/Docs/S2-2300758.zip S2-2300758-KI4&5-501 CR-PDUSetbasedhandling-samsung.docx> [retrieved on 20230109] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026091886A1 (fr) * 2024-10-29 2026-05-07 华为技术有限公司 Procédé et appareil de communication

Also Published As

Publication number Publication date
CN121002940A (zh) 2025-11-21

Similar Documents

Publication Publication Date Title
CN104902518B (zh) 实现反射式eps承载的系统和方法
CN112913280B (zh) 配置服务质量
CN111770531B (zh) 获取数据包延迟参数的方法、系统和装置
US20240015569A1 (en) Quality of service management for 5g networks
US12457542B2 (en) Method and apparatus for verifying compliance with UE route selection policy
KR20150113151A (ko) 맞춤가능한 이동 광대역 네트워크 시스템 및 이동 광대역 네트워크를 맞춤화하는 방법
EP4228304B1 (fr) Mises en uvre de qualité de service pour séparer un plan utilisateur
US20250168281A1 (en) Method and apparatus for traffic processing using traffic classification in wireless communication system
JP7622341B2 (ja) 次世代セルラーネットワークにおけるサービス機能チェイニングのための拡張サービス分類
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
US20180167418A1 (en) Apparatus and method for lawful interception
US10225130B2 (en) Method and apparatus for classifing IP flows for efficient quality of service realization
WO2024098632A1 (fr) Systèmes et procédés de détermination de capacité réseau par l&#39;intermédiaire d&#39;un plan de contrôle
US11751055B2 (en) User plane integrity protection in cellular networks
WO2024113069A1 (fr) Systèmes et procédés de gestion de qualité de service pour un trafic de réalité étendue
CN121002940A (zh) 与包括属于协议数据单元集的协议数据单元和不属于协议数据单元集的协议数据单元的应用服务流相关的方法和装置
WO2024209042A1 (fr) Appareil, procédé et programme informatique
US20250056317A1 (en) Apparatus and method for forward error correction packet scheduling in wireless communication system
US20250106165A1 (en) Method and apparatus for processing multiplexed data in a wireless communication system
GB2637166A (en) Method, apparatus and computer program
EP4607884A1 (fr) Procédé et appareil de transmission d&#39;informations sur la base d&#39;un changement de caractéristique de trafic dans un système de communication sans fil
EP4697668A1 (fr) Procédé et appareil de gestion de session dans un système de communication sans fil
WO2024156140A1 (fr) Systèmes et procédés de détermination de capacité de réseau par l&#39;intermédiaire d&#39;un plan d&#39;utilisateur
US20260025876A1 (en) Method and apparatus for pdu set based traffic management in wireless communication system
GB2630968A (en) Method, apparatus and computer program

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24717802

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202547107541

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202547107541

Country of ref document: IN

122 Ep: pct application non-entry in european phase

Ref document number: 24717802

Country of ref document: EP

Kind code of ref document: A1