[go: up one dir, main page]

WO2022118127A1 - Procédés, appareils, et produits programmes d'ordinateur pour fournir une surveillance de qualité de service sur des interfaces de communication - Google Patents

Procédés, appareils, et produits programmes d'ordinateur pour fournir une surveillance de qualité de service sur des interfaces de communication Download PDF

Info

Publication number
WO2022118127A1
WO2022118127A1 PCT/IB2021/060618 IB2021060618W WO2022118127A1 WO 2022118127 A1 WO2022118127 A1 WO 2022118127A1 IB 2021060618 W IB2021060618 W IB 2021060618W WO 2022118127 A1 WO2022118127 A1 WO 2022118127A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
service flow
timestamp
quality
downlink
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/IB2021/060618
Other languages
English (en)
Inventor
Péter SZILÁGYI
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
Publication of WO2022118127A1 publication Critical patent/WO2022118127A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H04L43/0835—One way packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/0858—One way delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/147—Network analysis or design for predicting network behaviour
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/149—Network analysis or design for prediction of maintenance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/026—Capturing of monitoring data using flow identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H04L43/0841—Round trip packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/0864—Round trip delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • An example embodiment relates generally to monitoring one or more quality of service metrics across one or more communication interfaces.
  • the 3rd Generation Partnership Project (3GPP) is a standards organization which develops protocols for mobile telephony and is known for the development and maintenance of various standards including second generation (2G), third generation (3G), fourth generation (4G), Long Term Evolution (LTE), and fifth generation (5G) standards.
  • the 5G network has been designed as a Service Based Architecture (SB A) or, in other words, a system architecture in which the system functionality is achieved by a set of network functions providing services to other authorized network functions to access their services.
  • SB A Service Based Architecture
  • the 5G network system allows for the support of Quality of Service (QoS) flow per User Equipment (UE) monitoring that enables the User Plane Function (UPF) and the Next-Generation Radio Access Network (NG-RAN) to cooperatively measure one way packet delays on their shared communication interface.
  • QoS Quality of Service
  • UE User Equipment
  • UPF User Plane Function
  • NG-RAN Next-Generation Radio Access Network
  • GTP Generic Packet Radio Service Tunneling Protocol
  • PDU Protocol Data Unit
  • PDU Protocol Data Unit
  • Methods, apparatuses, and computer program products are disclosed which facilitate the communication of improved QoS monitoring between a plurality of network entities via one or more network interfaces.
  • the present disclosure provides systems to extend the monitoring standards and improve Quality of Experience (QoE) monitoring and reporting capabilities of the plurality of network entities.
  • QoE Quality of Experience
  • the present disclosure provides for the detection of one way communication traffic flow between network entities and for the execution of bi-directional communication traffic flow procedures under such one way conditions.
  • the present disclosure further provides systems for data packet header extensions that facilitate monitoring lost data packets and delay time determination.
  • An example embodiment of the present disclosure utilizes a plurality of network entities to perform one way packet delay monitoring (e.g., uplink only traffic flow detection, etc.) across a network interface.
  • the UPF initiates/causes transmission of a Down Link (DL) data packet (e.g., a dummy downlink data packet or the like) configured for monitoring a QoS Flow (i.e., a monitoring data packet) to a base station (e.g., NG-RAN or the like).
  • DL Down Link
  • QoS Flow i.e., a monitoring data packet
  • the monitoring data packet is configured as at least a part of the PDU Type 0 GTP User Plane (GTP- U) header configured with the local time T1 of the UPF reflecting the time at which the monitoring data packet was sent out.
  • the NG-RAN may record the time T1 from the GTP-U header and generate the local time T2 information reflecting the time at which the monitoring data packet was received by the NG-RAN.
  • the T2 time information may be recorded in the GTP-U header by the NG-RAN or the like.
  • the plurality of network entities are one or more of a time synchronized UPF, a time synchronized NG-RAN, or the like.
  • the network interface is an N3 interface, such as between a RAN (e.g., NG-RAN, etc.) and one or more UPFs.
  • the NG-RAN may be configured to cause transmission of an Up Link (UL) data packet for a QoS Flow.
  • UL data packet and the DL data packet may be associated with the same QoS Flow.
  • the UL data packet may be configured as at least part of a PDU Type 1 GTP-U header configured to reflect the T1 and/or T2 times.
  • the NG-RAN may generate the local time T3 information that reflects the time at which the NG-RAN causes transmission of the UL data packet to the UPF.
  • the T3 time information may be recorded in the GTP-U header by the NG-RAN or the like.
  • the UPF may be configured to generate the local time T4 information that reflects the time at which the UPF received the UL data packet from the NG-RAN.
  • the T4 time information may be recorded in the GTP-U header by the UPF or the like.
  • the UPF may be configured to determine, based on one or more indicated times (e.g., recorded Tl, T2, T3, T4 information or the like) one or more one way data packet delays on the N3 interface.
  • the local time information Tl, T2, T3, and T4 are each associated with a respective timestamp Tl, T2, T3, and T4 and each respective timestamp reflects its associated local time information.
  • Timestamps for local time information may be associated with an indication of an associated type of data packet event (e.g., receipt of the UL data packet by the UPF, etc.).
  • the NG-RAN, or the like may generate a dummy monitoring data packet in the UL (e.g., a dummy UL data packet) to advance one or more operations (e.g., generate and record time information, etc.) upon receipt of a DL packet from the UPF.
  • QoS Flow Identifiers QoS Flow Identifiers (QFIs) may be associated with one or more monitoring data packets to identify and determine one or more duplicate data packets.
  • a duplicate data packet may be deleted or eliminated based on an associated QFI for a given QoS Flow that was configured to use redundant transport bearers.
  • the NG-RAN may be configured to monitor (e.g., count, identify, etc.) DL data packet losses to the UPF.
  • the NG-RAN may report DL data packet losses via a GTP-U header associated with a monitoring data packet based on one or more QFI or sequence numbers associated with the one or more QFI.
  • the reported DL data packet losses may be associated with the N3 interface.
  • An example embodiment of the present disclosure are configured to overcome and improve upon deficiencies identified by the inventor(s) in association with conventional systems. It should be appreciated, in light of the present disclosure, that conventional QoS Flow monitoring systems cannot initiate and/or record time information if there is no DL data packet associated with a QoS Flow for a respective time period. For example, conventional QoS Flow monitoring systems cannot initiate and/or record time information for UL only traffic, such as when up-streaming video from an Internet of Things (loT) associated camera. Moreover, conventional QoS Flow monitoring systems do not enable a UPF, or the like, to generate a dummy monitoring data packet in a DL to initiate a monitoring procedure (e.g., generation and recordation of time information, etc.).
  • a UPF or the like
  • the NG-RAN may provide an UL data packet to the UPF when up- streaming video
  • conventional systems do not provide for a return path for a dummy DL packet from the UPF to further the QoS Flow monitoring via at least the time information. Therefore, it should be appreciated in light of the present disclosure, that because of a lack of at least the use of dummy packets for the UPF in the DL for conventional QoS monitoring systems, it is not possible for conventional systems to perform UL only QoS Flow monitoring nor is it possible for conventional systems to monitor those time periods during which bi-directional traffic temporarily turns into UL only traffic.
  • the present disclosure provides an example embodiment that may be configured to facilitate QoS Flow monitoring via at least the UPF of the user plane traffic flow (e.g., via the N3 interface or the like) for UL only traffic flow and/or bi-directional traffic flow.
  • the UPF may be configured to generate one or more dummy monitoring data packets for monitoring QoS Flow in the DL to facilitate one or more QoS monitoring processes (e.g., generation and/or recordation of time information, etc.).
  • the UL only traffic flow may occur over at least a portion of a time period associated with the total traffic flow.
  • a QoS Flow may be UL only traffic flow during its entire lifetime (e.g., the total traffic flow), for example if there are only uplink packets transmitted in the QoS Flow.
  • a QoS Flow may also switch between bidirectional traffic flow and UL only traffic flow over particular time periods (e.g., time intervals during the total traffic flow lifetime).
  • the QoS Flow may comprise only UL data packet transmissions (e.g., the traffic characteristic defined by the end devices, of the network entities, may change from bi-directional traffic to UL only traffic and then back to bidirectional traffic).
  • the present disclosure provides for network entities, such as a NG-RAN and/or UPF, configured to monitor (e.g., detect, determine, report, etc.) that the QoS Flow is UL only traffic flow for one or more particular time periods (e.g., seconds, minutes, hours, etc.). If the duration of a UL only time period exceeds a predefined QoS monitoring time period (e.g., a time period between consecutive QoS monitoring events, etc.) then the UPF, or the like, should generate and cause transmission of one or more dummy monitoring data packets via the DL as a substitute for one or more other DL data packets (e.g., a DL data packet providing information other than an event trigger or time information).
  • a predefined QoS monitoring time period e.g., a time period between consecutive QoS monitoring events, etc.
  • the QoS Flow may be detected to be UL only traffic flow based on one or more of a time period, a number of data packets received or transmitted via a network entity, or the like.
  • a dummy monitoring data packet may be generated by one or more network entities (e.g., NG-RAN, UPF, etc.).
  • a dummy monitoring data packet may be generated in response to a detected/determined time period (e.g., a predefined time period, a UL only time period, the like, or combinations thereof).
  • the detection of the UL only traffic in the QoS Flow and the generation of the dummy monitoring data packet in the DL is performed by the UPF.
  • a dummy monitoring data packet may be configured to cause a response (e.g., generation and/or recordation of time information, etc.) at a network entity (e.g., NG-RAN, UPF, etc.) upon receipt of the dummy monitoring data packet by a network entity (e.g., NG-RAN, UPF, etc.).
  • a network entity e.g., NG-RAN, UPF, etc.
  • one or more dummy monitoring data packets may be generated at the same time, or time period, as when a UPF would initiate one or more QoS Flow monitoring processes (e.g., as described below with respect to FIGs. 5-7 or as described elsewhere herein).
  • a plurality of dummy monitoring data packets may be generated at the same time, or over the same time period, by one or more network entities.
  • one or more dummy monitoring data packets may be generated in response to receipt of a data packet by a network entity.
  • a UPF may generate a dummy monitoring data packet upon receipt of a suitable DL data packet from an NG-RAN at the same time the UPF would otherwise transmit a live/real data packet to the NG-RAN under other circumstances that require the UPF to respond with a live/real data packet.
  • an NG-RAN may use one or more dummy monitoring data packets for advancing one or more QoS Flow monitoring processes.
  • the NG-RAN and/or the UPF may discard the one or more dummy monitoring data packets from the user plane. For example, the RAN may discard, delete or remove a dummy monitoring data packet upon receipt of the dummy monitoring data packet and/or upon a determination that one or more QoS Flow monitoring operations have been initiated and/or completed.
  • An example embodiment of the present disclosure provide for an NG-RAN configured to utilize one or more DL QFI sequence numbers (e.g., a DL QFI sequence number put into the GTP header by the UPF associated with a PDU Type 0 packet or the like) for DL QoS Flow level packet loss detection. Gaps in a plurality of DL QFI sequence numbers may be detected and may define events of loss (e.g., loss of one or more data packets transmitted between the NG-RAN and the UPF via the N3 interface).
  • the NG-RAN may be configured to detect the gaps in the plurality of DL QFI sequence numbers and the NG-RAN may be configured to record each detected gap.
  • the NG-RAN may be configured to generate a PDU Type 1 packet for conveying its measurements of one or more QoS metrics to the UPF via UL.
  • the PDU Type 1 packet for conveying measurements of one or more QoS metrics may include without limitation DL data packet loss information determined based on at least detected gaps in the plurality of DL QFI sequence numbers.
  • a standardized field of the PDU Type 1 packet is associated with an indication of the packet loss information.
  • the initial sequence number of the plurality of DL QFI sequence numbers is determined by the UPF and indicated by the UPF to the NG-RAN via a first DL data packet of each QoS Flow.
  • the NG-RAN may be configured to record (e.g., at the NG-RAN) the initial sequence number of the first DL data packet of each QoS Flow.
  • the subsequent sequence numbers (e.g., a plurality of sequence numbers associated with, and received after, the initial sequence number of the first DL data packet) may be used for loss detection.
  • each of the data packets provide an indication of at least a DL QFI sequence number.
  • An example embodiment of the present disclosure provides for a UPF configured to utilize one or more UL QFI sequence numbers for UL QoS Flow level packet loss detection. Gaps in a plurality of UL QFI sequence numbers may be detected (e.g., by the UPF or the like) and may define events of loss (e.g., loss of one or more data packets transmitted between the NG-RAN and the UPF via the N3 interface).
  • the UPF may be configured to detect the gaps in the plurality of UL QFI sequence numbers and the UPF may be configured to record each detected gap.
  • the UPF may be configured to generate a PDU Type 1 packet for conveying its measurements of one or more QoS metrics to the NG-RAN.
  • the PDU Type 1 packet for conveying measurements of one or more QoS metrics may include without limitation UL data packet loss information determined based on at least detected gaps in the plurality of UL QFI sequence numbers.
  • a standardized field of the PDU Type 1 packet is associated with an indication of the packet loss information.
  • the initial sequence number of the plurality of UL QFI sequence numbers is determined by the UPF.
  • each of the data packets provide an indication of at least a UL QFI sequence number.
  • the UL data packet loss information is generated and recorded at the UPF without an indication being provided to the NG-RAN or another network entity.
  • a method that comprises causing transmission, to a user plane function, of a first uplink data packet associated with an uplink only traffic flow of a quality of service flow.
  • the method may further comprise receiving, from the user plane function, a dummy downlink data packet comprising a first timestamp, wherein the dummy downlink data packet is associated with the uplink only traffic flow of the quality of service flow.
  • the method may further comprise recording a second timestamp associated with a second local time at a radio access network reflecting a time at which the dummy downlink data packet was received by the radio access network.
  • the method may further comprise recording a third timestamp associated with a third local time at the radio access network reflecting a time at which a second uplink data packet was transmitted from the radio access network.
  • the method may further comprise causing transmission, to the user plane function, of the second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, the second timestamp, and the third timestamp.
  • the method may further comprise generating the first uplink data packet, wherein the first uplink data packet comprises a plurality of first uplink data packets transmitted over a time period associated with the uplink only traffic flow of the quality of service flow.
  • the method may further comprise recording the first timestamp received via the dummy downlink data packet.
  • the method may further comprise generating the second timestamp via at least a clock associated with the radio access network.
  • the method may further comprise discarding the dummy downlink data packet.
  • the method may further comprise generating the third timestamp via at least the clock associated with the radio access network.
  • the method may further comprise generating the second uplink data packet.
  • the method may further comprise recording the one or more downlink quality of service flow identifier sequence numbers associated with the dummy downlink data packet. In some embodiments, the method may further comprise associating the one or more downlink quality of service flow identifier sequence numbers with one or more respective uplink data packets based on at least an initial sequence number associated with a particular quality of service flow.
  • the first uplink data packet and second uplink data packet are associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension.
  • the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • the header extension comprises a downlink quality of service flow identifier cumulative packet loss counter value associated with a downlink quality of service flow identifier cumulative packet loss counter field.
  • the downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packet.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to cause transmission, to a user plane function, of a first uplink data packet associated with an uplink only traffic flow of a quality of service flow.
  • the apparatus may be further caused to at least receive, from the user plane function, a dummy downlink data packet comprising a first timestamp, wherein the dummy downlink data packet is associated with the uplink only traffic flow of the quality of service flow.
  • the apparatus may be further caused to at least record a second timestamp associated with a second local time at a radio access network reflecting a time at which the dummy downlink data packet was received by the radio access network.
  • the apparatus may be further caused to at least record a third timestamp associated with a third local time at the radio access network reflecting a time at which a second uplink data packet was transmitted from the radio access network.
  • the apparatus may be further caused to at least cause transmission, to the user plane function, of the second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, the second timestamp, and the third timestamp.
  • the apparatus may be further caused to at least generate the first uplink data packet, wherein the first uplink data packet comprises a plurality of first uplink data packets transmitted over a time period associated with the uplink only traffic flow of the quality of service flow.
  • the apparatus may be further caused to at least record the first timestamp received via the dummy downlink data packet.
  • the apparatus may be further caused to at least generate the second timestamp via at least a clock associated with the radio access network.
  • the apparatus may be further caused to at least discard the dummy downlink data packet.
  • the apparatus may be further caused to at least generate the third timestamp via at least the clock associated with the radio access network.
  • the apparatus may be further caused to at least generate the second uplink data packet.
  • the apparatus may be further caused to at least record the one or more downlink quality of service flow identifier sequence numbers associated with the dummy downlink data packet. In some embodiments, the apparatus may be further caused to at least associate the one or more downlink quality of service flow identifier sequence numbers with one or more respective uplink data packets based on at least an initial sequence number associated with a particular quality of service flow.
  • the first uplink data packet and second uplink data packet are associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension.
  • the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • the header extension comprises a downlink quality of service flow identifier cumulative packet loss counter value associated with a downlink quality of service flow identifier cumulative packet loss counter field.
  • the downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packet.
  • a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, by at least a processor, to cause transmission, to a user plane function, of a first uplink data packet associated with an uplink only traffic flow of a quality of service flow.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least receive, from the user plane function, a dummy downlink data packet comprising a first timestamp, wherein the dummy downlink data packet is associated with the uplink only traffic flow of the quality of service flow.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least record a second timestamp associated with a second local time at a radio access network reflecting a time at which the dummy downlink data packet was received by the radio access network.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least record a third timestamp associated with a third local time at the radio access network reflecting a time at which a second uplink data packet was transmitted from the radio access network.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least cause transmission, to the user plane function, of the second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, the second timestamp, and the third timestamp.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least generate the first uplink data packet, wherein the first uplink data packet comprises a plurality of first uplink data packets transmitted over a time period associated with the uplink only traffic flow of the quality of service flow.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least record the first timestamp received via the dummy downlink data packet.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least generate the second timestamp via at least a clock associated with the radio access network.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least discard the dummy downlink data packet. In some embodiments, the computer program product may be further configured, upon execution, by at least the processor, to at least generate the third timestamp via at least the clock associated with the radio access network. In some embodiments, the computer program product may be further configured, upon execution, by at least the processor, to at least generate the second uplink data packet.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least record the one or more downlink quality of service flow identifier sequence numbers associated with the dummy downlink data packet. In some embodiments, the computer program product may be further configured, upon execution, by at least the processor, to at least associate the one or more downlink quality of service flow identifier sequence numbers with one or more respective uplink data packets based on at least an initial sequence number associated with a particular quality of service flow.
  • the first uplink data packet and second uplink data packet are associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension.
  • the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • the header extension comprises a downlink quality of service flow identifier cumulative packet loss counter value associated with a downlink quality of service flow identifier cumulative packet loss counter field.
  • the downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packet.
  • an apparatus that comprises means for causing transmission, to a user plane function, of a first uplink data packet associated with an uplink only traffic flow of a quality of service flow.
  • the apparatus may further comprise means for receiving, from the user plane function, a dummy downlink data packet comprising a first timestamp, wherein the dummy downlink data packet is associated with the uplink only traffic flow of the quality of service flow.
  • the apparatus may further comprise means for recording a second timestamp associated with a second local time at a radio access network reflecting a time at which the dummy downlink data packet was received by the radio access network.
  • the apparatus may further comprise means for recording a third timestamp associated with a third local time at the radio access network reflecting a time at which a second uplink data packet was transmitted from the radio access network.
  • the apparatus may further comprise means for causing transmission, to the user plane function, of the second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, the second timestamp, and the third timestamp.
  • the apparatus may further comprise means for generating the first uplink data packet, wherein the first uplink data packet comprises a plurality of first uplink data packets transmitted over a time period associated with the uplink only traffic flow of the quality of service flow.
  • the apparatus may further comprise means for recording the first timestamp received via the dummy downlink data packet.
  • the apparatus may further comprise means for generating the second timestamp via at least a clock associated with the radio access network.
  • the apparatus may further comprise means for discarding the dummy downlink data packet.
  • the apparatus may further comprise means for generating the third timestamp via at least the clock associated with the radio access network.
  • the apparatus may further comprise means for generating the second uplink data packet.
  • the apparatus may further comprise means for recording the one or more downlink quality of service flow identifier sequence numbers associated with the dummy downlink data packet. In some embodiments, the apparatus may further comprise means for associating the one or more downlink quality of service flow identifier sequence numbers with one or more respective uplink data packets based on at least an initial sequence number associated with a particular quality of service flow.
  • the first uplink data packet and second uplink data packet are associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension.
  • the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • the header extension comprises a downlink quality of service flow identifier cumulative packet loss counter value associated with a downlink quality of service flow identifier cumulative packet loss counter field.
  • the downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packet.
  • a method that comprises receiving, from a radio access network, a first uplink data packet.
  • the method may further comprise detecting, based on at least the first uplink data packet, an uplink only traffic flow associated with a quality of service flow.
  • the method may further comprise recording a first timestamp associated with a first local time at a user plane function reflecting a time at which a dummy downlink data packet was transmitted from the user plane function.
  • the method may further comprise generating the dummy downlink data packet comprising the first timestamp.
  • the method may further comprise causing transmission, to the radio access network, of the dummy downlink data packet.
  • the method may further comprise receiving, from the radio access network, a second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, a second timestamp, and a third timestamp.
  • the method may further comprise recording a fourth timestamp associated with a fourth local time at the user plane function reflecting a time at which the second uplink data packet was received by the user plane function.
  • the method may further comprise determining, based on at least the first timestamp and the second timestamp, a downlink delay time associated with the quality of service flow.
  • the method may further comprise determining, based on at least the third timestamp and the fourth timestamp, an uplink delay time associated with the quality of service flow.
  • the method may further comprise generating the first timestamp via at least a clock associated with the user plane function. In some embodiments, the method may further comprise recording at least the second timestamp and the third timestamp received via the second uplink data packet. In some embodiments, the method may further comprise generating the fourth timestamp via at least the clock associated with the user plane function.
  • each uplink data packet is associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • a downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packets.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension. In some embodiments of the method, the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, from a radio access network, a first uplink data packet.
  • the apparatus may be further caused to at least detect, based on at least the first uplink data packet, an uplink only traffic flow associated with a quality of service flow.
  • the apparatus may be further caused to at least record a first timestamp associated with a first local time at a user plane function reflecting a time at which a dummy downlink data packet was transmitted from the user plane function.
  • the apparatus may be further caused to at least generate the dummy downlink data packet comprising the first timestamp.
  • the apparatus may be further caused to at least cause transmission, to the radio access network, of the dummy downlink data packet.
  • the apparatus may be further caused to at least receive, from the radio access network, a second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, a second timestamp, and a third timestamp.
  • the apparatus may be further caused to at least record a fourth timestamp associated with a fourth local time at the user plane function reflecting a time at which the second uplink data packet was received by the user plane function.
  • the apparatus may be further caused to at least determine, based on at least the first timestamp and the second timestamp, a downlink delay time associated with the quality of service flow.
  • the apparatus may be further caused to at least determine, based on at least the third timestamp and the fourth timestamp, an uplink delay time associated with the quality of service flow.
  • the apparatus may be further caused to at least generate the first timestamp via at least a clock associated with the user plane function. In some embodiments, the apparatus may be further caused to at least record at least the second timestamp and the third timestamp received via the second uplink data packet. In some embodiments, the apparatus may be further caused to at least generate the fourth timestamp via at least the clock associated with the user plane function.
  • each uplink data packet is associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • a downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packets.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension. In some embodiments of the apparatus, the header extension comprises one or more downlink quality of service flow identifier sequence numbers. [0047] According to an aspect of the present disclosure, there is provided a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, by at least a processor, to receive, from a radio access network, a first uplink data packet.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least detect, based on at least the first uplink data packet, an uplink only traffic flow associated with a quality of service flow.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least record a first timestamp associated with a first local time at a user plane function reflecting a time at which a dummy downlink data packet was transmitted from the user plane function.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least generate the dummy downlink data packet comprising the first timestamp.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least cause transmission, to the radio access network, of the dummy downlink data packet.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least receive, from the radio access network, a second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, a second timestamp, and a third timestamp.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least record a fourth timestamp associated with a fourth local time at the user plane function reflecting a time at which the second uplink data packet was received by the user plane function.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least determine, based on at least the first timestamp and the second timestamp, a downlink delay time associated with the quality of service flow. In some embodiments, the computer program product may be further configured, upon execution, by at least the processor, to at least determine, based on at least the third timestamp and the fourth timestamp, an uplink delay time associated with the quality of service flow.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least generate the first timestamp via at least a clock associated with the user plane function. In some embodiments, the computer program product may be further configured, upon execution, by at least the processor, to at least record at least the second timestamp and the third timestamp received via the second uplink data packet. In some embodiments, the computer program product may be further configured, upon execution, by at least the processor, to at least generate the fourth timestamp via at least the clock associated with the user plane function. [0050] In some embodiments of the computer program product, each uplink data packet is associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • a downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers. In some embodiments of the computer program product, each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packets.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension. In some embodiments of the computer program product, the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • an apparatus that comprises means for receiving, from a radio access network, a first uplink data packet.
  • the apparatus may further comprise means for detecting, based on at least the first uplink data packet, an uplink only traffic flow associated with a quality of service flow.
  • the apparatus may further comprise means for recording a first timestamp associated with a first local time at a user plane function reflecting a time at which a dummy downlink data packet was transmitted from the user plane function.
  • the apparatus may further comprise means for generating the dummy downlink data packet comprising the first timestamp.
  • the apparatus may further comprise means for causing transmission, to the radio access network, of the dummy downlink data packet.
  • the apparatus may further comprise means for receiving, from the radio access network, a second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, a second timestamp, and a third timestamp.
  • the apparatus may further comprise means for recording a fourth timestamp associated with a fourth local time at the user plane function reflecting a time at which the second uplink data packet was received by the user plane function.
  • the apparatus may further comprise means for determining, based on at least the first timestamp and the second timestamp, a downlink delay time associated with the quality of service flow.
  • the apparatus may further comprise means for determining, based on at least the third timestamp and the fourth timestamp, an uplink delay time associated with the quality of service flow.
  • the apparatus may further comprise means for generating the first timestamp via at least a clock associated with the user plane function. In some embodiments, the apparatus may further comprise means for recording at least the second timestamp and the third timestamp received via the second uplink data packet. In some embodiments, the apparatus may further comprise means for generating the fourth timestamp via at least the clock associated with the user plane function.
  • each uplink data packet is associated with the quality of service flow.
  • the dummy downlink data packet is associated with the quality of service flow.
  • the quality of service flow is active and associated with the uplink only traffic flow.
  • a downlink quality of service flow identifier cumulative packet loss counter value is determined based on a number of gaps associated with a plurality of downlink quality of service flow identifier sequence numbers.
  • each gap of the number of gaps associated with the plurality of downlink quality of service flow identifier sequence numbers reflects a loss event associated with one or more lost downlink data packets.
  • the header extension comprises one or more of a generic packet radio service tunneling protocol header extension, a protocol data unit type 0 extension, or a protocol data unit type 1 extension. In some embodiments of the apparatus, the header extension comprises one or more downlink quality of service flow identifier sequence numbers.
  • a method that comprises determining a protocol data unit header extension.
  • the method may further comprise determining one or more sequence numbers.
  • the method may further comprise generating a data packet comprising a header extension comprising a cumulative packet loss counter field and a cumulative packet loss counter value reflecting a number of loss events associated with one or more of a lost data packet.
  • the protocol data unit header extension comprises a protocol data unit type 0 extension or a protocol data unit type 1 extension.
  • the cumulative packet loss counter value is determined by at least a radio access network based on a number of gaps associated with the one or more sequence numbers.
  • the one or more sequence numbers comprises one or more of an initial sequence number or one or more downlink quality of service flow identifier sequence numbers.
  • the initial sequence number is selected by a user plane function and associated with a particular quality of service flow.
  • the header extension comprises a generic packet radio service tunneling protocol header extension.
  • the cumulative packet loss counter field comprises a downlink quality of service flow identifier cumulative packet loss counter field. In some embodiments of the method, the cumulative packet loss counter value comprises a downlink quality of service flow identifier cumulative packet loss counter value.
  • an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to determine a protocol data unit header extension.
  • the apparatus may be further caused to at least determine one or more sequence numbers.
  • the apparatus may be further caused to at least generate a data packet comprising a header extension comprising a cumulative packet loss counter field and a cumulative packet loss counter value reflecting a number of loss events associated with one or more of a lost data packet.
  • the protocol data unit header extension comprises a protocol data unit type 0 extension or a protocol data unit type 1 extension.
  • the cumulative packet loss counter value is determined by at least a radio access network based on a number of gaps associated with the one or more sequence numbers.
  • the one or more sequence numbers comprises one or more of an initial sequence number or one or more downlink quality of service flow identifier sequence numbers.
  • the initial sequence number is selected by a user plane function and associated with a particular quality of service flow.
  • the header extension comprises a generic packet radio service tunneling protocol header extension.
  • the cumulative packet loss counter field comprises a downlink quality of service flow identifier cumulative packet loss counter field. In some embodiments of the apparatus, the cumulative packet loss counter value comprises a downlink quality of service flow identifier cumulative packet loss counter value.
  • a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, by at least a processor, to determine a protocol data unit header extension.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least determine one or more sequence numbers.
  • the computer program product may be further configured, upon execution, by at least the processor, to at least generate a data packet comprising a header extension comprising a cumulative packet loss counter field and a cumulative packet loss counter value reflecting a number of loss events associated with one or more of a lost data packet.
  • the protocol data unit header extension comprises a protocol data unit type 0 extension or a protocol data unit type 1 extension.
  • the cumulative packet loss counter value is determined by at least a radio access network based on a number of gaps associated with the one or more sequence numbers.
  • the one or more sequence numbers comprises one or more of an initial sequence number or one or more downlink quality of service flow identifier sequence numbers.
  • the initial sequence number is selected by a user plane function and associated with a particular quality of service flow.
  • the header extension comprises a generic packet radio service tunneling protocol header extension.
  • the cumulative packet loss counter field comprises a downlink quality of service flow identifier cumulative packet loss counter field. In some embodiments of the computer program product, the cumulative packet loss counter value comprises a downlink quality of service flow identifier cumulative packet loss counter value.
  • an apparatus that comprises means for determining a protocol data unit header extension.
  • the apparatus may further comprise means for determining one or more sequence numbers.
  • the apparatus may further comprise means for generating a data packet comprising a header extension comprising a cumulative packet loss counter field and a cumulative packet loss counter value reflecting a number of loss events associated with one or more of a lost data packet.
  • the protocol data unit header extension comprises a protocol data unit type 0 extension or a protocol data unit type 1 extension.
  • the cumulative packet loss counter value is determined by at least a radio access network based on a number of gaps associated with the one or more sequence numbers.
  • the one or more sequence numbers comprises one or more of an initial sequence number or one or more downlink quality of service flow identifier sequence numbers.
  • the initial sequence number is selected by a user plane function and associated with a particular quality of service flow.
  • the header extension comprises a generic packet radio service tunneling protocol header extension.
  • the cumulative packet loss counter field comprises a downlink quality of service flow identifier cumulative packet loss counter field. In some embodiments of the apparatus, the cumulative packet loss counter value comprises a downlink quality of service flow identifier cumulative packet loss counter value.
  • FIG. 1 illustrates an example architecture for a communications network, according to some embodiments
  • FIG. 2 illustrates an example architecture for a communications network, according to some embodiments
  • FIG. 3 illustrates an example architecture for a communications network, according to some embodiments
  • FIG. 4 illustrates an example computing device for communicating over communication networks with other network entities, according to some embodiments
  • FIG. 5 is a flow diagram illustrating the signaling between communication devices via a network infrastructure, according to some embodiments.
  • FIG. 6 illustrates an example extension for a data packet header for communications via a network infrastructure, according to some embodiments
  • FIG. 7 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments;
  • FIG. 8 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments.
  • FIG. 9 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments.
  • data can be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention.
  • use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
  • circuitry refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, 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.
  • This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims.
  • circuitry also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • circuitry as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.
  • node As used herein, the terms “node,” “entity,” “intermediary,” “intermediate entity,” “go-between,” and similar terms can be used interchangeably to refer to computers connected via, or programs running on, a network or plurality of networks capable of data creation, modification, deletion, transmission, receipt, and/or storage in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
  • the terms “user equipment,” “user device,” “device,” “apparatus,” “mobile device,” “personal computer,” “laptop computer,” “laptop,” “desktop computer,” “desktop,” “mobile phone,” “tablet,” “smartphone,” “smart device,” “cellphone,” “computing device,” “communication device,” “user communication device,” “terminal,” and similar terms can be used interchangeably to refer to an apparatus, such as may be embodied by a computing device, configured to access a network or plurality of networks for at least the purpose of wired and/or wireless transmission of communication signals in accordance with certain embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.
  • a medium can take many forms, including, but not limited to a non-transitory computer- readable storage medium (e.g., non-volatile media, volatile media), and transmission media.
  • Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves.
  • Signals include man-made transient variations in amplitude, frequency, phase, polarization or other physical properties transmitted through the transmission media.
  • non-transitory computer-readable media examples include a magnetic computer readable medium (e.g., a floppy disk, hard disk, magnetic tape, any other magnetic medium), an optical computer readable medium (e.g., a compact disc read only memory (CD-ROM), a digital versatile disc (DVD), a Blu-Ray disc (BD), the like, or combinations thereof), a random access memory (RAM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), a FLASH-EPROM, or any other non-transitory medium from which a computer can read.
  • the term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it will be appreciated that where embodiments are described to use a computer-readable storage medium, other types of computer- readable mediums can be substituted for or used in addition to the computer-readable storage medium in alternative embodiments.
  • a communication device or terminal can be provided for wireless access via cells, base stations, access points, the like (e.g., wireless transmitter and/or receiver nodes providing access points for a radio access communication system and/or other forms of wired and/or wireless networks), or combinations thereof.
  • wired and/or wireless networks include, but are not limited to, networks configured to conform to 2G, 3G, 4G, LTE, 5G, and/or any other similar or yet to be developed future communication network standards.
  • the present disclosure contemplates that any methods, apparatuses, computer program codes, and any portions or combination thereof can also be implemented with yet undeveloped communication networks and associated standards as would be developed in the future and understood by one skilled in the art in light of the present disclosure.
  • Access points and hence communications there through are typically controlled by at least one appropriate control apparatus so as to enable operation thereof and management of mobile communication devices in communication therewith.
  • a control apparatus for a node can be integrated with, coupled to, and/or otherwise provided for controlling the access points.
  • the control apparatus can be arranged to allow communications between a user equipment and a core network or a network entity of the core network.
  • control apparatus can comprise at least one memory, at least one data processing unit such as a processor or the like, and an input/output interface (e.g., global positioning system receiver/transmitter, keyboard, mouse, touchpad, display, universal serial bus (USB), Bluetooth, ethernet, wired/wireless connections, the like, or combinations thereof). Via the interface, the control apparatus can be coupled to relevant other components of the access point.
  • the control apparatus can be configured to execute an appropriate software code to provide the control functions. It shall be appreciated that similar components can be provided in a control apparatus provided elsewhere in the network system, for example in a core network entity.
  • the control apparatus can be interconnected with other control entities.
  • the control apparatus and functions can be distributed between several control units.
  • each base station can comprise a control apparatus. In alternative embodiments, two or more base stations can share a control apparatus.
  • Access points and associated controllers can communicate with each other via a fixed line connection and/or via a radio interface.
  • the logical connection between the base station nodes can be provided for example by an X2, an SI, a similar interface, or combinations thereof. This interface can be used for example for coordination of operation of the stations and performing reselection or handover operations.
  • the logical communication connection between the initial communication node and the final communication node of the network can comprise a plurality of intermediary nodes. Additionally, any of the nodes can be added to and removed from the logical communication connection as required to establish and maintain a network function communication.
  • the communication device or user equipment can comprise any suitable device capable of at least receiving a communication signal comprising data.
  • the communication signal can be transmitted via a wired connection, a wireless connection, or combinations thereof.
  • the device can be a handheld data processing device equipped with radio receiver, data processing and user interface apparatus.
  • Non-limiting examples include a mobile station (MS) such as a mobile phone or what is known as a ‘smart phone,’ a portable computer such as a laptop or a tablet computer provided with a wireless interface card or other wireless interface facility, personal data assistant (PDA) provided with wireless communication capabilities, or any combinations of these or the like.
  • MS mobile station
  • PDA personal data assistant
  • wearable wireless devices such as those integrated with watches or smart watches, eyewear, helmets, hats, clothing, earpieces with wireless connectivity, jewelry and so on, Universal Serial Bus (USB) sticks with wireless capabilities, modem data cards, machine type devices or any combinations of these or the like.
  • USB Universal Serial Bus
  • a communication device e.g., configured for communication with the wireless network or a core network entity
  • a handheld or otherwise mobile communication device or user equipment can be exemplified by a handheld or otherwise mobile communication device or user equipment.
  • a mobile communication device can be provided with wireless communication capabilities and appropriate electronic control apparatus for enabling operation thereof.
  • the communication device can be provided with at least one data processing entity, for example a central processing unit and/or a core processor, at least one memory and other possible components such as additional processors and memories for use in software and hardware aided execution of tasks it is designed to perform.
  • the data processing, storage, and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets.
  • Data processing and memory functions provided by the control apparatus of the communication device are configured to cause control and signaling operations in accordance with certain embodiments as described later in this description.
  • a user can control the operation of the communication device by means of a suitable user interface such as touch sensitive display screen or pad and/or a keypad, one of more actuator buttons, voice commands, combinations of these, or the like.
  • a speaker and a microphone are also typically provided.
  • a mobile communication device can comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • a communication device can communicate wirelessly via one or more appropriate apparatuses for receiving and transmitting signals (e.g., global positioning system receiver/transmitter, remote touchpad interface with remote display, Wi-Fi interface, etc.).
  • a radio unit can be connected to the control apparatus of the device.
  • the radio unit can comprise a radio part and associated antenna arrangement.
  • the antenna arrangement can be arranged internally or externally to the communication device.
  • FIGS. 1-3 illustrate various example architectures for a communications network 100 in which the various methods, apparatuses, and computer program products can be carried out and/or used.
  • the communications network 100 can comprise any suitable configuration, number, orientation, positioning, and/or dimensions of components and specialized equipment configured to provide an air interface (e.g., New Radio (NR)) for communication or connection between a User Equipment 102 (UE 102) and a Data Network 116 (DN 116) via a Core Network 101 (CN 101) of the communications network 100.
  • NR New Radio
  • UE 102 User Equipment 102
  • DN 116 Data Network 116
  • CN 101 Core Network 101
  • the UE 102 can be associated with one or more devices associated with one or more network function (NF) service consumers.
  • NF network function
  • a communications network 100 can be provided in which the UE 102 is in operable communication with the Radio Access Network 104 (RAN 104), such as by way of a transmission tower, a base station, an access point, a network node, and/or the like.
  • the RAN 104 can communicate with the CN 101 or a component or entity thereof.
  • the CN 101 can facilitate communication between the UE 102 and the DN 116, such as for sending data, messages, requests, the like, or combinations thereof.
  • the DN 116 or the CN 101 can be in communication with an Application Server or Application Function 112 (AS/AF 112).
  • AS/AF 112 Application Server or Application Function 112
  • the RAN 104, CN 101, DN 116, and/or AS/AF 112 can be associated with a Network Repository Function (NRF), NF service producer, Service Communication Proxy (SCP), Security Edge Protection Proxy (SEPP), Policy Charging Function (PCF), the like, or combinations thereof.
  • NRF Network Repository Function
  • SCP Service Communication Proxy
  • SEPP Security Edge Protection Proxy
  • PCF Policy Charging Function
  • the communications network 100 can comprise a series of connected network devices and specialized hardware that is distributed throughout a service region, state, province, city, or country, and one or more network entities, which can be stored at and/or hosted by one or more of the connected network devices or specialized hardware.
  • the UE 102 can connect to the RAN 104, which can then relay the communications between the UE 102 and the CN 101, the CN 101 being connected to the DN 116, which can be in communication with one or more AS/AF 112.
  • the UE 102 can be in communication with a RAN 104, which can act as a relay between the UE 102 and other components or services of the CN 101.
  • the UE 102 can communicate with the RAN 104, which can in turn communicate with an Access and Mobility Management Function 108 (AMF 108).
  • AMF 108 Access and Mobility Management Function
  • the UE 102 can communicate directly with the AMF 108.
  • the AMF 108 can be in communication with one or more network functions (NFs), such as an Authentication Server Function 120 (AUSF 120), a Network Slice Selection Function 122 (NSSF 122), a Network Repository Function 124 (NRF 124), a Policy Charging Function 114 (PCF 114), a Network Data Analytics Function 126 (NWDAF 126), a Unified Data Management function 118 (UDM 118), the AS/AF 112, a Session Management Function 110 (SMF 110), and/or the like.
  • NFs network functions
  • the SMF 110 can be in communication with one or more User Plane Functions 106 (UPF 106, UPF 106a, UPF 106b, collectively “UPF 106”).
  • UPF 106 User Plane Functions 106
  • the UPF 106 can be in communication with the RAN 104 and the DN 116.
  • the DN 116 can be in communication with a first UPF 106a and the RAN 104 can be in communication with a second UPF 106b, while the SMF 110 is in communication with both the first and second UPFs 106a, b and the first and second UPFs 106a, b are in communication each with the other.
  • the UE 102 can comprise a single-mode or a dual-mode device such that the UE 102 can be connected to one or more RANs 104.
  • the UE 102 can comprise a single-mode or a dual-mode device such that the UE 102 can be connected to one or more RANs 104.
  • RAN 104 can be configured to implement one or more Radio Access Technologies (RATs), such as Bluetooth, Wi-Fi, and Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), LTE or 5G NR, among others, that can be used to connect the UE 102 to the CN 101.
  • RATs Radio Access Technologies
  • the RAN 104 can comprise or be implemented using a chip, such as a silicon chip, in the UE 102 that can be paired with or otherwise recognized by a similar chip in the CN 101, such that the RAN 104 can establish a connection or line of communication between the UE 102 and the CN 101 by identifying and pairing the chip within the UE 102 with the chip within the CN 101.
  • the RAN 104 can implement one or more base stations, towers or the like to communicate between the UE 102 and the AMF 108 of the CN 101.
  • the communications network 100 or components thereof e.g., base stations, towers, etc.
  • a communication device e.g., the UE 102
  • the communications network 100 can comprise or employ massive Multiple Input and Multiple Output (MIMO) antennas.
  • MIMO massive Multiple Input and Multiple Output
  • the communications network 100 can comprise Multi-User MIMO (MU-MIMO) antennas.
  • MU-MIMO Multi-User MIMO
  • the communications network 100 can employ edge computing whereby the computing servers are communicatively, physically, computationally, and/or temporally closer to the communications device (e.g., UE 102) in order to reduce latency and data traffic congestion.
  • the communications network 100 can employ other technologies, devices, or techniques, such as small cell, low-powered RAN, beamforming of radio waves, Wi-Fi cellular convergence, Non-Orthogonal Multiple Access (NOMA), channel coding, the like, or combinations thereof.
  • NOMA Non-Orthogonal Multiple Access
  • the UE 102 can be configured to communicate with the RAN 104 in a N1 interface, e.g., according to a Non-Access Stratum (NAS) protocol.
  • RAN 104 can be configured to communicate with the CN 101 or a component thereof (e.g., the AMF 108) in a N2 interface, e.g., in a control plane between a base station of the RAN 104 and the AMF 108.
  • the RAN 104 can be configured to communicate with the UPF 106 in a N3 interface, e.g., in a user plane.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with other services or network entities within the CN 101 in various different interfaces and/or according to various different protocols.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the AUSF 120 in a Nausf interface or an N12 interface.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the NSSF 122 in a Nnssf interface.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the NRF 124 in a Nnrf interface.
  • the AMF 108 and/or the SMF 110 can be configured to communicate with the PCF 114 in a Npcf interface or an N7 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the NWDAF 126 in a Nnwdaf interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the UDM 118 in a Nudm interface, an N8 interface, or an N10 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the AS/AF 112 in a Naf interface.
  • the SMF 110 can be configured to communicate with the UPF 106 in a N4 interface, which can act as a bridge between the control plane and the user plane, such as acting as a conduit for a Protocol Data Unit (PDU) session during which information is transmitted between, e.g., the UE 102 and the CN 101 or components/services thereof.
  • PDU Protocol Data Unit
  • FIGS. 1-3 illustrate various configurations and/or components of an example architecture of the communications network 100, many other systems, system configurations, networks, network entities, and pathways/protocols for communication therein are contemplated and considered within the scope of this present disclosure.
  • the apparatus 200 of an example embodiment can be configured to perform the functions described herein.
  • the apparatus 200 can more generally be embodied by a computing device, such as a server, a personal computer, a computer workstation or other type of computing device including those functioning as a user equipment and/or a component of a wireless network or a wireless local area network.
  • the apparatus of an example embodiment can be configured as shown in FIG. 4 so as to include, be associated with or otherwise be in communication with a processor 202 and a memory device 204 and, in some embodiments, and/or a communication interface 206.
  • the apparatus of an example embodiment may also optionally include a user interface, such as a touch screen, a display, a keypad, the like, or combinations thereof.
  • a user interface such as a touch screen, a display, a keypad, the like, or combinations thereof.
  • the apparatus according to an example embodiment can be configured with a global positioning circuit that comprises a global positioning receiver and/or global positioning transmitter configured for communication with one or more global navigation satellite systems (e.g., GPS, GLONASS, Galileo, the like, or combinations thereof).
  • the global positioning circuit may be configured for the transmission and/or receipt of direct/indirect satellite and/or cell signals in order to determine geolocation data (e.g., latitude, longitude, elevation, altitude, geographic coordinates, the like, or combinations thereof.) for the apparatus and/or another communication device associated with the apparatus or the one or more global navigation satellite systems.
  • geolocation data e.g., latitude, longitude, elevation, altitude, geographic coordinates, the like, or combinations thereof.
  • the processor 202 (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) can be in communication with the memory device 204 via a bus for passing information among components of the apparatus 200.
  • the memory device can include, for example, one or more volatile and/or non-volatile memories, such as a non-transitory memory device.
  • the memory device can be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that can be retrievable by a machine (e.g., a computing device like the processor).
  • the memory device can be configured to store information, data, content, applications, instructions, the like, or combinations thereof for enabling the apparatus to carry out various functions in accordance with an example embodiment.
  • the memory device could be configured to buffer input data for processing by the processor.
  • the memory device could be configured to store instructions for execution by the processor.
  • the apparatus 200 can, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus can be embodied as a chip or chip set. In other words, the apparatus can comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly can provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus can therefore, in some cases, be configured to implement an embodiment of the present disclosure on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset can constitute means for performing one or more operations for providing the functionalities described herein.
  • a chip or chipset can constitute means for performing one or more operations for providing the functionalities described herein.
  • the processor 202 can be embodied in a number of different ways.
  • the processor can be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Micro-Controller Unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor can include one or more processing cores configured to perform independently.
  • a multi-core processor can enable multiprocessing within a single physical package.
  • the processor can include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
  • the processor 202 can be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor.
  • the processor can be configured to execute hard coded functionality.
  • the processor can represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly.
  • the processor when the processor is embodied as an ASIC, FPGA, the like, or combinations thereof the processor can be specifically configured hardware for conducting the operations described herein.
  • the processor when the processor is embodied as an executor of instructions, the instructions can specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed.
  • the processor can be a processor of a specific device (e.g., an encoder and/or a decoder) configured to employ an embodiment of the present disclosure by further configuration of the processor by instructions for performing the algorithms and/or operations described herein.
  • the processor can include, among other things, a clock, an Arithmetic Logic Unit (ALU) and logic gates configured to support operation of the processor.
  • ALU Arithmetic Logic Unit
  • the communication interface can be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the apparatus 200, such as NF, NRF, a base station, an access point, SCP, UE 102, RAN 104, core network services, AS/AF 112, a database or other storage device, the like, or combinations thereof.
  • the communication interface can include, for example, one or more antennas and supporting hardware and/or software for enabling communications with a wireless communication network.
  • the communication interface can include the circuitry for interacting with the one or more antennas to cause transmission of signals via the one or more antennas or to handle receipt of signals received via the one or more antennas.
  • the one or more antennas may comprise one or more of a dipole antenna, monopole antenna, helix antenna, loop antenna, waveguide, horn antenna, parabolic reflectors, corner reflectors, dishes, micro strip patch array, convex-plane, concave-plane, convex-convex, concave-concave lenses, the like or combinations thereof.
  • the communication interface can alternatively or also support wired communication.
  • a session management function (e.g., SMF 110) can comprise a 5GC session management function for any suitable Control and User Plane Separation (CUPS) architecture, such as for the General Packet Radio Service (GPRS), Gateway GPRS Support Node Control plane function (GGSN-C), Trusted Wireless Access Gateway Control plane function (TWAG-C), Broadband Network Gateway Control and User Plane Separation (BNG-CUPS), N4- Interface, Sxa-Interface, Sxb-Interface, Sxc-Interface, Evolved Packet Core (EPC) Serving Gateway Control plane function (SGW-C), EPC Packet Data Network Gateway Control plane function (PGW- C), EPC Traffic Detection Control plane function (TDF-C), the like, or combinations thereof.
  • GPRS General Packet Radio Service
  • GGSN-C Gateway GPRS Support Node Control plane function
  • TWAG-C Trusted Wireless Access Gateway Control plane function
  • BNG-CUPS Broadband Network Gateway Control and User Plan
  • the apparatus 200 can include a processor 202 in communication with a memory 204 and configured to provide signals to and receive signals from a communication interface 206.
  • the communication interface 206 can include a transmitter and a receiver.
  • the processor 202 can be configured to control the functioning of the apparatus 200, at least in part.
  • the processor 202 can be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver.
  • the processor 202 can be configured to control other elements of apparatus 200 by effecting control signaling via electrical leads connecting the processor 202 to the other elements, such as a display or the memory 204.
  • the apparatus 200 can be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like.
  • Signals sent and received by the processor 202 can include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, Wireless Local Access Network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, Asymmetric Digital Subscriber Line (ADSL), Data Over Cable Service Interface Specification (DOCSIS), the like, or combinations thereof.
  • these signals can include speech data, user generated data, user requested data, the like, or combinations thereof.
  • the apparatus 200 and/or a cellular modem therein can be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, Session Initiation Protocol (SIP)), the like, or combinations thereof.
  • the apparatus 200 can be capable of operating in accordance with 2G wireless communication protocols Interim Standard (IS) 136 (IS-136), Time Division Multiple Access (TDMA), GSM, IS-95, Code Division Multiple Access, Code Division Multiple Access (CDMA), the like, or combinations thereof.
  • IS Interim Standard
  • TDMA Time Division Multiple Access
  • GSM Global System for Mobile communications
  • CDMA Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • the apparatus 200 can be capable of operating in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), the like, or combinations thereof. Further, for example, the apparatus 200 can be capable of operating in accordance with 3G wireless communication protocols, such as UMTS, Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), the like, or combinations thereof.
  • the NA 200 can be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), the like, or combinations thereof.
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the apparatus 200 can be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that can be subsequently developed.
  • the apparatus 200 can be capable of operating according to or within the framework of any suitable CUPS architecture, such as for the gateway GGSN-C, TWAG-C, Broadband Network Gateways (BNGs), N4-Interface, Sxa-Interface, Sxb-Interface, Sxc-Interface, EPC SGW-C, EPC PGW-C, EPC TDF-C, the like, or combinations thereof.
  • BNGs Broadband Network Gateways
  • the apparatus and method may be configured to operate in conjunction with a number of other types of systems including systems hereinafter developed and implemented.
  • Some of the embodiments disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic.
  • the software, application logic, and/or hardware can reside on memory 204, the processor 202, or electronic components, for example.
  • the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media.
  • a “computer-readable medium” can be any non-transitory media 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 a computer or data processor circuitry, with examples depicted at FIG. 4.
  • the computer-readable medium can comprise a non-transitory computer-readable storage medium that can be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • FIG. 5 is a flow diagram illustrating the signaling between communication devices via a network infrastructure, according to some embodiments.
  • FIG. 5 illustrates an example signal sequence 500, for the provision of dummy monitoring data packets for detection of UL only traffic based on per QoS Flow timers, between communication devices (e.g., apparatus 200, base station, server hosted network function, etc.) by way of at least a network infrastructure (e.g., communications network 100 or the like).
  • the example network infrastructure utilized for signal sequence 500 comprises at least RAN 104 and UPF 106.
  • RAN 104 and UPF 106 are communicably connected via at least an N3 interface.
  • the network infrastructure may be configured in accordance with 5G system standards, or the like (e.g., 4G, LTE, etc.) and RAN 104 can comprise one or more 5G radio nodes, such as a Next Generation Node B (gNB) or equivalent.
  • RAN 104 may comprise an NG-RAN or the like.
  • the example signal sequence 500 may be implemented utilizing one or more network infrastructures associated with one or more networks (e.g., Public Land Mobile Network (PLMN), etc.) and each of the one or more networks may comprise one or more network slices.
  • RAN 104 comprises one or more shared base stations (e.g., gNBs or the like) communicably connected to a plurality of networks.
  • the example signal sequence 500 starts at block 502 when RAN 104, causes transmission of an N3 GTP U-plane data packet (e.g., monitoring data packet, UL data packet, etc.), via at least the N3 interface, to UPF 106.
  • N3 GTP U-plane data packet e.g., monitoring data packet, UL data packet, etc.
  • RAN 104 may stream UL data packets to UPF 106 for a particular time period (e.g., 30 seconds, minutes, hours, etc.).
  • the UPF 106 upon receipt of the N3 GTP U-plane data packet from RAN 104 via the N3 interface is configured to detect UL only traffic in a QoS Flow, see block 504.
  • UPF 106 may be configured to detect that N3 GTP U-plane data packet, or the like, is at least part of UL only traffic based on one or more of an indication associated with the N3 GTP U-plane data packet, an elapsed time period based on a timer (e.g., a timer associated with the UPF 106, etc.), or the like.
  • a timer e.g., a timer associated with the UPF 106, etc.
  • UPF 106 Upon detection/determination that the received N3 GTP U-plane data packet, or the like, is part of UL only traffic flow, UPF 106 is configured to record a first timestamp T1 for the QoS Flow, see block 506. In some embodiments, UPF 106 may generate the first timestamp T1 (e.g., via one or more of a processor or other circuitry described herein with regards to apparatus 200, a local clock associated with UPF 106, or the like). At block 508, UPF 106 generates (e.g., via one or more processors or other circuitry described herein with regards to apparatus 200, or the like) at least a dummy monitoring data packet for the QoS Flow.
  • the dummy monitoring data packet may comprise a PDU Type 0 GTP User Plane (GTP-U) header, or the like for indication of one or more timestamps (e.g., the first timestamp Tl, etc.).
  • UPF 106 may generate a dummy monitoring data packet configured with at least the PDU Type 0 GTP User Plane (GTP-U) header indicating the first timestamp Tl indicative of the local time Tl at UPF 106 reflecting the time at which the monitoring data packet was transmitted, sent out, generated, or the like.
  • UPF 106 causes transmission of a dummy N3 GTP U-plane packet (i.e., the dummy monitoring data packet associated with the first timestamp Tl) that is configured for QoS measurement only (e.g., to provide indication of the first timestamp Tl to RAN 104).
  • a dummy N3 GTP U-plane packet i.e., the dummy monitoring data packet associated with the first timestamp Tl
  • RAN 104 is configured to at least record (e.g., store in memory 204, etc.) a second timestamp T2 for the QoS Flow, see block 512.
  • RAN 104 may generate the second timestamp T2 (e.g., via one or more of a processor or other circuitry described herein with regards to apparatus 200, a local clock associated with RAN 104, or the like). For example, RAN 104 may record the first timestamp Tl from the dummy N3 GTP U-plane packet and then generate the second timestamp T2 that is indicative of the local time T2 reflecting the time at which the monitoring data packet was received by RAN 104.
  • Ran 104 may be configured to generate and/or record a third timestamp T3 that is indicative of a local time T3 reflecting the time at which RAN 104 generated and/or causes transmission of an UL data packet (e.g., an N3 GTP U-plane packets with user data) to UPF 106, see block 516.
  • RAN 104 generates and/or causes transmission of one or more N3 GTP U- plane packets with user data comprising timestamps Tl, T2, and/or T3.
  • the one or more N3 GTP U-plane packets may provide an indication of each of timestamps Tl, T2, and/or T3 via a PDU Type 0 or Type 1 GTP-U header.
  • UPF 106 may generate and/or record a fourth timestamp T4 indicative of a local time T4 that reflects the time at which UPF 106 received the one or more N3 GTP U-plane packets from RAN 104, see block 520.
  • the fourth timestamp T4 may comprise a plurality of timestamps each associated with each of the one or more N3 GTP U-plane packets.
  • UL delay T4 - T3
  • signal sequence 500 may provide for detection of the UL only traffic based on per QoS Flow timers at UPF 106. For example, when there has been no DL data packet sent by UPF 106 in a QoS Flow within a particular time period (e.g., a predefined period of time associated with a setup of UPF 106), but there has been at least one uplink packet received by UPF 106 from RAN 104 during the same QoS Flow (i.e., the QoS Flow is active) then UPF 106 may determine that the QoS Flow comprises UL only traffic.
  • a particular time period e.g., a predefined period of time associated with a setup of UPF 106
  • UPF 106 may be configured to start generating and causing transmission of one or more dummy DL monitoring data packets to facilitate one or more delay measurements in the QoS Flow (e.g., via one or more timestamps).
  • UPF 106 may determine that the QoS Flow comprises bi-directional traffic.
  • UPF 106 may be configured to stop generating and/or causing transmission of the one or more dummy DL monitoring data packets in the DL.
  • the timer(s) e.g., for the generation of one or more timestamps, etc.
  • the timer(s) for the determination that a QoS Flow comprises UL only traffic may be configured to the same time period/interval that defines a frequency of measurements to be triggered if the QoS Flow has bidirectional traffic.
  • FIG. 6 illustrates an example header extension 602 for an example data packet header 600 for communications via a network infrastructure (e.g., communications network 100 or the like), according to some embodiments of the present disclosure.
  • data packet header 600 comprises header extension 602 that is configured to provide an indication of a DL QFI cumulative packet loss counter.
  • header extension 602 may be configured to provide for an extended PDU Type 1 data packet with a new field denoted in FIG. 6 as “DL QFI Cumulative Packet Loss Counter” and configured at least to carry the cumulative downlink packet loss counter value for the QoS Flow that is identified by the field “QoS Flow Identifier” of data packet header 600.
  • RAN 104 may be configured to utilize one or more DL QFI sequence numbers stored in association with the data packet header 600 (e.g., a GTP header or the like).
  • the data packet header 600 may be generated by and/or transmitted from UPF 106 to provide for DL QoS Flow level packet loss detection.
  • the DL QFI cumulative packet loss counter indicated by header extension 602 may be determined by counting the number of gaps in a plurality of DL QFI sequence numbers.
  • the gaps in the plurality of DL QFI sequence numbers may be detected (e.g., by the UPF 106 or the like) and may define events of loss (e.g., loss of one or more data packets transmitted between RAN 104 and UPF 106 via the N3 interface).
  • RAN 104 may be configured to detect the gaps in the plurality of DL QFI sequence numbers and RAN 104 may be configured to, at least in part, populate the DL QFI cumulative packet loss counter indicated by header extension 602.
  • data packet header 600 may be configured as one or more of a PDU Type 1 GTP-U header, a PDU Type 0 GTP-U header, or the like. In some embodiments, data packet header 600 may be configured as one or more of a PDU Type 1 GTP-U header, a PDU Type 0 GTP-U header, or the like. In some embodiments, header extension 602 may be configured as one or more of a PDU Type 1 header extension, a PDU Type 0 header extension, or the like.
  • header extension 602 may be configured to provide for the implementation of a DL data packet loss determination that is configured for a per QoS Flow cumulative counter at RAN 104 and that indicates the number of lost packets since the initiation of a respective QoS Flow.
  • RAN 104 may be configured to incremental increase a counter of a QoS Flow each time a DL QFI sequence number of a DL data packet in the QoS Flow is greater than the DL QFI sequence number of the preceding DL data packet plus one in the same QoS Flow (i.e., as long as the QoS Flow remains active).
  • RAN 104 may be configured to cause transmission of a value associated with each increment of the QoS Flow cumulative counter via each UL PDU Type 1 packet transmitted to UPF 106 in the same QoS Flow. This ensures that even if an UL data packet carrying the latest counter value is itself lost then the next UL data packet transmitted during the same QoS Flow that is received by UPF 106 may bring DL QFI cumulative packet loss counter value up-to-date.
  • UPF 106 may determine (e.g., calculate, compute, detect, etc.) one or more differences in subsequently received DL QFI cumulative packet loss counter value to detect immediate loss events within a QoS Flow in real time.
  • UPF 106 may determine in real-time that there are, for example, two DL data packets that were not received by RAN 104.
  • header extension 602 may be configured to assist the UltraReliable Low-Latency Communication (URLLC) QoS monitoring.
  • header extension 602 may provide for an indication of handover losses during URLLC QoS monitoring.
  • header extension 602 may be applied selectively to specific QoS Flows where handover loss monitoring during URLLC QoS is of extra importance, for example during the monitoring of critical applications.
  • header extension 602 may also be applied at least during critical times (e.g., during time periods of predictive handovers, etc.).
  • header extension 602 may be utilized in combination with predictive handovers such that header extension 602 may be turned on before the predicted handover and turned off after handover is completed.
  • FIG. 7 illustrates a flowchart of the operations of an example method 700 performed by an example apparatus 200 which, in some embodiments, may be embodied by a computing device of the RAN (e.g., base station, gNB, computing device, etc.) which may, in turn, include computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by at least processor 202.
  • a RAN, or a device associated therewith may be configured to perform at least some of the operations of example method 700 described with regards to FIG. 7 below.
  • the RAN, or a device associated therewith may be associated with one or more of an N3 interface, a UPF, or the like.
  • apparatus 200 e.g., a base station of an NG-RAN, etc.
  • apparatus 200 includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for executing instructions to at least cause transmission, to a user plane function, of a first uplink data packet associated with an uplink only traffic flow of a quality of service flow (e.g., a streaming video feed from a UE associated with an IOT camera).
  • the apparatus 200 may be configured to receive, from the user plane function, a dummy downlink data packet comprising a first timestamp, wherein the dummy downlink data packet is associated with the uplink only traffic flow of the quality of service flow, see block 704.
  • the dummy downlink data packet may be provided by the UPF (e.g., at least in part generated and transmitted by the UPF) in response to a detection that the apparatus 200 is causing transmission of uplink only traffic flow for at least a particular time period, or time interval, of the quality of service flow being monitored. Moreover, the UPF may record and apply to the dummy downlink data pack, the first timestamp which is representative of a first local time at the UPF reflecting a time at which the dummy downlink data packet was transmitted from the user plane function.
  • apparatus 200 (e.g., a base station of an NG-RAN, etc.) of this example embodiment includes means for executing instructions (e.g., computer program code, etc.) to at least record a second timestamp associated with a second local time at a radio access network reflecting a time at which the dummy downlink data packet was received by the radio access network. Further, at block 708, the apparatus 200 further records a third timestamp associated with a third local time at the radio access network reflecting a time at which a second uplink data packet was transmitted from the radio access network.
  • the second and third timestamps may be generated by apparatus 200, or a computing device associated therewith, via at least a clock associated with apparatus 200 that is configured to at least track the local time at apparatus 200.
  • apparatus 200 may be configured to discard the dummy downlink data packet and generate a second uplink data packet comprising a plurality of timestamps to facilitate the monitoring of a quality of service flow.
  • apparatus 200 e.g., a base station of an NG-RAN, etc.
  • apparatus 200 includes means for executing instructions (e.g., computer program code, etc.) to at least cause transmission, to the user plane function, of the second uplink data packet comprising a header extension, wherein the header extension comprises the first timestamp, the second timestamp, and the third timestamp.
  • the second uplink data packet may comprise one or more downlink quality of service flow identifier sequence numbers associated with the dummy downlink data packet associated by the apparatus 200 with at least the second uplink data packet based on at least an initial sequence number associated with a particular quality of service flow.
  • the UPF upon receipt of the second uplink data packet, may utilize one or more downlink quality of service flow identifier sequence numbers to determine one or more lost data packets.
  • FIG. 8 illustrates a flowchart of the operations of an example method 800 performed by an example apparatus 200 which, in some embodiments, may be embodied by a computing device associated with a network entity (e.g., a server associated with a UPF, etc.) which may, in turn, include computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by at least processor 202.
  • a UPF, or a device associated therewith may be configured to perform at least some of the operations of example method 800.
  • a UPF, or a device associated therewith may be associated with one or more of an N3 interface, a RAN, a server, a core network, or the like.
  • apparatus 200 e.g., a server associated with a UPF, etc.
  • apparatus 200 includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for executing instructions to at least receive, from a radio access network, a first uplink data packet.
  • the first uplink data packet may comprise a plurality of uplink data packets, such as a streaming video and/or audio feed to a server via at least a UPF.
  • the apparatus 200 may be further configured to detect, based on at least the first uplink data packet, an uplink only traffic flow associated with a quality of service flow, see block 804.
  • apparatus 200 of this example embodiment includes means for executing instructions (e.g., computer program code, etc.) to at least record a first timestamp associated with a first local time at a user plane function reflecting a time at which a dummy downlink data packet was transmitted from the user plane function.
  • the first timestamp may be generated by a UPF, or a computing device such as a server associated therewith, via at least a clock associated with the UPF that is configured to at least track the local time at the UPF or an associated server.
  • apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206 or the like (e.g., a clock, etc.), for executing instructions to generate the dummy downlink data packet comprising the first timestamp.
  • the UPF, or associated server may also be configured to generate the dummy downlink data packet with one or more sequence numbers (e.g., an initial sequence number for identification of a quality of service flow and/or data packets associated therewith).
  • sequence numbers may be utilized by some embodiments of apparatus 200, or the like, to monitor a quality of service flow, for example, a loss event associated with one or more lost downlink data packets of the quality of service flow.
  • apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for executing instructions to cause transmission, to the radio access network, of the dummy downlink data packet.
  • the RAN, or base station thereof may be configured to respond to the dummy downlink data packet and the UPF may be configured with means for receiving one or more other uplink data packets comprising a header extension with a plurality of timestamps to facilitate monitoring of the quality of service flow.
  • the UPF server may be configured to utilize at least processor 202 and the plurality of timestamps to determine a downlink delay time and an uplink delay time associated with the quality of service flow.
  • FIG. 9 illustrates a flowchart of the operations of an example method 900 performed by an example apparatus 200 which, in some embodiments, may be embodied by a computing device associated with a network entity (e.g., a server associated with a UPF, a RAN base station, a client device, or the like) which may, in turn, include a computer program product comprising a non- transitory computer-readable medium storing computer program code to be executed by at least processor 202.
  • a network entity e.g., a server associated with a UPF, a RAN base station, a client device, or the like
  • a computer program product comprising a non- transitory computer-readable medium storing computer program code to be executed by at least processor 202.
  • one or more of a UPF, a RAN, or a computing device may be configured to perform at least some of the operations of example method 900.
  • a data packet comprising a header extension may be associated with (e.g., generated, transmitted, received, stored, deleted, and/or modified by) one or more of an N3 interface, a RAN, a UPF, a computing device (e.g., a server, etc.), or the like.
  • apparatus 200 e.g., a server associated with a UPF, etc.
  • apparatus 200 includes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for executing instructions to at least determine a protocol data unit header extension.
  • the protocol data unit header extension may comprise a protocol data unit type 0 or 1 extension.
  • apparatus 200 e.g., a base station of an NG- RAN, etc.
  • apparatus 200 includes means for executing instructions (e.g., computer program code, etc.) to at least determine one or more sequence numbers.
  • the apparatus 200 may be configured, based on at least the determined protocol data unit header extension and/or the determined sequence number (s), to generate a data packet comprising a header extension comprising a cumulative packet loss counter field and a cumulative packet loss counter value reflecting a number of loss events associated with one or more of a lost data packet. Moreover, the apparatus 200 may be configured to include without limitation means for determining based on a number of gaps associated with the one or more sequence numbers the cumulative packet loss counter value. It should be appreciated, in light of the present disclosure, that at least some embodiments of the header extension described with respect to example method 900 may be configured in accordance with an example embodiment described with respect to FIG. 6.
  • any such computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implements the function specified in the flowchart blocks.
  • the computer program instructions can also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer- implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
  • a computer program product is therefore defined in those instances in which the computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium with the computer program instructions, such as the computer-readable program code portions, being configured, upon execution, to perform the functions described above.
  • the computer program instructions, such as the computer-readable program code portions need not be stored or otherwise embodied by a non- transitory computer-readable storage medium, but can, instead, be embodied by a transitory medium with the computer program instructions, such as the computer-readable program code portions, still being configured, upon execution, to perform the functions described above.
  • blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions. [0134] In some embodiments, certain ones of the operations, methods, steps, processes, or the like, above can be modified or further amplified. Furthermore, in some embodiments, additional optional operations, methods, steps, processes, or the like, can be included.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Des procédés, des appareils, et des produits programmes d'ordinateur sont fournis pour une surveillance de trafic de communication. Certains modes de réalisation donnés à titre d'exemple fournissent la détection d'un flux de trafic unidirectionnel. Certains modes de réalisation donnés à titre d'exemple permettent la génération et la transmission d'un paquet de données factices pour faciliter une surveillance via une ou plusieurs entités de réseau sur une ou plusieurs interfaces de communication. Certains modes de réalisation donnés à titre d'exemple concernent des entités de réseau qui peuvent être configurées pour enregistrer des moments pour des événements de communication pour faciliter une surveillance pour la détermination de temps de retard. Certains modes de réalisation donnés à titre d'exemple permettent de générer un paquet de données comprenant une extension d'en-tête comprenant des champs étendus pour des valeurs supplémentaires reflétant un ou plusieurs paquets de données perdus.
PCT/IB2021/060618 2020-12-04 2021-11-16 Procédés, appareils, et produits programmes d'ordinateur pour fournir une surveillance de qualité de service sur des interfaces de communication Ceased WO2022118127A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063121666P 2020-12-04 2020-12-04
US63/121,666 2020-12-04

Publications (1)

Publication Number Publication Date
WO2022118127A1 true WO2022118127A1 (fr) 2022-06-09

Family

ID=78821907

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/060618 Ceased WO2022118127A1 (fr) 2020-12-04 2021-11-16 Procédés, appareils, et produits programmes d'ordinateur pour fournir une surveillance de qualité de service sur des interfaces de communication

Country Status (1)

Country Link
WO (1) WO2022118127A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116193639A (zh) * 2022-12-30 2023-05-30 中国联合网络通信集团有限公司 服务质量保证方法、装置和存储介质
WO2024174268A1 (fr) * 2023-02-24 2024-08-29 北京小米移动软件有限公司 Procédé de mesure de station de base et appareil, dispositif de communication, et support d'enregistrement

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140092736A1 (en) * 2012-10-02 2014-04-03 Telefonaktiebolaget L M Ericsson (Publ) Method and system for radio service optimization using active probing over transport networks
EP3235177A1 (fr) * 2014-12-15 2017-10-25 Nokia Solutions and Networks Oy Coordination de mesurages dans des communications
US20170373950A1 (en) * 2015-01-27 2017-12-28 Nokia Solutions And Networks Oy Traffic flow monitoring
US20200145876A1 (en) * 2018-11-02 2020-05-07 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140092736A1 (en) * 2012-10-02 2014-04-03 Telefonaktiebolaget L M Ericsson (Publ) Method and system for radio service optimization using active probing over transport networks
EP3235177A1 (fr) * 2014-12-15 2017-10-25 Nokia Solutions and Networks Oy Coordination de mesurages dans des communications
US20170373950A1 (en) * 2015-01-27 2017-12-28 Nokia Solutions And Networks Oy Traffic flow monitoring
US20200145876A1 (en) * 2018-11-02 2020-05-07 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116193639A (zh) * 2022-12-30 2023-05-30 中国联合网络通信集团有限公司 服务质量保证方法、装置和存储介质
CN116193639B (zh) * 2022-12-30 2024-05-10 中国联合网络通信集团有限公司 服务质量保证方法、装置和存储介质
WO2024174268A1 (fr) * 2023-02-24 2024-08-29 北京小米移动软件有限公司 Procédé de mesure de station de base et appareil, dispositif de communication, et support d'enregistrement

Similar Documents

Publication Publication Date Title
EP3958540B1 (fr) Procédé, appareil et produit de programme informatique pour analyse de données améliorée dans des déploiements nwdaf multiples
FR2994049A1 (fr) Identification de trous de couverture utilisant des mesures de transfert intercellulaire inter-rat
US9094907B2 (en) High-precision time tagging for content synthesization
EP3429260A1 (fr) Procédé, appareil, et système de transmission de données
WO2022033944A1 (fr) Procédés, appareils et produits-programmes informatiques pour prendre en charge la facturation de services de synchronisation temporelle
US12426102B2 (en) Methods, apparatuses, and computer program products for supporting simultaneous access to mutally isolated network slices
US20230388769A1 (en) Method, apparatus, and computer program product for service-continuity indication in sidelink user equipment to network relay during path switch
WO2022118127A1 (fr) Procédés, appareils, et produits programmes d'ordinateur pour fournir une surveillance de qualité de service sur des interfaces de communication
CN107959984A (zh) 物联网中的rrc连接重建方法、基站和用户终端
US10271218B2 (en) Enable access point availability prediction
US20240049097A1 (en) Methods, apparatuses, and computer program products for fast cell selection using conditional handover and intercell beam management reporting
WO2022069481A2 (fr) Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence
US20160165646A1 (en) Apparatus and method for controlling speed of transmission layer in wireless communication system
CN118120303A (zh) 经由侧行链路中继用户设备请求和传送基于sib9的精确时间同步的方法
CN117223248A (zh) 测量间隙增强
CN114208218B (zh) 位置请求的协调
US9380580B2 (en) Method and apparatus for transmission synchronization utilizing a router advertisement
US20240430719A1 (en) Band estimating device and band estimate method
US20230388386A1 (en) Method, apparatus, and computer program product for enlarging usage of user category within a core network
US20240023007A1 (en) Method, apparatus, and computer program product to support multiple slices in case of overlayunderlay networking
WO2022252045A1 (fr) Mécanisme de synchronisation temporelle
US12532254B2 (en) Methods, apparatuses, and computer program products for supporting onboarding and authentication of user equipment for networks and network slices
US20260025323A1 (en) Communication method, device, chip, storage medium, and program product
WO2025076728A1 (fr) Inférence et dépannage d'aiml en temps réel en temps opportun en télécommunication
US20240243846A1 (en) System, method, and computer program for managing data packets transmission between network nodes based on pre-defined configuration and dynamic configuration

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21819966

Country of ref document: EP

Kind code of ref document: A1