Search

US-20260129508-A1 - METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR SERVICE ENABLER ARCHITECTURE LAYER DATA DELIVERY TRAFFIC SYNCHRONIZATION IN MOBILE NETWORKS

US20260129508A1US 20260129508 A1US20260129508 A1US 20260129508A1US-20260129508-A1

Abstract

A method, implemented in a WTRU is described herein. The method may include sending configuration information to a WTRU. The configuration information may indicate the WTRU to send reporting information to the network element about a buffering event related to a traffic flow. The method may include receiving the reporting information from the WTRU indicating that (1) the buffering event related to the traffic flow may have occurred at the WTRU and (2) the buffering event may be associated with a buffering condition being satisfied at the WTRU. The method may include determining a corrective action associated with the traffic flow based on the reporting information to prevent the buffering condition from being satisfied. The method may include performing the corrective action associated with the traffic flow.

Inventors

  • Michel Roy
  • Michael Starsinic
  • Xavier De Foy
  • Kevin Di Lallo

Assignees

  • INTERDIGITAL PATENT HOLDINGS, INC.

Dates

Publication Date
20260507
Application Date
20241107

Claims (20)

  1. 1 . A network element comprising circuitry, including any of transceiver, a processor, and memory, configured to: send configuration information to a wireless transmit/receive unit (WTRU), wherein the configuration information indicates to the WTRU to send reporting information to the network element about a buffering event related to a traffic flow; receive, from the WTRU, the reporting information indicating that (1) the buffering event related to the traffic flow has occurred at the WTRU and (2) the buffering event is associated with a buffering condition being satisfied at the WTRU; determine a corrective action associated with the traffic flow based on the reporting information to prevent the buffering condition from being satisfied; and perform the corrective action associated with the traffic flow.
  2. 2 . The network element of claim 1 , wherein the buffering condition is satisfied at the WTRU based on an amount of data buffered at the WTRU being higher than a first threshold.
  3. 3 . The network element of claim 2 , wherein the buffering condition is satisfied at the WTRU based on the amount of data buffered at the WTRU being higher than the first threshold for more than an amount of time.
  4. 4 . The network element of claim 3 , wherein the configuration information indicates any of the first threshold and the amount of time.
  5. 5 . The network element of claim 1 , wherein the buffering condition is satisfied at the WTRU based on an amount of data buffered at the WTRU being lower than a second threshold.
  6. 6 . The network element of claim 5 , wherein the buffering condition is satisfied at the WTRU based on the amount of data buffered at the WTRU being lower than the second threshold for more than an amount of time.
  7. 7 . The network element of claim 6 , wherein the configuration information indicates any of the second threshold and the amount of time.
  8. 8 . The network element of claim 1 , wherein the configuration information indicates an identifier of the traffic flow.
  9. 9 . The network element of claim 1 , wherein the configuration information indicates to send the reporting information based on the buffering condition being satisfied at the WTRU.
  10. 10 . The network element of claim 1 , wherein the reporting information indicates a level of criticality.
  11. 11 . The network element of claim 10 , wherein the circuitry is configured to determine the corrective action associated with the traffic flow based on the level of criticality.
  12. 12 . The network element of claim 1 , wherein the circuitry is configured to determine, based on the reporting information, whether the buffering event corresponds to a buffer over utilization or to a buffer underutilization at the WTRU.
  13. 13 . The network element of claim 12 , wherein the circuitry is configured to determine the corrective action associated with the traffic flow including to determine the corrective action to be traffic influence via requesting a higher delay value to a network based on the buffer event corresponding to the buffer over utilization at the WTRU.
  14. 14 . The network element of claim 13 , wherein the circuitry is configured to request the higher delay value to the network including to send a request to a network exposure function of the network indicating a packet delay budget value corresponding to the higher delay value.
  15. 15 . The network element of claim 13 , wherein the circuitry is configured to request the higher delay value to the network including to send a request to a policy control function of the network indicating a requested 5G system delay corresponding to the higher delay value.
  16. 16 . The network element of claim 12 , wherein the circuitry is configured to determine the corrective action associated with the traffic flow including to determine the corrective action to be traffic influence via data boost based on the buffer event corresponding to the buffer underutilization at the WTRU.
  17. 17 . The network element of claim 16 , wherein the circuitry is configured to perform a data boost including to mark packets of the traffic flow with an urgency identification to reduce a delay of the traffic flow.
  18. 18 . The network element of claim 1 , comprising a service enabler architecture layer for data delivery server.
  19. 19 . A method implemented in a network element, the method comprising: sending configuration information to a wireless transmit/receive unit (WTRU), wherein the configuration information indicates to the WTRU to send reporting information to the network element about a buffering event related to a traffic flow; receiving, from the WTRU, the reporting information indicating that (1) the buffering event related to the traffic flow has occurred at the WTRU and (2) the buffering event is associated with a buffering condition being satisfied at the WTRU; determining a corrective action associated with the traffic flow based on the reporting information to prevent the buffering condition from being satisfied; and performing the corrective action associated with the traffic flow.
  20. 20 . The method of claim 19 , wherein the buffering condition is satisfied at the WTRU based on an amount of data buffered at the WTRU being higher than a first threshold.

Description

TECHNICAL FIELD The present disclosure is generally directed to the fields of communications, software and encoding, including methods, architectures, apparatuses, and systems directed to service enabler architecture layer data delivery traffic synchronization in mobile networks. BACKGROUND The service enabler architecture layer for data delivery (SEALDD) is a framework designed to facilitate efficient and flexible data delivery in distributed systems and applications. It focuses on improving (e.g., optimizing) data flow between service providers and consumers. Embodiments described herein have been designed with the foregoing in mind. SUMMARY Methods, architectures, apparatuses, and systems directed to SEALDD traffic synchronization in mobile networks are described herein. In an embodiment, a network element is described. The network element may include circuitry including any of transmitter, a receiver, a processor, and a memory. The network element may be configured to send configuration information to a wireless transmit/receive unit (WTRU). In various embodiments, the configuration information may indicate the WTRU to send reporting information to the network element about a buffering event related to a traffic flow. The network element may be configured to receive the reporting information from the WTRU indicating that (1) the buffering event related to the traffic flow may have occurred at the WTRU and (2) the buffering event may be associated with a buffering condition being satisfied at the WTRU. The network element may be configured to determine a corrective action associated with the traffic flow based on the reporting information to prevent the buffering condition from being satisfied. The network element may be configured to perform the corrective action associated with the traffic flow. In an embodiment, a method implemented in a network element is described. The method may include sending configuration information to a WTRU. In various embodiments, the configuration information may indicate the WTRU to send reporting information to the network element about a buffering event related to a traffic flow. The method may include receiving the reporting information from the WTRU indicating that (1) the buffering event related to the traffic flow may have occurred at the WTRU and (2) the buffering event may be associated with a buffering condition being satisfied at the WTRU. The method may include determining a corrective action associated with the traffic flow based on the reporting information to prevent the buffering condition from being satisfied. The method may include performing the corrective action associated with the traffic flow. BRIEF DESCRIPTION OF THE DRAWINGS A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals (“ref.”) in the FIGs. indicate like elements, and wherein: FIG. 1A is a system diagram illustrating an example communications system; FIG. 1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A; FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A; FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A; FIG. 2 is a diagram illustrating an example SEALDD functional architecture; FIG. 3 is a diagram illustrating an overview example method for SEALDD traffic synchronization; FIG. 4 is a diagram illustrating an example method for performing SEALDD traffic synchronization configuration; FIG. 5 is a diagram illustrating an example procedure for performing SEALDD traffic synchronization monitoring and coordination; and FIG. 6 is a diagram illustrating an example method for SEALDD traffic synchronization in mobile networks. DETAILED DESCRIPTION In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided e