WO2026031096A1 - Changements dynamiques de caractéristiques de trafic dans un plan utilisateur - Google Patents

Changements dynamiques de caractéristiques de trafic dans un plan utilisateur

Info

Publication number
WO2026031096A1
WO2026031096A1 PCT/CN2024/110805 CN2024110805W WO2026031096A1 WO 2026031096 A1 WO2026031096 A1 WO 2026031096A1 CN 2024110805 W CN2024110805 W CN 2024110805W WO 2026031096 A1 WO2026031096 A1 WO 2026031096A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
data flow
flow
qos
traffic characteristic
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.)
Pending
Application number
PCT/CN2024/110805
Other languages
English (en)
Inventor
Hua Chao
Markus Sakari ISOMÄKI
Laurent Thiébaut
Georgios GKELLAS
Devaki Chandramouli
Yong Gang Wang
Matti Einari Laitila
Colin Kahn
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 Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
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 Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2024/110805 priority Critical patent/WO2026031096A1/fr
Priority to CN202511101088.0A priority patent/CN121547142A/zh
Publication of WO2026031096A1 publication Critical patent/WO2026031096A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
    • H04L1/203—Details of error rate determination, e.g. BER, FER or WER
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • Various example embodiments of this disclosure relate to a method, apparatus, system and computer program and in particular but not exclusively to a method, apparatus, system supports dynamic traffic characteristic changes in user plane.
  • a communication network can be seen as a facility that enables communications between two or more communication devices or provides communication devices access to a data network.
  • a mobile or wireless communication network is one example of a communication network.
  • a communication device may be provided with a service by an application server.
  • the information indicating the at least one change of the at least one traffic characteristic of the service data flow comprises at least one of the following:
  • the information indicating the at least one change of the at least one traffic characteristic of the service data flow is in a real time transport protocol (RTP) header or a RTP payload type header.
  • RTP real time transport protocol
  • the information indicating the at least one change of the at least one traffic characteristic of the service data flow is transmitted as per-packet metadata of the service data flow.
  • the at least one QoS profile comprises at least one target QoS profile to be adopted based on the at least one change of the at least one traffic characteristic of the service data flow.
  • the at least one QoS profile comprises a QoS profile which is adopted when the at least one change of the at least one traffic characteristic of the service data flow occurs.
  • an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:
  • the request comprises information indicating at least one profile of at least one traffic characteristic of the service data flow which are able to be adopted after a quality-of-service (QoS) flow associated with the service data flow is established;
  • QoS quality-of-service
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the at least one profile comprises an initial profile which indicates at least one initial value of the at least one traffic characteristic to be initially adopted after the QoS flow associated with the service data flow is established.
  • the request further comprises an indication of a time of adopting the initial profile.
  • the information indicating the at least one profile comprises at least one of the following:
  • a profile comprising one or more parameter identifiers for each traffic characteristic
  • the apparatus is further caused to:
  • applying the changes to the QoS flow associated with the service data flow based on the at least one change of the at least one traffic characteristic of the service data flow after the QoS flow associated with the service data flow is established comprises at least one of the following:
  • the apparatus is further caused to:
  • the network receives, from the network, a response associated with establishing the service data flow, wherein the response comprises information indicating at least one initial value of the at least one traffic characteristic of the service data flow which is to be initially adopted after the service data flow is established.
  • an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • detect the at least one change of the at least one traffic characteristic associated with one or more packets carried by the service data flow comprises:
  • the information indicating at least one of the at least one change of the at least one traffic characteristic of the service data flow comprises at least one of the following:
  • the information indicating at least one of the at least one change of the at least one traffic characteristic associated with the one or more packets carried by the service data flow is carried in a downlink general packet radio service tunnelling protocol user plane (GTP-U) packet of the QoS flow associated with the service data flow, a dummy GTP-U packet or an information element comprising a GTP-U header.
  • GTP-U downlink general packet radio service tunnelling protocol user plane
  • the apparatus is further caused to: receive, from the network node, a response indicating a status of receiving the information indicating the at least one change of the at least one traffic characteristic associated with the one or more packets carried by the service data flow.
  • the apparatus is caused to transmit, to the network node, information indicating the at least one change of the at least one traffic characteristic associated with the service data flow by:
  • PFCP Packet Forwarding Control Protocol
  • an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the information indicating the at least one change of the at least one traffic characteristic associated with the QoS flow associated with the service data flow comprises at least one of the following:
  • At least one parameter identifier for the at least one traffic characteristic or at least one value of the at least one traffic characteristic.
  • the apparatus is further caused to:
  • the apparatus is caused to apply the changes associated with the QoS flow based on the at least one change of the at least one traffic characteristic of the QoS flow by at least one of the following:
  • the apparatus is further caused to:
  • the request comprises information indicating at least one profile of the at least one traffic characteristic associated with the QoS flow associated with the service data flow which are able to be adopted after the QoS flow is established.
  • the at least one profile comprises an initial profile which indicates at least one initial value of the at least one traffic characteristic to be initially adopted after the QoS flow is established.
  • the request further comprises an indication of a time of adopting the initial profile.
  • the information indicating the at least one profile comprises at least one of the following:
  • a profile comprising one or more parameter identifiers for each traffic characteristic, or one or more values for each traffic characteristic.
  • the apparatus is further caused to:
  • the apparatus is further caused to:
  • an apparatus comprising:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the information indicating the at least one change of the at least one traffic characteristic of the service data flow comprises at least one of the following:
  • the information indicating the at least one change of the at least one traffic characteristic of the service data flow is in a real time transport protocol (RTP) header or a RTP payload type header.
  • RTP real time transport protocol
  • the information indicating the at least one change of the at least one traffic characteristic of the service data flow is transmitted as per-packet metadata of the service data flow.
  • the apparatus further comprises:
  • the at least one QoS profile comprises at least one target QoS profile to be adopted based on the at least one change of the at least one traffic characteristic of the service data flow.
  • the at least one QoS profile comprises a QoS profile which is adopted when the at least one change of the at least one traffic characteristic of the service data flow occurs.
  • the apparatus comprises an application client or an application server.
  • an apparatus comprising:
  • the request comprises information indicating at least one profile of at least one traffic characteristic of the service data flow which are able to be adopted after a quality-of-service (QoS) flow associated with the service data flow is established;
  • QoS quality-of-service
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the at least one profile comprises an initial profile which indicates at least one initial value of the at least one traffic characteristic to be initially adopted after the QoS flow associated with the service data flow is established.
  • the request further comprises an indication of a time of adopting the initial profile.
  • the information indicating the at least one profile comprises at least one of the following:
  • a profile comprising one or more parameter identifiers for each traffic characteristic
  • the apparatus further comprises:
  • applying the changes to the QoS flow associated with the service data flow based on the at least one change of the at least one traffic characteristic of the service data flow after the QoS flow associated with the service data flow is established comprises at least one of the following:
  • the apparatus further comprises:
  • an apparatus comprising:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • means for detecting the at least one change of the at least one traffic characteristic associated with one or more packets carried by the service data flow comprises:
  • the information indicating at least one of the at least one change of the at least one traffic characteristic of the service data flow comprises at least one of the following:
  • the apparatus further comprises:
  • means for transmitting, to the network node, information indicating the at least one change of the at least one traffic characteristic associated with the service data flow comprises:
  • an apparatus comprising:
  • QoS quality-of-service
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the information indicating the at least one change of the at least one traffic characteristic associated with the QoS flow associated with the service data flow comprises at least one of the following:
  • the information indicating the at least one change of the at least one traffic characteristic associated with the QoS flow associated with the service data flow is carried in a downlink general packet radio service tunnelling protocol user plane (GTP-U) packet of the QoS flow, a dummy GTP-U packet or an information element comprising a GTP-U header.
  • GTP-U downlink general packet radio service tunnelling protocol user plane
  • the apparatus further comprises:
  • means for apply the changes associated with the QoS flow based on the at least one change of the at least one traffic characteristic of the QoS flow comprises at least one of the following:
  • the apparatus further comprises:
  • the at least one profile comprises an initial profile which indicates at least one initial value of the at least one traffic characteristic to be initially adopted after the QoS flow is established.
  • the request further comprises an indication of a time of adopting the initial profile.
  • the information indicating the at least one profile comprises at least one of the following:
  • a profile comprising one or more parameter identifiers for each traffic characteristic
  • the apparatus further comprises:
  • the apparatus further comprises:
  • a method comprising:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the request comprises information indicating at least one profile of at least one traffic characteristic of the service data flow which are able to be adopted after a quality-of-service (QoS) flow associated with the service data flow is established;
  • QoS quality-of-service
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a computer readable medium comprising instructions which, when executed by a user equipment, cause the user equipment to perform at least the following:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a computer readable medium comprising instructions which, when executed by a user equipment, cause the user equipment to perform at least the following:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a computer readable medium comprising instructions which, when executed by a user equipment, cause the user equipment to perform at least the following:
  • the at least one traffic characteristic comprises at least one of the following:
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method according to any of the preceding aspects.
  • FIG. 2 shows an example of an apparatus for the communication system of FIG. 1 according to some embodiments of the present disclosure
  • FIG. 5 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • FIG. 9 shows a flowchart of a process according to an embodiment of the present disclosure.
  • FIG. 1 shows a schematic representation of a 5GS.
  • the 5GS may comprise a user equipment (UE) (or Terminal (node) ) , an access network, such as a (radio) access network ( (R) AN) or a next generation radio access network (NG-RAN) , a 5GC, and one or more application functions (AFs) .
  • UE user equipment
  • R Radio
  • AN radio access network
  • NG-RAN next generation radio access network
  • 5GC a 5GC
  • AFs application functions
  • One AF may be deployed in the 5GS as a trusted AF.
  • an AF may be deployed or hosted on one or more application servers of a data network (DN) .
  • DN data network
  • Such AF are an untrusted AF.
  • the 5GS connects the UE to the DN via the access network and the 5GC (e.g., a user plane function (UPF) of the 5GC) .
  • UPF user plane function
  • FIG. 2 illustrates an example of a network apparatus 20 for controlling/implementing one or more (network) functions or one or more network entities of the 5GS shown in FIG. 1 (e.g., the (R) AN illustrated in FIG. 1, a next-generation RAN (NG-RAN) , a base station (BS) , a gNB central unit (gNB-CU) , a gNB distributed unit (gNB-DU) , the NEF, the UDM, the AUSF, the AMF, the SMF, the UPF, ..., etc) . That is, in some embodiments, each (network) function or each network entity of 5GC is deployed or hosted on one network apparatus 20.
  • NG-RAN next-generation RAN
  • BS base station
  • gNB-CU gNB central unit
  • gNB-DU gNB distributed unit
  • each (network) function or each network entity of 5GC is deployed or hosted on one network apparatus 20.
  • the network apparatus 20 may comprise at least one processor 200 (such as a microprocessor or Application Specific Integrated Circuit (ASIC) ) , a storage unit 210 and a communication unit 220.
  • the storage unit 210 may be any data storage device that stores a program code 212, which is accessed and executed by the processor 200. Examples of the storage unit 210 include but are not limited to read-only memory (ROM) , flash memory, random-access memory (RAM) , hard-disk, and optical data storage device.
  • the processor 200, the storage unit 210 (e.g., ROM and the RAM) , the communication unit 220 and other circuitry (e.g., a modem) of the network apparatus 20 may be provided on a circuit board, in chipsets, or in a system on chip.
  • the interface unit 322 may be internally or externally arranged to the network apparatus 30 and may comprise one or more antenna elements.
  • the antenna arrangement may be a multi-input multi output (MIMO) antenna.
  • the communication unit 320 and/or the interface unit 322 may be implemented by an external device (electrically) coupled to the network apparatus 30.
  • Traffic of many applications such as extended reality (XR) media streams (e.g., video, audio, haptics streams) can be characterized by a set of parameters including traffic periodicity (how often the application sends a burst of packets (i.e., data burst) ) or the maximum burst size. There are also other characteristics such as burst duration, level of forward error correction protection, or burst or packet level delay that may be relevant. The knowledge of such characteristics may be used in the network, especially in the (5G/6G) RAN, to optimize the traffic treatment with regarding to power saving or scheduling. Some of these parameters are defined as assistance information that can be provided to the RAN for optimization purposes.
  • XR extended reality
  • QoS quality-of-service
  • RTP Header Extensions are introduced in 3GPP TS 26.522 V18.0.0, clause 4.4, in which one-byte or two-byte RTP Header Extensions are introduced.
  • the RTP Header Extension for PDU Set marking can be used by an application server (AS) or a sender UE that sends media to a receiver UE (e.g., an application client (AC) (configured/deployed in the UE) ) using the RTP.
  • AS application server
  • AC application client
  • the AF may request QoS from the 5GS by specifying QoS service requirements and optionally Alternative service requirements in a request transmitted to the NEF/PCF (see, e.g., 3GPP TS23.502 V18.6.0, clause 4.15.6.6) .
  • the Alternative service requirements comprise one or more sets of Requested Alternative QoS Parameter Sets (e.g., comprising one or more of Guaranteed Flow Bit Rate (GFBR) , Packet Delay Budget (PDB) , or Packet Error Rate (PER) ) or references to those set (s) of parameters in a prioritized order.
  • GFBR Guaranteed Flow Bit Rate
  • PDB Packet Delay Budget
  • PER Packet Error Rate
  • the PCF Based on the information provided by the AF or local configuration, the PCF formulates a Policy and Charging Control (PCC) rule containing QoS parameters which is then sent to the SMF. If the Alternative Service Requirements (QoS References or individual parameters) are also provided, the PCF includes the Alternative QoS parameter sets in the PCC rule (s) .
  • PCC Policy and Charging Control
  • the TSCAI parameters are not part of the QoS profile or alternative QoS profiles. There is only one set of TSCAI per AF session or QoS flow, no alternatives.
  • the AF can propose several periodicity values or a range of periodicity value that the application is willing to support, and the 5GS/RAN can choose the best one out of the proposed periodicity values or the proposed range from its perspective.
  • the 5GS/RAN selects one periodicity value, only the selected periodicity value will be associated with the QoS flow and be in use.
  • the non-selected values proposed by the AF are not “remembered” by the 5GS/RAN and cannot be referred to in later procedures.
  • the application can efficiently indicate to the RAN that its traffic characteristics have changed.
  • the indication may need to be implemented over the User Plane (UP) , since the indication via AF session update procedures and PDU session update procedures via the Control Plane (CP) may be too slow and/or unscalable.
  • UP User Plane
  • CP Control Plane
  • Such mechanism refers to required changes/capabilities at the AF, the 5GC and the RAN level, where the required changes at the 5GC level includes the required changes/capabilities at one or more of the NEF, the PCF, the SMF and the UPF.
  • one of relevant parameters in the traffic characteristics may be the traffic periodicity, which is expected to change relatively frequently (in a matter of seconds) . Under such conditions, using the exposure/CP based procedure to update the traffic periodicity may be unscalable for the RAN to be able to adapt itself in a meaningful way before the next change in the traffic periodicity.
  • Other relevant parameters similar to the traffic periodicity e.g., the parameter changes dynamically/rapidly
  • one or more this kind of the parameters may be included in an assistance information profile, to be flexible to embrace any future extensions beyond the parameters listed in the present disclosure.
  • the parameter included in the assistance information profile is called a set of assistance information parameters or a set of assistance information.
  • the assistance information profile comprises/indicates value (s) of the set of assistance information (parameter (s) ) .
  • bit rates may change from time to time. For example, as scene changes, the best bit rates for each resolution would also be adjusted or the bit rates is derived by the encoder to achieve the desired minimum quality level.
  • the application layer encoder may use changeable time durations to encode different contents (e.g., scenes or frames) . Therefore, jitter of the arrival times of different contents is also changed together with the change in the bit rate and may need to be considered to be included in the assistance information profile.
  • bitrate adaptation based on congestion control methods including the traditional packet loss-based ones, the more recent Low Latency Low Loss Scalable throughput (L4S) , or based on explicit signals from the network about available bit rate, applied QoS profile, level of congestion, ..., etc.
  • Such bitrate adaption mechanisms may support various bitrates or quality levels and seek to adapt to what is available in a dynamic manner. By doing so their traffic characteristics also get updated dynamically.
  • a framework and set of methods are proposed to allow the Application (e.g., the AS and/or the AC) to efficiently indicate to the network update (s) /change (s) in its traffic characteristics.
  • the framework is discussed at least in the following three parts:
  • the Application consists of AS and AC.
  • the AF and AS/AC are assumed to be able to coordinate between each other.
  • the AC is located/comprised/deployed in the UE.
  • the methods allow the traffic characteristics change initiated by the application (e.g., the AC in the UE or the AS behind the UPF) by using negotiation between the 5GS and the AF about the traffic characteristics among a set of traffic characteristics (in terms of assistance information profiles or parameter values) and when it shall apply. After the negotiation, actual traffic characteristics can be detected in the UPF and then indicated to and applied in the RAN. The detection of the updated traffic characteristics is based on various approaches including update from the Application (e.g., the AC in the UE or AS behind the UPF) .
  • the AF/AS/AC when/if the AF/AS/AC foresees potential usages of different codec profiles, i.e., a set of specific collections of encoding tools and algorithms, the AF/AS/AC provides, via the NEF to the 5GS, information allowing the 5GS to associate a profile ID with actual assistance information and optionally a set of protocol description (s) .
  • the profile ID may also be associated with a QoS/Alt-QoS profile.
  • the SMF provides the assistance information (parameter (s) or profile (s) ) to the RAN and the UPF.
  • the Application e.g., the AC in the UE or the AS behind the UPF
  • the SMF may sends a new assistance information profile ID to be applied or new parameter value (s) to an existing assistance information profile.
  • This new assistance information profile ID or the new parameter value (s) is provided by the UPF over the 5GS UP (e.g., over GTP-U) to the RAN and may also be used by the UPF for its processing of the DL PDU.
  • the RAN considers/determines the updated or latest applied assistance information (parameter (s) /profile) and optionally a set of protocol description (s) corresponding to the new assistance information profile ID or new parameter value (s) received from the UPF.
  • the assistance information profile ID may also be associated with a QoS/Alt-QoS profile.
  • one assistance information profile and optionally a set of protocol description (s) applies at a given time.
  • one assistance information may also be associated with a QoS/Alt-QoS profile.
  • the traffic characteristics (comprised in the assistance information (profile) ) or the assistance information (parameters) includes at least one of the following:
  • Periodicity which refers to a time period between (starts of) two data bursts
  • FIG. 4 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • the process shown in FIG. 4 comprises at least the following steps:
  • Step 401 The AF provides 5GS, via the NEF, one or more (alternative) assistance information profiles or assistance information parameter values (i.e., values of assistance information (parameters) ) along with service requirements of the application traffic.
  • one of the provided assistance information profiles or provided parameter values may be indicated as initial/default assistance information profile/parameter values to be applied (e.g., the first on the list of the provided (alternative) assistance information profiles or assistance information parameter values) or as the default assistance information profile/parameter values to be used when/if no “Assistance information” is available via the UP.
  • RAN selection of the initial assistance information profile/parameter values may be supported. That is the RAN selection of the initial assistance information profile/parameter values reporting to AF in steps 406 to 408 shown in FIG. 4 may be optional.
  • Steps 402 and 403 The (alternative) assistance information profiles or parameter values are conveyed to the RAN via the 5GC (e.g., the NEF, the PCF, the SMF and the AMF (not shown in the FIG. 4) ) .
  • the 5GC e.g., the NEF, the PCF, the SMF and the AMF (not shown in the FIG. 4)
  • Step 404 The SMF provides/transmits protocol descriptions for the application to the UPF.
  • the protocol descriptions may be based on the service requirements of the application traffic and the initial/default assistance information profile/parameter values.
  • Step 405 The RAN selects/determines one of the assistance information profiles or parameter values as the initial assistance information profile or parameter values.
  • the initial/default assistance information profile/parameter values are indicated in the information received from the 5GC/AF.
  • the RAN applies the initial assistance information profile or parameter values based on the indication.
  • the RAN selection of initial assistance information profile/parameter values is supported.
  • the RAN may neglect the indication received from the 5GC/AF, if any, determines/selects the assistance information profile/parameter values (e.g., based on the service requirements of the application traffic) and performs steps 406 to 408 to report the determined/selected assistance information profile/parameter values.
  • Steps 406 to 408 The RAN feedbacks the determined/selected initial assistance information profile or parameter values to the AF via the 5GC.
  • the RAN may be allowed to dictate, to the AF via the 5GC, a minimum time value for the change of the assistance information profiles or parameter values and/or associated QoS/Alt-QoS profiles.
  • the minimum time value refers to or indicates a minimum period required by the RAN to switch/change from (applying/using) a profile A to (applying/using) another profile B, wherein the profiles A and B can be assistance information profiles and/or (associated) QoS profiles.
  • the RAN switches/changes (to applying/using) or applies/uses one profile means that the RAN applies/adopts the parameter values (indicated) in the profile for the corresponding parameters/traffic characteristics.
  • one of the assistance information profiles or parameter values may be indicated as initial/default assistance information profile or parameter values to be used when no “Assistance information” is available via the UP.
  • the RAN selection of the initial assistance information may be supported. That is the RAN selection of the initial assistance information reporting to the AF in steps 406 to 408 may optional.
  • steps 406 and 408 are performed for reporting (only) the minimum time value for the change of the assistance information profiles or parameter values and/or the associated QoS/Alt-QoS profiles.
  • the RAN may report, to the AF via the 5GC, the minimum time value for the change of the assistance information profiles or parameter values and/or the associated QoS/Alt-QoS profiles.
  • Steps 409a and 409b The process shown in FIG. 4 works for both downlink (DL) and uplink (UL) traffic.
  • step 409a is performed.
  • step 409b is performed.
  • the UE e.g., AC configured/deployed in the UE
  • the UPF i.e., via UP
  • the AS transmits assistance information to the UPF (i.e., via UP) , to indicate change (s) in the assistance information of the DL traffic.
  • at least one of the steps 409a and 409b are performed.
  • Steps 410 and 411 The UPF detects changes in/of the assistance information or parameter values and updates assistance information profile (s) or parameter value (s) to the RAN.
  • Step 412 (Optional) : The RAN sends feedback to the UPF to indicate a successful reception of the (updated) assistance information profile or parameter value (s) .
  • Step 413 The RAN adapts to the updated assistance information profile or parameter values.
  • Step 414 The RAN decides to change the (alternative) QoS profiles or not based on the updated assistance information profile or parameter values.
  • the assistance information in Steps 409a, 409b and 410 may comprise a profile ID or actual values.
  • the RAN may require a minimum time value for a change of an updated assistance information profile or assistance information parameter value (s) and associated QoS/Alt-QoS profile or switching between QoS/Alt-QoS profiles.
  • the RAN is not expected to change the assistance information profile/parameter values and/or the associated QoS/Alt-QoS Profiles if the minimum time value is violated.
  • the RAN may also be allowed to dictate the minimum time value to the AF via the 5GC.
  • the NEF in step 408 can provide the AF with the minimum time value allowed between two QoS/Alt-QoS profile changes performed in step 413. This minimum time value may be provided as feedback from the RAN in steps 406 and 407 or be provided as policy configured on local policy of the PCF and/or NEF.
  • Option-1 refers to that there is a (pre-defined) mapping relationship between assistance information profiles/parameter values and QoS/Alt-QoS profiles.
  • Option-2 refers to that there is not a (pre-defined) mapping relationship between assistance information profiles and QoS/Alt-QoS profiles. That is the assistance information profiles/parameter values are independent from the QoS/Alt-QoS profiles.
  • METHOD A refers to a method of identifying/indicating values of the assistance information (parameter (s) ) by using/indicating an assistance information profile (ID) .
  • METHOD B refers to a method of identifying/indicating the identifying value (s) of the assistance information (parameter (s) ) by using/indicating ID (s) of assistance information (parameter (s) ) .
  • METHOD C refers to a method of identifying the identifying/indicating value (s) of the assistance information (parameter (s) ) by using/indicating actual value (s) of the assistance information (parameter (s) ) .
  • behaviors of the Application may comprise at least one of the following:
  • the AC in the UE or the AS behind the UPF may have a communication context with the UPF via a tunnel over which the AS passes its traffic towards the AC.
  • the AC may have a communication context with the UPF via a tunnel it uses to pass its traffic towards the AS.
  • the AS and/or AC may be aware whether and how the network (e.g., 5GS) supports the dynamic changes in/of assistance information profile or parameter values via an UP-based method either by AF based negotiation or by configuration.
  • the AS and/or the AC may also learn about how the network supports for the dynamic changes during tunnel establishment with the UPF. Both the UPF and the AS/AC indicate the methods they support and based on the indications the AS/AC learns which method (s) can be used and for which parameters the method is used.
  • the AS/AC may indicate at any time the change (s) in/of the assistance information profile (s) or parameter values with an identifier (ID) (METHOD A/B) or actual values of the assistance information parameters (METHOD C) via the UP by using one of the following methods to the UPF.
  • the indication can be done in a reliable way by a request sent by the AS which the UPF acknowledges.
  • the ID of the selected assistance information profile or (each) parameter value (METHOD A or B) is included in an RTP protocol header.
  • the RTP protocol headers may contain the actual value (s) of the assistance information parameter (s) (METHOD C) .
  • This header can be either:
  • An RTP “Traffic characteristics ID” header extension which supports multiple independent profile IDs (METHOD A) or parameter value IDs (METHOD B) .
  • such header or PT may be included in all RTP packets as long as the values are applicable or in a limited number of RTP packets after an update to reduce overhead.
  • the AC can only update the assistance information related to the UL traffic while the AS can only update the assistance information related to the DL traffic.
  • the ID of the applied assistance information profile (METHOD A) or assistance information parameter value (s) (METHOD B) , or actual value (s) of the assistance information (METHOD C) is provided to the UPF as new per-packet metadata using per-packet metadata carrying methods.
  • the metadata is either a single “Traffic characteristics profile/parameter value ID” or an actual value defined per parameter. Based on this method, both the AC and the AS can update both the UL and/or DL related information, depending on internal behaviour of the Application.
  • the (alternative) assistance information profiles or the (alternative) assistance information values for each parameter may be associated with a specific QoS/Alt-QoS profile (Option-1) or be independent from QoS/Alt-QoS profiles (Option-2) .
  • the Application includes the ID that points to the ID (s) of the QoS parameter (s) (in the QoS/Alt-QoS profile) and the corresponding assistance information. Note that, if the change (s) in the assistance information necessitates a change in QoS/Alt-QoS, the same or different IDs may simultaneously point to a corresponding QoS/Alt-QoS profile.
  • behaviors of the AF may comprise at least one of the following:
  • the AF provides (alternative) traffic characteristics (i.e., (alternative) assistance information profiles or (alternative) assistance information parameter values) to the network (e.g., 5GS) and negotiates with the network for initial values of the traffic characteristics.
  • the AF may indicate the network when to apply the initial values of the traffic characteristics.
  • Alternative traffic characteristics may be provided to the network in different methods discussed below:
  • the AF provides the network, along with the service requirements of the application traffic, one or more (alternative) assistance information profiles.
  • the one or more (alternative) assistance information profiles may be separate/independent from QoS/Alt-QoS profiles.
  • the purpose of providing the assistance information profiles is to assist the RAN in its processing, for example, scheduling or power saving.
  • the AF can provide and update the one or more (alternative) assistance information profiles at any time via the exposure methods.
  • the AF may indicate one of the assistance information profiles as the initial assistance information profile and optionally when the initial assistance information profile is expected to apply.
  • the AF may indicate a preference order for the assistance information profiles, or called as alternative assistance information profiles, and depends on the RAN to determine the initial assistance information profile or initial assistance information parameter values during the QoS flow establishment procedure.
  • Each (alternative) assistance information profile has an ID by which it can be referenced via subsequent CP or UP procedures.
  • the (alternative) assistance information profiles are provided to the network in a way of Option-1: separately for the main QoS profile and each alternative QoS profile is either inline within the QoS profile or via reference to their IDs; or in another way of Option-2: the assistance information profiles are provided independent from the QoS/Alt-QoS profiles.
  • the AF provides only a single assistance information profile containing/comprising at least one (e.g., two or more) alternative parameter value for individual assistance information parameter.
  • each parameter value has an ID which can be referenced with via subsequent CP or UP procedures.
  • the AF may indicate which one of the values is the initial value for each assistance information parameter.
  • the AF can indicate an order of preference for the alternative values and depends on the RAN to determine the initially applied value (s) of the assistance information parameter (s) during the QoS flow establishment procedure.
  • the AF may also receive a RAN indication for the selected initial assistance information profile or parameter value (s) if the RAN has the capability. Then the AF uses the received initial assistance information profile or parameter value (s) to instruct the AS for the traffic transmissions.
  • the AF may also indicate its capabilities to support assistance information profile or parameter value updates via the UP and learns about the capabilities of the network for the same. Based on this, the Application would have knowledge of which type of update methods it can use. These capabilities may indicate which assistance information parameters are updatable and by which of the methods.
  • the AF does not provide 5GS assistance information profiles or parameter value (s) with IDs as precondition for UP dynamic updates.
  • the AF transmits an indication of that the AF supports the dynamic updates via UP using explicit assistance information parameter value (s) and optional the initial assistance information parameter value (s) .
  • the network e.g., 5GS and/or RAN
  • the network supports the dynamic updates using the explicit assistance information parameter value (s)
  • the network indicates such support back to the AF.
  • the AF and the network may exchange a list of preferred values for each assistance information parameter.
  • behaviors of the UPF may comprise at least one of the following:
  • the UPF detects the change (s) in/of the assistance information profile or parameter value (s) by the above-mentioned methods and updates the changed assistance information profile or parameter value (s) to RAN.
  • the UPF may send an assistance information update indication to the RAN.
  • the assistance information update indication could be carried in any DL GTP-U (GPRS Tunneling Protocol for the UP) packet of the corresponding QoS flow or in a dummy GTP-U packet with a new GTP-U header or information element containing/comprising the existing GTP-U header.
  • the indication may include the “Assistance information profile ID” (METHOD A) , the parameter value ID (s) (METHOD B) of each supported assistance parameter (same as listed above for AS/AC to UPF) , or actual value (s) of the assistance information parameter (s) (METHOD C) .
  • an assistance information update response indication of the assistance information update indication being successfully received by the RAN (e.g., carried in a true GTP-U packet or a dummy GTP-U packet) can be specified, which the RAN sends in response to the assistance information update indication.
  • the UPF acknowledges that the RAN successfully received the assistance information update indication.
  • the UPF considers/determines that the transmission of the assistance information update indication fails, and the transmission Failure may be notified to the AF/AS.
  • the assistance information update indication may be alternatively transmitted from the UPF to the RAN via Control Plane using a new PFCP report parameter.
  • the PFCP report parameter comprising the assistance information update indication is transmitted from the UPF to the SMF, and the SMF updates PFCP report parameter to RAN using a PDU Session modification procedure.
  • the UPF may send its acknowledgement in response to an update request from the AC/AS only after the UPF has been acknowledged by the RAN.
  • behaviors of the RAN may comprise at least one of the following:
  • the RAN stores the updated (alternative) assistance information profile or (alternative) parameter value (s) received from the UPF and (optionally) selects, based on the updated assistance information profile or parameter value (s) , one of the (alternative) assistance information profiles or (alternative) parameter values as the assistance information profile or parameter values applied on the corresponding traffic.
  • the RAN may send an assistance information update response indication to the UPF, to indicate a successful reception of the indication from the core network (e.g., 5GC (UPF or SMF) ) as explained in the above behaviors of the UPF.
  • the core network e.g., 5GC (UPF or SMF)
  • the RAN selects the QoS/Alt-QoS profile based on admission control results.
  • the assistance information profile or parameter value (s) is selected among the ones associated with the selected QoS/Alt-QoS profile. If one of the assistance information profiles or parameter value (s) is indicated as initial assistance information profiles or parameter value (s) , the RAN applies that. If an indicator of when the initial profile or parameter value (s) is expected to apply, the RAN determine the RAN processing (e.g., resource allocation) based on the indicator. If there is an order of preference for the assistance information profiles or assistance information parameter value (s) , the RAN chooses one of them based on the order of preference and its own preference.
  • Option-2 In this option, it is assumed that there is no association relationship between the (alternative) assistance information profiles or parameter values and the QoS/Alt-QoS profiles.
  • the RAN applies the (alternative) assistance information profile or parameter value (s) indicated as the initial assistance information profile or assistance information parameter value (s) .
  • the RAN selects the (alternative) assistance information profile or assistance information parameter value (s) based on the provided order of preference and its own preferences.
  • the RAN sends the applied assistance information profile or parameter value to the SMF.
  • the RAN re-applies or re-selects the assistance information profile or parameter value (s) .
  • the re-selection of the assistance information profile or parameter value (s) has the following options:
  • the RAN determines whether the associated QoS/Alt-QoS profile can be applied or (re-) selected. If yes, the RAN notifies the network (e.g., CN) and the network notifies the AF about the (re-) selected QoS/Alt-QoS profile.
  • the network e.g., CN
  • the RAN may utilize the received/updated/changed assistance information profile/parameter value (s) to further perform the QoS enforcement. If the RAN decides, based on the received/updated/changed assistance information profile/parameter value (s) , to update the QoS/Alt-QoS profile, the RAN notifies the network (e.g., CN) and notifies the AF about the selected QoS/Alt-QoS profile.
  • the network e.g., CN
  • the AF may need to know such minimum time value.
  • the RAN is not expected to change/switch QoS/Alt-QoS Profiles if the minimum time value is violated or cannot be satisfied.
  • the RAN may be allowed to dictate the minimum time value to the AF via the network (e.g., CN or 5GC) .
  • behaviors of the network may comprise at least one of the following:
  • the minimum time value for a change of an updated assistance information profile or assistance parameter value (s) and associated QoS/Alt-QoS profile or switching between QoS/Alt-QoS profiles is reported to the AF either based on at least one of:
  • FIG. 5 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • QNC QoS notification control
  • the RAN e.g., NG-RAN
  • Alternative QoS Profile s
  • the process shown in FIG. 5 comprises the following steps:
  • Steps 500a to 500c The UE establishes at least one PDU session (step 500b) . In some embodiments, there is tunnel established between the AS and the UPF (step 500c) . In the embodiments of applying Option 1, step 500a is performed, a pre-defined mapping relationship between the assistance information profiles and QoS/Alt-QoS profiles is predefined/configured in the RAN.
  • Step 501 The AF transmits an AF request to the NEF and the PCF, to establish a service data flow of the established PDU session.
  • the AF request comprises service requirement (s) , alternative service requirement (s) and (alternative) assistance information profile (s) .
  • Step 501 is done via extension of the existing exposure mechanisms such as AFSessionWithQoS API defined in 3GPP TS 23.502 V18.6.0 clause 5.2.6.9.
  • Step 502 The PCF generates PCC rules including the assistance information profile (s) .
  • the assistance information profiles IDs and their associated assistance information parameter value (s) are added in the definition of PCC rules in 3GPP TS 23.503 V18.6.0 clause 6.3.1.
  • Step 503 The PCC rules are forwarded to the SMF (e.g., via Npcf_SMPolicyControl service defined in 3GPP TS 23.502 V18.6.0 clause 5.2.5.4) .
  • Step 504 The SMF updates the RAN with the assistance information profiles, which may imply/require changes of/in QoS PDU session related information for NGAP protocol defined in 3GPP TS 38.413 V18.2.0.
  • Step 505 The SMF updates the UPF with the Protocol Description in packet detection rule (PDR) , to facilitate the UPF to perform assistance information identification and marking, which may imply changes to/in definition of the PDR and QoS Enforcement Rule (QER) in 3GPP TS 29.244 V18.6.0 (e.g., to control the information that UPF may need to provide in GTP-u extensions) .
  • PDR packet detection rule
  • QER QoS Enforcement Rule
  • Step 506 The RAN performs the admission control for the new QoS flow. If/When the RAN receives from the SMF the freedom to select the initial assistance information profile. The RAN selects the initial assistance information profile and informs the SMF the selected initial assistance information profile in Step 507.
  • the RAN feedbacks the minimum time value required for changing the assistance information profile (or assistance information parameter value (s) and the associated QoS/Alt-QoS profile or switching between QoS/Alt-QoS profiles.
  • the change/switch possibly happens at any time during the QoS flow lifetime (e.g., in step 515) .
  • Steps 508 to 510 The selected initial assistance information profile or parameter value (s) is sent to the AF.
  • the minimum time value may also be provided to the AF from the RAN in steps 507 to 510.
  • the NEF provides AF with the minimum time value as policy configured on the PCF or local policy of the NEF.
  • Steps 507 to 510 may be omitted if/when the RAN is not allowed to select the initial assistance information profile.
  • steps 507 to 510 are performed for providing only the minimum time value required for changing the assistance information profile (or assistance information parameter value (s) ) and the associated QoS/Alt-QoS profile or switching between QoS/Alt-QoS profiles.
  • Steps 511 a and 511 b The AC in the UE and/or the AS behind the UPF may decide to update the assistance information (profile/parameter value (s) ) at any time after the QoS flow is established.
  • the assistance information profile/parameter value (s)
  • the updated assistance information (profile/parameter value (s) ) is updated with the application data.
  • the application data is received by the UPF from the AS or from the UE/AC.
  • the assistance information update from the UE/AC or the AS to the UPF may not be piggybacked within the UL or DL traffic data, but rather being provided over the tunnel in a specific flow-metadata-update or assistance-information update request and response.
  • the UPF may send a response immediately after it has received the request or only after receiving the corresponding response from the RAN.
  • the UPF may send a certain type of response at both of those stages.
  • the details of the service flow or assistance information metadata update may use HTTP requests and responses. For instance, if only the AS to UPF tunnel exists without the AC to UPF tunnel, the AS would update the information about both UL and DL directions.
  • Step 512 The UPF detects dynamic change (s) in the assistance information profile or parameter value (s) .
  • the detection may be based on RTP (header extension or payload header extension) traffic detection or based on XRM metadata information received in a tunnel over which the AS passes its traffic towards the AC via the UPF.
  • RTP head extension or payload header extension
  • a dedicate RTP header extension or existing RTP payload header maybe applied.
  • the PT value corresponds to the profile ID or parameter value ID.
  • the AF provides the mapping between the PT values and the profile/parameter IDs (e.g. 96->0, 97->1, and so on) to the 5GS in the AF/5GS procedure. The mapping is provided with the profile IDs to RAN or to the UPF which can also act as the mapper.
  • the UPF performs the GTP-U packet marking by using the detected updated assistance information (change (s) ) .
  • the UPF detects the change without involving the AS.
  • the UPF may use mechanisms defined in TS 23.501 V18.6.0, clause 5.37.8.2, to derive the N6 jitter and periodicity as the assistance information parameter “jitter” in the detected assistance information changes.
  • Step 513 The UPF may send an assistance information update indication to the RAN (e.g., carried in GTP-U packets sent in DL traffic, and these packets may carry actual data or correspond to dummy packets) .
  • the UPF uses the detected assistance information change (s) to mark the GTP-U header (s) to the RAN.
  • Step 514 The RAN, if possible, changes/updates the currently applied assistance information profile or parameter value (s) to the detected updated assistance information profile or parameter value (s) received from the UPF.
  • the RAN changes/updates the currently applied assistance information profile or parameter value (s) to the detected updated assistance information profile or parameter value (s) received from the UPF.
  • only one assistance information profile e.g., the maximum burst size and the periodicity
  • the traffic on a QoS flow/DRB at any given time.
  • Step 515 The RAN may need to determine whether to use/adopt new QoS/Alt-QoS profile if/when the assistance information (profile/parameter value (s) ) is updated in step 514. If Option-1 is applied, the RAN can use the applied/updated assistance information profile/parameter value (s) to determine an associated QoS/Alt-QoS profile based on the mapping relationship between applied/updated assistance information (profile/parameter value (s) ) and the QoS/Alt-QoS profiles. If Option-2 is applied, the RAN determines the newly adopted QoS/Alt-QoS profile based on the updated assistance information (profile/parameter value (s) ) . If the RAN decides to adopt/apply new QoS/alt-QoS profile, the RAN notifies the AF via the 5GC about the newly applied QoS/Alt-QoS profile in step 517.
  • Step 516 (optional) The RAN sends an assistance information update response indication (carried in a true or a dummy GTP-U packet) as response to the indication received by the UPF.
  • an assistance information update response indication carried in a true or a dummy GTP-U packet
  • the UPF knows that the RAN received the assistance information update indication successfully. Feedback received after the time expires will be considered as failure. Failure will be notified to the AF/AS via the CP or the UP (not shown in FIG. 5) .
  • Step 517 (Optional) : The RAN notifies the AF via 5GC about the new applied QoS/Alt-QoS profile.
  • the RAN tries to fulfil the QoS profile or any Alternative QoS Profile that has higher priority because the QNC is enabled for the GBR flow. If the RAN decides to update/change the fulfilled alternative QoS profile, RAN may determine whether an (alternative) assistance information (profile/parameter value (s) ) needs to be re-selected.
  • an (alternative) assistance information profile/parameter value (s)
  • the RAN may indicate the selected assistance information (profiles or parameter value (s) ) for the alternative QoS profile for the indicated QoS flow via the CP (e.g., together with the QNC notification) or the UP.
  • the RAN may still keep the assistance information (profile/parameter values) unchanged until receiving an explicit indication of changing the assistance information (profile/parameter values from the UPF.
  • FIG. 6 shows a flowchart of a process/method according to an embodiment of the present disclosure.
  • the process/method shown in FIG. 6 may be used in an Application (entity) , such as an AC (configured in the UE) , a UE or an AS, and comprises the following steps:
  • Step 601 Transmit, to a UPF, information indicating change (s) of traffic characteristic (s) associated with a service data flow.
  • the application transmits information indicating change (s) of traffic characteristic (s) associated with a service data flow to a UPF, to update the traffic characteristic (s) of the service data flow via the UP.
  • the network e.g., the RAN is able to timely update the corresponding parameters of the service data flow.
  • the traffic characteristic comprises at least one of the following: a periodicity which is a time period between starts of two data bursts of the service data flow; a maximum data burst size of the data bursts of the service data flow; a forward Error Correction ratio associated with successfully decoding each data burst of the service data flow; or a duration of transmitting the data bursts of the service data flow.
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a maximum data burst size of the data bursts of the service data flow a forward Error Correction ratio associated with successfully decoding each data burst of the service data flow
  • a duration of transmitting the data bursts of the service data flow refers to the aforementioned assistance information profile, one or more assistance information parameter (s) comprised in the assistance information profile, assistance information, or assistance information parameter (s) .
  • the information indicating the change (s) of the traffic characteristic (s) of the service data flow comprises at least one of the following: an ID of a profile (i.e. METHOD A) ; parameter ID (s) for the traffic characteristic (s) (i.e., METHOD B) ; or value (s) of the traffic characteristic (s) . That is the Application indicates the changes in/of the traffic characteristic (s) of the service data flow by indicating/updating the changed traffic characteristic value (s) . In some embodiments, the Application indicates the change (s) of the traffic characteristic (s) of the service data flow by indicating/updating the difference (s) between the changed traffic characteristic value (s) and the currently adopted traffic characteristic value (s) .
  • the Application transmits the information in an RTP header or a RTP payload type header.
  • the Application transmits the information as per-packet metadata of the service data flow.
  • the Application further transmits an indication of QoS profile (s) to the UPF, to indicate the QoS profile (s) associated with the change (s) of the traffic characteristic (s) of the service data flow.
  • the indicated QoS profile (s) may be QoS profile candidate (s) to be adopted (by the network) if/when the network updates the corresponding parameters of the service data flow based on the change (s) of the traffic characteristic (s) of the service data flow.
  • the QoS profile (s) comprises target QoS profile to be adopted based on the at least one change of the at least one traffic characteristic of the service data flow.
  • the QoS profile (s) comprises a QoS profile which is adopted when the at least one change of the at least one traffic characteristic of the service data flow occurs (i.e., when/if the traffic characteristic (s) of the service data flow is changed/updated to be the indicated change (s) of the traffic characteristic (s) of the service data flow.
  • FIG. 7 shows a flowchart of a process/method according to an embodiment of the present disclosure.
  • the process/method shown in FIG. 7 may be used in an AF (e.g., a network apparatus /device/entity/node comprising the AF or a network apparatus/device/entity/node performing at least part of the functionalities of the AF) and comprises the following step:
  • an AF e.g., a network apparatus /device/entity/node comprising the AF or a network apparatus/device/entity/node performing at least part of the functionalities of the AF
  • Step 701 Transmit, to a network, a request associated with establishing a service data flow.
  • the AF transmits to a network (node) (e.g., PCF/NEF) a request associated with establishing a service data flow.
  • the request comprises information indicating (assistance information) profile (s) of traffic characteristic (s) of the service data flow which are able to be adopted after a QoS flow associated with the service data flow is established, wherein the traffic characteristic (s) comprises at least one of the following: a periodicity which is a time period between starts of two data bursts of the service data flow; a jitter associated with the periodicity; a maximum data burst size of the data bursts of the service data flow; a forward Error Correction ratio associated with successfully decoding each data burst of the service data flow; or a duration of transmitting the data bursts of the service data flow.
  • a periodicity which is a time period between starts of two data bursts of the service data flow
  • a jitter associated with the periodicity
  • the AF indicates, in the request, an initial profile which indicates/comprises initial value (s) of the traffic characteristic (s) to be initially adopted after the QoS flow associated with the service data flow is established.
  • the AF indicates, in the request, an indication of a time of adopting the initial profile.
  • the information indicating the profile (s) comprises at least one of the following: ID (s) of the profile (s) ; a profile comprising parameter ID (s) for each traffic characteristic; or value (s) for each traffic characteristic.
  • the AF may receive, from the network, a minimum time of applying changes to the QoS flow associated with the service data flow based on change (s) of/in the traffic characteristic (s) of the service data flow after the QoS flow associated with the service data flow is established.
  • the changes applied to the QoS flow may comprise at least one of the following:
  • the AF may receive, from the network, a response associated with establishing the service data flow.
  • the response comprises information indicating initial value (s) of the traffic characteristic (s) of the service data flow which is to be initially adopted after the service flow is established.
  • FIG. 8 shows a flowchart of a process/method according to an embodiment of the present disclosure.
  • the process/method shown in FIG. 8 may be used in a UPF (e.g., a network apparatus /device/entity/node comprising the UPF or a network apparatus/device/entity/node performing at least part of the functionalities of the UPF) and comprises the following steps:
  • Step 801 Detect change (s) of traffic characteristic (s) associated with packet (s) carried by a service data flow.
  • Step 802 Transmit, to a network node, information indicating the change (s) of the traffic characteristic (s) associated with a QoS flow associated with the service data flow.
  • the UPF is configured to detect change (s) of traffic characteristic (s) associated with packet (s) carried by a service data flow and informs a network node (e.g., BS, RAN, NG-RAN) about the detected change (s) of the traffic characteristic (s) associated with packet (s) .
  • the traffic characteristic (s) comprises at least one of the followings:
  • the traffic characteristic (s) refers to the aforementioned assistance information profile, one or more assistance information parameter (s) comprised in the assistance information profile, assistance information, or assistance information parameter (s) .
  • the network node Based on the transmission of the indication of the detected change (s) in/of the traffic characteristic (s) , the network node is able to timely apply changes on transmission parameters of the QoS flow associated with the service data flow.
  • the communication quality and/or resource efficiency can be increased, therefore.
  • the UPF detects the change (s) of the traffic characteristic (s) associated with the packet (s) carried by the service data flow via/if/when receiving, from an Application entity (e.g., AC configured in UE, UE or AS) , information indicating at least one of the change (s) of the traffic characteristic (s) associated with the one or more packets of the service data flow.
  • an Application entity e.g., AC configured in UE, UE or AS
  • the Application entity may transmit the information indicating the change (s) of at least one of the following: the periodicity of transmitting data burst of the service data flow; a maximum data burst size of the data bursts of the service data flow; a forward Error Correction ratio associated with successfully decoding each data burst of the service data flow; or a duration of transmitting the data bursts of the service data flow.
  • the information indicating the change (s) is configured/carried in a DL GTP-U packet of the QoS flow associated with the service data flow, a dummy GTP-U packet or an information element comprising a GTP-U header.
  • the UPF receives a response from the network node.
  • the response may indicate successful reception of the information indicating the change (s) of the traffic characteristic (s) associated with the packets (s) carried by the service data flow.
  • the UPF transmits the information indicating the change (s) of the traffic characteristic (s) associated with the packets (s) carried by the service data flow in a PFCP report.
  • FIG. 9 shows a flowchart of a process/method according to an embodiment of the present disclosure.
  • the process/method shown in FIG. 9 may be used in a network node (e.g., BS, RAN, NG-RAN) and comprises the following steps:
  • Step 901 Receive, from a network, information indicating change (s) of traffic characteristic (s) associated with a QoS flow associated with a service data flow.
  • Step 902 Apply changes associated with the QoS flow based on the change (s) of the at least one traffic characteristic (s) of the QoS flow.
  • the network node receives information indicating change (s) of traffic characteristic (s) associated with a QoS flow associated with a service data flow from a network (e.g., UPF, SMF, core network, 5GC) .
  • a network e.g., UPF, SMF, core network, 5GC
  • the service data flow is mapped to the QoS flow by the network.
  • the network node may only recognize QoS flow.
  • the network node may consider that information indicates the change (s) of the traffic characteristic (s) associated with/of the QoS flow. Based on the indicated changes of the traffic characteristic (s) , the network node applies changes associated with the QoS flow.
  • the traffic characteristic (s) comprises at least one of the following: a periodicity which is a time period between starts of two data bursts of the service data flow; a jitter associated with the periodicity; a maximum data burst size of the data bursts of the service data flow; a forward Error Correction ratio associated with successfully decoding each data burst of the service data flow; or a duration of transmitting the data bursts of the service data flow.
  • the information indicating the change (s) of the traffic characteristic (s) associated with the QoS flow associated with the service data flow is carried in a DL GTP-U packet of the QoS flow, a dummy GTP-U packet or an IE comprising a GTP-U header.
  • the network node transmits, to the network, a response indicating a status of receiving the information indicating the at least one change of the at least one traffic characteristic of associated with the QoS flow associated with the service data flow. For example, the network node may transmit the response indicating a successful reception of the information to the network if/when successfully receiving the information.
  • the applied changes associated with the QoS flow may comprise at least one of the following:
  • the changes are applied after the QoS flow is established.
  • the network node applies an initial/default setting when the QoS flow is established.
  • the network node Based on the received changes of the traffic characteristics associated with the QoS flow (associated with the service data flow) , the network node performs the changes on the QoS flow to accordingly change the initial/default setting.
  • the network node receives, from the network (e.g., core network, 5GC, SMF) , a request of establishing the QoS flow.
  • the request comprises information indicating profile (s) of/for the at least one traffic characteristic associated with the QoS flow (associated with the service data flow) which are able to be adopted after the QoS flow is established.
  • the request comprises (indication of) an initial profile which indicates initial value (s) of the traffic characteristic (s) to be initially adopted after the QoS flow is established.
  • the request may further comprise an indication of a time of adopting the initial profile.
  • the information indicating profile (s) of/for the at least one traffic characteristic associated with the QoS flow comprises at least one of the following:
  • the network node transmits, to the network, (information/indication of) a minimum time value of applying the changes associated with the QoS flow based on the change (s) of the traffic characteristic (s) associated with the QoS flow (associated with the service data flow) after the QoS flow is established.
  • the network node may be allowed/able to determine/decide/select the initial value (s) of the traffic characteristic (s) associated with the QoS flow (associated with the service data flow) based on its preference.
  • the network node transmits, to the network, a response associated with establishing the QoS flow, wherein the response comprises information indicating the determined/decided/selected initial value (s) of the traffic characteristic (s) associated with the QoS flow which is to be initially adopted after the QoS flow is established.
  • references in the above to various network functions may be implemented by apparatus (e.g., network apparatus 20) that performs at least some of the functionality associated with those network functions.
  • apparatus e.g., network apparatus 20
  • an apparatus configured to implement a network function may further be configured to implement a virtual network function instance of that network function.
  • the apparatus may be or comprise a network function, such as an AF, NEF, UDM/UDR, AMF, ..., etc.
  • a network function such as an AF, NEF, UDM/UDR, AMF, ..., etc.
  • an apparatus being/comprising a network function refers to an apparatus/device configured to provide/perform at least part of functionalities of that network function.
  • apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and/or reception.
  • apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • the expression “and/or” includes any and all combinations of the listed terms, including at least any one of the elements, at least any two or more of the elements, or at least all of the elements.
  • the term “or” refers to a non-exclusive “or” unless otherwise indicated (e.g., use of “or else” or “or in the alternative” ) .
  • performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
  • performing a step or functionality “based on A” does not indicate that the step or functionality is performed solely based on “A” as one or more additional conditions may be included.
  • the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting and illustrative examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware.
  • Computer software or program also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks.
  • a computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments.
  • the one or more computer-executable components may be at least one software code or portions of it.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software (code) stored on a (non-transitory) computer-readable medium.
  • non-transitory is a limitation of the medium itself (e.g., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
  • the memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, DSPs, ASIC, FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
  • unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according embodiments of the present disclosure.

Landscapes

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

Abstract

Cette invention concerne un appareil. L'appareil comprend au moins un processeur et au moins une mémoire stockant des instructions qui, lorsqu'elles sont exécutées par le ou les processeurs, amènent l'appareil au moins à : transmettre, à une fonction de plan utilisateur, des informations indiquant au moins un changement d'au moins une caractéristique de trafic associée à un flux de données de service ; la ou les caractéristiques de trafic comprenant au moins l'un des éléments suivants : une périodicité qui est une période entre le début de deux salves de données du flux de données de service ; une taille de salve de données maximale des salves de données du flux de données de service ; un rapport de correction d'erreur sans voie de retour associé à un décodage réussi de chaque salve de données du flux de données de service ; ou une durée de transmission des salves de données du flux de données de service.
PCT/CN2024/110805 2024-08-08 2024-08-08 Changements dynamiques de caractéristiques de trafic dans un plan utilisateur Pending WO2026031096A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2024/110805 WO2026031096A1 (fr) 2024-08-08 2024-08-08 Changements dynamiques de caractéristiques de trafic dans un plan utilisateur
CN202511101088.0A CN121547142A (zh) 2024-08-08 2025-08-07 用户平面中的动态业务特性变化

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/110805 WO2026031096A1 (fr) 2024-08-08 2024-08-08 Changements dynamiques de caractéristiques de trafic dans un plan utilisateur

Publications (1)

Publication Number Publication Date
WO2026031096A1 true WO2026031096A1 (fr) 2026-02-12

Family

ID=98734526

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/110805 Pending WO2026031096A1 (fr) 2024-08-08 2024-08-08 Changements dynamiques de caractéristiques de trafic dans un plan utilisateur

Country Status (2)

Country Link
CN (1) CN121547142A (fr)
WO (1) WO2026031096A1 (fr)

Also Published As

Publication number Publication date
CN121547142A (zh) 2026-02-17

Similar Documents

Publication Publication Date Title
US11968565B2 (en) User plane information reporting method and apparatus
CN102714824B (zh) 针对分组传送模式下的无线设备的优化资源分配
JP7192896B2 (ja) 通信システム
US11751096B2 (en) Congestion control method and device, and base station
EP3864879B1 (fr) Commande de notification dans un système de communication
CN113923269A (zh) 用于执行数据完整性保护的方法和计算设备
EP3162114A1 (fr) Adaptation de débit direct pour un chemin de communication de bout en bout par un noeud de réseau cellulaire
US9942795B2 (en) Adapting QoS for a radio bearer
CN107634822B (zh) 一种基于harq的传输方法和装置
US11533266B2 (en) Rate adjustment techniques
TW202344089A (zh) 網路擁塞減緩
JP2020511032A (ja) コーデックレートアダプテーションのためのビットレート要求の無線状態トリガ
JP2020188472A (ja) Ｒａｎ補助のレートアダプテーションのためのフィードバック
CN112262593A (zh) 调整传输速率的技术
CN119422406A (zh) 用于通过用户面传送服务质量信息的方法和设备
CN102714823B (zh) 针对分组传送模式下的无线设备的优化资源分配
US8005477B2 (en) Method for improving quality of service management in a mobile packet radio communication cellular system
JP2024506094A (ja) ハンドオーバ手順に基づくメッセージ送信方法、装置、機器及びプログラム
CN107079515B (zh) 提高通信效率
CN108632933B (zh) 数据传输方法、装置及用户设备
WO2026031096A1 (fr) Changements dynamiques de caractéristiques de trafic dans un plan utilisateur
WO2024209042A1 (fr) Appareil, procédé et programme informatique
WO2017177356A1 (fr) Procédé de transmission de données, station de base et équipement utilisateur
WO2023045839A1 (fr) Procédé, appareil et dispositif de communication et dispositif de réseau central
WO2025028194A1 (fr) Nœud de réseau d'accès radio, nœud de réseau central et procédés associés

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: 24950146

Country of ref document: EP

Kind code of ref document: A1